Search results

I posted PR instead, as I'm a bit slow getting used to GitHub: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199460

Addition: when I mount the directory via NFS and perform the upgrade using "url: file://NFSMOUNT" the upgrade works. It seems as though there is something odd with the SSH-access

I installed the new pkg-1.5.0 this morning, and after this my updates all fail when done via SSH My REPO.conf: REPO: { url: ssh://$USER@$REPOHOST:/usr/local/poudriere/data/packages/release101amd64-default, mirror_type: "NONE", enabled: yes } The error message...

The easiest way of doing this would still be to modify the existing port. Just change the parts that are relevant to the version, and then check if it builds. Usually changing a port from one minor version to the next isn't a huge work, in any case it is much less error prone than trying to...

While it is something completely different than RStudio, perhaps Pandas for python http://pandas.pydata.org/ might be an alternative.

I ran into this today as well. Upgraded from 9.2 to 10.1-RELEASE. Solved it by reextracting base.txz. Would really have been nice to know what went wrong.

I'll give those things a try when I get time. It seems like they could work.

It does do the "right thing(tm)" if it is run from a port, and yes, it basically just copies files. I tried the cd ${WRKSRC} thing, but it didn't work, the install script has an internal variable for where it installs to, I would need to adjust that one.

I was afraid that that might be the best solution. Now I have to learn enough Ruby to manage that.

I am in the process of attempting to create a new port. So far so good. However I get stuck at the following problem: the install process has an install script, located in ${SOMEDIR}/bin/install, which when called references ${SOMEDIR}/config.file in order to determine the path to install it to...

I love the new pkg. All the ports I need with different options just get built using poudriere, and then I am a happy camper. Actually being able to replace the whole version of, say php53 to php55, in one step is fantastic.

Nope, nothing wierd in my /etc/nsswitch.conf, just the standard settings there. Yep, I found that out when I tried it. My copy is in a svn-repository, which gets checked out by portshaker, and is then copied into the poudriere ports tree. This method is not the problem. I do the same for...

The port is obviously not in the ports-tree, that is why I am attempting to port it. I use portshaker to feed it into my poudriere build, which works wonderfully for other ports where I want to do some local patching. I might give it a try with NO_STAGE though, see if that makes a difference.

This problem still persists. I think it seems very odd, using "GROUPS=" is the method suggested in the porters handbook, and the git group is in the default /usr/ports/GIDs group

This issue magically resolved itself after a couple of unnecessary reboots. I have no idea what happened.

I am trying to port the newest version 10 of gitlab, and since it depends on gitlab-shell, also gitlab-shell. However, it fails during the staging process due to an illegal group name in a chown operation. In the Makefile: USERS= git GROUPS= git The compile log, with added...

pkg -vv pkg: Warning: Major version upgrade detected. Running "pkg-static install -f pkg" recommended Version : 1.3.7 PKG_DBDIR = "/var/db/pkg"; PKG_CACHEDIR = "/var/cache/pkg"; PORTSDIR = "/usr/ports"; INDEXDIR = ""; INDEXFILE = "INDEX-9"; HANDLE_RC_SCRIPTS = false...

I updated a 9.3 machine to 10.0, now I keep getting messages that implore me to run "pkg-static install -f pkg", but that does not solve the problem. It seems as though nothing happens when I do. Output and commands below. What is the issue that I am facing? root@HOST:/home/USER # pkg...

Great news. Thanks for the good work.

Errors: no. None that I see. The language type is already set to en_US.UTF-8.