Re: Glassfish port update (Bug 194097)
Thank you very much Kevin, and thanks for the clarification about the maintainer approval. I read about poudriere in the Porter’s guide but seemed overkill to me for the simple port I was updating. However, if that speeds things up, I’ll manage to setup a FreeBSD VM with poudriere for ports development. Cheers, -- Enrico Maria Crisostomo On 14 Oct 2014 at 20:23:12, Kevin Oberman (rkober...@gmail.com) wrote: On Tue, Oct 14, 2014 at 4:22 AM, Enrico Maria Crisostomo wrote: Hi all, Some days ago I’ve submitted a PR to update the Glassfish port to 4.1, since the existing one is pretty old: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194097 Am I required to do something else or somebody will look at this as it is? Thanks and regards, -- Enrico Maria Crisostomo In theory, no. But in reality, if "some days" have passed, you need to bug the maintainer to approve it. Your statement that the maintainer approves is not adequate. He needs to submit the approval himself. Once he approves it, it is just waiting until a committer has the time to look at it and, if there are no issues, committing it. That will probably move faster if you include the output of a poudiere or redports run in the ticket. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkober...@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 you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ deskutils/osmo | 0.2.10 | 0.2.12 +-+ graphics/gifsicle | 1.84| 1.86 +-+ math/giacxcas | 1.1.0 | 1.1.3 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. ___ 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: [kde-freebsd] KDE
On Tue, 14 Oct 2014 11:43:04 -0700 Kevin Oberman wrote: > On Tue, Oct 14, 2014 at 11:17 AM, Alberto Villa wrote: > > > Hi, > > > > KDE SC 4.14.1 is currently being tested via exp-run, it will hit the ports > > soon. > > > > On Tue, Oct 14, 2014 at 4:10 AM, jmdennis @dslextreme.com < > > jmden...@dslextreme.com> wrote: > > > > > I was wondering when KDE 14.4.1 would be released. I know it has to be > > > compiled since it is made for Linux and not FreeBSD but it would be nice > > to > > > have the newer version released which fixes a lot of issues and is > > faster. > > -- > > Alberto Villa, FreeBSD committer > > http://people.FreeBSD.org/~avilla > > > After 10.1-RELEASE, I hope. I hope to get it before the release. Why do you want it after? ___ 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"
8th IWWT, submit your abstract
8 IWWT 2015 To unsubscribe or change your subscription options, please contact: newsletter8IWWT ___ 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: Glassfish port update (Bug 194097)
Hello, > I read about poudriere in the Porter's guide but seemed overkill > to me for the simple port I was updating. In theory, it looks like overkill, in praxis, I found the @dirrm issue in the pkg-plist that way. Because @dirrm entries in pkg-plist are no longer needed, since 20140922, see http://www.freshports.org/commit.php?message_id=201409220547.s8m5lxxk054...@svn.freebsd.org Have a look at the commit and the poudriere build logs: http://people.freebsd.org/~pi/logs/www__glassfish-10x-1413393068.txt http://people.freebsd.org/~pi/logs/www__glassfish-91a-1413393068.txt http://people.freebsd.org/~pi/logs/www__glassfish-84i-1413393068.txt > However, if that speeds > things up, I'll manage to setup a FreeBSD VM with poudriere for > ports development. It helps to provide cleaner diffs, yes. Thanks for the patch, btw! It's committed! -- p...@opsec.eu+49 171 3101372 6 years to go ! ___ 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"
Fwd: Squid -vs- IPv6
FYI (I'm not on this list): A patch might no longer be needed. - Forwarded message - Date: Wed, 15 Oct 2014 18:03:04 +0100 From: "Craig R. Skinner" To: po...@openbsd.org Subject: Re: Squid -vs- IPv6 User-Agent: Mutt/1.5.22 (2013-10-16) On 2014-05-19 Mon 12:01 PM |, Craig R. Skinner wrote: > FYI: This breaks Squid 3.3.8 on 5.4 release: > > $ fgrep family /etc/resolv.conf > family inet4 > (this may effect other daemons too) > > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > Bugged by the FreeBSD ports team: > http://www.freebsd.org/cgi/query-pr.cgi?pr=176951 > > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > Bugged @ Squid HQ: > http://bugs.squid-cache.org/show_bug.cgi?id=4024 > > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Bug now patched by the Squid team: Status: RESOLVED FIXED --- Comment #11 from Amos Jeffries 2014-10-14 07:28:10 UTC --- I have applied a patch to Squid-3 to log a warning but not abort if ::1 and *only* ::1 has failed to resolve. http://bugs.squid-cache.org/show_bug.cgi?id=4024#c11 Cheers, -- Craig Skinner | http://twitter.com/Craig_Skinner | http://linkd.in/yGqkv7 - End forwarded message - ___ 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: ghostscript9-9.06_8 seems broken
I decided to try the problem with some pdf files from Adobe's web site. This
file (from Quick start guides):
http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/products/acrobat/pdfs/adobe-acrobat-xi-work-with-microsoft-sharepoint-hosted-pdf-files-tutorial-ue.pdf
Gives this error:
$ pdf2ps -dLanguageLevel=2 adobe.pdf out.ps
Warning: File has an empty CropBox. Using the current page size
instead.
Error reading a content stream. The page may be incomplete.
This file had errors that were repaired or ignored.
The file was produced by:
Adobe PDF Library 9.9
Please notify the author of the software that produced this
file that it does not conform to Adobe's published PDF
specification.
For this 2-page document, the first page of out.ps gets transformed but the
second page does not. The original file is 256.4 KB, while transformed ps is
5.0 MB size. Printing out.ps via lpd to PS-II capable printer shows same
(page 1 has data, page 2 is blank).
So what do you guys think? Should I follow the instructions above and advise
Adobe that one of their documents does not conform to "published PDF
specifications"?
-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/ghostscript9-9-06-8-seems-broken-tp5956678p5957060.html
Sent from the freebsd-ports mailing list archive at Nabble.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: [kde-freebsd] KDE
On Wed, Oct 15, 2014 at 4:37 AM, Max Brazhnikov wrote: > On Tue, 14 Oct 2014 11:43:04 -0700 Kevin Oberman wrote: >> On Tue, Oct 14, 2014 at 11:17 AM, Alberto Villa wrote: >> >> > Hi, >> > >> > KDE SC 4.14.1 is currently being tested via exp-run, it will hit the ports >> > soon. >> > >> > On Tue, Oct 14, 2014 at 4:10 AM, jmdennis @dslextreme.com < >> > jmden...@dslextreme.com> wrote: >> > >> > > I was wondering when KDE 14.4.1 would be released. I know it has to be >> > > compiled since it is made for Linux and not FreeBSD but it would be nice >> > to >> > > have the newer version released which fixes a lot of issues and is >> > faster. >> > -- >> > Alberto Villa, FreeBSD committer >> > http://people.FreeBSD.org/~avilla >> >> >> After 10.1-RELEASE, I hope. > > I hope to get it before the release. Why do you want it after? I get very nervous about major port updates that involve large numbers of ports and have a major impact on a lot of users just prior to a release. Looking at the schedule, which has not slipped at all (Amazing!), 10.1 is 2 weeks off. I'd hope that if it comes before 10.1 that there is time for a package build and time for people to install it before the 10.1 release. This week's package build is underway and may be complete. So if you get 4.14 out before next Wednesday, I guess it should be OK, but if not, I'd suggest waiting until a week or two after 10.1 hits the streets. Probably I'm just being paranoid. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkober...@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"
Fix www/squid unexpectedly using -march=native
Hi, Since http://bazaar.launchpad.net/~squid/squid/3-trunk/revision/12842, Squid's configure script defaults to -march=native, if the flag is supported by the compiler. And this even *overrides* your own specified CPUTYPE or -march= flag! So I personally experienced Squid 3.4 crashing on an old Celeron, when it was built on a Core i7. :-( Proposed fix is to explicitly tell the configure script to *not* enable -march=native by default: Index: www/squid/Makefile === --- www/squid/Makefile (revision 370765) +++ www/squid/Makefile (working copy) @@ -181,7 +181,8 @@ --disable-epoll \ --disable-linux-netfilter \ --disable-linux-tproxy \ - --disable-translation + --disable-translation \ + --disable-arch-native .include Note that only squid 3.4 suffers from this bug, 3.3 is not affected. -Dimitry signature.asc Description: Message signed with OpenPGP using GPGMail
Re: FreeBSD Port: courier-0.65.3_3
Found a few issues with the last patch. Linked a new one below. I haven't found any issues running the new version of Courier, but I have a pretty simple installation. Link to diff: http://stoneyforest.net/~chris/courier-0.73.2-20141015.diff.gz ~Chris Stone On 10/7/2014 12:51 AM, Milan Obuch wrote: On Mon, 06 Oct 2014 16:41:46 -0400 "Christopher T. Stone" wrote: On Sun, 14 Sep 2014 01:16:03 -0400 "Saigol.ca Admin" wrote: Hello, It seems that the Courier-MTA current version is 0.73.2. The latest FreeBSD port is based on version 0.65.3, which seems to be more than 3 years old. Are there any plans to update the port to the latest version of the software? Thanks, Abid Yes, there are. Unfortunatelly, other tasks have currently more urgent attention here, and there are some issues to be solved - new dependencies are introduced and new port should be created first for library needed to build new courier... also old port was recently staged, which was necessary to keep it in tree at all. Also it looks like recently a bit more work needs to be put into patch to get new version committed into port tree, so it will take a bit of time before new version of mail/courier could be published in port tree. Before that, I will contact you as soon as I will have something to test. Your setup is most probably different from mine and thus together we can cover more usage scenarios, which is good thing everytime. Regards, Milan Milan & Abid, I'm still working on checking functionality, but the liked diff builds (the new Unicode library was already in the ports tree). I only reviewed the old patches that were broken, anything that applied cleanly I left, those that were broken need a fair number of changes so I suspect the rest could use some review. Link to diff: http://stoneyforest.net/~chris/courier-0.73.2-20141006.diff.gz Apply to the mail/courier directory with: gunzip -c ../courier-0.73.2-20141006.diff.gz | patch ~Chris Stone Big thanks for the patch. I am going to verify it here in my test setup. If it works for you, it will do hopefully for me as well. Abid, could you test it too? If nothing bad comes from my testing, I will prepare upgrade for port then. Regards, Milan ___ 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"
linux-f10 -> linux-c6 success
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi porters, I just wanted to give kudos for the linux-c6 transition. I first noticed it in /usr/src/UPGRADING, and then found that github explanation. I followed the instructions and was able to remove all of the security suicide kludges in poudriere for building linux-f10 ports. I have had no issues after two weeks. So a big THANK YOU! I'm on a recent current. You might want to publicize it a bit more? Best regards, Russell -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBAgAGBQJUPyj1AAoJEFnLrGVSDFaENiUQAKs8QgZI1/QXJMNDx8yDF7V1 qX/LzquCfZgvqKwajGWUxEWymtcFEjSuQyBXY9meO+WsigNTpbrIYFro5mczRplX dY+90XeVVa1W7icnhqnkJZHnpVtqc53LeLgozWbszrX4dCMeNvfU+DoWdt0gbbhm +xripQmF6kzv2iXzr3OJK3mUDF66tVqKiSwA2vcHAf6IOcc2aikjeoeY78GEG0lJ ODiIJmHvkw3drE3y0cd/vRfprT7XJCqJjnqpsPwa/7UR5414hgcM74Ktxj0sFUx0 7E5hxuhBVFOY3a7d/dDyFWGbbw1cSzc6JZi6ltKu2/0YS3iZtGexQQdpI8KJhzkB LyMgAEfhKbAlv/orrNMga6JysOBV8+i0KrogHtLsadqLaBxXkhHGQsyaANrTkuZ5 mV4c+V3XqcLDkT4CMeeNNXVSguUMyt7kvD7+FwurPtMGjirRfvf+W9GaTOUJANN2 /KuHJ2dVjMTs+jjv3UUYGzJkcPPEhDufY4ZIZEYzsxGv2zpeaJVt9IWBmAyjTuiE FzgkZOuL+3WSfYCSLAfbX+HLRZFAFa0ShUp7aYXiMtmTsqyN4eZFOeAFAF7GKR6b ZnbdMtwbMgnQa9/Ynh78cNr2CuXBHToVcx/36c/7HNFOMUsCn1p7/Kdno7RB3YWJ ega5JN99u+PO8S0HyB/p =taab -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"
Is py-sqlite3 broken (missing _ctypes)?
Trying to update www/seamonkey, I failed on an error in databases/py-sqlite3 relating to _ctypes, am not really familiar with that. Did I do something wrong, or is this a more general bug? I am on FreeBSD-current amd64, r272279. I tried to portmaster databases/py-sqlite3 separately after initial failure, to isolate the error. Log file is short: ===>>> Currently installed version: py27-sqlite3-2.7.6_4 ===>>> Port directory: /usr/ports/databases/py-sqlite3 ===>>> Gathering distinfo list for installed ports ===>>> Launching 'make checksum' for databases/py-sqlite3 in background ===>>> Gathering dependency list for databases/py-sqlite3 from ports ===>>> Initial dependency check complete for databases/py-sqlite3 ]0;portmaster: py27-sqlite3-2.7.6_4 ===>>> Starting build for databases/py-sqlite3 <<<=== ===>>> All dependencies are up to date ===> Cleaning for py27-sqlite3-2.7.8_5 ===> License PSFL accepted by the user ===> py27-sqlite3-2.7.8_5 depends on file: /usr/local/sbin/pkg - found ===> Fetching all distfiles required by py27-sqlite3-2.7.8_5 for building ===> Extracting for py27-sqlite3-2.7.8_5 => SHA256 Checksum OK for python/Python-2.7.8.tar.xz. ===> Patching for py27-sqlite3-2.7.8_5 ===> py27-sqlite3-2.7.8_5 depends on package: py27-setuptools27>0 - found ===> py27-sqlite3-2.7.8_5 depends on file: /usr/local/bin/python2.7 - found ===> py27-sqlite3-2.7.8_5 depends on shared library: libsqlite3.so - found (/usr/local/lib/libsqlite3.so.0.8.6) ===> Configuring for py27-sqlite3-2.7.8_5 ===> FreeBSD 10 autotools fix applied to /usr/ports/databases/py-sqlite3/work11.amd64/Python-2.7.8/Modules/_ctypes/libffi/aclocal.m4 ===> FreeBSD 10 autotools fix applied to /usr/ports/databases/py-sqlite3/work11.amd64/Python-2.7.8/Modules/_ctypes/libffi/acinclude.m4 ===> FreeBSD 10 autotools fix applied to /usr/ports/databases/py-sqlite3/work11.amd64/Python-2.7.8/Modules/_ctypes/libffi/m4/libtool.m4 ===> FreeBSD 10 autotools fix applied to /usr/ports/databases/py-sqlite3/work11.amd64/Python-2.7.8/Modules/_ctypes/libffi/configure ===> FreeBSD 10 autotools fix applied to /usr/ports/databases/py-sqlite3/work11.amd64/Python-2.7.8/Modules/zlib/configure ===> FreeBSD 10 autotools fix applied to /usr/ports/databases/py-sqlite3/work11.amd64/Python-2.7.8/configure Traceback (most recent call last): File "", line 1, in File "setup.py", line 36, in import ctypes File "/usr/local/lib/python2.7/ctypes/__init__.py", line 10, in from _ctypes import Union, Structure, Array ImportError: No module named _ctypes *** Error code 1 Stop. make: stopped in /usr/ports/databases/py-sqlite3 ===>>> make build failed for databases/py-sqlite3 ===>>> Aborting update ===>>> You can restart from the point of failure with this command line: portmaster databases/py-sqlite3 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"
