Re: flashplugin 11.2r202.238
01.10.2012 21:33, Jerry wrote: I just finished installing linux-f10-flashplugin-11.2r202.238. For some inexplicable reason, it is no longer working. I followed the directions in UPDATING but without success. I even cleared out the entries in the ~/.mozilla/plugins directory and reran the command without results. In fact, now nothing is listed in the directory and flash still doesn't work. Every time I reach a page that requires flash, I am greeted with a message telling me I need to download and install it. Could you please rerun nspluginwrapper -v -a -i? Is there anything in the system log? -- 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
removing non-existent ports from /var/db/pkg ?
I have on one system: # ls /var/db/pkg apr-1.4.6.1.4.1_1 help2man-1.40.10pkgconf-0.8.4 auditfile help2man-1.40.11pkgconf-0.8.5 autoconf-2.69 help2man-1.40.12pkgconf-0.8.6 automake-1.12.2 libconfuse-2.7 pkgconf-0.8.7_2 automake-1.12.3 libxml2-2.7.8_5 pkgconf-0.8.8 automake-1.12.4 local.sqlitepkgconf-0.8.9 ganglia-monitor-core-3.1.7_4mpfr-3.1.1 python27-2.7.3_3 gcc-4.7.2.20120721 neon29-0.29.6_4 rsync-3.0.9_2 gcc-4.7.2.20120728 pcre-8.31_1 sqlite3-3.7.14 gcc-4.7.2.20120804 pkg-1.0 subversion-1.7.5 gcc-4.7.2.20120825 pkg-1.0.r4 subversion-1.7.6 gcc-4.7.2.20120908 pkg-1.0.r4_1sudo-1.8.5.p3 gcc-4.7.3.20120929 pkg-1.0.r5_1sudo-1.8.6.p3_1 gmake-3.82_1pkg-1.0.r6_1 # pkg info -xo gcc-4.7 gcc-4.7.3.20120929: lang/gcc47 # I wonder why I have old versions of several ports, which no longer exist, e.g. gcc47. I update with portmaster. Does the normal update procedure remove the old version entry from /var/db/pkg if the update has been successful? Thanks Anton ___ 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: security/sudo *** [pre-install] Signal 11
From mexas Mon Oct 1 10:51:13 2012 To: freebsd-ports@freebsd.org, w...@freebsd.org Subject: security/sudo *** [pre-install] Signal 11 Reply-To: me...@bristol.ac.uk # make install FORCE_PKG_REGISTER=1 === Installing for sudo-1.8.6.p3_1 === Generating temporary packing list if test -d ./.hg cd .; then if hg log --style=changelog -b default ChangeL og.tmp; then mv -f ChangeLog.tmp ChangeLog; else rm -f ChangeLog.tmp; fi; f i for d in compat common plugins/sudoers src include doc; do (cd $d exec make pre-install) continue; exit $?; done Checking existing sudoers file for syntax errors. *** [pre-install] Signal 11 Note: this is on ia64 r235474. I deleted the existing /usr/local/etc/sudoers, and the update was then successful. However, I'm getting: # visudo Segmentation fault (core dumped) # and nothing from the gdb: # gdb /usr/local/sbin/visudo visudo.core GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as ia64-marcel-freebsd... Core was generated by `visudo'. Program terminated with signal 11, Segmentation fault. #0 0x in ?? () (gdb) thread apply all bt Thread 1 (process 100111): #0 0x in ?? () #1 0x25036ae0 in ?? () Previous frame identical to this frame (corrupt stack?) (gdb) I build WITH_DEBUG= How can I debug this further? All tests fail when running make check under /usr/ports/security/sudo/work/sudo-1.8.6p3: Script started on Tue Oct 2 10:16:25 2012 make check for d in compat common plugins/sudoers src include doc; do (cd $d exec make check) continue; exit $?; done check_addr: 9 tests run, 0 errors, 100% success rate Segmentation fault (core dumped) Segmentation fault (core dumped) Segmentation fault (core dumped) check_symbols: 7 tests run, 0 errors, 100% success rate Segmentation fault (core dumped) 0a1,175 # word wrap at 60 characters Jul 11 11:30:17 : tu2sp3-a : command not allowed ; TTY=pts/1 ; PWD=/home/tu2sp3-a ; USER=root ; COMMAND=/opt/quest/bin/vastool list users # word wrap at 61 characters Jul 11 11:30:17 : tu2sp3-a : command not allowed ; TTY=pts/1 ; PWD=/home/tu2sp3-a ; USER=root ; COMMAND=/opt/quest/bin/vastool list users # word wrap at 62 characters Jul 11 11:30:17 : tu2sp3-a : command not allowed ; TTY=pts/1 ; PWD=/home/tu2sp3-a ; USER=root ; COMMAND=/opt/quest/bin/vastool list users # word wrap at 63 characters Jul 11 11:30:17 : tu2sp3-a : command not allowed ; TTY=pts/1 ; PWD=/home/tu2sp3-a ; USER=root ; COMMAND=/opt/quest/bin/vastool list users # word wrap at 64 characters Jul 11 11:30:17 : tu2sp3-a : command not allowed ; TTY=pts/1 ; PWD=/home/tu2sp3-a ; USER=root ; COMMAND=/opt/quest/bin/vastool list users # word wrap at 65 characters Jul 11 11:30:17 : tu2sp3-a : command not allowed ; TTY=pts/1 ; PWD=/home/tu2sp3-a ; USER=root ; COMMAND=/opt/quest/bin/vastool list users # word wrap at 66 characters Jul 11 11:30:17 : tu2sp3-a : command not allowed ; TTY=pts/1 ; PWD=/home/tu2sp3-a ; USER=root ; COMMAND=/opt/quest/bin/vastool list users # word wrap at 67 characters Jul 11 11:30:17 : tu2sp3-a : command not allowed ; TTY=pts/1 ; PWD=/home/tu2sp3-a ; USER=root ; COMMAND=/opt/quest/bin/vastool list users # word wrap at 68 characters Jul 11 11:30:17 : tu2sp3-a : command not allowed ; TTY=pts/1 ; PWD=/home/tu2sp3-a ; USER=root ; COMMAND=/opt/quest/bin/vastool list users # word wrap at 69 characters Jul 11 11:30:17 : tu2sp3-a : command not allowed ; TTY=pts/1 ; PWD=/home/tu2sp3-a ; USER=root ; COMMAND=/opt/quest/bin/vastool list users # word wrap at 70 characters Jul 11 11:30:17 : tu2sp3-a : command not allowed ; TTY=pts/1 ; PWD=/home/tu2sp3-a ; USER=root ; COMMAND=/opt/quest/bin/vastool list users # word wrap at 71 characters Jul 11 11:30:17 : tu2sp3-a : command not allowed ; TTY=pts/1 ; PWD=/home/tu2sp3-a ; USER=root ; COMMAND=/opt/quest/bin/vastool list users # word wrap at 72 characters Jul 11 11:30:17 : tu2sp3-a : command not allowed ; TTY=pts/1 ; PWD=/home/tu2sp3-a ; USER=root ; COMMAND=/opt/quest/bin/vastool list users # word wrap at 73 characters Jul 11 11:30:17 : tu2sp3-a : command not allowed ; TTY=pts/1 ; PWD=/home/tu2sp3-a ; USER=root ; COMMAND=/opt/quest/bin/vastool list users # word wrap at 74 characters Jul 11 11:30:17 : tu2sp3-a : command not allowed ; TTY=pts/1 ; PWD=/home/tu2sp3-a ; USER=root ; COMMAND=/opt/quest/bin/vastool list users # word wrap at 75 characters Jul 11 11:30:17 : tu2sp3-a
Re: removing non-existent ports from /var/db/pkg ?
On 02/10/2012 09:08, Anton Shterenlikht wrote: I have on one system: # ls /var/db/pkg apr-1.4.6.1.4.1_1 help2man-1.40.10pkgconf-0.8.4 auditfile help2man-1.40.11pkgconf-0.8.5 autoconf-2.69 help2man-1.40.12pkgconf-0.8.6 automake-1.12.2 libconfuse-2.7 pkgconf-0.8.7_2 automake-1.12.3 libxml2-2.7.8_5 pkgconf-0.8.8 automake-1.12.4 local.sqlitepkgconf-0.8.9 ganglia-monitor-core-3.1.7_4mpfr-3.1.1 python27-2.7.3_3 gcc-4.7.2.20120721 neon29-0.29.6_4 rsync-3.0.9_2 gcc-4.7.2.20120728 pcre-8.31_1 sqlite3-3.7.14 gcc-4.7.2.20120804 pkg-1.0 subversion-1.7.5 gcc-4.7.2.20120825 pkg-1.0.r4 subversion-1.7.6 gcc-4.7.2.20120908 pkg-1.0.r4_1sudo-1.8.5.p3 gcc-4.7.3.20120929 pkg-1.0.r5_1 sudo-1.8.6.p3_1 gmake-3.82_1pkg-1.0.r6_1 # pkg info -xo gcc-4.7 gcc-4.7.3.20120929: lang/gcc47 # I wonder why I have old versions of several ports, which no longer exist, e.g. gcc47. I update with portmaster. Does the normal update procedure remove the old version entry from /var/db/pkg if the update has been successful? This is an unfortunate effect of using pkgng to handle packages and portmaster+patches to build them. The old pkg_tools were the owners of that whole /var/db/pkg/ sub-directory structure, and used to take care of deleting old entries once ports were updated or removed. portmaster stores some of its meta-data in those directories but it doesn't itself remove any that are out of date. pkg only uses the data in local.sqlite -- so there's nothing left willing to clean up the mess. This is something that should probably be added to the portmaster patch when used with pkgng. Cheers, Matthew ___ 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: Problem upgrading misc/help2man: missing language files
from Bas Smeelen b.smee...@ose.nl: Below it looks like the creation of the backup package fails, which get's deleted by default after the new port is installed. I Just update ports on a CURRENT server with csup from cvsup4.nl.FreeBSD.org and the help2man version is still 1.40.12 I will go ahead and update from cvsup9.freebsd.org . . . No help2man-1.40.13 yet. Maybe csup the portstree again and retry portmaster misc/help2man? Did portmaster end with lines like Upgrade of help2man-1.40.11 to help2man-1.40.12 But then help2man-1.40.12 to help2man-1.40.13 instead of the above? The it should be OK. No, I was trying to upgradr from 1.40.12 to 1.40.13 I used portsnap fetch update, and I saw the new version 1.40.13 Perhaps I could use portmaster -B misc/help2man to prevent creating another backup. Maybe my installation of 1.40.12 was corrupted, or maybe it was a matter of not having NLS option for 1.40.12 This raises the question of how one rebuilds and reinstalls a corrupted port installation when backing up would not be desired. Tom ___ 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: removing non-existent ports from /var/db/pkg ?
[ Matthew Seaman wrote on Tue 2.Oct'12 at 10:32:56 +0100 ] On 02/10/2012 09:08, Anton Shterenlikht wrote: I have on one system: # ls /var/db/pkg apr-1.4.6.1.4.1_1 help2man-1.40.10 pkgconf-0.8.4 auditfile help2man-1.40.11 pkgconf-0.8.5 autoconf-2.69 help2man-1.40.12 pkgconf-0.8.6 automake-1.12.2 libconfuse-2.7 pkgconf-0.8.7_2 automake-1.12.3 libxml2-2.7.8_5 pkgconf-0.8.8 automake-1.12.4 local.sqlite pkgconf-0.8.9 ganglia-monitor-core-3.1.7_4mpfr-3.1.1 python27-2.7.3_3 gcc-4.7.2.20120721 neon29-0.29.6_4 rsync-3.0.9_2 gcc-4.7.2.20120728 pcre-8.31_1 sqlite3-3.7.14 gcc-4.7.2.20120804 pkg-1.0 subversion-1.7.5 gcc-4.7.2.20120825 pkg-1.0.r4 subversion-1.7.6 gcc-4.7.2.20120908 pkg-1.0.r4_1 sudo-1.8.5.p3 gcc-4.7.3.20120929 pkg-1.0.r5_1 sudo-1.8.6.p3_1 gmake-3.82_1pkg-1.0.r6_1 # pkg info -xo gcc-4.7 gcc-4.7.3.20120929: lang/gcc47 # I wonder why I have old versions of several ports, which no longer exist, e.g. gcc47. I update with portmaster. Does the normal update procedure remove the old version entry from /var/db/pkg if the update has been successful? This is an unfortunate effect of using pkgng to handle packages and portmaster+patches to build them. The old pkg_tools were the owners of that whole /var/db/pkg/ sub-directory structure, and used to take care of deleting old entries once ports were updated or removed. portmaster stores some of its meta-data in those directories but it doesn't itself remove any that are out of date. pkg only uses the data in local.sqlite -- so there's nothing left willing to clean up the mess. This is something that should probably be added to the portmaster patch when used with pkgng. Hi Matthew and Anton, so in the meantime what is the best way to clear this old stuff out? I do like to clear out code and files that are redundant, where possible. What would you suggest? Cheers, Jamie ___ 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: removing non-existent ports from /var/db/pkg ?
On 02/10/2012 11:33, Jamie Paul Griffin wrote: Hi Matthew and Anton, so in the meantime what is the best way to clear this old stuff out? I do like to clear out code and files that are redundant, where possible. What would you suggest? At the moment, the only way to clear up is to manually remove the outdated subdirectories from /var/db/ports. You can work out what is out of date by comparing the list of sub-dirs to the list of installed ports obtained by pkg info -aq Should only take a few minutes to write a small script to do that. Be careful not to trash local.sqlite, repo.sqlite or auditfile -- in fact, anything in /var/db/pkg which is not a directory should be preserved. Note: even if you do delete subdirs that are actually still in use, this shouldn't be a huge disaster. The only data still in those directories will be portmaster's cache of distfile info (which it can cope without: it uses it to efficiently identify old distfiles that can themselves be tidied up) and flag files like +IGNOREME which you will want to regenerate before you next do a ports update. Cheers, Matthew ___ 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
sudo-1.8.6.p3_1 is broken on ia64 -current. What svn revision do I need to get back to sudo-1.8.5.p3
I updated from sudo-1.8.5.p3 to sudo-1.8.6.p3_1 on ia64 r235474. The new version segfaults all the time. I'm in a hurry to get a working sudo back, because it's required for the portscluster builds. Please advise what svn revision I need to go back to get to sudo-1.8.5p3. Thanks Anton ___ 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: sudo-1.8.6.p3_1 is broken on ia64 -current. What svn revision do I need to get back to sudo-1.8.5.p3
On Tue, 2 Oct 2012 12:30:26 +0100 (BST) Anton Shterenlikht me...@bristol.ac.uk wrote: I updated from sudo-1.8.5.p3 to sudo-1.8.6.p3_1 on ia64 r235474. The new version segfaults all the time. I'm in a hurry to get a working sudo back, because it's required for the portscluster builds. Please advise what svn revision I need to go back to get to sudo-1.8.5p3. Thanks Anton ___ 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 Rev 302692 See also http://www.freebsd.org/cgi/cvsweb.cgi/ports/security/sudo/Makefile -- Michael Gmelin ___ 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: removing non-existent ports from /var/db/pkg ?
[ Matthew Seaman wrote on Tue 2.Oct'12 at 12:13:05 +0100 ] At the moment, the only way to clear up is to manually remove the outdated subdirectories from /var/db/ports. You can work out what is out of date by comparing the list of sub-dirs to the list of installed ports obtained by pkg info -aq Should only take a few minutes to write a small script to do that. Be careful not to trash local.sqlite, repo.sqlite or auditfile -- in fact, anything in /var/db/pkg which is not a directory should be preserved. Note: even if you do delete subdirs that are actually still in use, this shouldn't be a huge disaster. The only data still in those directories will be portmaster's cache of distfile info (which it can cope without: it uses it to efficiently identify old distfiles that can themselves be tidied up) and flag files like +IGNOREME which you will want to regenerate before you next do a ports update. Ok, thanks for clarifying that for us. Very much appreciated. Best wishes, Jamie ___ 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: security/sudo *** [pre-install] Signal 11
From mexas Tue Oct 2 10:21:10 2012 From mexas Mon Oct 1 10:51:13 2012 # make install FORCE_PKG_REGISTER=1 === Installing for sudo-1.8.6.p3_1 === Generating temporary packing list if test -d ./.hg cd .; then if hg log --style=changelog -b default ChangeL og.tmp; then mv -f ChangeLog.tmp ChangeLog; else rm -f ChangeLog.tmp; fi; f i for d in compat common plugins/sudoers src include doc; do (cd $d exec make pre-install) continue; exit $?; done Checking existing sudoers file for syntax errors. *** [pre-install] Signal 11 Note: this is on ia64 r235474. I deleted the existing /usr/local/etc/sudoers, and the update was then successful. [skip] Segmentation fault (core dumped) cmp: EOF on regress/sudoers/test8.out sudoers/test8: FAIL 0a1,7 Parse error in sudoers near line 8. User_AliasUA1 = xy User_AliasUA2 = xy User_AliasUA3 = xy sudoers/test8 (toke): FAIL 0a1,7 Parse error in sudoers near line 8. User_AliasUA1 = xy User_AliasUA2 = xy User_AliasUA3 = xy sudoers: 0/16 tests passed; 16/16 tests failed I downgraded to 1.8.5p3. Now the segfaults have gone away, and sudo is generally usable, but all tests still fail: http://seis.bris.ac.uk/~mexas/sudo-185p3-check.log Anton ___ 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
How to check out ports
Are we supposed to be using cvs or svn to check out ports now? If cvs, I'm getting prompted for a password which fails. -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead. Thomas Jefferson There are some ideas so wrong that only a very intelligent person could believe in them. George Orwell ___ 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: How to check out ports
On Tue, Oct 02, 2012 at 11:23:23AM -0500, Paul Schmehl wrote: Are we supposed to be using cvs or svn to check out ports now? If cvs, I'm getting prompted for a password which fails. That depends on the nature of the repository you are using. What I do is maintain local private mirrors of the FreeBSD src, doc, and ports SVN repositories, and check out what I want to use via svn using those repositories. This does not require a password. It is unlikely that most folks will want (let alone need) to maintain such mirrors, but I find it easy and useful for what I do. Note that there has been an end of the line posted re: the current CVS exporter for ports: there is a date in the not-too-distant future when only SVN will be supported by the FreeBSD project (again, for ports). (The doc repo never had a CVS exporter after its conversion from CVS to SVN. AFAIK, there are no current plans to turn off the CVS exporter for the src repo -- but doc src are off-topic for this list.) 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.gpg for my public key. pgprIuWACM4Ej.pgp Description: PGP signature
Re: How to check out ports
On 10/02/12 11:23, Paul Schmehl wrote: Are we supposed to be using cvs or svn to check out ports now? If cvs, I'm getting prompted for a password which fails. I think you are supposed to use *csup* or svn. But use svn - it is easy, and csup is going to be phased out very soon. ___ 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: How to check out ports
Paul Schmehl pschmehl_li...@tx.rr.com writes: Are we supposed to be using cvs or svn to check out ports now? If cvs, I'm getting prompted for a password which fails. If you rarely need more than the latest version of the ports tree, then portsnap(8) is worth strong consideration. If you have an existing setup that's working (such as csup/cvsup/anonymous cvs), you can stick with that until the svn-to-cvs export stops. Otherwise, use svn. ___ 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: How to check out ports
--On October 2, 2012 1:00:52 PM -0400 Lowell Gilbert freebsd-ports-lo...@be-well.ilk.org wrote: Paul Schmehl pschmehl_li...@tx.rr.com writes: Are we supposed to be using cvs or svn to check out ports now? If cvs, I'm getting prompted for a password which fails. If you rarely need more than the latest version of the ports tree, then portsnap(8) is worth strong consideration. If you have an existing setup that's working (such as csup/cvsup/anonymous cvs), you can stick with that until the svn-to-cvs export stops. Otherwise, use svn. I obviously wasn't very clear. I'm a port maintainer. I need to update one of my ports. I used to do this by checking out the port into a purpose-created directory in which I would use cvs to make changes and test. After everything checked out, I would submit the diff. Now cvs isn't working, so how, as a port maintainer, do I check out a single port so I can update it and submit it in a PR? -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead. Thomas Jefferson There are some ideas so wrong that only a very intelligent person could believe in them. George Orwell ___ 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: How to check out ports
On 2 October 2012 14:37, Paul Schmehl pschmehl_li...@tx.rr.com wrote: I obviously wasn't very clear. I'm a port maintainer. I need to update one of my ports. I used to do this by checking out the port into a purpose-created directory in which I would use cvs to make changes and test. After everything checked out, I would submit the diff. We need to be better about announcing these changes as not to frustrate maintainers. :) Now cvs isn't working, so how, as a port maintainer, do I check out a single port so I can update it and submit it in a PR? You should do things the same way you did before, but instead you should use svn to checkout out your port. Note that 'module names' no longer work so you must use the full name: e..g., svn checkout svn://svn.freebsd.org/ports/head/editors/nano It may help to keep a folder of ports-I-maintain with the ports you maintain checked out. Before you update them do svn update * and to generate a diff do svn diff foldername -- Eitan Adler ___ 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: How to check out ports
--On October 2, 2012 2:44:46 PM -0400 Eitan Adler li...@eitanadler.com wrote: On 2 October 2012 14:37, Paul Schmehl pschmehl_li...@tx.rr.com wrote: I obviously wasn't very clear. I'm a port maintainer. I need to update one of my ports. I used to do this by checking out the port into a purpose-created directory in which I would use cvs to make changes and test. After everything checked out, I would submit the diff. We need to be better about announcing these changes as not to frustrate maintainers. :) Now cvs isn't working, so how, as a port maintainer, do I check out a single port so I can update it and submit it in a PR? You should do things the same way you did before, but instead you should use svn to checkout out your port. Note that 'module names' no longer work so you must use the full name: e..g., svn checkout svn://svn.freebsd.org/ports/head/editors/nano It may help to keep a folder of ports-I-maintain with the ports you maintain checked out. Before you update them do svn update * and to generate a diff do svn diff foldername I got on the wiki and figured out how to check ou the port using svn, but now I'm stuck again. This port has moved to github, and I don't have a clue how to download it in the Makefile. There's no mention of github in /usr/ports/Mk, so I assume the method hasn't even been written yet. The source is here: https://github.com/firnsy/barnyard2/, but I don't see a tarball, and I don't know enough about ports to know if it's even possible to fetch it from github. -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead. Thomas Jefferson There are some ideas so wrong that only a very intelligent person could believe in them. George Orwell ___ 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
Possible regression in i386 build with gcc 4.6
I found a situation where gcc v4.2 compiles a i386 working binary and
v4.6 doesn't. (Currently 4.7 and 4.8 fail to build this code) I have
verified that this happens with 8.2/8.3/9.0 i386 systems. x86_64
versions build without issue as does clang i386/x86_64.
It appears that the x86_64 target of gcc offers gcc atomics while the
i386 target doesn't - and this appears to be a freebsd specific setup,
the i386 targets then fall back to using tbb atomics.
Is this some subtle bug I'm missing? can it be alleviated with compiler
flags/more universal code?
I have tried to cut this down to just the call that triggers a
segmentation fault but the one call itself isn't enough.
The issue can be found in graphics/openimageio. The easiest way I know
to cause the segmentation fault is with the image viewer that is part of
the port (it is a Qt app) it seg faults during startup. There is no need
to open any images just starting iv with an empty window is fine.
The makefile is setup to USE_GCC=4.6+ for i386/8.2 - this is a leftover
from earlier versions that will be removed next update.
cd /usr/ports/graphics/openimageio
make
./work/.build/iv/iv
The error appears to stem from line 193 of src/libutil/ustring.cpp
atomic_exchange_and_add (ustring_stats_constructed, 1);
Commenting this line prevents the crash but isn't a valid fix.
the relevant function it calls is -- src/include/thread.h:283
which uses the atomic class template from tbb for the i386 build.
inline long long
atomic_exchange_and_add (volatile long long *at, long long x)
{
#ifdef USE_GCC_ATOMICS
return __sync_fetch_and_add (at, x);
#elif USE_TBB
atomiclong long *a = (atomiclong long *)at;
return a-fetch_and_add (x);
#elif defined(__APPLE__)
snip
#endif
}
___
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: removing non-existent ports from /var/db/pkg ?
From: Matthew Seaman m.sea...@infracaninophile.co.uk On 02/10/2012 12:38, Jamie Paul Griffin wrote: [ Matthew Seaman wrote on Tue 2.Oct'12 at 12:13:05 +0100 ] =20 =20 At the moment, the only way to clear up is to manually remove the outdated subdirectories from /var/db/ports. You can work out what is out of date by comparing the list of sub-dirs to the list of installed= ports obtained by pkg info -aq Should only take a few minutes to write a small script to do that. Be careful not to trash local.sqlite, repo.sqlite or auditfile -- in fact, anything in /var/db/pkg which is not a directory should be prese= rved. Note: even if you do delete subdirs that are actually still in use, th= is shouldn't be a huge disaster. The only data still in those directorie= s will be portmaster's cache of distfile info (which it can cope without= : it uses it to efficiently identify old distfiles that can themselves b= e tidied up) and flag files like +IGNOREME which you will want to regenerate before you next do a ports update. =20 Ok, thanks for clarifying that for us. Very much appreciated.=20 I just committed this: http://git.io/G2qIIg Which makes the patch compatible with portmaster-3.14 and also now makes portmaster remove superfluous subdirectories of $PKG_DBDIR when removing any packages. This should keep $PKG_DBDIR reasonably tidy going forwards, but it won't clean up all of the existing problem subdirs. For that you'll need a one-off job to clean up as described above. Thanks, the patch applied fine. Will see what happens with $PKG_DBDIR next time I update something. Anton ___ 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: How to check out ports
--On October 2, 2012 11:28:12 PM +0200 Michael Gmelin free...@grem.de wrote: On Tue, 02 Oct 2012 14:14:26 -0500 Paul Schmehl pschmehl_li...@tx.rr.com wrote: --On October 2, 2012 2:44:46 PM -0400 Eitan Adler li...@eitanadler.com wrote: On 2 October 2012 14:37, Paul Schmehl pschmehl_li...@tx.rr.com wrote: I obviously wasn't very clear. I'm a port maintainer. I need to update one of my ports. I used to do this by checking out the port into a purpose-created directory in which I would use cvs to make changes and test. After everything checked out, I would submit the diff. We need to be better about announcing these changes as not to frustrate maintainers. :) Now cvs isn't working, so how, as a port maintainer, do I check out a single port so I can update it and submit it in a PR? You should do things the same way you did before, but instead you should use svn to checkout out your port. Note that 'module names' no longer work so you must use the full name: e..g., svn checkout svn://svn.freebsd.org/ports/head/editors/nano It may help to keep a folder of ports-I-maintain with the ports you maintain checked out. Before you update them do svn update * and to generate a diff do svn diff foldername I got on the wiki and figured out how to check ou the port using svn, but now I'm stuck again. This port has moved to github, and I don't have a clue how to download it in the Makefile. There's no mention of github in /usr/ports/Mk, so I assume the method hasn't even been written yet. The source is here: https://github.com/firnsy/barnyard2/, but I don't see a tarball, and I don't know enough about ports to know if it's even possible to fetch it from github. Hi Paul, What about using the ZIP https://github.com/firnsy/barnyard2/zipball/master (this will give you the current master branch in a ZIP file) or a tarball https://github.com/firnsy/barnyard2/tarball/master If you want to keep things more stable (since the master branch might change frequently and break your build), limit yourself to a specific version. Fortunately this software is using tags for versioning, so it's easy to get zips from github, e.g.: https://github.com/firnsy/barnyard2/zipball/v2-1.10 or if you prefer a tarball (which is usually nicer to have) https://github.com/firnsy/barnyard2/tarball/v2-1.10 Github provides tarballs (and zipballs) for all branches and tags. See also: https://github.com/blog/12-tarball-downloads Hope that helps How do I handle this? firnsy-barnyard2-v2-1.10-0-g2f5d496.tar.gz Is the string at the end (g2f5d496) auto-generated? If so, that's another problem. I guess something like this? Sheesh. What a PITA. PORTNAME= barnyard2-v2 PORTVERSION=1.10 PKGNAMEPREFIX= firnsy- PKGNAMESUFFIX= -0-g2f5d496 Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead. Thomas Jefferson There are some ideas so wrong that only a very intelligent person could believe in them. George Orwell ___ 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: How to check out ports
On 2 October 2012 22:54, Paul Schmehl pschmehl_li...@tx.rr.com wrote: --On October 2, 2012 11:28:12 PM +0200 Michael Gmelin free...@grem.de wrote: On Tue, 02 Oct 2012 14:14:26 -0500 Paul Schmehl pschmehl_li...@tx.rr.com wrote: --On October 2, 2012 2:44:46 PM -0400 Eitan Adler li...@eitanadler.com wrote: On 2 October 2012 14:37, Paul Schmehl pschmehl_li...@tx.rr.com wrote: I obviously wasn't very clear. I'm a port maintainer. I need to update one of my ports. I used to do this by checking out the port into a purpose-created directory in which I would use cvs to make changes and test. After everything checked out, I would submit the diff. We need to be better about announcing these changes as not to frustrate maintainers. :) Now cvs isn't working, so how, as a port maintainer, do I check out a single port so I can update it and submit it in a PR? You should do things the same way you did before, but instead you should use svn to checkout out your port. Note that 'module names' no longer work so you must use the full name: e..g., svn checkout svn://svn.freebsd.org/ports/head/editors/nano It may help to keep a folder of ports-I-maintain with the ports you maintain checked out. Before you update them do svn update * and to generate a diff do svn diff foldername I got on the wiki and figured out how to check ou the port using svn, but now I'm stuck again. This port has moved to github, and I don't have a clue how to download it in the Makefile. There's no mention of github in /usr/ports/Mk, so I assume the method hasn't even been written yet. The source is here: https://github.com/firnsy/barnyard2/, but I don't see a tarball, and I don't know enough about ports to know if it's even possible to fetch it from github. Hi Paul, What about using the ZIP https://github.com/firnsy/barnyard2/zipball/master (this will give you the current master branch in a ZIP file) or a tarball https://github.com/firnsy/barnyard2/tarball/master If you want to keep things more stable (since the master branch might change frequently and break your build), limit yourself to a specific version. Fortunately this software is using tags for versioning, so it's easy to get zips from github, e.g.: https://github.com/firnsy/barnyard2/zipball/v2-1.10 or if you prefer a tarball (which is usually nicer to have) https://github.com/firnsy/barnyard2/tarball/v2-1.10 Github provides tarballs (and zipballs) for all branches and tags. See also: https://github.com/blog/12-tarball-downloads Hope that helps How do I handle this? firnsy-barnyard2-v2-1.10-0-g2f5d496.tar.gz Is the string at the end (g2f5d496) auto-generated? If so, that's another problem. Looks like the git hash: use GH_ACCOUNT GH_PROJECT and GH_COMMIT (see bsd.sites.mk for details) -- Eitan Adler ___ 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: How to check out ports
On 10/2/2012 10:54 PM, Paul Schmehl wrote: How do I handle this? firnsy-barnyard2-v2-1.10-0-g2f5d496.tar.gz Is the string at the end (g2f5d496) auto-generated? If so, that's another problem. I guess something like this? Sheesh. What a PITA. PORTNAME= barnyard2-v2 PORTVERSION=1.10 PKGNAMEPREFIX= firnsy- PKGNAMESUFFIX= -0-g2f5d496 Paul Schmehl, Senior Infosec Analyst See /usr/ports/deskutils/growl-for-linux/Makefile for an example, bsd.sites.mk has support for github. It was the first example I could find with grep. I believe its a new ports feature. ___ 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
