Re: net-im/prosody post install error
On Mon, Mar 31, 2014 at 4:13 PM, Ross Penner ro...@f-m.fm wrote: On Sat, 15 Mar 2014, at 08:47 AM, Scot Hetzel wrote: On Fri, Mar 14, 2014 at 9:55 PM, Ross Penner ro...@f-m.fm wrote: When I try to build prosody (on FreeBSD 9.2-RELEASE-p3), I get the following error once it gets to the installation phase. The error references already having a prosody user and group. They were created the first time I tried to install and this message is from my second attempt. === Installing for prosody-0.9.3 /bin/sh /usr/ports/net-im/prosody/work/pkg-install prosody-0.9.3 PRE-INSTALL prosody:*:242: You already have a group prosody, so I will use it. pw: user 'prosody' already exists Adding user prosody failed... *** [pre-install] Error code 1 Thanks for any help or insight you can provide. The pkg-install script should be detecting the user, what does the following command show? /usr/sbin/pw user show prosody ; echo $? On my system with no prosody user it returns with: pw: no such user `prosody` 67 It should return with a value of zero, when the port is installed: # /usr/sbin/pw user show prosody ; echo $? prosody:*:242:1::0:0:Prosody XMMP Server:/nonexistent:/usr/sbin/nologin 0 I have tried installing/deinstalling/re-installing the port, and don't get the prosody user already exists error. ok, so I run /usr/sbin/pw user show prosody ; echo $? and I get the same error you do on your system with no user. When I look at /etc/passwd, the prosody user is there: prosody:*:242:1:Prosody XMPP Server:/nonexistent:/usr/sbin/nologin Also, when I try to remove the prosody user, it fails: # pw userdel -n prosody pw: no such user `prosody' Is the prosody user in /etc/master.passwd? Try running: /usr/sbin/pwd_mkdb -p /etc/master.passwd to re-create the password databases and /etc/passwd. Note: - make backups of /etc/passwd, /etc/spwd.db and /etc/pwd.db - make sure that all of your users are in /etc/master.passwd -- 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
FreeBSD Port: py27-unidecode-0.04.14
من جهاز الـ iPhone الخاص بي ___ 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 +-+ security/i2p| 0.9.11 | 0.9.12 +-+ 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: net-im/prosody post install error
On Mon, 31 Mar 2014, at 10:35 PM, Scot Hetzel wrote: Is the prosody user in /etc/master.passwd? Yes Try running: /usr/sbin/pwd_mkdb -p /etc/master.passwd to re-create the password databases and /etc/passwd. Note: - make backups of /etc/passwd, /etc/spwd.db and /etc/pwd.db - make sure that all of your users are in /etc/master.passwd That seemed to have fixed the issue! I installed prosody now with no problems. Thanks for your help. It is greatly appreciated. ___ 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
Updating less-than-everything with poudriere pkgng
Poudriere and pkgng have been great tools for managing large numbers of FreeBSD ports. However, we would like to optimize the build in some cases. Consider a poudriere-generated pkgng repository with about 10,000 packages in it. Now, just because the FreeBSD ports collection is the way it is, about 8,000 of those packages are going to depend directly or indirectly on perl. Now suppose one of those 10,000 packages is foobar-1.2.2. A security advisory is released, and it is now urgent to upgrade all the machines using this repository to foobar-1.2.3 ASAP. But foobar-1.2.3 (like 7,999 of its brethren) depends on perl, and perl has also been updated from perl-5.12.3.4_5a to 5.12.3.4_5a1. What we want is to do a poudriere build that updates to foobar-1.2.3 and rebuild anything that depends on foobar. But the first thing poudriere is going to do is whack perl-5.12.3.4_5a and all 8000 packages that depend on it. This is a problem for two reasons. First, this takes at least a day to build, during which time foobar-1.2.2 is out there waiting to be exploited. (Alternatively you can try to build less than the full set to get it done quicker, but this introduces its own set of problems; packages that didn't get rebuilt may stop working.) Second, it's virtually a guarantee that hidden somewhere in those 8000 packages is an update that breaks something for somebody using that repository. So poudriere creates this situation where to get any security update, you have to take every other unrelated update, even if they are very bad for you. Is there any way to either: - Convince poudriere only to build a specific port and its dependents, or - Build port(s) outside of poudriere and then inject them into the pkgng repo maintained by poudriere? For example, if there were some way we could manually delete what we want rebuilt and tell poudriere to rebuild only the missing, not the outdated, that would be great. (It would be *ideal* if we could just delete the target package and poudriere would take care of deleting its dependents.) Thanks for any advice! ___ 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: Updating less-than-everything with poudriere pkgng
On 04/01/14 16:18, J David wrote: Consider a poudriere-generated pkgng repository with about 10,000 packages in it. Now, just because the FreeBSD ports collection is the way it is, about 8,000 of those packages are going to depend directly or indirectly on perl. Now suppose one of those 10,000 packages is foobar-1.2.2. A security advisory is released, and it is now urgent to upgrade all the machines using this repository to foobar-1.2.3 ASAP. But foobar-1.2.3 (like 7,999 of its brethren) depends on perl, and perl has also been updated from perl-5.12.3.4_5a to 5.12.3.4_5a1. What we want is to do a poudriere build that updates to foobar-1.2.3 and rebuild anything that depends on foobar. But the first thing poudriere is going to do is whack perl-5.12.3.4_5a and all 8000 packages that depend on it. This is why the quarterly branches exist. 2014Q1 (Just EoL'd) and 2014Q2 (just branched from head) will now get only security and port-fix type upgrades for the next 3 months. Therefore if your poudriere repo had been tracking 2014Q1 it would probably not have had those perl updates to deal with, but it would have had foobar-1.2.3 security fixes. Of course, right about now, you get to have an upgrade frenzy applying 3 months worth of changes in one fell swoop, as there's the switchover from 2014Q1 to 2014Q2 happening right now. There's no way I know of to use poudriere to selectively update just packages from the dependency tree involving foobar but not ones involving perl. So, yes, you'll end up with your package builder doing a lot of building, and you will have a window of exposure while that is happening. About the only way I can think of to achieve that is to apply selective updates to your ports tree that you have checked out of SVN, which is a pain in the posterior and not always guarranteed to work properly. Cheers, Matthew signature.asc Description: OpenPGP digital signature
Re: Updating less-than-everything with poudriere pkgng
01.04.2014 19:18, J David пишет: - Build port(s) outside of poudriere and then inject them into the pkgng repo maintained by poudriere? I'd go this way: 1. Update/install the latest portstree at one system that uses your custom packages. 2. Build/install/package a new version of the needed port using port's infrastructure. 3. Copy the new package to your distributing server. 4. Use PKG-REPO(8) to create a package repository catalog. -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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 Port: www/tomcat-native
Hello,
It looks like the recent update of apr has broken this port. However
there is a simple fix.
LIB_DEPENDS=libapr-1.so.4:${PORTSDIR}/devel/apr1
needs to be changed to
LIB_DEPENDS=libapr-1.so.5:${PORTSDIR}/devel/apr1
Or perhaps its better not to specify the exact library version.
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: LPPL10 license consequences intended? (arabic/arabtex)
I just wanted to express my general concerns, since in past I was also making posts in the tone of the OP, and I wanted people to speak up so badly, I decided not to remain silent this time, even if the original problem is not really on my playground. I would also like to see portmgr actively participating in the discussions, leading by example and well, basically, leading and managing. If portmgr cant react on high number of port related PR's and the time it takes to handle them, ports quality, license framework, then... what actually portmgr can do and what's its point? I am aware we're all volunteers, but at the end, we've volunteered to certain duties, as maintainers, commiters and portmgr's, havent we? Even more, few people volunteered on multiple discussions in past, that they'd love to help with certain duties, and, well, they've been ignored. That really makes me wonder if anyone is actually in charge, has ideas, power and will to implement those, 'right' to make decisions, or are we just drifting in random directions depending on who takes what action and who does (or not) replies to stop them or not? Regards, BL On Sat, Mar 29, 2014 at 4:35 PM, Mark Linimon lini...@lonesome.com wrote: On Sat, Mar 29, 2014 at 11:34:29AM +0100, John Marino wrote: Don't dish it out if you don't want a response. The fact that you want to put it in these terms tells me everything I need to know. mcl ___ 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
[QAT] 349891: 4x leftovers
Bring back from the dead; take ownership Distfile is hosted in my public_distfiles - Build ID: 20140401211601-45638 Job owner: f...@freebsd.org Buildtime: 13 minutes Enddate: Tue, 01 Apr 2014 21:28:34 GMT Revision: 349891 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=349891 - Port:security/amavis-stats 0.1.12_3 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~f...@freebsd.org/20140401211601-45638-311430/amavis-stats-0.1.12_3.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~f...@freebsd.org/20140401211601-45638-311431/amavis-stats-0.1.12_3.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~f...@freebsd.org/20140401211601-45638-311432/amavis-stats-0.1.12_3.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~f...@freebsd.org/20140401211601-45638-311433/amavis-stats-0.1.12_3.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140401211601-45638 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: editors/lazarus-lcl-units Not installed/updated on 10-stable amd64
There was an PR about this: ports/187961 While there's no discussion on thisthe gist is that there were stray files left behind by the previous version that was confusing the build. And, that removing the .lazarus directory from the port builder's home directory would make it work (IE: /root/.lazarus) And, that the port is now more aggressive on uninstalling, so this problem shouldn't happen anymore. On 03/28/14 01:21, Alex V. Petrov wrote: There are solutions? Hint: Start of reading config file /usr/local/etc/fpc.cfg Hint: End of reading config file /usr/local/etc/fpc.cfg Free Pascal Compiler version 2.6.4 [2014/03/26] for x86_64 Copyright (c) 1993-2014 by Florian Klaempfl and others Target OS: FreeBSD for x86-64 Compiling lazcontrols.pas Compiling dividerbevel.pas dividerbevel.pas(19,12) Fatal: Can't find unit LResources used by DividerBevel Fatal: Compilation aborted gmake[1]: *** [lazcontrols.ppu] Ошибка 1 gmake[1]: Выход из каталога `/usr/ports/editors/lazarus-lcl- units/work/lazarus/components/lazcontrols' *** Error code 2 Stop. make: stopped in /usr/ports/editors/lazarus-lcl-units -- Who: Lawrence K. Chen, P.Eng. - W0LKC - Sr. Unix Systems Administrator For: Enterprise Server Technologies (EST) -- SafeZone Ally ___ 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
