Re: XMMS options and plugins
On Wed, 9 Apr 2014 20:47:23 + (UTC) Christian Weisgerber na...@mips.inka.de wrote: Finally, who uses XMMS's RUSXMMS_PATCHES option? These patches are very intrusive and getting rid of them would simplify the port. please, leave it if you can, I use it. RUSXMMS_PATCHES_DESC= Patches to handle broken non-Unicode ID3 tags looks strange to me, IMO it must be fixed, s/broken// :) -- wbr, tiger ___ 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: XMMS options and plugins
On Wed, 9 Apr 2014 20:47:23 + (UTC) Christian Weisgerber wrote: Finally, who uses XMMS's RUSXMMS_PATCHES option? These patches are very intrusive and getting rid of them would simplify the port. If you decide to keep them then maybe also restore the russian/xmms slave port. ___ 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 ports which are currently scheduled for deletion
On Wed, 9 Apr 2014 20:26:09 + (UTC) Christian Weisgerber wrote: On 2014-04-09, John Marino freebsd.cont...@marino.st wrote: In the meantime -- it's still a non-problem as long as svn revert works. svn revert throws away local changes. I don't think that's what you mean. In fact, I don't know how to even find (the history of) removed files with Subversion. For instance, at some point there must have been a port russian/xmms, but neither svnweb nor svn log show it. You can check the log of MOVED. The revision that deleted it is: http://svnweb.freebsd.org/ports?view=revisionrevision=348843 You can undo the russian part of that commit using: cd /usr/ports svn merge -c -348843 russian russian Then remove the russian/xmms line from MOVED and commit. ___ 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: Why java/linux-sun-jdk18 added?
Koichiro IWAO ha scritto: java/linux-sun-jdk18 was added just now but isn't it identical to java/linux-oracle-jdk18 ? Why -sun- port is needed? It was removed 30 minutes after the commit :-) -- Alex Dupre ___ 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
[QAT] 350791: 8x leftovers
Convert to USES=gecko:firefox With hat: portmgr - Build ID: 20140410090200-2633 Job owner: b...@freebsd.org Buildtime: 39 minutes Enddate: Thu, 10 Apr 2014 09:40:53 GMT Revision: 350791 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=350791 - Port:german/bsdforen-firefox-searchplugin Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~b...@freebsd.org/20140410090200-2633-315338/de-bsdforen-firefox-searchplugin-0.3_8.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~b...@freebsd.org/20140410090200-2633-315339/de-bsdforen-firefox-searchplugin-0.3_8.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~b...@freebsd.org/20140410090200-2633-315340/de-bsdforen-firefox-searchplugin-0.3_8.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~b...@freebsd.org/20140410090200-2633-315341/de-bsdforen-firefox-searchplugin-0.3_8.log - Port:german/bsdgroup-firefox-searchplugin Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~b...@freebsd.org/20140410090200-2633-315342/de-bsdgroup-firefox-searchplugin-0.2_9.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~b...@freebsd.org/20140410090200-2633-315343/de-bsdgroup-firefox-searchplugin-0.2_9.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~b...@freebsd.org/20140410090200-2633-315344/de-bsdgroup-firefox-searchplugin-0.2_9.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~b...@freebsd.org/20140410090200-2633-315345/de-bsdgroup-firefox-searchplugin-0.2_9.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140410090200-2633 redports https://qat.redports.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 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 +-+ print/cups-filters | 1.0.50 | 1.0.52 +-+ science/InsightToolkit | 2.8.1 | 4.5.2 +-+ www/groupoffice | 3.7.24 | 5.0.53 +-+ 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: Repair pkgng
Hi, On Wed, 9 Apr 2014, John Marino wrote: This still doesn't make sense. Distfiles are of no concern to binary packages, so why would I continue to clutter /var/db/pkg with a large tree of directories that is then duplicated to /var/db/ports? What problem in portmaster or the options framework was solved by moving this? If the portmaster-created distfiles bother you, stop using portmaster, perhaps? It seems superfluous to me anyway; I don't get why people feel they need it with pkg. I already did a while back. Yet, it's still the recommended tool in the handbook if I'm not mistaken. FreeBSD has also always adhered to a sensible hier(7), which portmaster is now breaking. IFAIK, options has always been in /var/db/ports, this is not new. It didn't get moved. Correct. Portmaster moved it's distfiles file. I'm not sure what you are trying to achieve with the what problem was solved line of questioning. If it were moved, are you trying to get it moved back? What's the goal here? Yeah. One of the advantages and early implementation goals of pkg(1) was to reduce clutter in /var/db/pkg. Secondly, 70-80% of common ports now use an options file (think DOCS, EXAMPLES, NLS), so the chance that /var/db/ports/portname already exists is pretty high. Why then reintroduce files/directories in /var/db/pkg that affect both port building and deployment? I don't understand what the upside to this change in portmaster is and thus assume that it solved an issue. -- Melvyn ___ 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
mail/mpop fails with option OpenSSL but builds with gnutls
I was unable to build mail/mpop with OpenSSL option selected but then switched to gnutls and succeeded. This is a case where at most one of two or more options can be selected. Is this a known problem, any relation to the Heartbleed problem that hit the news? Most relevant part of log file is checking pkg-config is at least version 0.9.0... yes checking for libssl... yes checking for libidn... yes checking for libgnome_keyring... no configure: WARNING: library libgnome-keyring not found: configure: WARNING: Package gnome-keyring-1 was not found in the pkg-config search path. Perhaps you should add the directory containing `gnome-keyring-1.pc' to the PKG_CONFIG_PATH environment variable Package 'gnome-keyring-1', required by 'world', not found configure: WARNING: libgnome-keyring is provided by Gnome; Debian package: libgnome-keyring-dev checking for SecKeychainGetVersion... no configure: creating ./config.status config.status: creating Makefile config.status: creating src/Makefile config.status: creating po/Makefile.in config.status: creating doc/Makefile config.status: creating scripts/Makefile config.status: creating config.h config.status: executing depfiles commands config.status: executing po-directories commands config.status: creating po/POTFILES config.status: creating po/Makefile Install prefix . : /usr/local TLS/SSL support : yes (Library: OpenSSL) GNU SASL support ... : no GNU Libidn support . : yes NLS support : yes GNOME Keyring support .. : no MacOS X Keychain support : no === Building for mpop-1.0.28 /usr/bin/make all-recursive Making all in src CC conf.o CC delivery.o CC list.o CC mpop.o CC net.o CC netrc.o CC pop3.o CC readbuf.o CC stream.o CC tools.o CC uidls.o CC xalloc.o CC md5.o CC md5-apps.o CC tls.o CC base64.o CCLD mpop /usr/local/bin/ld: tls.o: undefined reference to symbol 'X509_free' //lib/libcrypto.so.7: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status *** Error code 1 This is a case where at most one of two or more options can be selected (GNUTLS or OPENSSL). 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: Repair pkgng
On Thu, Apr 10, 2014 at 5:45 AM, Melvyn Sopacua mel...@magemana.nl wrote:
Hi,
On Wed, 9 Apr 2014, John Marino wrote:
This still doesn't make sense. Distfiles are of no concern to binary
packages, so why would I continue to clutter /var/db/pkg with a large
tree of directories that is then duplicated to /var/db/ports?
What problem in portmaster or the options framework was solved by moving
this?
If the portmaster-created distfiles bother you, stop using portmaster,
perhaps? It seems superfluous to me anyway; I don't get why people feel
they need it with pkg.
I already did a while back. Yet, it's still the recommended tool in the
handbook if I'm not mistaken. FreeBSD has also always adhered to a
sensible hier(7), which portmaster is now breaking.
IFAIK, options has always been in /var/db/ports, this is not new. It
didn't get moved.
Correct. Portmaster moved it's distfiles file.
Portmaster is not breaking hier(7).
Portmaster was originally designed to use the old pkg tools
(pkg_install, ...), it has ALWAYS placed it's files
(PM_UPGRADE_DONE_FLAG, +IGNOREME, distfiles) in
/var/db/pkg/${PKGNAME}.
The options framework is relatively new in regards to portmaster, as
portmaster was created before the options framework existed.
I'm not sure what you are trying to achieve with the what problem was
solved line of questioning. If it were moved, are you trying to get it
moved back? What's the goal here?
Yeah. One of the advantages and early implementation goals of pkg(1) was
to reduce clutter in /var/db/pkg.
Secondly, 70-80% of common ports now use an options file (think DOCS,
EXAMPLES, NLS), so the chance that /var/db/ports/portname already exists
is pretty high.
Why then reintroduce files/directories in /var/db/pkg that affect both
port building and deployment? I don't understand what the upside to this
change in portmaster is and thus assume that it solved an issue.
--
DISCLAIMER:
No electrons were maimed while sending this message. Only slightly bruised.
___
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: Repair pkgng
On Thu, 10 Apr 2014 08:07:55 -0500
Scot Hetzel wrote:
Portmaster is not breaking hier(7).
It's not, because it's information about what was used to build the
packages, so /var/db/pkg is a legitimate location.
Portmaster was originally designed to use the old pkg tools
(pkg_install, ...), it has ALWAYS placed it's files
(PM_UPGRADE_DONE_FLAG, +IGNOREME, distfiles) in
/var/db/pkg/${PKGNAME}.
The options framework is relatively new in regards to portmaster, as
portmaster was created before the options framework existed.
It's newer than the recently reworked version of the options
framework, but /var/db/port was used for options before that.
___
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: Repair pkgng
On Thu, 10 Apr 2014 15:03:09 +0100 RW wrote: It's newer than the recently reworked version of the options framework, but /var/db/port was used for options before that. Sorry, I meant: the recently reworked version of the options framework is newer than portmaster, ___ 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
[QAT] 350811: 4x leftovers
Fix build issues by changing LIB_DEPENDS to devel/libzookeeper Strip ZooKeeper.so on install Remove duplicate @dirrm entries from pkg-plist - Build ID: 20140410145000-56048 Job owner: skreu...@freebsd.org Buildtime: 5 minutes Enddate: Thu, 10 Apr 2014 14:55:23 GMT Revision: 350811 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=350811 - Port:devel/p5-Net-ZooKeeper 0.35_1 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~skreu...@freebsd.org/20140410145000-56048-315414/p5-Net-ZooKeeper-0.35_1.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~skreu...@freebsd.org/20140410145000-56048-315415/p5-Net-ZooKeeper-0.35_1.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~skreu...@freebsd.org/20140410145000-56048-315416/p5-Net-ZooKeeper-0.35_1.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~skreu...@freebsd.org/20140410145000-56048-315417/p5-Net-ZooKeeper-0.35_1.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140410145000-56048 redports https://qat.redports.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
INDEX build failed for 8.x
INDEX build failed with errors:
Generating INDEX-8 - please
wait../home/indexbuild/tindex/ports/Mk/bsd.gecko.mk, line 511: Malformed
conditional (${USE_MOZILLA:M-nspr})
/home/indexbuild/tindex/ports/Mk/bsd.gecko.mk, line 517: Malformed
conditional (${USE_MOZILLA:M-nss})
/home/indexbuild/tindex/ports/Mk/bsd.port.mk, line 6655: if-less endif
/home/indexbuild/tindex/ports/Mk/bsd.port.mk, line 6658: if-less endif
make: fatal errors encountered -- cannot continue
=== www/gecko-sharp20 failed
*** [describe.www] Error code 1
*** [/home/indexbuild/tindex/ports/INDEX-8] Error code 1
Stop in /home/indexbuild/tindex/ports.
*** [index] Error code 1
Stop in /home/indexbuild/tindex/ports.
1 error
Committers on the hook:
bapt bdrewery erwin marino pawel skreuzer
Most recent SVN update was:
Updating '.':
UMk/bsd.gecko.mk
UMk/bsd.port.mk
Demulators/vgba-bin/pkg-plist
Uemulators/vgba-bin/Makefile
Demulators/vgb-bin/pkg-plist
Uemulators/vgb-bin/Makefile
Uirc/ircd-ru/Makefile
Ulang/gcc-aux/Makefile
Ulang/gcc-aux/files/diff-cxx-testsuite
Ulang/gcc-aux/Makefile.common
Udevel/p5-Net-ZooKeeper/pkg-plist
Udevel/p5-Net-ZooKeeper/Makefile
Adevel/libzookeeper
Adevel/libzookeeper/Makefile
Adevel/libzookeeper/distinfo
Adevel/libzookeeper/pkg-descr
Adevel/libzookeeper/pkg-plist
Udevel/tcl-trf/files/patch-md2
Adevel/tcl-trf/files/patch-md2d
Udevel/tcl-trf/pkg-plist
Udevel/tcl-trf/Makefile
Udevel/Makefile
Uwww/npm/Makefile
Updated to revision 350811.
___
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
Interesting Ideas for you to Consider
Hello, My name is Henry Parker; I run a business selling consumer goods (home appliances electronics). Sitting at the cash counter the whole day, often leaves me with a lot of spare time, to actively follow my other passion: writing. I love writing about the consumer goods business as I know its ins and outs. My eventual aim is to establish myself as a writer of some repute. I am keen to feature an article on your site as it would do wonders for my portfolio as a writer and also help me reach out to a really large audience. Here are a few ideas that I feel you will like: 1. Latest Samsung phones you should know about2. 5 effective ideas for improving your stereo mixing3.Increasing craze of the Phablet4. Apple vs Samsung; which is more consumer friendly?5.Best user friendly phones for your aging parents6. The best audio devices available in the market7. How best to set up your Home Theatre System to get optimum results8.Top 10 budget cell phones with all features9. Things to keep in mind while buying speakers for your laptop 10.Why is Blackberry losing its edge?11. Why a pocket television app makes a lot of sense12. Tips on improving the acoustics of your living room for a better movie watching experience13. 5 reasons why shelf stereos are soon to become extinct14. A DIY car stereo installation guide I hope this proposal is agreeable, so that your readers get the opportunity to benefit from what I can contribute. In fact, I am also open to any suggestions or ideas that you might have.Lastly, I am willing to give $30 to have my article published as I am really keen to feature on your site and hence feel that it would be sound investment. Shall eagerly await your reply. RegardsHenry ___ 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 ports which are currently scheduled for deletion
Tijl Coosemans: You can undo the russian part of that commit using: cd /usr/ports svn merge -c -348843 russian russian After consulting the Subversion book, I think svn cp ^/head/russian/xmms@348842 russian would be the better way to resurrect a port. Then remove the russian/xmms line from MOVED and commit. -- Christian naddy Weisgerber na...@mips.inka.de ___ 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
New port, what's next?
Hi, I created a new port, Typo3-LTS. The tgz contains - Makefile - distinfo - pkg-plist - pkg-descr - a diff from www/typo3 The file has ~150kB so I assume it's to big for a PR. www/typo345 and www/typo347 will deprecate and only www/typo3 and www/typo3-LTS shall remain in the ports tree. What's next? Thanks in advance, Helmut --- Diese E-Mail ist frei von Viren und Malware, denn der avast! Antivirus Schutz ist aktiv. http://www.avast.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: FreeBSD ports which are currently scheduled for deletion
On Wed, Apr 09, 2014 at 11:28:43AM +0200, John Marino wrote: On 4/9/2014 11:22, Big Lebowski wrote: While we are not having any way to measure ports usage (or am I wrong here?), we're still building packages from ports, and I would hope that we could get some statistics of pkg usage for certain packages from official repositories, could we? This is not exactly direct relationship for the port being used but I would think that such knowledge is better than none. How do you distinguish packages downloaded by mirrors versus those downloaded by pkg? At DragonFly, we'd love to know how to do this because it always comes up when the it's kill to kill i386 platform discussion comes up. Every time somebody brings up a statistic about how many times packages are download (or what % packages downloaded are i386) then the very next questions is: are those legitimate downloads. As a sidenote, perhaps its the time to introduce some sort of package/ports usage data gathering to FreeBSD just like Debian/Ubuntu are doing it, that would be anonymous and optional? Maybe pkg adds some unique variable to the download URL. If not, it could, and statistics could be tracked that way by analyzing the web server logs. The useragent for pkg is pkg/version :D Exactly for that purpose regards, Bapt pgpX2f3CmySY7.pgp Description: PGP signature
Re: New port, what's next?
On 10/04/2014 18:53, Helmut Schneider wrote: I created a new port, Typo3-LTS. The tgz contains - Makefile - distinfo - pkg-plist - pkg-descr - a diff from www/typo3 The file has ~150kB so I assume it's to big for a PR. I assume the bulk of that is the pkg-plist. The largest pkg-plist in the ports tree is 4M. In my opinion huge plists should be dynamically generated, but in your case I'd just I'd just temp-host the file somewhere and file a PR with a link and a checksum. Regards -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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: New port, what's next?
Dominic Fandrey wrote: On 10/04/2014 18:53, Helmut Schneider wrote: I created a new port, Typo3-LTS. The tgz contains - Makefile - distinfo - pkg-plist - pkg-descr - a diff from www/typo3 The file has ~150kB so I assume it's to big for a PR. In my opinion huge plists should be dynamically generated Tell me more. :) ___ 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: New port, what's next?
On 4/10/2014 19:44, Helmut Schneider wrote: Dominic Fandrey wrote: On 10/04/2014 18:53, Helmut Schneider wrote: I created a new port, Typo3-LTS. The tgz contains - Makefile - distinfo - pkg-plist - pkg-descr - a diff from www/typo3 The file has ~150kB so I assume it's to big for a PR. In my opinion huge plists should be dynamically generated Tell me more. :) http://svnweb.freebsd.org/ports/head/lang/gcc-aux/Makefile?revision=350807view=markup Look at the post-install target for an example how to do this. here's another example: http://svnweb.freebsd.org/ports/head/www/aws/Makefile?revision=349237view=markup John ___ 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
[CFT] audio/xfce4-mixer 4.11.0
Hi, New release (targetted development) has been published yesterday. It's already present in Xfce repository [1]. This release is mostly bugfix. As xfce4-mixer uses old GStreamer API (0.10) not anymore maintained by upstream, so I wonder, if it's interesting to replace our previous port. Moreover, GstMixerInterface (opaque structure for sound card in GStreamer) has been removed in the new API (1.0). I think in the future, update of xfce4-mixer will be rare. If you want to test: svn co https://svn.redports.org/olivierd/xfce4/tags/4.11/audio/xfce4-mixer Then copy repository into your ports tree. If someone prefers patch, tell me. [1] https://svn.redports.org/olivierd/xfce4/ -- olivier ___ 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
INDEX now builds successfully on 8.x
___ 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: New port, what's next?
On Thu, Apr 10, 2014 at 07:32:31PM +0200, Dominic Fandrey wrote: On 10/04/2014 18:53, Helmut Schneider wrote: I created a new port, Typo3-LTS. The tgz contains - Makefile - distinfo - pkg-plist - pkg-descr - a diff from www/typo3 The file has ~150kB so I assume it's to big for a PR. I assume the bulk of that is the pkg-plist. The largest pkg-plist in the ports tree is 4M. In my opinion huge plists should be dynamically generated, but in your case I'd just I'd just temp-host the file somewhere and file a PR with a link and a checksum. Regards -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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 Autoplist are harmful! and should be avoided as much as possible, I know python and ruby has it but I m really not happy about that autoplist is dangerous because we have no way to control that what is package is what the maintainer expect to be packaged! therefore we often end up with unoticed problems regards, Bapt pgpn99DPGuQTq.pgp Description: PGP signature
Missing binary package security updates?
Hi, I recently started using the new fancy pkgng binary packages on some machines that I maintain. I thought I could save a lot of time as I would not need to keep compiling ports manually any more. Unfortunately it seems that it was not such a good idea: # date Thu Apr 10 21:27:22 EEST 2014 # pkg audit openssl-1.0.1_9 is vulnerable: OpenSSL -- Multiple vulnerabilities - private data exposure CVE: CVE-2014-0076 CVE: CVE-2014-0160 WWW: http://portaudit.FreeBSD.org/5631ae98-be9e-11e3-b5e3-c80aa9043978.html 1 problem(s) in the installed packages found. # pkg upgrade Updating repository catalogue Nothing to do # This is on FreeBSD 8/i386. I think I have noticed binary package updates only about once a week. Is my observation correct? Why such an infrequent update cycle? If there is some real reason to build package updates so rarely, would it be possible to hasten the cycle whenever serious issues like CVE-2014-0160 are found? Right now pkgng binary packages are not really suitable for production use because of lacking essential security updates. (There should be a loud and clear warning about this in the Handbook if it stays this way?) Best Regards, -- Janne Snabb sn...@epipe.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: New port, what's next?
On 4/10/2014 20:28, Baptiste Daroussin wrote: On Thu, Apr 10, 2014 at 07:32:31PM +0200, Dominic Fandrey wrote: On 10/04/2014 18:53, Helmut Schneider wrote: I created a new port, Typo3-LTS. The tgz contains - Makefile - distinfo - pkg-plist - pkg-descr - a diff from www/typo3 The file has ~150kB so I assume it's to big for a PR. I assume the bulk of that is the pkg-plist. The largest pkg-plist in the ports tree is 4M. In my opinion huge plists should be dynamically generated, but in your case I'd just I'd just temp-host the file somewhere and file a PR with a link and a checksum. Autoplist are harmful! and should be avoided as much as possible, I know python and ruby has it but I m really not happy about that autoplist is dangerous because we have no way to control that what is package is what the maintainer expect to be packaged! therefore we often end up with unoticed problems Yes, but 6,000 - 20,000 line plists are unwieldy to say the least. And the danger can be mitigated by the maintainer by reviewing the internal temporary package list, ideally on multiple platforms. Also some plists are really hard to make manually if there are many options or if the plist morphs depending on the combination of options. yes, a safety net is removed with a generated plist but it has it's place. The maintainer just has to be vigilant. John ___ 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: Missing binary package security updates?
On 4/10/2014 1:35 PM, Janne Snabb wrote: Hi, I recently started using the new fancy pkgng binary packages on some machines that I maintain. I thought I could save a lot of time as I would not need to keep compiling ports manually any more. Unfortunately it seems that it was not such a good idea: # date Thu Apr 10 21:27:22 EEST 2014 # pkg audit openssl-1.0.1_9 is vulnerable: OpenSSL -- Multiple vulnerabilities - private data exposure CVE: CVE-2014-0076 CVE: CVE-2014-0160 WWW: http://portaudit.FreeBSD.org/5631ae98-be9e-11e3-b5e3-c80aa9043978.html 1 problem(s) in the installed packages found. # pkg upgrade Updating repository catalogue Nothing to do # This is on FreeBSD 8/i386. I think I have noticed binary package updates only about once a week. Is my observation correct? Why such an infrequent update cycle? If there is some real reason to build package updates so rarely, would it be possible to hasten the cycle whenever serious issues like CVE-2014-0160 are found? (I am involved in building the packages) Yes packages currently start building Tuesday night. It takes until Saturday/Sunday for all release/arch to finish building. As each release/arch is finished the packages are uploaded. I did want to expedite updating this package but was blocked by a number of things. I regret we did not, and will not, have a package available sooner for all release/archs. I have started an internal discussion on building packages more frequently for security updates. Right now pkgng binary packages are not really suitable for production use because of lacking essential security updates. (There should be a loud and clear warning about this in the Handbook if it stays this way?) Best Regards, -- Regards, Bryan Drewery signature.asc Description: OpenPGP digital signature
Re: PKGNG + portmaster /var/db/pkg/ not empty
-- Weitergeleitete Nachricht --
From: Scot Hetzel swhet...@gmail.com
To: Michael Schuh michael.sc...@gmail.com
Cc: FreeBSD Ports freebsd-ports@freebsd.org
Date: Wed, 9 Apr 2014 22:31:01 -0500
Subject: Re: PKGNG + portmaster /var/db/pkg/ not empty
On Wed, Apr 9, 2014 at 5:22 PM, Michael Schuh michael.sc...@gmail.com
wrote:
Hi there,
as far as i understood /var/db/pkg should be empty, after an fresh update
to stable 10 and
# pkg delete -a -f
WITH_PKGNG=yes
is set in /etc/make.conf
the next inquiry of pkg asks for
the installation of pkg. everything fine so far.
now i would going to use the freshly updated ports tree
to reinstall all packages starting with portmaster.
the call up of
# make config
shows only a message like options changed, but no dialog.
thanks google i could figure out to install dialog4 ports first,
then i got this working again.
for my opinion:
it should get installed automatically or the dialog from the system
should
get used
or at least iot should printout a hint or error message.
installing portmaster now and inquire an
portmaster `cat installed-ports-list` like in the man page of portmaster
recommended, i get the
/var/db/pkg filled again. beside the local.sqlite db from pkng.
for the fun, some packages didn'r installed files in /var/db/pkg.
it are exactly 4 packages difference, any relation to MAKEARGS=-j4 ?
Any ideas how to get rid of this behaviour?
When portmaster is run, it creates a
/var/db/pkg/${PKGNAME}/PM_UPGRADE_DONE_FLAG file to keep track of
which ports it has upgraded. This allows portmaster to skip over
ports it has already upgraded. When it has successfully completed the
run, the PM_UPGRADE_DONE_FLAG is removed, but the
/var/db/pkg/$PKGNAME} is left behind.
--
DISCLAIMER:
No electrons were maimed while sending this message. Only slightly bruised.
Ha, ok thank you.
Right the electrons get a bit more bruised then.
i expected the portmaster consitent in his behaviour and
cleanup. i thought of he respects WITH_PKGNG he would be
aware, that he is the only one, who uses those dirs.
___
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: Missing binary package security updates?
On 4/10/2014 22:05, Bryan Drewery wrote: On 4/10/2014 1:35 PM, Janne Snabb wrote: I think I have noticed binary package updates only about once a week. Is my observation correct? Why such an infrequent update cycle? If there is some real reason to build package updates so rarely, would it be possible to hasten the cycle whenever serious issues like CVE-2014-0160 are found? (I am involved in building the packages) Yes packages currently start building Tuesday night. It takes until Saturday/Sunday for all release/arch to finish building. As each release/arch is finished the packages are uploaded. I think there is also some misconceptions here. There are over 24,000 packages. Even with incremental building, one week's worth of changes forces between 7000 and 15000 packages to rebuild. I assume some people think that touching 300 packages in a week means only 300 packages need to be rebuilt, but the reality is that it's hundreds. Depending on the machines and how many there are, it could take multiple days to make packages for just one platform. If it takes two days and there are 4 platforms to build, that's 8 days right there. So the words infrequent update cycle I think is a signal that these parameters aren't understood. (Note, I am not involved in building FreeBSD packages) Right now pkgng binary packages are not really suitable for production use because of lacking essential security updates. (There should be a loud and clear warning about this in the Handbook if it stays this way?) What would make it better? Even if somebody designed a particular vulnerability so important that it merited an out of cycle build (and all the ripples that would cause) it is still looking at 2-3 days cycle, minimum. How many of these security updates are essential and can't wait 7 days?. heartbleed doesn't happen every day... Depending on what is deemed acceptable, I can't envision how binary packages (a courtesy ultimately) can be made good enough from a security standpoint. John ___ 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: New port, what's next?
On Thu, Apr 10, 2014 at 08:37:45PM +0200, John Marino wrote: On 4/10/2014 20:28, Baptiste Daroussin wrote: On Thu, Apr 10, 2014 at 07:32:31PM +0200, Dominic Fandrey wrote: On 10/04/2014 18:53, Helmut Schneider wrote: I created a new port, Typo3-LTS. The tgz contains - Makefile - distinfo - pkg-plist - pkg-descr - a diff from www/typo3 The file has ~150kB so I assume it's to big for a PR. I assume the bulk of that is the pkg-plist. The largest pkg-plist in the ports tree is 4M. In my opinion huge plists should be dynamically generated, but in your case I'd just I'd just temp-host the file somewhere and file a PR with a link and a checksum. Autoplist are harmful! and should be avoided as much as possible, I know python and ruby has it but I m really not happy about that autoplist is dangerous because we have no way to control that what is package is what the maintainer expect to be packaged! therefore we often end up with unoticed problems Yes, but 6,000 - 20,000 line plists are unwieldy to say the least. And the danger can be mitigated by the maintainer by reviewing the internal temporary package list, ideally on multiple platforms. Also some plists are really hard to make manually if there are many options or if the plist morphs depending on the combination of options. yes, a safety net is removed with a generated plist but it has it's place. The maintainer just has to be vigilant. Can't we teach the ports system to handle pkg-plist.gz? pgpVQZOwTagy4.pgp Description: PGP signature
[QAT] 350860: 4x leftovers
- Unbreak python support - Fix pkg-plist issue - Bump PORTREVISION PR: ports/188440 Submitted by: Johannes Jost Meixner x...@freebsd.org - Build ID: 20140410215000-60496 Job owner: z...@freebsd.org Buildtime: 5 minutes Enddate: Thu, 10 Apr 2014 21:55:28 GMT Revision: 350860 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=350860 - Port:net-mgmt/net-snmp 5.7.2_6 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~z...@freebsd.org/20140410215000-60496-315586/net-snmp-5.7.2_6.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~z...@freebsd.org/20140410215000-60496-315587/net-snmp-5.7.2_6.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~z...@freebsd.org/20140410215000-60496-315588/net-snmp-5.7.2_6.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~z...@freebsd.org/20140410215000-60496-315589/net-snmp-5.7.2_6.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140410215000-60496 redports https://qat.redports.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
[QAT] 350862: 4x leftovers
- Fix another pkg-plist issue - Bump PORTREVISION - Build ID: 20140410220400-14847 Job owner: z...@freebsd.org Buildtime: 5 minutes Enddate: Thu, 10 Apr 2014 22:09:19 GMT Revision: 350862 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=350862 - Port:net-mgmt/net-snmp 5.7.2_7 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~z...@freebsd.org/20140410220400-14847-315590/net-snmp-5.7.2_7.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~z...@freebsd.org/20140410220400-14847-315591/net-snmp-5.7.2_7.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~z...@freebsd.org/20140410220400-14847-315592/net-snmp-5.7.2_7.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~z...@freebsd.org/20140410220400-14847-315593/net-snmp-5.7.2_7.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140410220400-14847 redports https://qat.redports.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: Why java/linux-sun-jdk18 added?
I read commit message and got what happened, thanks. On Thu, Apr 10, 2014 at 10:40:24AM +0200, Alex Dupre wrote: Koichiro IWAO ha scritto: java/linux-sun-jdk18 was added just now but isn't it identical to java/linux-oracle-jdk18 ? Why -sun- port is needed? It was removed 30 minutes after the commit :-) -- Alex Dupre -- `whois vmeta.jp | nkf -w` meta m...@vmeta.jp ___ 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 regenerative medicine can improve outcomes in patients with chronic wounds
= a:link { text-decoration: none !important; color: #2E3192 } a:visited
{ text-decoration: none !important; color: #2E3192 } a:hover {
text-decoration: none !important; color: #2E3192 } a:active {
text-decoration: none !important; color: #2E3192 } #outlook a {
padding: 0; } /* Force Outlook to provide a view in browser button.
*/ body { width: 100% !important; margin: 0; padding: 0; }
.ReadMsgBody { width: 100%; } .ExternalClass { width: 100%; } /*
Force Hotmail to display emails at full width */ body {
-webkit-text-size-adjust: 100%; -ms-text-size-adjust: 100%;
-webkit-font-smoothing: antialiased; } .yshortcuts, .yshortcuts a,
.yshortcuts a:link, .yshortcuts a:visited, .ysh= ortcuts a:hover,
.yshortcuts a span { text-decoration: none !important; border-bottom:
none !important; background: none !important; } /* Reset Margins and
Paddings */ h1, h2, h3, p { margin-top: 0 !important; margin-right: 0
!important; margin-bottom: 10px !important; margin-left: 0!
!important;
} img { border: 0; display: block; -ms-interpolation-mode: bicubic; }
.img-inline { display: inline; border: 0; vertical-align: -2px;
-moz-border-radius: 0 !important; -webkit-border-radius: 0 !important;
border-radius: 0 !important; } .BGtable { height: 100% !important;
margin: 0; padding: 0; width: 100% !important; } br { line-height:
20px; } @media only screen and (max-width: 640px) { img[class~=img] {
width: 100% !important; height: 100% !important; max-height: auto
!important; max-width: auto !important; } img[class~=imgspkr] {
width: 100% !important; height: 100% !important; max-height: 94px
!important; max-width: 73px !important; } img[class~=imgevent] {
width: 100% !important; height: 100% !important; max-height: 205px
!important; max-width: 248px !important; text-align: center !important;
} img[class~=container] { width: 100% !important; height: 10px
!important; } td[class~=sidebar-maincontent-right] { padding-left:
10px !important; } td[!
class~=sidebar-maincontent] { padding-right:
10px !important; } td[class~=general-td] { padding: 10px 10px 0 10px
!important; } td[class~=general-img-td] { padding: 10px !important; }
/*--Table Size--*/ table[class~=row] { width: 560px
!important; } table[class=sidebar] { width: 38% !important; }
table[class=maincontent] { width: 62% !important; }
table[class~=col2] { width: 50% !important; } table[class~=col3] {
width: 33% !important; } table[class~=col-2-3] { width: 67%
!important; } table[class~=col4] { width: 50% !important; }
/*---footer table---*/ table[class=footer-left] { width: 65%
!important; } table[class=footer-right] { width: 35% !important; }
/*---img-size--*/ img[class=wrap] { width: 100% !important;
height: 10px !important; } img[class=img-166h] { max-width: 130px
!important; } img[class=devider-img] { width: 100% !important;
height: 10px !important; } } @media only screen and (max-width: 480px)
{ /*container*/ table[
class~=row] { width: 400px !important; }
/*small table*/ tab!
le[class=sidebar] { width: 100% !important; }
table[class=maincontent] { width: 100% !important; }
table[class~=col2] { width: 100% !important; }
table[class~=col3][class~=full] { width: 100% !important; }
table[class~=col-2-3] { width: 100% !important; }
table[class~=col3] { width: 50% !important; } table[class~=col4] {
width: 50% !important; } /*footer table*/ table[class=footer-left] {
width: 100% !important; } table[class=footer-right] { width: 100%
!important; } table[class=footer-left] td { text-align: left
!important; } table[class=footer-right] td { text-align: left
!important; } /*---img-size--*/ table[class~=col4] .img {
max-width: 100% !important; } td[class~=sidebar-maincontent] {
padding: 0 !important; } td[class~=sidebar-maincontent-right] {
padding: 0 !important; } td[class~=webonly], span[class~=webonly] {
display: none !important; } } @media only screen and (max-width: 360px)
{ table[class~=row] { width: 320px !!
important; }
table[class~=col3], table[class~=col4] { width: 100% !important; }
img[class=img-166h] { width: 100px !important; } img[class=wrap] {
width: 98% !important; height: 10px !important; } td[class~=top-bar]
{ padding: 5px 10px !important; } } @media only screen and (max-width:
320px) { table[class~=row] { width: 300px !important; }
img[class=img-166h] { width: 80px !important; } }
tire track of sessions dedicated to Limb Preserva= tion
includ!
ing:
Offloading: Preventing and Treating Diabetic Foot Ulcers
The Challenge of Chronic Osteomyelitis: Diagnosis and Treatment
An Interdisciplinary Approach to Treating Critical Limb Ischemia
Bioengineered Tissue
Arterial Interventions
Podiatric Surgery: Biomechanical Diabetic Foot Ulcer Healing
Healthcare Reform and the Wound Team
In addition to sessions f= ocused on Limb Preservation, SAWC
Spring/WHS provides more= than 2,000 physicians, podiatrist= s, nurses,
physical therapists, a= nd allied health professionals access to dozens
of other provoca= tive new ses= sions and late-breaking
Re: PKGNG + portmaster /var/db/pkg/ not empty
On 4/10/2014 3:16 PM, Michael Schuh wrote: -- Weitergeleitete Nachricht -- From: Scot Hetzel swhet...@gmail.com To: Michael Schuh michael.sc...@gmail.com Cc: FreeBSD Ports freebsd-ports@freebsd.org Date: Wed, 9 Apr 2014 22:31:01 -0500 Subject: Re: PKGNG + portmaster /var/db/pkg/ not empty On Wed, Apr 9, 2014 at 5:22 PM, Michael Schuh michael.sc...@gmail.com wrote: Hi there, as far as i understood /var/db/pkg should be empty, after an fresh update to stable 10 and Being tracked here: https://github.com/freebsd/portmaster/issues/37 -- Regards, Bryan Drewery signature.asc Description: OpenPGP digital signature
ADVERTISING
A serious minded Car owner is needed by our company to put our Advert on is Car while driving around on his normal route to create awareness for our customer. ___ 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
