Re: MP3 licensing over - can we remove LAME restrictions?
Quoting Matthieu Volat (from Tue, 16 May 2017 17:31:39 +0200): On Tue, 16 May 2017 14:44:52 + Ben Woods wrote: On Tue, 9 May 2017 at 1:07 pm, Koichiro IWAO wrote: > Hi, > > FYI, MP3 is coming back to Fedora. I think FreeBSD may able to do that. > https://fedoramagazine.org/full-mp3-support-coming-soon-to-fedora/ > If this analysis is correct, it sounds like the final patents will expire by the end of this year? http://www.tunequest.org/a-big-list-of-mp3-patents/20070226/ https://www.iis.fraunhofer.de/en/ff/amm/prod/audiocodec/audiocodecs/mp3.html That should be it? Now we can wait for aac, h264, h265 ;) See the comment in the LAME port next to the RESTRICTED line. Bye, Alexander. -- http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.orgnetch...@freebsd.org : PGP 0x8F31830F9F2772BF pgpXvVclGN9x6.pgp Description: Digitale PGP-Signatur
Re: MP3 licensing over - can we remove LAME restrictions?
Am Freitag, den 19.05.2017, 13:29 +0200 schrieb Alexander Leidinger: > Quoting Matthieu Volat (from Tue, 16 May 2017 > 17:31:39 +0200): > > > > > On Tue, 16 May 2017 14:44:52 + > > Ben Woods wrote: > > > > > > > > On Tue, 9 May 2017 at 1:07 pm, Koichiro IWAO > > > wrote: > > > > > > > > > > > Hi, > > > > > > > > FYI, MP3 is coming back to Fedora. I think FreeBSD may able to > > > > do that. > > > > https://fedoramagazine.org/full-mp3-support-coming-soon-to-fedo > > > > ra/ > > > > > > > If this analysis is correct, it sounds like the final patents > > > will expire > > > by the end of this year? > > > > > > http://www.tunequest.org/a-big-list-of-mp3-patents/20070226/ > > > > > https://www.iis.fraunhofer.de/en/ff/amm/prod/audiocodec/audiocodecs > > /mp3.html > > > > That should be it? Now we can wait for aac, h264, h265 ;) > > See the comment in the LAME port next to the RESTRICTED line. > > Bye, > Alexander. > I *love* this kind of thoroughness! :) Mathias -- Mathias Picker Geschäftsführer mathias.pic...@virtual-earth.de virtual earth Gesellschaft für Wissens re/prä sentation mbH http://www.virtual-earth.de/ HRB126870 supp...@virtual-earth.de Westendstr. 142 089 / 1250 3943 80339 München ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: mesa libs issue
On 05/17/17 08:00, tech lists wrote: > [...] > What I did was this, after seeing David's very helpful email to the > list: > > pkg delete -f libEGL-17.0.3 libGL-17.0.3 libglesv2-17.0.3 gbm-17.0.3 > libglapi-17.0.3 dri-17.0.3.2 > [...] More generally: pkg delete -f libEGL libGL libglesv2 gbm libglapi dri in case you are upgrading from a different current version. -- George signature.asc Description: OpenPGP digital signature
Re: Please commit Tor NODOCS regression fix: #219246 and #219248
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219246 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219248 These patches fix the port regression, and also update tor to 3.0.7, which fixes a security problem. Please commit these patches. Thanks, Yuri ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
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 +-+ math/giacxcas | 1.2.2-57| 1.2.3-45 +-+ 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 https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Please commit Tor NODOCS regression fix: #219246 and #219248
Hi! > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219246 Done. -- p...@opsec.eu+49 171 3101372 3 years to go ! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Please commit Tor NODOCS regression fix: #219246 and #219248
Hi! > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219248 Done. -- p...@opsec.eu+49 171 3101372 3 years to go ! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [Openvpn-devel] security/openvpn23 tarball size mismatch
Hi, (let's see if I can actually mail to the folks and lists on CC: or not :) ) On Thu, May 18, 2017 at 09:27:04AM +0200, Matthias Andree wrote: > Upstream maintainers will need to talk about this and may need to > release 2.3.16 to resolve any uncertainties. Which is what we did. Rounded up a handful of minor bugfixes, and released a single, well-defined and well-distributed 2.3.16 tarball. Apologies again for the mess. gert -- USENET is *not* the non-clickable part of WWW! //www.muc.de/~gert/ Gert Doering - Munich, Germany g...@greenie.muc.de fax: +49-89-35655025g...@net.informatik.tu-muenchen.de signature.asc Description: PGP signature
devel/glib20: Undefined symbol "environ"
On recent CURRENT, FreeBSD 12.0-CURRENT #93 r318480: Thu May 18 20:48:25 CEST 2017 amd64, with WITH_LLD_IS_LD=yes set, mplayer rejects to work and fails to start and quits immediately with: /usr/local/lib/libglib-2.0.so.0: Undefined symbol "environ" I already tried to recompile mplayer with "portmaster -df" to hit all ports required or especially recompiled libglib-2.0, but without success. Its strange ... Is there any hint? Kind regards and thanks in advance, O. Hartmann p.s.: Please CC me, I'm not a subscriber of this list. pgpxrBuF3BRNb.pgp Description: OpenPGP digital signature
Re: devel/glib20: Undefined symbol "environ"
There exists a PR: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218659 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD Port: nvidia-driver-375.39
I'm having a problem loading the nvidia-driver 375.39. I get the following error: link_elf_obj: symbol sc_get_softc undefined linker_load_file: Unsupported file type Any suggestions? Kevin Arch = amd64 Freebsd 11.0 stable ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: How should we name node-js ports ?
On 14/5/17 8:16 pm, Rodrigo Osorio wrote: Hi, I have a bunch of nodejs ports to add, most of them as dependencies, and I wonder if we can find a naming standard like adding 'node' or 'node-js' prefix in the name ; I personally prefer 'node'. As a result a port who install the node package xxx will be named 'node-xxx' Does it sounds good to you ? Thanks for your time, this brings up the whole question of whether we should package these things ourselves anyhow. python and perl have their own schemes (pip et al.) and with npm (and others) node is no exception. it seems that to chase these packages down manually is a never ending task. maybe the way we should handle it is to have a generic "handover to external package manager" feature, so that we somehow let npm (or whatever) do it ting but then take the output result an put it into our database. At $JOB we have the issue of many many node modules for our new gen UI and it causes us a great headache. -- rodrigo ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
