Re: pkg 1.4 freeze please test test test!
On Tue, Oct 28, 2014 at 4:19 PM, Baptiste Daroussin b...@freebsd.org wrote: - new 3 way merge code (stolen from the fossil-scm) to allow automerging configuration files - new @config keyword to mark a file as a config file (during upgrade/reinstallation it will try to merge the configuration with the one the user may have modified) an option AUTOMERGE is available to prevent automerging if automerge fails a .pkgnew file will be created along with the untouched user version of the configuration Would it make sense to let the user specify the merge tool to use and always use it, instead of having to support the merge code within pkg? Anton ___ 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: pkg 1.4 freeze please test test test!
On Wed, Oct 29, 2014 at 1:08 PM, Baptiste Daroussin b...@freebsd.org wrote: On Wed, Oct 29, 2014 at 01:05:49PM -0700, Anton Afanasyev wrote: On Tue, Oct 28, 2014 at 4:19 PM, Baptiste Daroussin b...@freebsd.org wrote: - new 3 way merge code (stolen from the fossil-scm) to allow automerging configuration files - new @config keyword to mark a file as a config file (during upgrade/reinstallation it will try to merge the configuration with the one the user may have modified) an option AUTOMERGE is available to prevent automerging if automerge fails a .pkgnew file will be created along with the untouched user version of the configuration Would it make sense to let the user specify the merge tool to use and always use it, instead of having to support the merge code within pkg? That will defeat cross installation/upgrades (install arm package in an arm chroot) but yes allowing a users to define their own merge tool in general instead of the internal one could make sense. regards, Bapt I (and this is just a personal opinion of one man, of course) find it better to be explicitly told that this default config file has changed and you need to review it and merge with your local changed copy, even if you didn't make any drastic changes to your version, as opposed to by the way, we merged a new version of this config file with your changes, as that forces one to know what and why has changed. I've already lost a config file for one of my ports (squid, the last 2.something version) due to it getting overwritten with the default, so wouldn't want anything like that to happen again (and yes, I know, I must have backups; but that's not the point here). If auto-merging is going to stay, an option to turn it off and always use a merge tool or perform the merge manually would be appreciated. Anton ___ 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: poudriere and local patches to ports
On Wed, Jun 11, 2014 at 11:04 AM, G. Paul Ziemba pz-freebsd-po...@ziemba.us wrote: Disclaimer: I set up my poudriere environment almost a year ago, so there could be new poudriere features to address this issue that I'm not aware of. NOTE: I have not tested the method I describe, but I've exercised this idea mentally for a while. If you do end up taking this approach, I would appreciate it if you let me know how it worked out for you. Poudriere supports updating its ports tree via alternative methods, namely git and svn. You could thus set up a clone of FreeBSD's ports repository that gets refreshed periodically (a simple script) and to which you would also commit your own patches. This also has the added benefit of making the history of all your patches' changes easily available. Anton ___ 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 vs. portupgrade reporting ports outdated
On Fri, Apr 4, 2014 at 4:44 PM, sindrome sindr...@gmail.com wrote: Here's more information foo:107:/home/foobar# pkg update Updating repository catalogue foo:108:/home/foobar# pkg upgrade Updating repository catalogue Nothing to do Now when I do a 'pkg_version -v|grep needs' I have pkg_* tools use the old packages database, while the pkg tool uses its own, new, database. After you upgraded to pkgng and started using it for all your package needs, your old database stopped being updated (because the old pkg_* tools aren't being used to install packages anymore). This is why the old pkg_* tools are still reporting old version information - they only see what's in their old database. Anton ___ 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: Port Request: Mono Moonlight
On Thu, Mar 20, 2014 at 4:32 AM, Paul Pathiakis pathia...@yahoo.com wrote: I'd like to see moonlight ported to FreeBSD. It's software to allow the use of Microsoft Silverlight. It would be very useful to allow streaming of Netflix videos (Silverlight format) to a FreeBSD desktop. I'm not sure if the latest version of Moonlight is good enough to support Netflix as I have not used it for this purpose. However, Moonlight development is dead, and Silverlight itself seems to be just as dead. (at least some of) Our Linux brethren are using Pipelight, e.g. see here: https://wiki.archlinux.org/index.php/Pipelight. I think porting Pipelight would be more beneficial than reviving Moonlight, as it, at the very least, would provide full Silverlight functionality instead of the subset offered by Moonlight. Anton ___ 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: Samba to web
I was thinking more about some kind of web interface and I came up with some search results: _ smb2www was in the port tree, but removed a couple of years ago; maybe I could try to download and hack it; _ there's SMB Web Client (http://sourceforge.net/projects/smbwebclient/) _ Davenport (which brings WebDav in), _ Others? Before I start digging them all, has anyone faced this task before? Any hint? Why not simply set up a web server with the same auth settings as in Samba? Granted, this isn't exactly what you wanted, and you may end up having to maintain two sets of settings, but that could be a smaller investment than setting up something like one of the above. That said, if you do end up using one of the solutions you mentioned (or similar), it would be great if you could provide some details (perf, your number of users, typical load, etc). Anton ___ 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: devel/py-mercurialserver broken by last commit
I've run into this problem too.
Michael, while I haven't tried your patch yet, I'm curious to know why you
added the extra line to post-install? I couldn't find any place where a
similar one may have been removed, so just interested to know why it needed
to be added.
You may also want to submit a PR to have your patch noticed quicker:
http://www.freebsd.org/support.html
On Thu, Jan 2, 2014 at 7:29 AM, Michael Vorobyov mic6...@gmail.com wrote:
Good day and happy New Year )
The last commit into devel/py-mercurialserver (rev. 337698) broke it.
Buildlog tail:
===
changing mode of build/scripts-2.7/refresh-auth from 644 to 755
=== Staging for py27-mercurialserver-1.2.0
=== py27-mercurialserver-1.2.0 depends on executable: hg - found
=== py27-mercurialserver-1.2.0 depends on file: /usr/local/bin/python2.7
- found
** Missing /usr/ports/devel/py-mercurialserver/files/pkg-message.in for
py27-mercurialserver-1.2.0.
*** [apply-slist] Error code 1
Stop in /usr/ports/devel/py-mercurialserver.
===
I suggest next patch (tested in tinderbox):
--- Makefile.orig 2013-12-27 18:34:14.0 +0800
+++ Makefile2014-01-02 23:08:47.0 +0800
@@ -24,10 +24,8 @@
USERS= ${HGUSER}
GROUPS=${HGGROUP}
-SUB_FILES= pkg-message
SUB_LIST= PORTNAME=${PORTNAME} \
HGUSER=${HGUSER}
-PKGMESSAGE=${WRKDIR}/pkg-message
USE_PYTHON=yes
USE_PYDISTUTILS=yes
@@ -41,6 +39,7 @@
${SED} -I .orig -e
s#/etc/mercurial-server/#${PREFIX}/etc/${PORTNAME}/#
${WRKSRC}/src/init/dot-mercurial-server
post-install:
+ ${MKDIR} ${STAGEDIR}${PREFIX}/hg
${MKDIR} ${STAGEDIR}${PREFIX}/etc/${PORTNAME}/remote-hgrc.d
${MKDIR} ${STAGEDIR}${PREFIX}/etc/${PORTNAME}/keys/users
${MKDIR} ${STAGEDIR}${PREFIX}/etc/${PORTNAME}/keys/root
___
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 Port: py27-pytz-2013.8,1
On Thu, Nov 28, 2013 at 12:57 PM, Nicola Vitale ni...@freebsd.org wrote: That confirms what said by Li-Wen: there's something wrong with the installation of devel/py-distribute on your system. I was running into the same issue as Fabien, and I noticed that deve/py-distribute is deprecated in favor of devel/py-setuptools. My best guess is that the latter has a different set of options than the former, but this is just a guess. That said, it looks like everything compiles and installs fine today (November 29), even with staging turned on, so I think this must've been corrected somewhere in the Python-related part of the ports framework. Anton ___ 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: Upgrading Perl... Somebody just shoot me and put me out of my misery!
On Sat, Nov 23, 2013 at 12:17 PM, Ronald F. Guilmette r...@tristatelogic.com wrote: OK, but please help me understand here. What is it, exactly, that is _now_ being threaded, that wasn't threaded before? ... (Part of what is confusing about this is that I was under the impression... perhaps naive... that Perl was already set up for threads support quite some long time ago.) Perl _was_ set up to be threaded (although I have no idea what is actually threaded there), but the port option to enable it being threaded was not enabled by default. The implication is that if you compiled it with default options, it wasn't threaded. But now it (the option) has been changed to be enabled by default, and so the point of that UPDATING entry was that if you are running with default options, then your Perl will switch from non-threaded to threaded when you recompile it, and you will thus need to recompile all ports that depend on Perl. IF you already had this option enabled to begin with, I believe you don't need to recompile and reinstall anything (including Perl itself, but do note that the ports system will then keep thinking that Perl hasn't been upgraded - which isn't an issue, since the only thing changed here is the defaults and not any functionality, and so you can just wait to recompile it when something more serious changes; this is up to you though). Hope this clears it up a bit. Anton ___ 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: bsdadminscripts and pkng
Real bumps when converted to pkgng was: - portmaster cannot use packages for dependencies- huge let down This one is a big issue for me as well. I usually compile my own, but let portmaster install build-time dependencies from packages. No pkgng support means it has to recompile everything, AND it then doesn't uninstall those build-time deps, despite my supplying it the option to do so. I've started looking at portmaster source to see if this could be solved quickly, but I'm still trying to wrap my head around the code, so it would be great if it turned out that someone somewhere has done this already. ___ 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 or packages?
Speaking of using portmaster with PKGNG, any idea if PKGNG support for the --packages-build portmaster option is in the works somewhere? I couldn't find anything, but maybe I didn't look hard enough. Thanks, Anton On Sun, Aug 11, 2013 at 5:26 PM, Janky Jay jan...@unfs.us wrote: Hello, On 08/11/2013 06:24 PM, Mehmet Erol Sanliturk wrote: On Sun, Aug 11, 2013 at 7:15 PM, Stan Gammons s_gamm...@charter.net wrote: On Aug 11, 2013, at 4:23 PM, Mehmet Erol Sanliturk m.e.sanlit...@gmail.com wrote: On Sun, Aug 11, 2013 at 4:59 PM, Stan Gammons s_gamm...@charter.net wrote: I know the binary packages were taken down after the security incident a while back. Are many/any binary packages available now or does one still have to build most everything from ports? If binary packages are available now, what is the URL to the repository? Stan ___ http://www.freebsd.org/ports/index.html ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/ ftp://ftp1.freebsd.org/pub/FreeBSD/ports/amd64/ ftp://ftp2.freebsd.org/pub/FreeBSD/ports/amd64/ Assuming one has converted to the new packagement tool and added WITH_PKGNG=yes to /etc/make.conf, one could use the links for packagesite in pkg.conf to install binary packages with pkg? Can one have multiple packagesite statements in pkg.conf? I see the repositories don't have the latest versions, so portupgrade or portmaster would be needed to upgrade to the latest versions from ports? If so, can one mix and match pkg and portupgrade or portmaster or is that asking for trouble? i.e. use pkg to install packages and portupgrade or portmaster to upgrade packages. Stan The above links are NOT containing new pkgng kind packages yet . For pkgng compatible packages , you may see the following pages : http://www.exonetric.com/ http://mirror.exonetric.net/pub/pkgng/ http://mirror.exonetric.net/pub/pkgng/freebsd%3A10%3Ax86%3A64/2013-02-09/All/ Thank you very much . Mehmet Erol Sanliturk I +1 this. Also, regarding your question about mixing packages (PNGNG) and ports is just fine. I use PKGNG and portmaster all the time and they work fine together. I can't speak for portupgrade, though. Regards, Janky Jay, III ___ 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: Why was the ventrilo-server port removed?
On Wed, Jun 5, 2013 at 5:25 AM, Bob Willcox b...@immure.com wrote: I'd be willing to. I don't think anything for it has changed. The distfile is still available at the same location. I still run it and don't see any issues with it. It looks like the port was deprecated because no more public distfiles: http://portsmon.freebsd.org/portoverview.py?category=audioportname=ventrilo-server Anton ___ 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: Dropbox on FreeBSD
On Tue, Mar 5, 2013 at 5:16 PM, Erik Zoltan erikzol...@gmail.com wrote: [...] I'm currently looking for a good alternative [...] http://owncloud.org/ self-hosted on a server somewhere with a fast connection and enough bandwidth? Anton ___ 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: Quick status update on Squid 3.x ports
On Thu, Sep 27, 2012 at 12:07 AM, Ruslan Mahmatkhanov cvs-...@yandex.ruwrote: First thank you for working on this. According to squid web-page, 3.2 is the only stable version (Current versions suitable for production use.), that is actively maintained. 3.1 and less are listed in Old versions - Provided for archival purposes only. Not intended for general use in new installations. Is there still 2.7 users?! As for me, 3.2 should go to www/squid and some kind of exp-run should be done to make sure the ports depending on it builds fine. There are bound to be at least some 2.7 users who are waiting for all 2.7's features to be implemented in the 3.x branch. e.g. an equivalent of url_rewrite_program doesn't exist in pre-3.2. Anton ___ 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
