latest freebsd:11:x86:64 repo and ruby 1.9 - 2.0
$ pkg upgrade
Updating FreeBSD repository catalogue...
FreeBSD repository is up-to-date.
Updating poudriere repository catalogue...
poudriere repository is up-to-date.
All repositories are up-to-date.
Checking for upgrades (24 candidates): 100%
Checking integrity... done (1 conflicting)
Checking integrity... done (0 conflicting)
The following 24 packages will be affected (of 0 checked):
First, a minor nit: of 0 checked?
Installed packages to be REMOVED:
ruby-1.9.3.547_3,1
porttools-1.02
newfile-1.0.14_4
hub-1.12.2
libchk-1.10.3
zfs-snapshot-mgmt-20090201_2
Then the real problem, I do not want these packages to be removed except for
ruby-1.9.3.547_3,1. In other words, I want to keep using zfs-snapshot-mgmt,
libchk, hub and porttools. What should I do?
BTW, the updating entry for ruby says If you use pkgng, simply upgrade.
New packages to be INSTALLED:
ruby: 2.0.0.576_1,1 [FreeBSD]
Installed packages to be UPGRADED:
zsh: 5.0.6_2 - 5.0.7 [FreeBSD]
libgpg-error: 1.15 - 1.16 [FreeBSD]
p11-kit: 0.20.3_1 - 0.22.1 [FreeBSD]
ImageMagick: 6.8.9.8_1,1 - 6.8.9.8_2,1 [FreeBSD]
hplip: 3.14.4_3 - 3.14.4_4 [FreeBSD]
mediastreamer: 2.10.0_5 - 2.10.0_6 [FreeBSD]
curl: 7.38.0_1 - 7.38.0_2 [FreeBSD]
GeoIP: 1.6.2_1 - 1.6.2_2 [FreeBSD]
portlint: 2.15.4 - 2.15.6 [FreeBSD]
apache22: 2.2.29_1 - 2.2.29_2 [FreeBSD]
chromium: 37.0.2062.124_1 - 38.0.2125.101_1 [FreeBSD]
libmodplug: 0.8.8.5_1 - 0.8.8.5_2 [FreeBSD]
syslinux: 6.02 - 6.02_1 [FreeBSD]
gmake: 3.82_2 - 4.1 [FreeBSD]
tbb: 4.3.0 - 4.3.0_1 [FreeBSD]
mk-configure: 0.27.0 - 0.28.0 [FreeBSD]
Installed packages to be REINSTALLED:
vim-7.4.430_2 [FreeBSD] (needed shared library changed)
The process will require 20 MB more space.
Proceed with this action? [y/N]:
And my pkg configuration:
Version : 1.3.8
PKG_DBDIR = /usr/local/var/db/pkg;
PKG_CACHEDIR = /var/cache/pkg;
PORTSDIR = /usr/ports;
INDEXDIR = ;
INDEXFILE = INDEX-11;
HANDLE_RC_SCRIPTS = false;
ASSUME_ALWAYS_YES = false;
REPOS_DIR [
/etc/pkg/,
/usr/local/etc/pkg/repos/,
]
PLIST_KEYWORDS_DIR = ;
SYSLOG = false;
ABI = freebsd:11:x86:64;
DEVELOPER_MODE = false;
VULNXML_SITE = http://www.vuxml.org/freebsd/vuln.xml.bz2;;
FETCH_RETRY = 3;
PKG_PLUGINS_DIR = /usr/local/lib/pkg/;
PKG_ENABLE_PLUGINS = true;
PLUGINS [
]
DEBUG_SCRIPTS = false;
PLUGINS_CONF_DIR = /usr/local/etc/pkg/;
PERMISSIVE = false;
REPO_AUTOUPDATE = true;
NAMESERVER = ;
EVENT_PIPE = ;
FETCH_TIMEOUT = 30;
UNSET_TIMESTAMP = false;
SSH_RESTRICT_DIR = ;
PKG_ENV {
}
PKG_SSH_ARGS = ;
DEBUG_LEVEL = 0;
ALIAS {
}
CUDF_SOLVER = ;
SAT_SOLVER = ;
RUN_SCRIPTS = true;
CASE_SENSITIVE_MATCH = false;
LOCK_WAIT = 1;
LOCK_RETRIES = 5;
SQLITE_PROFILE = false;
WORKERS_COUNT = 0;
READ_LOCK = false;
PLIST_ACCEPT_DIRECTORIES = false;
IP_VERSION = 0;
Repositories:
FreeBSD: {
url : pkg+http://pkg.FreeBSD.org/freebsd:11:x86:64/latest;,
enabled : yes,
mirror_type : SRV,
signature_type : FINGERPRINTS,
fingerprints: /usr/share/keys/pkg
}
poudriere: {
url :
file:///usr/local/poudriere/data/packages/basejail-default,
enabled : yes
}
--
Andriy Gapon
___
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 +-+ textproc/py-jaxml | 3.02| 16.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 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: postgresql-server depends on client. Why?
On Oct 17, 2014, at 10:44 AM, Palle Girgensohn gir...@pingpong.net wrote: Thing is, we install header files and man pages in the client only, if memory serves me right. Also, tools like createdb are in the client package. So, apart from the obvious I want to upgrade the client separately (before) the server, there are no arguments for not doing it the way we do it now. But maybe that argument is enough to motivate a change? “want” is not part of the issue. Upgrading the client before upgrading the server is standard procedure as documented by the PostgreSQL project. Palle 17 okt 2014 kl. 16:40 skrev Olli Hauer oha...@gmx.de: In case the dependency on thr client will be removed all ports depending on the server alone at the moment should be checked if they also require the client part. Additional clients should not define a conflict with server versions client version -- Sent from my Android phone with GMX Mail. Please excuse my brevity. Chris Rees cr...@physics.org wrote: Hi Dan, http://svnweb.freebsd.org/ports/head/databases/postgresql90-server/Makefile?revision=286930view=markup#l64 It was always supposed to be the case, however I agree that it's probably not necessary. Anyone mind if it doesn't depend? Chris On 17 October 2014 15:12:51 BST, Dan Langille d...@langille.org wrote: Why is postgresql-server dependent upon postgresql-client? This wasn’t the case in the past and seems to be the case not. Not all server installations need the client. In addition, upgrading the client before upgrading the server is standard procedure: http://www.postgresql.org/docs/9.3/static/upgrading.html i.e. upgrade the client, pg_dump using the new client, then upgrade server, pg_restore. Thanks — Dan Langille -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ 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 — Dan Langille signature.asc Description: Message signed with OpenPGP using GPGMail
Patching a Java package substituting a precompiled class
Hi, I’m trying to fix a Java port (logstash) that's crashing in FreeBSD because of a bug in a Java class in a JAR that's included as a dependency. Three different persons, included I, have submitted a PR upstream (you can see mine here: https://github.com/jnr/jnr-ffi/pull/26) but the activity in that project is pretty slow and nobody has taken action yet. Now, this issue is blocking the port update in FreeBSD and since I'm not confident upstream is going to answer quickly, I thought about updating the port so that it patches the binary distribution. Fortunately, the offending class is just one so that the patching process may be as simple as this: * Download the binary distribution. * Extract it to the working directory. * Copy the library containing the offending class to a temporary directory. * Extract the JAR. * Substitute the offending class with the patched class. * Recreate the JAR. * Copy the update library to the working directory. The patched class could be distributed as a binary file belonging to the port itself. I'm not sure this approach fits the FreeBSD port philosophy, but on the other hand we could leverage the Java platform independence to simplify a great deal the patch phase of the port: after all, this is a no-build port. Otherwise, the port should grab the sources of the dependent library, building them, and then use the compiled class to perform the aforementioned changes. Since this library (jnr-ffi) is a Maven project, building it would require Maven as a dependency, and during the build Maven would fetch quite a lot of dependencies to perform its job. If I should give somebody a solution, I'm not sure I'd choose the latter. Would you please share your thoughts about this issue? Any feedback and suggestions are greatly appreciated. Regards, -- Enrico smime.p7s Description: S/MIME cryptographic signature
Re: Patching a Java package substituting a precompiled class
On Sat, Oct 18, 2014 at 1:07 PM, Enrico Maria Crisostomo enrico.m.crisost...@gmail.com wrote: Hi, I'm trying to fix a Java port (logstash) that's crashing in FreeBSD because of a bug in a Java class in a JAR that's included as a dependency. Three different persons, included I, have submitted a PR upstream (you can see mine here: https://github.com/jnr/jnr-ffi/pull/26) but the activity in that project is pretty slow and nobody has taken action yet. Thanks for doing that. I lot of people in the Java world don't care much about FreeBSD, so this process can be painful. There is another option that you may wish to consider. (1) Take your https://github.com/emcrisostomo/jnr-ffi/ fork on github. (2) Make a release of the jnr package and put it at https://github.com/emcrisostomo/jnr-ffi/releases/ (3) Change the FreeBSD port to use your version of jnr (4) When the upstream version of jnr changes to accept your patch, delete your fork, and change the port back to using the original jnr. Thanks for doing this. It takes some pushing but eventually upstream will take our patches. I did the same thing for https://github.com/jenkinsci/jenkins/pull/1387 and Jenkins. -- Craig ___ 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
