Re: How to get pkg to recognize local repository?

El día lunes, julio 17, 2017 a las 05:10:06a. m. +, Thomas Mueller escribió: > How do I get pkg to recognize a local repository such as > /mnt/usr/packages/All, or does pkg only recognize remote repositories? > > ... I use: $ ls -l /usr/local/etc/pkg/repos/*.conf -rw-r--r-- 1 root wheel

Re: How to get pkg to recognize local repository?

> On 17. Jul 2017, at 7:10 AM, Thomas Mueller wrote: > > pkg-static: Ignoring bad configuration entry in > /usr/local/etc/pkg/repos/mytemprepo.conf: "file:///mnt/usr/packages/All" > pkg-static: Warning: Major OS version upgrade detected. Running "pkg-static > install -f

How to get pkg to recognize local repository?

How do I get pkg to recognize a local repository such as /mnt/usr/packages/All, or does pkg only recognize remote repositories? In this case, /mnt was a mount point for another FreeBSD 11.1-PRERELEASE installation from the same svn revision. Second was installed from the first using NFS.

Re: Look for a committer

Thanks Kurt! added olgeni@ I just run poudriere testport for 10.3 i386, py27-bear build fine, and the devel/erlang is not involved as a dependency. devel/bear build log: https://raw.githubusercontent.com/amutu/data/master/py27-bear-2.3.6.log 2017-07-17 1:49 GMT+08:00 Kurt Jaeger

Re: Firefox/GTK3 issue and reinstalling dependent ports

On 16/07/2017 13:35, Kurt Jaeger wrote: Hi! Hmm, I found this: pkg clean -a cleans the cache and pkg install -R -f firefox should force a reinstallation of the package and all dependencies. Well, indeed, as you posted already, it does not 8-( I didn't try pkg clean -a before pkg

Re: Look for a committer

Hi! > I made a new port named /deve/bear, which is a tool that generates a > compilation database for clang tooling. It is useful for > clang-tidy/clang-check with non-cmake project. > > PR: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220475 I build it in poudriere, worked on current,

Anybody knows how to patch tarballs that bazel extracts?

Bazel (devel/bazel) based projects tend to fetch tarballs directly. WORKSPACE can be patched to change the fetch URL to one in /usr/ports/distfiles. However, what to do when the contents of tarballs need to be patched? It there an easy way to tell bazel to patch tarball contents? Yuri

Re: Firefox/GTK3 issue and reinstalling dependent ports

Hi! > Hmm, I found this: > > pkg clean -a > cleans the cache and > > pkg install -R -f firefox > > should force a reinstallation of the package and all dependencies. Well, indeed, as you posted already, it does not 8-( -- p...@opsec.eu+49 171 3101372 3

Re: Firefox/GTK3 issue and reinstalling dependent ports

Hi! > Will either pkg clean -a or pkg delete -a uninstall any of the installed > ports? Yes. pkg delete -a deinstalls all installed ports. That's the problem with that approach. Hmm, I found this: pkg clean -a cleans the cache and pkg install -R -f firefox should force a reinstallation of

Re: Firefox/GTK3 issue and reinstalling dependent ports

On 16/07/2017 12:45, Kurt Jaeger wrote: I am using poudriere and wanted to track down which repository/option is responsible for this issue. I created a new repository where I compiled Firefox with all its dependencies with default options. But I don't know how to reinstall Firefox with all

Re: Firefox/GTK3 issue and reinstalling dependent ports

Hi! > This is a re-post from FreeBSD forum > > Firefox on my computer expresses a weird UI issue where many controls > are rendered without their borders. For example, radios or checkboxes > can be selected but are invisible, since they have no border. I've seen the behaviour -- thanks for

Firefox/GTK3 issue and reinstalling dependent ports

This is a re-post from FreeBSD forum Firefox on my computer expresses a weird UI issue where many controls are rendered without their borders. For example, radios or checkboxes can be selected but are invisible, since they have no border. Also selecting text doesn't highlight the selected

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,