FreeBSD Port: syslog-ng-rc-3.3.7_4
hi there. i just did a portsnap update and portmaster -a my system tried to get syslog-ng.tar.gz the balabit.com site and then the freebsd site. the freebsd site doesn't have version i ended up downloading from the website balabit.com using my web browser if i just try to wget the link i get an error "301 moved permanently". regards Andrew Perry Merry Xmas from Shoalhaven City Council Councillors and staff would like to wish you the very best for the festive season and a happy and safe New Year. Council's Administration Offices will be closed to the public from 4pm Friday 21st December 2012 and will re-open 9am Wednesday 2nd January 2013. Please see your local newspaper or Council's website for details regarding Libraries and other facilities. For urgent enquiries during the holiday period contact (02) 4421 3100. This message may contain both confidential and privileged information intended only for the addressee named above. If you have received this email in error, please notify the sender immediately then destroy the original 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: Ports "make fetchindex" still getting outdated INDEX-9
I had forgotten about it again. I will try and to get it fixed within the next couple of days. -- Simon L. B. Nielsen Via mobile Sorry about the top posting On 13 Dec 2012 16:57, "Jim Pingle" wrote: > I saw a thread last month about the servers that build INDEX files being > down since the security incident - is that still the case? > > The files obtained via make fetchindex are still out of date, so I > assume they're still off, but a while back they were just missed after > some maintenance as well so part of me hoped that it may be the case yet > again. > > Any ETA on when that service might return? I can always build the index > manually or use portsnap, but fetchindex is really convenient and I'd > love to see it brought back to life. > > Perhaps the fetchindex target could be altered to print a brief message > in the interim so people know that it's not currently being updated? > > Jim > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: freebsd-ports: CGI-Application-Plugin-DBH
On 12/4/2012 4:10 PM, Felippe de Meirelles Motta wrote: Kurt, This port (p5-CGI) is very old and I not sure because it was repocopied to www/p5-CGI-modules. However I reviewed CGI-Application-Plugin-DBH port dependencies and maybe we can update it according to Makefile[1], which p5-CGI[-Modules] is not needed anymore. Could you test this patch[2] and give me a feedback ? [1] - http://cpansearch.perl.org/src/MARKSTOS/CGI-Application-Plugin-DBH-4.00/Makefile.PL [2] - http://people.freebsd.org/~lippe/logs/work/ports_www_p5-CGI-Application-Plugin-DBH.patch Thanks! lippe@ I was finally able to get my test machine installed with the 9.1-RELEASE image from the ftp server, and then rebuild all my ports on that server. I was able to use your patched Makefile, and have the CGI-Application-Plugin-DBH port build and install properly. So, as far as I'm concerned, this patch is well worth installing into the ports tree. Thanks! (I'm sorry it took several days before I could do a complete reinstall of everything and verify that things worked in a completely 'from scratch' environment.) -Kurt On Tue, Dec 4, 2012 at 3:38 PM, Kurt Lidl wrote: Greetings! I use this port in my application software. (Along with a bunch of other stuff for perl5.) In preparation for FreeBSD-9.1, I installed the 9.1-RC3 snapshot, and attempted to rebuild all the supporting modules for my application software. I ran into difficulty with this port, or more specifically, this port, its dependencies and its interaction with the new 'pkg' command. I have a script that attempts to install all the ports for the various perl modules that are needed by my application, and this is the only port that failed to install. The dependencies for CGI-Application-Plugin-DBH list "p5-CGI-modules", which conflicts with the regular old "p5-CGI" module, at least as reported by the new 'pkg' command. As far as I can see, the "p5-CGI-modules" port is a subset of the "p5-CGI" module, so if p5-CGI is already installed, then CGI-Application-Plugin-DBH is good to go. Could the dependencies for CGI-Application-Plugin-DBH be changed to be either "p5-CGI-modules" or "p5-CGI"? The particular error that gets punted out by p5-CGI-Modules is this: ===> Compressing manual pages for p5-CGI-modules-2.76^M ===> Registering installation for p5-CGI-modules-2.76 as automatic^M Installing p5-CGI-modules-2.76...pkg: p5-CGI-modules-2.76 conflicts with p5-CGI. pm-3.63,1 (installs files into the same place). Problematic file: /usr/local/li b/perl5/5.16.2/man/man3/CGI::Carp.3.gz^M *** [fake-pkg] Error code 70^M ^M Stop in /usr/ports/www/p5-CGI-modules.^M Thanks. -Kurt ___ 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: [RFC/HEADSUP] portmaster default -w (preserve shared libraries)
On 12/12/2012 1:57 AM, Matthias Andree wrote: > Am 11.12.2012 20:34, schrieb Jeremy Messenger: > >> If can't update all ports then please wait until when you can. I never >> have any problem to update all ports at a time by ran it over night >> time. Or even better, use packages if you can't afford the ports >> system. > > This is ridiculous. We know that there have been extended (months!) > periods where we were stuck because all useful versions of some > important library had security vulnerabilities. The last pain I > recollect was libxul. Old version vulnerable, no new version, and then > when the new version was around, some dependencies did not work with > libxul-10*. This would in effect have meant "no update for months". > > > Bryan, practially, I propose that portmaster should > > - list stored libraries on each and every run, and ask that the user > updates those ports that use the old, saved, libraries, pointing to > bsdadminutils and pkg_libchk. > > - we may need to save more than just the .so files, namely, the origin > and portname of a saved library so that portmaster can run portaudit > against those names to complain about security issues in saved libraries. > Good points and ideas. I will keep those in mind. -- Regards, Bryan Drewery bdrewery@freenode/EFNet signature.asc Description: OpenPGP digital signature
Ports "make fetchindex" still getting outdated INDEX-9
I saw a thread last month about the servers that build INDEX files being down since the security incident - is that still the case? The files obtained via make fetchindex are still out of date, so I assume they're still off, but a while back they were just missed after some maintenance as well so part of me hoped that it may be the case yet again. Any ETA on when that service might return? I can always build the index manually or use portsnap, but fetchindex is really convenient and I'd love to see it brought back to life. Perhaps the fetchindex target could be altered to print a brief message in the interim so people know that it's not currently being updated? Jim ___ 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: building libzrtpcpp-2.3.2
2012/12/13 Alex Povolotsky > Hello! > > I'm trying to build new linphone (2.5, it claims to have SRTP). It > requires libzrtpcpp 2, while we have only 1 in ports. > > Attempt to build failed on (apparently) a macro NAMESPACE_COMMONCPP, which > is defined... I wonder where it is defined. > > maybe someone has managed to build libzrtpcpp or something else with that > macro? > > Alex > ___ > 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" > Hi Alex libzrtpcpp ports has been updated to 2.3.2 some minutes ago. Please try again Greetings ACM ___ 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 +-+ devel/k8048 | 1.04| 2.06 +-+ misc/freeswitch-scripts-devel | 1.2.3 | 1.2.5.3 +-+ net/freeswitch-curl-devel | 1.2.3 | 1.2.5.3 +-+ net/freeswitch-insideout-devel | 1.2.3 | 1.2.5.3 +-+ net/freeswitch-sbc-devel| 1.2.3 | 1.2.5.3 +-+ net/freeswitch-vanilla-devel| 1.2.3 | 1.2.5.3 +-+ textproc/p5-Spreadsheet-WriteExcel-Styler | 1.00| 1.02 +-+ 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 If wish to stop receiving portscout reminders, please contact portsc...@portscout.freebsd.org 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"
building libzrtpcpp-2.3.2
Hello! I'm trying to build new linphone (2.5, it claims to have SRTP). It requires libzrtpcpp 2, while we have only 1 in ports. Attempt to build failed on (apparently) a macro NAMESPACE_COMMONCPP, which is defined... I wonder where it is defined. maybe someone has managed to build libzrtpcpp or something else with that macro? Alex ___ 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: Notes on upgrades after libpcre update
I agree. On the other hand, we should also mark yet unmarked ports that directly depend on pcre. The main pain comes from glib20, ports using it are directly linked against pcre but there is no information about this and we need this documented. I am releasing devel/pcre back to ports@, who wants can take care of it. On 13.12.2012 10:56, Tijl Coosemans wrote: > On 12-12-2012 10:03, Alex Dupre wrote: >> Kevin Oberman ha scritto: >>> As many of you noticed, the update of devel/pcre bumped hte version of >>> libpcre.so which is a dependency of LOTS of things. >> This was a very poor choice, we shouldn't have bumped the version. When >> there is a bump between two minor releases (8.31 -> 8.32) a red led >> should blink in port maintainer. The port should have defined: >> >> USE_AUTOTOOLS= libtool >> USE_GNOME= ltverhack >> >> to avoid bumbing the version. In fact this is the diff in configure.ac: >> >> -m4_define(libpcre_version, [1:1:0]) >> -m4_define(libpcre16_version, [0:1:0]) >> +m4_define(libpcre_version, [3:0:2]) >> +m4_define(libpcre16_version, [2:0:2]) >> >> It says that the new shared lib is compatible with the old lib (only new >> interfaces were added), since: >> >> 1 - 0 = 3 - 2 = 1 >> 1 - 0 = 2 - 2 = 0 >> >> (from the [current:revision:age] version = current - age rule) > This should be mandatory knowledge for every ports committer. > -- Martin Matuska FreeBSD committer http://blog.vx.sk ___ 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: pkgng: sqlite: database is locked
On 12/13/2012 5:16 AM, Baptiste Daroussin wrote: > On Thu, Dec 13, 2012 at 12:08:00PM +0100, Mathias Picker wrote: >> (FYI: if I stop responding, I will be in hospital, I'm waiting for an >> operation...) > > Take care of yourself, we will continue investigating, health first ! > >> >> OK, I can reproduce it now reliably, running portmaster -a, the >> following is happening three times now: >> >> > sounds like a pkgng support in portmaster bugs we will investigate > Yes, portmaster has an obscure job bug even without pkgng. It manifests with the "Terminated" output. I believe it's causing the pkgng db to be opened twice here. I'm looking into it. -- Regards, Bryan Drewery bdrewery@freenode/EFNet signature.asc Description: OpenPGP digital signature
Re: pkgng: sqlite: database is locked
Oh well, after building pkg with debug the error went away... :( I rebuild pkg just before I started portmaster -a the first time, so either it's the time it took to rebuild pkg with debug, or the debug build itself... Portmaster is still running, so maybe it comes up again Cheers, Mathias Am Donnerstag, den 13.12.2012, 12:16 +0100 schrieb Baptiste Daroussin: > On Thu, Dec 13, 2012 at 12:08:00PM +0100, Mathias Picker wrote: > > (FYI: if I stop responding, I will be in hospital, I'm waiting for an > > operation...) > > Take care of yourself, we will continue investigating, health first ! > > > > > OK, I can reproduce it now reliably, running portmaster -a, the > > following is happening three times now: > > > > > sounds like a pkgng support in portmaster bugs we will investigate > > Thanks. > > regards, > Bapt > > > > ===> Building for p5-IO-Socket-SSL-1.81 > > cp lib/IO/Socket/SSL.pm blib/lib/IO/Socket/SSL.pm > > Manifying blib/man3/IO::Socket::SSL.3 > > pkg: sqlite: database is locked > > Assertion failed: (db->lock_count == 0), function pkgdb_close, file > > pkgdb.c, line 842. > > Abort trap (core dumped) > > > > > > No locks active > > > > mp# fstat /var/db/pkg/pkgdb.db /var/db/pkg/local.sqlite > > USER CMD PID FD MOUNT INUM MODE SZ|DV R/W > > NAME > > mp# sockstat | grep -e local.sqlite -e pkgdb.db > > mp# > > > > So I guess ist's a pkg problem > > > > Which additional information might be needed to debug this? > > > > I just wanted to recompile pkg with debug info, but get > > > > mp# make > > /usr/ports/ports-mgmt/pkg/work/pkg-1.0.3/pkg-static/pkg-static: not > > found > > *** [check-vulnerable] Error code 127 > > > > Stop in /usr/ports/ports-mgmt/pkg. > > mp# make extract > > /usr/ports/ports-mgmt/pkg/work/pkg-1.0.3/pkg-static/pkg-static: not > > found > > *** [check-vulnerable] Error code 127 > > > > Stop in /usr/ports/ports-mgmt/pkg. > > > > ?? Never seen this... Will have to investigate before continuing. > > > > / Mathias > > > > ___ > > freebsd-ports@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkgng: sqlite: database is locked
On Thu, Dec 13, 2012 at 12:08:00PM +0100, Mathias Picker wrote: > (FYI: if I stop responding, I will be in hospital, I'm waiting for an > operation...) Take care of yourself, we will continue investigating, health first ! > > OK, I can reproduce it now reliably, running portmaster -a, the > following is happening three times now: > > sounds like a pkgng support in portmaster bugs we will investigate Thanks. regards, Bapt > > ===> Building for p5-IO-Socket-SSL-1.81 > cp lib/IO/Socket/SSL.pm blib/lib/IO/Socket/SSL.pm > Manifying blib/man3/IO::Socket::SSL.3 > pkg: sqlite: database is locked > Assertion failed: (db->lock_count == 0), function pkgdb_close, file > pkgdb.c, line 842. > Abort trap (core dumped) > > > No locks active > > mp# fstat /var/db/pkg/pkgdb.db /var/db/pkg/local.sqlite > USER CMD PID FD MOUNT INUM MODE SZ|DV R/W > NAME > mp# sockstat | grep -e local.sqlite -e pkgdb.db > mp# > > So I guess ist's a pkg problem > > Which additional information might be needed to debug this? > > I just wanted to recompile pkg with debug info, but get > > mp# make > /usr/ports/ports-mgmt/pkg/work/pkg-1.0.3/pkg-static/pkg-static: not > found > *** [check-vulnerable] Error code 127 > > Stop in /usr/ports/ports-mgmt/pkg. > mp# make extract > /usr/ports/ports-mgmt/pkg/work/pkg-1.0.3/pkg-static/pkg-static: not > found > *** [check-vulnerable] Error code 127 > > Stop in /usr/ports/ports-mgmt/pkg. > > ?? Never seen this... Will have to investigate before continuing. > > / Mathias > > ___ > 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" pgpR27c6m1Jzo.pgp Description: PGP signature
pkgng: sqlite: database is locked
(FYI: if I stop responding, I will be in hospital, I'm waiting for an operation...) OK, I can reproduce it now reliably, running portmaster -a, the following is happening three times now: ===> Building for p5-IO-Socket-SSL-1.81 cp lib/IO/Socket/SSL.pm blib/lib/IO/Socket/SSL.pm Manifying blib/man3/IO::Socket::SSL.3 pkg: sqlite: database is locked Assertion failed: (db->lock_count == 0), function pkgdb_close, file pkgdb.c, line 842. Abort trap (core dumped) No locks active mp# fstat /var/db/pkg/pkgdb.db /var/db/pkg/local.sqlite USER CMD PID FD MOUNT INUM MODE SZ|DV R/W NAME mp# sockstat | grep -e local.sqlite -e pkgdb.db mp# So I guess ist's a pkg problem Which additional information might be needed to debug this? I just wanted to recompile pkg with debug info, but get mp# make /usr/ports/ports-mgmt/pkg/work/pkg-1.0.3/pkg-static/pkg-static: not found *** [check-vulnerable] Error code 127 Stop in /usr/ports/ports-mgmt/pkg. mp# make extract /usr/ports/ports-mgmt/pkg/work/pkg-1.0.3/pkg-static/pkg-static: not found *** [check-vulnerable] Error code 127 Stop in /usr/ports/ports-mgmt/pkg. ?? Never seen this... Will have to investigate before continuing. / Mathias ___ 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: Notes on upgrades after libpcre update
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tijl Coosemans ha scritto: >> It says that the new shared lib is compatible with the old lib >> (only new interfaces were added), since: >> >> 1 - 0 = 3 - 2 = 1 1 - 0 = 2 - 2 = 0 Ops, the last should be 0 - 0 obviously. >> (from the [current:revision:age] version = current - age rule) > > This should be mandatory knowledge for every ports committer. Yes, it should. It's explained here: http://www.freebsd.org/gnome/docs/gnome_porting.html Not much visible or clear that it's not limited to gnome ports. - -- Alex Dupre -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (FreeBSD) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlDJqY4ACgkQgRXp2M5fVU0b9ACg6w3eHCpLMRK6088l+dSIJ8CZ HB0AoKcxHQn3MlkURZuHUyxcV3iKofto =aEoz -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Notes on upgrades after libpcre update
On 12-12-2012 10:03, Alex Dupre wrote: > Kevin Oberman ha scritto: >> As many of you noticed, the update of devel/pcre bumped hte version of >> libpcre.so which is a dependency of LOTS of things. > > This was a very poor choice, we shouldn't have bumped the version. When > there is a bump between two minor releases (8.31 -> 8.32) a red led > should blink in port maintainer. The port should have defined: > > USE_AUTOTOOLS= libtool > USE_GNOME= ltverhack > > to avoid bumbing the version. In fact this is the diff in configure.ac: > > -m4_define(libpcre_version, [1:1:0]) > -m4_define(libpcre16_version, [0:1:0]) > +m4_define(libpcre_version, [3:0:2]) > +m4_define(libpcre16_version, [2:0:2]) > > It says that the new shared lib is compatible with the old lib (only new > interfaces were added), since: > > 1 - 0 = 3 - 2 = 1 > 1 - 0 = 2 - 2 = 0 > > (from the [current:revision:age] version = current - age rule) This should be mandatory knowledge for every ports committer. signature.asc Description: OpenPGP digital signature
