Re: rename a port

On Tue, Mar 14, 2017 at 11:18:24AM +0100, Kurt Jaeger wrote: > Hi! > > > I would like to rename a port. How is the best way? > > > > Svn cp /port/oldname / port/newname > > svn mv old new > > should work. > > Please provide an entry for /usr/ports/MOVED, too. > > > And then a diff with

ports-mgmt/pkg wrong pkg version info when more repositories are used

Hi, I have machines configured with more then on repository (two exactly) and "pkg version -vRL =" says "needs updating (remote has..." for packages which exists in both repositories but where installed from one which intentionally does not have newer version. Should not this comparison be

FreeBSD Port: cacti-1.0.1

ERR_TOO_MANY_REDIRECTS on logging in to admin on the first attempt. I can’t seem to find out why this happens. I have installed acute at least ten time prior to this port but on 1.0.1 I can’t get past this error. Any help would be appreciated. Thank you

Re: dependency tree display

or http://portsmon.freebsd.org/portdependencytree.py?category=sysutils=hal . This runs a make(1) command on the latest version of the tree, so it's slow, but accurate. mcl ___ freebsd-ports@freebsd.org mailing list

Re: dependency tree display

Thanks! That one looks great! On Wed, Mar 15, 2017 at 1:22 PM, Kurt Jaeger wrote: > Hi! > > > Is there a way to visualize the dependencies of a port in a tree-like > > fashion? That is, if A depends on B, and B depends on C, show me A -> B > -> > > C. > > ports-mgmt/porttree

Re: dependency tree display

Hi! > Is there a way to visualize the dependencies of a port in a tree-like > fashion? That is, if A depends on B, and B depends on C, show me A -> B -> > C. ports-mgmt/porttree claims to do this. -- p...@opsec.eu+49 171 3101372 3 years to go !

Re: dependency tree display

> On 15 Mar, 2017, at 11:18, Vick Khera wrote: > > Is there a way to visualize the dependencies of a port in a tree-like > fashion? That is, if A depends on B, and B depends on C, show me A -> B -> > C. > > When I upgrade something in node using npm, it gives this kind of nice

dependency tree display

Is there a way to visualize the dependencies of a port in a tree-like fashion? That is, if A depends on B, and B depends on C, show me A -> B -> C. When I upgrade something in node using npm, it gives this kind of nice tree: hal@2.0.0 /u/lorax1/home/hubot/hal ├─┬ aws2js@0.8.3 │ └─┬

XENSERVER USERS

Hi, Would you be interested in a marketing contact database of companies currently using XENSERVER? We can provide you with TOP Decision Makers from these companies to better assist you sales and marketing campaigns. Information Fields: Contact name, Company Name, Business Email,

Re: pkg checksum mismatch for a variety of ports

On Wed, 15 Mar 2017 14:55:00 + tech-lists wrote: > Hello ports@, > > What's the significance of this and what can I do about it? Deinstalling > and reinstalling doesn't help. These were installed with ports r436245 > on 11.0-stable r314138: > > # pkg check -s > >

pkg checksum mismatch for a variety of ports

Hello ports@, What's the significance of this and what can I do about it? Deinstalling and reinstalling doesn't help. These were installed with ports r436245 on 11.0-stable r314138: # pkg check -s Checking all packages: 3% bluefish-2.2.10: checksum mismatch for

Re: FreeBSD Port: netatalk3-3.1.11

Hi! > Would you be so kind to port new 3.1.11 version? > This version contain > "FIX: dsi_stream_read: len:0, unexpected EOF, GitHub#82" > https://github.com/Netatalk/Netatalk/blob/branch-netatalk-3-1/NEWS > > This fix is very important in production environment. A patch is here:

FreeBSD Port: netatalk3-3.1.11

Hello, Thank you for you work with netatalk3 port! It's very useful and powerful software. Would you be so kind to port new 3.1.11 version? This version contain "FIX: dsi_stream_read: len:0, unexpected EOF, GitHub#82" https://github.com/Netatalk/Netatalk/blob/branch-netatalk-3-1/NEWS This fix

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,