PR stalled/timeout (was: ports/170632: devel/otrs: please update to current version)
Hi, would someone please takeover PR ports/170632? It's been open for 6 months now. The version in the ports collection is already 6 patchlevels behind the current version of OTRS. But it's not due to a lack of maintenance or contributions. Several people invested time, sent patches, posted build logs, wrote followups, but all work is lost, if no one actually commits the changes to the ports repository. Thank you for taking notice. Regards - Frank ___ 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
Current unassigned ports problem reports
(Note: an HTML version of this report is available at http://www.freebsd.org/cgi/query-pr-summary.cgi?category=ports .) The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description f ports/176415sysutils/linuxfdisk does not fetch o ports/176411scan_ffs fails in port search. o ports/176408[maintainer update] audio/spek 0.8.2 o ports/176402databases/gtksql invalid WWW o ports/176398[maintainer update] print/qpdf update to 4.0.1 o ports/176388devel/allegro update and maintainer change o ports/176387cad/electric-ng update and maintainer change f ports/176383sysutils/ipmitool cannot connect over SOL o ports/176382ports dependencies not being recorded o ports/176378[PATCH] Fix several typos in the ports tree o ports/176377New port: sysutils/cbsd Yet another FreeBSD Jail Manag o ports/176354[new port]: cad/logisim Design and simulate logic circ o ports/176352ports rebuilds unneeded packages o ports/176290Utilize sf.net CDN o ports/176249[NEW PORT] benchmarks/spp: Calculates round trip time o ports/176237[MAINTAINER UPDATE/REPOCOPY] textproc/apache-solr - t f ports/176223feature request - ports/net/quagga o ports/176195[PATCH] games/cre: Set NO_WRKSUBDIR and BUILD_WRKSRC i o ports/176180mail/mailman broken without NLS f ports/176178Implement upstream fix where multiple net/iaxmodem ins f ports/176172graphics/povray37: /usr/local/bin/ld: disp_sdl.o: unde o ports/176156Add multi-instance support to dns/nsd rc script o ports/176130New port: www/cakephp23 f ports/176106net-mgmt/collectd5 port update o ports/176103[MAINTAINER] devel/gdb: Adding an option to disable TU o ports/176096[NEW PORT] www/xibo-server: Xibo - Digital Signage (se o ports/176095[NEW PORT] www/zikula: MVC web application framework ( f ports/176080multimedia/xbmc uses external ffmpeg for part of build o ports/176044ports: print/ghostview (1.5_3) segfault/coredump f ports/176016devel/libftdi LIB_DEPENDS for boost_system.4, current f ports/176012irc/inspircd fails to detect OpenSSL in base running r o ports/176011[patch] update devel/boehm-gc from 7.1 to 7.2d f ports/175993new port net-mgmt/ostinato f ports/175987audio/clementine-player 1.1.0_1 - album art not displ f ports/175976[patch] Install desktop icon for games/boswars o ports/175947[NEW PORT] www/sogo: Groupware server with a focus on o ports/175946[NEW PORT] devel/sope: An extensive set of GNUstep web f ports/175944[PATCH] x11-wm/obmenu: OptionsNG, changed Makefile, De f ports/175936[NEW PORT] x11-wm/lxmed: LXDE Main Menu Editor f ports/175884deskutils/cairo-dock deskutils/cairo-dock-plugins Plea f ports/175879fail non-interactive installation sysutils/bsdstats f ports/175868security/nessus-libnasl: nasl_crypto.c:25:10: fatal er f ports/175813[patch] mail/dovecot2 doesn't detect libstemmer or ext f ports/175798FreeBSD 10 unable to build sysutils/fusefs-kmod f ports/175772Update to finance/php-tclink o ports/175748New port: www/your-freedom A SOCKS proxy application o ports/175744[MAINTAINER] sysutils/gigolo: [SUMMARIZE CHANGES] f ports/175733devel/libatomic_ops: Segmentation fault : install - o ports/175723postfix+dovecot+ldap_sasl marked BROKEN f ports/175656[patch] databases/sqlite3: update to 3.7.15.2 f ports/175621update net/dhcpcd o ports/175620New port: devel/bashdb, Bash debugger o ports/175612New port: devel/remake version of GNU make utility th f ports/175611sysutils/zfs-periodic package do not enable cron to ho f ports/175534[patch] net-mgmt/rackmonkey: Fix a redirect o ports/175527security/expiretable doesn't work in FreeBSD 9.x f ports/175523pkgng: mail/dovecot2-pigeonhole conflicts with mail/do f ports/175429audio/clementine-player: build error o ports/175385dns/fastresolve does not compile f ports/175373[patch] mail/getlive: need to update to latest CVS ver o ports/175337New port: devel/pecl-parsekit - static analysis f ports/175316multimedia/xbmc 12.0.rc3 build error f ports/175310[maintainer update] net-p2p/retroshare to 0.5.4d o ports/175308[NEW PORT]
pam_ssh_agent_auth: ENOENT
Am 20.02.2013 um 16:34 schrieb Kimmo Paasiala kpaas...@gmail.com: On Wed, Feb 6, 2013 at 12:28 AM, Stefan Bethke s...@lassitu.de wrote: I can confirm that with the new port version on a two day old current, the module doesn't work: $ uname -a FreeBSD freebsd-current.lassitu.de 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r246283: Sun Feb 3 16:55:16 CET 2013 r...@freebsd-current.lassitu.de:/usr/obj/usr/src/sys/GENERIC amd64 $ pkg info|grep pam pam_ssh_agent_auth-0.9.4 PAM module which permits authentication via ssh-agent $ sudo ls sudo: unable to initialize PAM: No error: 0 If I downgrade to the previous port version (and apply Kimmo's patch), it's working properly. Here's a slightly different error message on 9-stable: $ uname -a FreeBSD diesel.lassitu.de 9.1-STABLE FreeBSD 9.1-STABLE #7 r245996: Sun Jan 27 22:36:05 CET 2013 r...@diesel.lassitu.de:/usr/obj/usr/src/sys/DIESEL amd64 stb@diesel:~$ sudo ls sudo: unable to initialize PAM: No such file or directory Latest version pam_ssh_agent_auth-0.9.4_1 seems to finally work without any extra patches when built on a 9.1-RELEASE system. Hhm, with a 9.1-stable from this morning, I'm still getting ENOENT. Can you spot anything different in my setup? My /usr/local/etc/pam.d/sudo looks like this: # # PAM configuration for the sudo service # # auth authsufficient /usr/local/lib/pam_ssh_agent_auth.so file=~/.ssh/authorized_keys authinclude system # account account include system # session # XXX: pam_lastlog (used in system) causes users to appear as though # they are no longer logged in in system logs. session requiredpam_permit.so # password passwordinclude system /var/log/messages reports: Feb 25 17:41:01 lokschuppen sudo: in openpam_load_module(): no /usr/local/lib/pam_ssh_agent_auth found Feb 25 17:41:01 lokschuppen sudo: stb : unable to initialize PAM : No such file or directory ; TTY=pts/0 ; PWD=/root/eisenboot ; USER=root ; COMMAND=/bin/ls # ls -l /usr/local/lib/pam_ssh_agent_auth.so -rwxr-xr-x 1 root wheel 100194 Feb 25 08:48 /usr/local/lib/pam_ssh_agent_auth.so* # pkg_info|grep pam_ssh pam_ssh_agent_auth-0.9.4_1 PAM module which permits authentication via ssh-agent # ldd /usr/local/lib/pam_ssh_agent_auth.so /usr/local/lib/pam_ssh_agent_auth.so: libcrypto.so.6 = /lib/libcrypto.so.6 (0x801214000) libutil.so.9 = /lib/libutil.so.9 (0x8015bc000) libpam.so.5 = /usr/lib/libpam.so.5 (0x8017cf000) libcrypt.so.5 = /lib/libcrypt.so.5 (0x8019d7000) libc.so.7 = /lib/libc.so.7 (0x80081b000) What other reasons could PAM have to report ENOENT? This is the same configuration that used to work with the earlier version. Stefan -- Stefan Bethke s...@lassitu.de Fon +49 151 14070811 ___ 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
Would someone please commit ports/176156?
It was approved by the maintainer a week ago, but hasn't been committed yet. If someone would pick this one up soon it would be appreciated, 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: pam_ssh_agent_auth: ENOENT
On Mon, Feb 25, 2013 at 7:50 PM, Stefan Bethke s...@lassitu.de wrote: Am 20.02.2013 um 16:34 schrieb Kimmo Paasiala kpaas...@gmail.com: On Wed, Feb 6, 2013 at 12:28 AM, Stefan Bethke s...@lassitu.de wrote: I can confirm that with the new port version on a two day old current, the module doesn't work: $ uname -a FreeBSD freebsd-current.lassitu.de 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r246283: Sun Feb 3 16:55:16 CET 2013 r...@freebsd-current.lassitu.de:/usr/obj/usr/src/sys/GENERIC amd64 $ pkg info|grep pam pam_ssh_agent_auth-0.9.4 PAM module which permits authentication via ssh-agent $ sudo ls sudo: unable to initialize PAM: No error: 0 If I downgrade to the previous port version (and apply Kimmo's patch), it's working properly. Here's a slightly different error message on 9-stable: $ uname -a FreeBSD diesel.lassitu.de 9.1-STABLE FreeBSD 9.1-STABLE #7 r245996: Sun Jan 27 22:36:05 CET 2013 r...@diesel.lassitu.de:/usr/obj/usr/src/sys/DIESEL amd64 stb@diesel:~$ sudo ls sudo: unable to initialize PAM: No such file or directory Latest version pam_ssh_agent_auth-0.9.4_1 seems to finally work without any extra patches when built on a 9.1-RELEASE system. Hhm, with a 9.1-stable from this morning, I'm still getting ENOENT. Can you spot anything different in my setup? My /usr/local/etc/pam.d/sudo looks like this: # # PAM configuration for the sudo service # # auth authsufficient /usr/local/lib/pam_ssh_agent_auth.so file=~/.ssh/authorized_keys authinclude system # account account include system # session # XXX: pam_lastlog (used in system) causes users to appear as though # they are no longer logged in in system logs. session requiredpam_permit.so # password passwordinclude system /var/log/messages reports: Feb 25 17:41:01 lokschuppen sudo: in openpam_load_module(): no /usr/local/lib/pam_ssh_agent_auth found Feb 25 17:41:01 lokschuppen sudo: stb : unable to initialize PAM : No such file or directory ; TTY=pts/0 ; PWD=/root/eisenboot ; USER=root ; COMMAND=/bin/ls # ls -l /usr/local/lib/pam_ssh_agent_auth.so -rwxr-xr-x 1 root wheel 100194 Feb 25 08:48 /usr/local/lib/pam_ssh_agent_auth.so* # pkg_info|grep pam_ssh pam_ssh_agent_auth-0.9.4_1 PAM module which permits authentication via ssh-agent # ldd /usr/local/lib/pam_ssh_agent_auth.so /usr/local/lib/pam_ssh_agent_auth.so: libcrypto.so.6 = /lib/libcrypto.so.6 (0x801214000) libutil.so.9 = /lib/libutil.so.9 (0x8015bc000) libpam.so.5 = /usr/lib/libpam.so.5 (0x8017cf000) libcrypt.so.5 = /lib/libcrypt.so.5 (0x8019d7000) libc.so.7 = /lib/libc.so.7 (0x80081b000) What other reasons could PAM have to report ENOENT? This is the same configuration that used to work with the earlier version. Stefan -- Stefan Bethke s...@lassitu.de Fon +49 151 14070811 Looks like the port is still broken if compiled on a 9-STABLE system with new vis(3) functions included. Compiling it on a 9.1-RELEASE system produces a working package. I use devel/poudriere-devel for compiling packages and I didn't test the port by compiling it manually. -Kimmo ___ 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: PR stalled/timeout (was: ports/170632: devel/otrs: please update to current version)
On 2/25/2013 4:13 AM, Frank Wall wrote: Hi, would someone please takeover PR ports/170632? It's been open for 6 months now. The version in the ports collection is already 6 patchlevels behind the current version of OTRS. But it's not due to a lack of maintenance or contributions. Several people invested time, sent patches, posted build logs, wrote followups, but all work is lost, if no one actually commits the changes to the ports repository. Thank you for taking notice. Regards - Frank I have taken it. -- Regards, Bryan Drewery signature.asc Description: OpenPGP digital signature
Re: Would someone please commit ports/176156?
On Monday 25 February 2013 11:44:20 Darren Pilgrim wrote: It was approved by the maintainer a week ago, but hasn't been committed yet. If someone would pick this one up soon it would be appreciated, thanks. I got it and committed the patch. Beech ___ 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
Share /var/cache/pkg/ between machines
I'd like to share packages between a couple of nearly identical machines in a server farm. I think I have the following options: 1. Set up apache httpd on one primary machine to serve the packages to the others by pointing website root to to /var/cache/pkg/ and setting PACKAGESITE in the other servers. This looks like it might work except that repo.txz is missing from /var/cache/pkg/ 2. rsync /var/cache/pkg/ from the primary machine to the others. Set PACKAGESITE on all machines to point to some central repository where all these packages originally were built (we run poudriere in another location). 3. Something else How do other people cache/proxy built packages under pkgng? I don't want to have to pull the same 80Mb JDK package onto 10 machines across the internet. Thanks Ari -- -- Aristedes Maniatis ish http://www.ish.com.au Level 1, 30 Wilson Street Newtown 2042 Australia phone +61 2 9550 5001 fax +61 2 9550 4001 GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A ___ 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: PR stalled/timeout (was: ports/170632: devel/otrs: please update to current version)
On 2/25/2013 4:13 AM, Frank Wall wrote: Hi, would someone please takeover PR ports/170632? It's been open for 6 months now. The version in the ports collection is already 6 patchlevels behind the current version of OTRS. But it's not due to a lack of maintenance or contributions. Several people invested time, sent patches, posted build logs, wrote followups, but all work is lost, if no one actually commits the changes to the ports repository. Thank you for taking notice. Regards - Frank I have updated it to 3.1.13. -- Regards, Bryan Drewery bdrewery@freenode/EFNet signature.asc Description: OpenPGP digital signature
Re: Share /var/cache/pkg/ between machines
Just to add a 'something else', unsure how fully it may suffice... [details at the bottom] --- On Mon, 2/25/13, Aristedes Maniatis a...@ish.com.au wrote: From: Aristedes Maniatis a...@ish.com.au Subject: Share /var/cache/pkg/ between machines To: freebsd-ports@freebsd.org Date: Monday, February 25, 2013, 6:57 PM I'd like to share packages between a couple of nearly identical machines in a server farm. I think I have the following options: 1. Set up apache httpd on one primary machine to serve the packages to the others by pointing website root to to /var/cache/pkg/ and setting PACKAGESITE in the other servers. This looks like it might work except that repo.txz is missing from /var/cache/pkg/ 2. rsync /var/cache/pkg/ from the primary machine to the others. Set PACKAGESITE on all machines to point to some central repository where all these packages originally were built (we run poudriere in another location). 3. Something else How do other people cache/proxy built packages under pkgng? I don't want to have to pull the same 80Mb JDK package onto 10 machines across the internet. Thanks Ari -- -- Aristedes Maniatis portmaster? [Cannot directly answer the post question, but...] If you put /portmatster-download/ on /da0 (a thumbdrive) mount -t unionfs /dev/da0 /usr/ports/packages... then the thumbdrive packages will appear to be already downloaded to portmaster, for migrating between machines. [I set up an ftp server for similar functionality, but find this method quicker and reconfigurable. YMMV of course depending upon the number/physical placment of your servers] Sorry to not answer about /pkg/, not fully implemented on most machines, here. [portmaster -d -B -P -i -g category/port category/port... or scripted equivalent in pkg or shell syntax.] I've seen it handily upgrade thirty p5 ports at a stretch using a pipe... just because a thumbdrive was in place, where otherwise it would mean duplicate builds etc. J. Bouquet ___ 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: Share /var/cache/pkg/ between machines
You could put /var/cache/pkg on NFS, writable by all clients. However, my preference would be to put the pkg repo on NFS and not use cache at all. At the moment I clean out cache daily via periodic(8). -- James. ___ 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: Share /var/cache/pkg/ between machines
-Original Message- From: owner-freebsd-po...@freebsd.org [mailto:owner-freebsd-po...@freebsd.org] On Behalf Of Aristedes Maniatis Sent: Tuesday, 26 February 2013 1:58 PM To: freebsd-ports@freebsd.org Subject: Share /var/cache/pkg/ between machines I'd like to share packages between a couple of nearly identical machines in a server farm. I think I have the following options: 1. Set up apache httpd on one primary machine to serve the packages to the others by pointing website root to to /var/cache/pkg/ and setting PACKAGESITE in the other servers. This looks like it might work except that repo.txz is missing from /var/cache/pkg/ 2. rsync /var/cache/pkg/ from the primary machine to the others. Set PACKAGESITE on all machines to point to some central repository where all these packages originally were built (we run poudriere in another location). 3. Something else How do other people cache/proxy built packages under pkgng? I don't want to have to pull the same 80Mb JDK package onto 10 machines across the internet. Thanks Ari -- -- Aristedes Maniatis ish http://www.ish.com.au Level 1, 30 Wilson Street Newtown 2042 Australia phone +61 2 9550 5001 fax +61 2 9550 4001 GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A ___ 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 Ari, We've been doing 1. for a few years, including remote servers. The pkg_ suite suits our needs and will be retained until retired. To reduce package sizes, we remove content that isn't required, such as: doc, include files, examples, content of share etc. But this requires effort to get right and may not suit your needs. Portmaster maintains the ports collection. Regards, Dewayne. ___ 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: Share /var/cache/pkg/ between machines
I don't understand how do you imagine magical appearing 80 Mb JDK from any one place to other without pulling data from internet? :) In any case, with any kind of sharing you probably will have almost same traffic, maybe even greater than if you choose simple `pkg install` traffic. 1 - pointless, you can set up simple nginx, pointing to poudriere build packages directory and set up packagesite in /u/l/e/pkg.conf, without any proxy machine, which must download these cached packages in any case to be served by apache. AFAIK that machine will download something only while installing, right? So you overcomplicate your setup. 2. rsync will produce packagesize traffic + constant little more, due to checks of alteration. You'll lose in that case in long shot. My advice - put nginx to serve poudriere's built packages dir, and trust to xz compression level = easy to setup, not big traffic really. This is of course based on sentence ... onto 10 machines across the internet - if you have some clusters with PCs in some nets, then you could think about rsync with primary poudriere, to serve locally packages for few other PCs. Hope this help :) -- Regards, Alexander Yerenkow ___ 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: Share /var/cache/pkg/ between machines
On 26/02/13 5:22pm, Alexander Yerenkow wrote: I don't understand how do you imagine magical appearing 80 Mb JDK from any one place to other without pulling data from internet? :) In any case, with any kind of sharing you probably will have almost same traffic, maybe even greater than if you choose simple `pkg install` traffic. Perhaps I oversimplified our setup. Here is what we have: - pkg.office.example.com (poudriere): builds all packages (pkgng). Runs apache to serve repository to other servers. -- server1.office.example.com pulls files from build server (PACKAGESITE points to pkg.office.example.com) -- server2.office.example.com, etc.. as above office -- VPN tunnel -- colo (data centre) - pkg.colo.example.com also pulls files from build server (PACKAGESITE points to pkg.office.example.com) -- server[2-10].colo.example.com... rather than pull packages over the slow VPN tunnel, I want to pull them from pkg.colo.example.com Now, one approach is to rsync the poudriere output folder on pkg.office.example.com to pkg.colo.example.com. And given the complexity of other options, that's probably what I'll do. It means more network traffic than optimal, because poudriere will bulk many packages which aren't actually needed in the colo (and more often than the colo machines are actually updated as well since poudriere in the office might do a run twice a week, but the colo is updated once every 3 months or when there is a security patch we care about). So I was hoping to rely on pkg install to pull the package over the VPN network, and then replicate the data out to the other servers (NFS/rsync/etc) in the colo. Sorry for confusing you with my abbreviated problem description. Hopefully this is clearer. Ari 1 - pointless, you can set up simple nginx, pointing to poudriere build packages directory and set up packagesite in /u/l/e/pkg.conf, without any proxy machine, which must download these cached packages in any case to be served by apache. AFAIK that machine will download something only while installing, right? So you overcomplicate your setup. 2. rsync will produce packagesize traffic + constant little more, due to checks of alteration. You'll lose in that case in long shot. My advice - put nginx to serve poudriere's built packages dir, and trust to xz compression level = easy to setup, not big traffic really. This is of course based on sentence ... onto 10 machines across the internet - if you have some clusters with PCs in some nets, then you could think about rsync with primary poudriere, to serve locally packages for few other PCs. Hope this help :) -- Regards, Alexander Yerenkow -- -- Aristedes Maniatis ish http://www.ish.com.au Level 1, 30 Wilson Street Newtown 2042 Australia phone +61 2 9550 5001 fax +61 2 9550 4001 GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A ___ 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
