Re: [SOLVED] request for portmgr approval on bug 238170

[Koichiro Iwao]

I've already got feedback from portmgr, thanks!

On Fri, Oct 09, 2020 at 04:11:12PM +0900, Koichiro Iwao wrote:
> 
> Hi,
> 
> I suppose this kind of changes require portmgr's approval, right?
> I'd appreciate if someone tell me the correct procedure to request
> portmgr to approve such patches.
> 
> Or tell me this change actually requires portmgr's approval or not.
> 
> I'm sure this doesn't break anything.
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238170
> 
> -- 
> meta 

-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

request for portmgr approval on bug 238170

[Koichiro Iwao]

Hi,

I suppose this kind of changes require portmgr's approval, right?
I'd appreciate if someone tell me the correct procedure to request
portmgr to approve such patches.

Or tell me this change actually requires portmgr's approval or not.

I'm sure this doesn't break anything.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238170

-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: tigervnc-server-1.11.0 error build

[Koichiro Iwao]

> >> Just remove net/tigervnc-server/files/patch-unix_xserver_hw_vnc_xvnc.c
> >> and try again.  It looks like the committer forgot to remove an obsolete
> >> patch.

Exactly. Thanks for the fix!


-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Recommendation softether

[Koichiro Iwao]

On 2020-05-16 07:52, Michael Butler via freebsd-ports wrote:

It's already there ..

security/softether-devel Softether VPN 4 (stable beta version)
security/softether SoftEther VPN 4 (RTM version)
security/softether5 SoftEther VPN 5 (Developer Edition)


Yup, I do maintain these. I'm also contributing to SoftEther upstream.
Each of them works well on FreeBSD but if you want to run SoftEther on
architectures other than x86(-64) such as Raspberry Pi,
security/softether5 is the only version that supports such 
architectures.


Rgds,
--
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: How to use base OpenSSL with meson-based ports?

[Koichiro Iwao]

In my ports, I patch configure.ac to find OpenSSL not relying on
pkg-config.

https://svnweb.freebsd.org/ports/head/net/xrdp/files/patch-configure.ac?revision=469777=markup#l8

See also this. 

http://empt1e.blogspot.com/2011/05/dealing-with-pkg-config-detection-of.html
https://github.com/neutrinolabs/xrdp/pull/514

On Tue, Mar 31, 2020 at 11:24:58AM +0400, Gleb Popov wrote:
> Hello.
> 
> Meson build system uses pkg-config to locate dependencies. However, OpenSSL
> in base does not provide a .pc file (unlike, say, zlib - see
> /usr/libdata/pkgconfig/). I haven't found a way in meson to manually set up
> a dependency in this case.
> 
> I got a suggestion to write my own .pc file and hook it into the build of
> my port, but this looks somewhat hackish for me. Why can't we provide a
> proper .pc file in the base system?
> 
> Thanks in advance.
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: OpenSSL multiple names?

[Koichiro Iwao]

Hi, 

I think UPDATING 20200101 should help you.

On Wed, Feb 05, 2020 at 06:41:19PM -0700, @lbutlr wrote:
> When trying to port upgrade mariadb it reinstalled openssl (just about 
> everything for the last month has reinstalled openssl)
> 
> I get this after a successful build
> 
> ===>   Registering installation for openssl-1.1.1d,1
> Installing openssl-1.1.1d,1...
> pkg-static: openssl-1.1.1d,1 conflicts with openssl111-1.1.1d
> 
> There is /usr/ports/security/openssl
> 
> So why are there two different formats on the port name and how do I fix this?
> 
> 
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: xterm-353

[Koichiro Iwao]

Reported to the maintainer. It should be fixed shortly.

On Sun, Feb 02, 2020 at 10:36:00AM -0500, ajtiM via freebsd-ports wrote:
> Update of xterm to version 253 has a problem:
> 
> ===>  License MIT accepted by the user
> ===>   xterm-353 depends on file: /usr/local/sbin/pkg - found
> ===> Fetching all distfiles required by xterm-353 for building
> => SHA256 Checksum mismatch for xterm-353.tgz.
> => SHA256 Checksum OK for bsd-xterm-icons-1.tgz.
> ===>  Giving up on fetching files:  xterm-353.tgz 
> Make sure the Makefile and distinfo file (/usr/ports/x11/xterm/distinfo)
> are up to date.  If you are absolutely sure you want to override this
> check, type "make NO_CHECKSUM=yes [other args]".
> *** Error code 1
> 
> Stop.
> make[2]: stopped in /usr/ports/x11/xterm
> *** Error code 1
> 
> Stop.
> make[1]: stopped in /usr/ports/x11/xterm
> *** Error code 1
> 
> Stop.
> make: stopped in /usr/ports/x11/xterm
> 
> ===>>> make build failed for x11/xterm
> ===>>> Aborting update
> 
> ===>>> Update for x11/xterm failed
> ===>>> Aborting update
> 
> Thank you.
> 
> -- 
> “In politics stupidity is not a handicap”. 
> 
> Napoleon Bonaparte
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Committing updates for three ports (graphics/py-glfw, sysutils/zrep, and misc/py-tqdm)

[Koichiro Iwao]

Hi! Everything has been committed.

On Mon, Nov 18, 2019 at 02:44:16PM -0500, Neel Chauhan wrote:
> Hi freebsd-ports@ mailing list,
> 
> Could someone please be able to commit updates for these three ports:
> 
>  * graphics/py-glfw (Bugzilla:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241883)
> 
>  * misc/py-tqdm (Bugzilla:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242063)
> 
>  * sysutils/zrep (Bugzilla:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242064)
> 
> These were all tested and passes Poudriere on FreeBSD 12.0/12.1.
> 
> -Neel
> 
> ===
> 
> https://www.neelc.org/
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: golang apps try to use network during build and build erro on

[Koichiro Iwao]

On Tue, Nov 05, 2019 at 09:27:58AM +0900, Koichiro Iwao wrote:
> I'm not familiar with golang build system. I'm not sure why this happens
> and the differences between golang apps use network and don't. I'd
> appreciate if you give me some advice how do golang folks avoid using
> network during build?
> 
> ===>  Building cli53 from ./cmd/cli53
> go: github.com/aws/aws-sdk-go@v1.13.34: Get
> https://proxy.golang.org/github.com/aws/aws-sdk-go/@v/v1.13.34.mod: dial tcp
> : lookup proxy.golang.org on 192.168.24.1:53: write udp 
> 127.0.0.1:52854->192.168.24.1:53: write: permission denied

Finally succeeded to update dns/cli53 and devel/lazygit thanks to decke@
and dmgk@'s advice. Now I understand how to use USES=go:modules.

https://svnweb.freebsd.org/changeset/ports/516857
https://svnweb.freebsd.org/changeset/ports/516860

-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: golang apps try to use network during build and build erro on

[Koichiro Iwao]

Hi, 

Thank you both. I'll give it a try.

-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

golang apps try to use network during build and build erro on

[Koichiro Iwao]

poudriere
Reply-To:
X-Operating-System: FreeBSD 12.1-STABLE amd64


Hi,

I recently noticed some golang apps (recent vewsion?) try to use network
during build.  As we know, this causes build error on poudriere.

I'm not familiar with golang build system. I'm not sure why this happens
and the differences between golang apps use network and don't. I'd
appreciate if you give me some advice how do golang folks avoid using
network during build?

===>  Building cli53 from ./cmd/cli53
go: github.com/aws/aws-sdk-go@v1.13.34: Get
https://proxy.golang.org/github.com/aws/aws-sdk-go/@v/v1.13.34.mod: dial tcp
: lookup proxy.golang.org on 192.168.24.1:53: write udp 
127.0.0.1:52854->192.168.24.1:53: write: permission denied

-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FLAVORS for Ruby

[Koichiro Iwao]

On Tue, Sep 17, 2019 at 07:34:27AM -0400, Steve Wills wrote:
> Hi,
> 
> On 9/17/19 2:40 AM, Mathieu Arnold wrote:
> > 
> > What we are all trying to say is that adding flavors for ruby will have
> > a big impact on build time and ressources required for building.
> > 
> > If all you want is to have ruby flavors for the kicks of it, then I am
> > glad to tell you that no, it will not be done.
> > 
> > Now, the question is, why would someone need to have ruby flavors?
> > 
> > The answer cannot be "because it should be fun" or "there is no reason
> > there should not be".
> > 
> > Give us a real reason about why it would be required.
> > 
> 
> We have multiple versions of Ruby, we should provide the gems for each
> version. Right now, there is no way for users of Ruby 2.4 to install gem
> packages except to change the default ruby and then build their own
> packages. We want people to have fewer reasons to build their own packages,
> not more.
> 
> We keep the latest Ruby as not default because it tends to have more bugs
> and gems lag, and the older version of Ruby is available because some gems
> tend to lag really badly. So, users do have legitimate reasons for using the
> non-default versions of Ruby. Also, upstream supports latest and two
> versions back.
> 
> It wasn't until Ruby 2.6 was out that GitLab even supported 2.5, to give
> just one example.
> 
> So, we have those versions of Ruby, and they should be usable, and that
> includes installing gems via pkg.
> 
> There's the point that maybe we should only package gems that are needed by
> other things, which I can understand, but don't know if I necessarily agree
> with, because then you have users confused on what the "right" way to
> install a gem is. "Oh, this one is packaged because something else in ports
> needs it, so use the pkg, but this other one isn't packaged, so you have to
> use gem."
> 
> And I'd think the same applies to python modules or perl modules, etc. One
> could ask, why not provide flavors for all versions of python, that is, 3.5,
> 3.6 and 3.7, along with the 2.7 ones as well, but to me that doesn't seem
> quite necessary because the compatibility is better there, as far as I can
> tell. But, I wouldn't be opposed to it personally, if someone did make the
> argument in favor of it. Same with Perl and especially things that depend on
> Java.
> 
> But that's all beside the point, really.
> 
> Steve

Hello again everyone, 

I'm sorry I cannot express my thoughts correctly in English and I clould not
explain why flavors for Ruby required but swills explained far better than me.

Based on his explanation, will it be a valid reason to introduce flavors
on Ruby ports?

-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FLAVORS for Ruby

[Koichiro Iwao]

On Mon, Sep 16, 2019 at 08:54:17AM -0600, Adam Weinberger wrote:
> On Mon, Sep 16, 2019 at 8:39 AM Koichiro Iwao  wrote:
> >
> > On Sat, Sep 14, 2019 at 10:52:45AM -0600, Adam Weinberger wrote:
> > > The issue is that FLAVORS has added a substantial (and painful) 
> > > complexity to python ports and python.mk. It means that a number of 
> > > people have had to be hyper-vigilant and watch commits closely to catch 
> > > errors introduced when people utilize the paradigm incorrectly. It’s a 
> > > bitter pill, but it’s accepted because the use-case for multiple 
> > > concurrent python versions is essential.
> > >
> > > As Antoine said, inconsistency isn’t a strong enough use case. Which 
> > > brings us back to the original question: is there a specific use-case for 
> > > concurrent ruby that makes the substantial increase in cognitive load, 
> > > complexity, and monitoring worth it?
> >
> > PHP also have FLAVORS. What about PHP? Multiple concurrent PHP versions
> > is essential?
> 
> We're going in circles here. I've for the third time now that what
> we'd need to get on board is a use case, a description of the end-user
> problem that we're trying to solve.
> 
> What you've provided (for the fourth time in this thread) is a straw
> man argument. What other languages have is irrelevant. We are much
> less concerned with "consistency" than with solving end-user problems
> in a way that fits the specific use case.
> 
> Steve seemed interested in the idea. I'd explore it with him, and I
> hope you are able to make it happen. I'm done here.

Thanks. I see a gap between you and me but I'll give it a try anyway
with swills.

You:  If there's no valid reasons, don't do it.
Me:   If there's no invalid reasons, try it.

I believe that the reason Ruby don't have FLAVORS is just nobody worked
on that. In fact, swills worked on that a little.

BTW, if I can do something only necessary, what a boring life.

-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FLAVORS for Ruby

[Koichiro Iwao]

On Sat, Sep 14, 2019 at 10:52:45AM -0600, Adam Weinberger wrote:
> The issue is that FLAVORS has added a substantial (and painful) complexity to 
> python ports and python.mk. It means that a number of people have had to be 
> hyper-vigilant and watch commits closely to catch errors introduced when 
> people utilize the paradigm incorrectly. It’s a bitter pill, but it’s 
> accepted because the use-case for multiple concurrent python versions is 
> essential.
> 
> As Antoine said, inconsistency isn’t a strong enough use case. Which brings 
> us back to the original question: is there a specific use-case for concurrent 
> ruby that makes the substantial increase in cognitive load, complexity, and 
> monitoring worth it?

PHP also have FLAVORS. What about PHP? Multiple concurrent PHP versions
is essential?

-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FLAVORS for Ruby

[Koichiro Iwao]

On Sat, Sep 14, 2019 at 08:39:12AM +0200, Antoine Brodin wrote:
> On Sat, Sep 14, 2019 at 6:27 AM Koichiro Iwao  wrote:
> > On Fri, Sep 13, 2019 at 09:33:43AM -0600, Adam Weinberger wrote:
> > > Systems MUST be able to support concurrent installations of python2.7
> > > and actual python. What is your use case for concurrent ruby?
> >
> > I know the importance of Python 2. Even if it is EoL-ed, it will be
> > required over the next a few years because not a few applications don't
> > migrate to Python 3. So that's true and reasonable.
> >
> > Excuse me that I'm answering your question with a question. What about
> > PHP? Concurrent installation is a MUST?
> >
> > FreeBSD ports allows concurrent installations of multiple Ruby versions
> > however doesn't allow concurrent installations of rubygems for multiple
> > Ruby versions. This inconsistency is the issue for me.
> 
> This isn't a valid reason for me.
> Why do you need ruby version 2.4 or 2.5 concurrently installed with version 
> 2.6?
> Is there a bug in version 2.6?

You don't understand the issue. The necessity of concurrent Ruby
versions isn't the issue. The inconsistency is the issue. If rubygems cannot
be installed for multiple ruby versions, FreeBSD ports shouldn't allow
to install multiple versions of Ruby.

You have doubts about installing multiple ruby versions concurrently,
you should also have doubts about why multiple ruby ruby can be installed
concurrently Disabling multiple ruby 

Alternatively, Python 3.5 and 3.6 can be installed concurrently and 
py- ports can be installed concurrently for each python versions.

-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FLAVORS for Ruby

[Koichiro Iwao]

On Fri, Sep 13, 2019 at 09:14:01AM -0400, Steve Wills wrote:
> We provide multiple versions of Ruby, it would make sense to provide gems
> for each version. In fact, I worked on this but never finished it:
> 
> https://reviews.freebsd.org/D1
> 
> Steve

That's nice. I will do anything that I can so if you need help.
What should we start from with that to continute?

-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FLAVORS for Ruby

[Koichiro Iwao]

On Fri, Sep 13, 2019 at 09:33:43AM -0600, Adam Weinberger wrote:
> Systems MUST be able to support concurrent installations of python2.7
> and actual python. What is your use case for concurrent ruby?

I know the importance of Python 2. Even if it is EoL-ed, it will be
required over the next a few years because not a few applications don't
migrate to Python 3. So that's true and reasonable.

Excuse me that I'm answering your question with a question. What about
PHP? Concurrent installation is a MUST?

FreeBSD ports allows concurrent installations of multiple Ruby versions
however doesn't allow concurrent installations of rubygems for multiple
Ruby versions. This inconsistency is the issue for me.

-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: dos2unix patch?

[Koichiro Iwao]

On Fri, Sep 13, 2019 at 11:20:06AM +0200, Tijl Coosemans wrote:
> You could add the patches to DISTFILES instead of PATCHFILES and then
> maybe do-extract will just copy them to WRKDIR, but if not, you can set
> EXTRACT_ONLY to the original distfile and copy the patches to WRKDIR in
> post-extract.  Then dos2unix should work and you can add the WRKDIR
> patches to EXTRA_PATCHES.

Thanks, I give it a try!

-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FLAVORS for Ruby

[Koichiro Iwao]

On Fri, Sep 13, 2019 at 10:00:19AM +0200, Antoine Brodin wrote:
> On Fri, Sep 13, 2019 at 9:45 AM Koichiro Iwao  wrote:
> > Hi,
> >
> > I would like to suggest introducing FLAVOR to Ruby ports.
> >
> > AFAIK multiple version of Ruby ports (lang/ruby??) can be installed at
> > the same time.  One of these ruby ports will be *default* installed as
> > PREFIX/bin/ruby. In contrast of Ruby lang, rubygem ports cannot be
> > installed for multiple Ruby version at the same time.
> >
> > I would say Ruby and rubygem ports needs FLAVORS like Python ports.
> > In Python ports, the same origin py- ports can be installed for multiple
> > versions such as py27, py35, py36. If the same thing can be done with
> > Ruby ports, FreeBSD Ruby ports will be much improved.
> >
> > I would appreciate if you Ruby folks bounce some ideas off each other.
> > Let me know if someone's already working on FLAVORS on Ruby. Is there
> > something that I can help you with?
> 
> Please no.  I don't see valid reasons.

Why? I don't see invalid reasons. Had Ruby FLAVORS already denied in the
past?  What's the difference between Rython and Ruby? py- ports can be
installed for py35 and py36 at the same time. Why not for Ruby?

I'm just brainstorming Ruby FLAVORS. Both positive opinions and negative
opinions are welcome.

-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

FLAVORS for Ruby

[Koichiro Iwao]

Hi, 

I would like to suggest introducing FLAVOR to Ruby ports.

AFAIK multiple version of Ruby ports (lang/ruby??) can be installed at
the same time.  One of these ruby ports will be *default* installed as
PREFIX/bin/ruby. In contrast of Ruby lang, rubygem ports cannot be
installed for multiple Ruby version at the same time.

I would say Ruby and rubygem ports needs FLAVORS like Python ports.
In Python ports, the same origin py- ports can be installed for multiple
versions such as py27, py35, py36. If the same thing can be done with
Ruby ports, FreeBSD Ruby ports will be much improved.

I would appreciate if you Ruby folks bounce some ideas off each other.
Let me know if someone's already working on FLAVORS on Ruby. Is there
something that I can help you with?

Thanks,
-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: dos2unix patch?

[Koichiro Iwao]

Finally I decided to manage all ports patches in my GitHub fork.

I describe current status of the port:

- Upstream source is CRLF
- patches in FILESDIR are LF because CRLF patches in svn repo should be
  marked as binary
- To apply these patches, convert to LF using USE=dos2unix

I believe this is common technique and now a few numbers of ports do so.
The problem is adding a backport patch from upstream. I pick a git
commit from upstream and add to PATCHFILES. Patching is done after
dos2unix. Applying upstream patch to dos2unix-ed source will fail.

So I wanted to apply CRLF patch before dos2unix, apply LF patches after
dos2unix but current ports framework cannot do such hack.  Finally
I quit mixing CRLF patchs and LF patches. I commit ports patches to
my GitHub fork of upstream product and fetch from there. This does not
cause line-ending mismatch.

On Thu, Sep 12, 2019 at 02:23:58PM +0900, Koichiro Iwao wrote:
> Hi,
> 
> is it possible to run dos2unix to patches fetched from PATCH_SITES?
> or how can I change order of patch and dos2unix.
> 
> I would like to apply dos2unix-ed patches to dos2unix-ed source.
> Alternatively, applying patch first and then running dos2unix on
> patched-source is OK to me.
> 
> Patches fetched from PATCH_SITES have .patch suffix so I added *.patch
> to DOS2UNIX_GLOB but it didn't work.
> 
> USES= dos2unix
> DOS2UNIX_GLOB= *.c *.h
> 
> -- 
> meta 
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

dos2unix patch?

[Koichiro Iwao]

Hi,

is it possible to run dos2unix to patches fetched from PATCH_SITES?
or how can I change order of patch and dos2unix.

I would like to apply dos2unix-ed patches to dos2unix-ed source.
Alternatively, applying patch first and then running dos2unix on
patched-source is OK to me.

Patches fetched from PATCH_SITES have .patch suffix so I added *.patch
to DOS2UNIX_GLOB but it didn't work.

USES= dos2unix
DOS2UNIX_GLOB= *.c *.h

-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: category for VPN softwares?

[Koichiro Iwao]

On Tue, Apr 02, 2019 at 03:45:43PM +0200, Mathieu Arnold wrote:
> And in any case, see our documentation:
> 
> https://www.freebsd.org/doc/en/articles/committers-guide/ports.html#ports-qa-new-category

I've raised bug 239395. I'd appreciate if someone tell me I need to
get who's approval to commit this.

[1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239395


-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: please update rrdtool port from 1.7.0_2 to 1.7.2

[Koichiro Iwao]

Hi, 

Just a note to let you know that the patch is already submitted.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238832

On Tue, Jul 02, 2019 at 05:58:58PM +0200, Philippe Maechler wrote:
> Hello BSD Users
> 
>  
> 
> I see that rrdtool 1.7.1 was released on February 2019 and 1.7.2 in may 2019. 
> Freshports or the FreeBSD Ports still have the version 1.7.0_2 . 
> 
>  
> 
> If someone with the needed skills has time, I would appreciate if he/she can 
> update the port. There are options I really like to use (--allow-shrink with 
> --rigid) 
> 
> /BR
> 
> Philippe
> 
>  
> 
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

portscount is down

[Koichiro Iwao]

Hi,

portscout.FreeBSD.org seems to be down (Error 503 Backend fetch failed)
for the last few days. Is anyone aware of this already?

-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: net/xrdp: Issue(s) with Channels/Clipboard.

[Koichiro Iwao]

Hi!

Good work! Thank you for your investigation. Regarding LAME,
I'm planning to drop it as default because AAC is enough.

FYI, here's an upstream issue regarding audio codec license:
https://github.com/neutrinolabs/xrdp/issues/634

On Wed, Jun 05, 2019 at 07:56:29AM -0600, Janky Jay, III wrote:
> I think I may have found an/the issue here.
> 
> Comparing two systems (one that works and one that does not), I noticed
> that "/usr/local/sbin/xrdp-chansrv" was not even running on system that
> wasn't working. So, I manually ran it to find it was missing some
> libraries which I checked with "ldd":
> 
> #~ ldd /usr/local/sbin/xrdp-chansrv
> 
> 
> 
> /usr/local/sbin/xrdp-chansrv:
> libcommon.so.0 => /usr/local/lib/xrdp/libcommon.so.0 (0x800267000)
> libSM.so.6 => /usr/local/lib/libSM.so.6 (0x80028)
> libICE.so.6 => /usr/local/lib/libICE.so.6 (0x80028a000)
> libXfixes.so.3 => /usr/local/lib/libXfixes.so.3 (0x8002a7000)
> libXrandr.so.2 => /usr/local/lib/libXrandr.so.2 (0x8002af000)
> libX11.so.6 => /usr/local/lib/libX11.so.6 (0x8002bc000)
> libfdk-aac.so.2 => not found (0)
> libopus.so.0 => /usr/local/lib/libopus.so.0 (0x8003fd000)
> libmp3lame.so.0 => not found (0)
> libthr.so.3 => /lib/libthr.so.3 (0x80046f000)
> libcrypto.so.111 => /lib/libcrypto.so.111 (0x80049a000)
> libssl.so.111 => /usr/lib/libssl.so.111 (0x800787000)
> libc.so.7 => /lib/libc.so.7 (0x80081c000)
> libXext.so.6 => /usr/local/lib/libXext.so.6 (0x800c0f000)
> libXrender.so.1 => /usr/local/lib/libXrender.so.1 (0x800c23000)
> libxcb.so.1 => /usr/local/lib/libxcb.so.1 (0x800c2f000)
> libm.so.5 => /lib/libm.so.5 (0x800c58000)
> libXau.so.6 => /usr/local/lib/libXau.so.6 (0x800c8a000)
> libXdmcp.so.6 => /usr/local/lib/libXdmcp.so.6 (0x800c8f000)
> 
> Here, I noticed that both "libfdk-aac" and "libmp3lame" are missing
> which is keeping xrdp-chansrv from starting. I was able to install
> "fdk-aac-2.0.0" via "pkg install" without any issues but installing
> "audio/lame" does not appear to be an option via "pkg". Apparently,
> there is a licensing issue. So, this needed to be built from ports. I
> would imagine that these are important to people using sound (I am not)
> so some audio dependencies should remain. However, I'm not sure it
> should be "audio/lame" if there is not a package available for it.
> Perhaps finding an alternative or removing it as a dependency from the
> xrdp-devel package? Not sure.
> 
> Anyhow, getting these two libs installed fixed the chansrv timeout issue
> for me. So, hopefully that can help troubleshoot the package install of
> xrdp-devel (I haven't tried the port but I'd imagine it probably works
> fine).
> 
> Regards,
> Janky Jay, III
> 
> On 5/8/19 4:00 PM, Janky Jay, III wrote:
> > Hello Koichiro,
> > 
> >     Is there any update to this? I've since upgraded both systems to
> > FBSD 12.0-RELEASE-p3 and there have also been (I think) two (2) xrdp
> > port/pkg updates as well but the problem still remains the same.
> > Connections to chansrv work 100% of the time on one system and 0% of the
> > time on the other.
> > 
> >     Also, can you please provide a link to the GH post/report that you
> > created? I'd like to take a look and follow that as well if I can.
> > Thanks again!
> > 
> > Regards,
> > Janky Jay, III
> > 
> > On 2019-02-17 12:23, Janky Jay, III wrote:
> >> Hello Meta,
> >>
> >> On 2/16/19 6:37 PM, Koichiro Iwao wrote:
> >>> On Fri, Feb 15, 2019 at 11:31:36AM -0700, Janky Jay, III wrote:
> >>>>  This also causes the connection to take 16 seconds to open XFCE4 once
> >>>> it finally gives up on channels. I see 4 errors so I'm guessing there's
> >>>> a 4 second timeout between attempts. Something similar to the
> >>>> issue/recommendation reported at
> >>>> https://github.com/neutrinolabs/xrdp/issues/1288. I've tried the
> >>>> recommended disallowing of channels to see if it would connect faster
> >>>> but it does nothing. Still attempts the connections to "chansrv" and
> >>>> takes 16 seconds.
> >>> I don't think that is recommended in the upstream issue. Just he reporter
> >>> tried as workaround. Who recommended? As commented in the ticket, 
> >>> disabling
> >>> all channels don't stop connecting to chansrv. That's why *not to
> >>

Re: category for VPN softwares?

[Koichiro Iwao]

Concluding everyone's opinion, starting with virtual category sounds much
easier.  Thanks. I'll create a list of VPN softwares first.

-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: category for VPN softwares?

[Koichiro Iwao]

On Tue, Apr 02, 2019 at 11:38:15AM +0200, Mateusz Piotrowski wrote:
> I am not sure if it should be vpn or net-vpn. I feel net-vpn is
> more suitable.

As you know, we already have net-im, net-p2p, net-mgmt categories.
This is one of reasons why I feel net-vpn is more suitable.

-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: starting virtual box VM instantly crashes FreeBSD after upgrade from 11 to 12

[Koichiro Iwao]

Hi,

did you rebuild virtualbox-ose-kmod?

On Tue, Apr 02, 2019 at 04:04:49PM +1100, Graham Menhennitt wrote:
> Hello all,
> 
> I recently upgraded my desktop box from 11-Stable to 12-Stable via source.
> I've rebuilt and installed the 5.2.26 virtualbox-ose and virtualbox-ose
> ports from scratch and made sure that no traces of older versions exist.
> 
> I start the VirtualBox GUI successfully and see the table of my VMs. I
> select one of them and start it and FreeBSD instantly crashes. My screen
> goes blank and eventually FreeBSD reboots.
> 
> The only thing I can see in my /var/log/messages is:
> 
>   Apr  2 15:07:14 starker kernel: vboxdrv:  VMMR0.r0
>   Apr  2 15:07:14 starker kernel: vboxdrv:  VBoxDDR0.r0
> 
> after the crash and just before the reboot sequence.
> 
> I can't see anything in /usr/ports/UPDATING that's relevant. It was all
> working correctly under 11-Stable.
> 
> Does anybody have any clues, please? How can I diagnose further?
> 
> Thanks in advance for any help.
> 
> Graham
> 
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: category for VPN softwares?

[Koichiro Iwao]

On Tue, Apr 02, 2019 at 06:41:51AM +0200, Kurt Jaeger wrote:
> Create a real category vpn and move everything to it ?

Sounds better! Gentoo has net-vpn category. Just FYI, Gentoo also have
net-dialup category. PPP/PPPoE/L2TP softwares are put under net-dialup
but I feel that classification is too fine. At least creating vpn or
net-vpn souds good.

-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

category for VPN softwares?

[Koichiro Iwao]

Hi, 

some VPN softwares are in security category/directory. OTOH, some VPN
softwares are in net category/directory. Which is correct & preferred?
Incoherent categories are a little bit surprising and confusing for me.

I'd like to sort out categories of VPN softwares. Probably we have
following options. What do you think? I'd appreciate any comments or
suggestions.

1. Incoherent categories are OK and leave it as-is
2. Move all VPN softwares to either of net or security
3. Create a new virtual category "vpn" and leave phys categories as-is
4. Create a new virtual category "vpn" and also sort out phys categories
5. Another option

-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Call for testers/review/help: separating net/tigervnc into -server and -client

[Koichiro Iwao]

Committed at r497400. Let me know if something's inconvenient for you.

https://svnweb.freebsd.org/changeset/ports/497400

On Tue, Mar 26, 2019 at 06:22:38PM +0900, Koichiro Iwao wrote:
> Hi,
> 
> I'm working on separating net/tigervnc into -server and -client.
> If you're a user of TigerVNC, I'd appreciate if you test/review my changes.
> 
> Also Java version of vncviewer will be added later.
> 
> https://reviews.freebsd.org/D19709
> 
> I'd like to commit this before next quarterly branch is branched.
> 
> -- 
> meta 
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Bug report commit request

[Koichiro Iwao]

Regarding the PR, koobs@ has already taken it. I leave it to him.
I'm also a big user of certbot, I can also understand your change
and commit it.

If you add me to CC list when you submit a PR, I'll look at
yours AMAP. Particularly japanese/* ports and popular ports
in Japan.

Thanks always for your work.

On Thu, Mar 28, 2019 at 05:57:21PM +0900, Yasuhiro KIMURA wrote:
> Dear Committers,
> 
> Would someone please commit following bug report?
> 
> Bug 236367 - security/py-acme security/py-certbot*: Update to 0.32.0.
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236367
> 
> Best Regards.
> 
> ---
> Yasuhiro KIMURA
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Call for testers/review/help: separating net/tigervnc into -server and -client

[Koichiro Iwao]

Hi,

I'm working on separating net/tigervnc into -server and -client.
If you're a user of TigerVNC, I'd appreciate if you test/review my changes.

Also Java version of vncviewer will be added later.

https://reviews.freebsd.org/D19709

I'd like to commit this before next quarterly branch is branched.

-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: loose dependency

[Koichiro Iwao]

On Thu, Mar 14, 2019 at 06:50:43PM +0100, Tijl Coosemans wrote:
> You mean building from ports versus poudriere?  Poudriere would always
> select ImageMagick6 with the BUILD_DEPENDS line above, but that's fine.
> 
> Options aren't a good interface for this because the user can select an
> option that conflicts with the installed version.  It's not really a
> port option but a system-wide option.  If this needs to be configurable
> for poudriere then an entry should be added to bsd.default-versions.mk.
> Then the BUILD_DEPENDS line above can become:
> 
> BUILD_DEPENDS=convert:graphics/ImageMagick${IMAGEMAGICK_DEFAULT}

I'm still not sure whether OPTIONS for IM[67] are needed. tijl@ and
adamw@ say different thing but the below works fine for me in both ports
and pkg schenario. Even if IM6 installed, no problem for me.

BUILD_DEPENDS=  convert:graphics/ImageMagick7

-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: loose dependency

[Koichiro Iwao]

On Thu, Mar 14, 2019 at 11:20:09AM -0600, Adam Weinberger wrote:
> This makes building from ports behave differently from pkg. Please,
> just make an OPTIONS_SINGLE for it, and default it to the current
> version (7), not the old version.

Yes, I'm going to switch to 7. The current port using 6 but it's not my
intension [1]. I've created a review [2]. I'd appreciate if you give me
some advice on OPTIONS_SINGLE.

[1] 
https://svnweb.freebsd.org/ports/head/net/tigervnc/Makefile?r1=484427=484640
[2] https://reviews.freebsd.org/D19585
-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: loose dependency

[Koichiro Iwao]

On Thu, Mar 14, 2019 at 02:33:30PM +0100, Tijl Coosemans wrote:
> Like hrs already said: since this is a build dependency you can just
> write:
> 
> BUILD_DEPENDS=convert:graphics/ImageMagick6
> 
> This does not install ImageMagick6 if 7 is installed.  It will only
> install 6 if convert does not exist.  It is a loose dependency.

I understand now. This is what I wanted. Perfect!

> This is not the case for RUN_DEPENDS because dependencies in a package
> are currently specified using package names (including version).  They
> would have to be specified using features where multiple packages can
> then provide a feature.

That's good to know. I'd been thinking the only difference between RUN_
and BUILD_DEPENDS is when the dependency is checked.

Thanks,

-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: loose dependency

[Koichiro Iwao]

On Thu, Mar 14, 2019 at 04:50:18PM +0900, Hiroki Sato wrote:
>  That is a workaround while increasing maintenance cost.  It is at the
>  maintainer's discretion.

Thanks for the advice. Fortunely, icons are not updated too open. The
maintenance cost is not negligible but might be acceptable.

-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: loose dependency

[Koichiro Iwao]

On Thu, Mar 14, 2019 at 01:01:42PM +0700, Eugene Grosbein wrote:
> 14.03.2019 11:40, Hiroki Sato wrote:
> 
> > Koichiro Iwao  wrote
> >   in <20190314031726.aaspgwdcuithh...@icepick.vmeta.jp>:
> > 
> > me> Hi,
> > me>
> > me> If a port have runtime dependency on bin/convert command of ImageMagick
> > me> but whichever ImageMagick{6,7}{,-nox11} are OK, how port Makefile should
> > me> be written?
> > me>
> > me> ImageMagick6 and 7 conflicts each other. I want to respect user's
> > me> choice which ImageMagick to use.
> > 
> >  There is no easy solution to solve it completely because currently
> >  package dependency is solved in a strict manner including package
> >  names and version numbers, not only existence of specific files.
> >  Creating multiple ports which depend on each software or using
> >  FLAVORS to make it easier is a way to provide packages with every
> >  possible combinations of dependency and let one to choose.
> 
> OTOH, one still may create a port depending on existence of specific file
> and fetching another port automatically in case of file absence.
> It works just fine for those using ports as primary source, not packages.
> 
> And yes, if one uses packages, it is forced to live with "default" versions
> including dependencies or build its own pkg repo.

In this case, I think FLAVORS don't fit but that's OK.

Regarding FLAVORS, is it possible to depend on any of FLAVORS, not on
one specific FLAVORS? For example, a port requires some command written
in python but python version doesn't matter.

-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: loose dependency

[Koichiro Iwao]

On Thu, Mar 14, 2019 at 03:12:43PM +0900, Koichiro Iwao wrote:
> On Thu, Mar 14, 2019 at 01:40:14PM +0900, Hiroki Sato wrote:
> >  There is no easy solution to solve it completely because currently
> >  package dependency is solved in a strict manner including package
> >  names and version numbers, not only existence of specific files.
> >  Creating multiple ports which depend on each software or using
> >  FLAVORS to make it easier is a way to provide packages with every
> >  possible combinations of dependency and let one to choose.
> 
> Specifically talking, net/tigervnc is the case. Actually, the dependency
> is build dependency not runtime. ImageMagick is used to create multiple
> sizes of icons such as 24x24, 32x32, 48x48 during the build. Whichever
> versions of ImageMagick in the current ports tree can be used for the
> purpose. Once the port is built, ImageMagick is not required at all and
> can be uninstalled if no other packages depends on it.
> 
> I think FLAVORS does not fit such case. Creating
> net/tigervnc@ImageMagick[67] sounds me stupid. But If I specify IM6,
> IM7 users cannot build net/tigervnc due to ImageMagick conflict and
> vise cersa.
> 
> I'm stuck :(

BTW, what about this idea?

I prepare pre-converted icons and put it to public_distfiles. The port
fetches it as EXTRA_DIST.  It still sounds me a little bit stupid but
I can remove the dependency on ImageMagick from the port...

-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: loose dependency

[Koichiro Iwao]

On Thu, Mar 14, 2019 at 01:40:14PM +0900, Hiroki Sato wrote:
>  There is no easy solution to solve it completely because currently
>  package dependency is solved in a strict manner including package
>  names and version numbers, not only existence of specific files.
>  Creating multiple ports which depend on each software or using
>  FLAVORS to make it easier is a way to provide packages with every
>  possible combinations of dependency and let one to choose.

Specifically talking, net/tigervnc is the case. Actually, the dependency
is build dependency not runtime. ImageMagick is used to create multiple
sizes of icons such as 24x24, 32x32, 48x48 during the build. Whichever
versions of ImageMagick in the current ports tree can be used for the
purpose. Once the port is built, ImageMagick is not required at all and
can be uninstalled if no other packages depends on it.

I think FLAVORS does not fit such case. Creating
net/tigervnc@ImageMagick[67] sounds me stupid. But If I specify IM6,
IM7 users cannot build net/tigervnc due to ImageMagick conflict and
vise cersa.

I'm stuck :(

-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

loose dependency

[Koichiro Iwao]

Hi,

If a port have runtime dependency on bin/convert command of ImageMagick
but whichever ImageMagick{6,7}{,-nox11} are OK, how port Makefile should
be written?

ImageMagick6 and 7 conflicts each other. I want to respect user's
choice which ImageMagick to use.

-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: net/xrdp: Issue(s) with Channels/Clipboard.

[Koichiro Iwao]

On Fri, Feb 15, 2019 at 11:31:36AM -0700, Janky Jay, III wrote:
>   This also causes the connection to take 16 seconds to open XFCE4 once
> it finally gives up on channels. I see 4 errors so I'm guessing there's
> a 4 second timeout between attempts. Something similar to the
> issue/recommendation reported at
> https://github.com/neutrinolabs/xrdp/issues/1288. I've tried the
> recommended disallowing of channels to see if it would connect faster
> but it does nothing. Still attempts the connections to "chansrv" and
> takes 16 seconds.

I don't think that is recommended in the upstream issue. Just he reporter
tried as workaround. Who recommended? As commented in the ticket, disabling
all channels don't stop connecting to chansrv. That's why *not to
connect when all channels disabled* feature is suggedted.
 
I know some people have the same issue and already recoeded to upstream
GH issue. Hang tight. If I need to know more detail of reproduction,
I might ask you help.

I also reproduce the issue but not 100%.

Thanks,

-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Committer request for print/lilypond-devel

[Koichiro Iwao]

Done.

On Thu, Jan 10, 2019 at 08:05:41PM +1300, Jonathan Chen wrote:
> Hi,
> 
> Could a kind committer please take a look at:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234082
> 
> It's an update by the maintainer, just waiting for a commit.
> 
> Thanks!
> -- 
> Jonathan Chen 
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Bug report commit request

[Koichiro Iwao]

I'll take this one.

On Wed, Dec 26, 2018 at 11:13:12AM +0900, Yasuhiro KIMURA wrote:
> Dear Committers,
> 
> Would someone please commit following bug report?
> 
> [NEW PORT] mail/s-nail: Send and receive Internet mail
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232189
> 
> Best Regards.
> 
> ---
> Yasuhiro KIMURA
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

security/openssl111 TLSv1.3 port options

[Koichiro Iwao]

Hi,

OpenSSL 1.1.1 has been added to ports tree. AFAIK OpenSSL 1.1.1 supports 
TLSv1.3

but no port options for TLSv1.3. There're only TLS1, TLS1_1, TLS1_2.

I assume TLSv1.3 will be enabled by default unless disabled explicitly 
so
security/openssl111 will always be built with TLSv1.3 enabled, am I 
correct?
And why not add port options to enable/disable TLSv1.3 as well as older 
TLS versions?


--
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: xproto merge

[Koichiro Iwao]

On Tue, Jul 31, 2018 at 05:33:48PM -0700, Kevin Oberman wrote:
> Well, not quite. I forgot  evieext-1.1.1. It did not show up as orphaned. I
> think that this needs to be fixed as it certainly should have been. Once I
> deleted evieext, the install went smoothly.

zeising@ has just removed evieext and upated UPDATING. Now everything
should go smoothly.

https://svnweb.freebsd.org/ports?view=revision=476150

-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Please test!

[Koichiro Iwao]

On Mon, Jul 09, 2018 at 04:59:38PM +0900, 山田真由 wrote:
> My port is located at http://taurus.ics.nara-wu.ac.jp/my/

403

-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

order of multiple PKGNAMEPREFIX?

[Koichiro Iwao]

Hi, 

I have a question when a port has multiple PKGNAMEPREFIX. I'm still not
sure after reading porter's handbook[1]. If prefixed ports such as p5-,
py-, rubygem- are under language or region category, which prefix should
appear earlier?

As well as other existing ports, I believe language_region- should
appear earlier. Am I correct?

See also: https://reviews.freebsd.org/D16002

[1] https://www.freebsd.org/doc/en/books/porters-handbook/makefile-naming.html

-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: rubgem update to 3.2.7

[Koichiro Iwao]

On Mon, Jul 09, 2018 at 12:02:22AM +0200, Walter Schwarzenfeld via 
freebsd-ports wrote:
> Portmaster tries to build the update in the wrong order.
> 
> Right order for me was (depend on which packages are installed):
> 
> rubygem-glib2
> rubygem-gobject-introspection
> rubygem-gio2
> rubygem-gdk_pixbuf2
> rubygem-pango
> rubygem-gdk3
> 
> rubygem-gtk3
> 
> rubygem-atk

I can also confirm the issue. I always perform portmaster in order that
you shown by hand when rubygem-gtk ports updated. portmaster needs to be fixed.

-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Why portmaster uses g++ not g++6 nor clang++?

[Koichiro Iwao]

On Fri, May 18, 2018 at 08:30:38PM +0200, Stefan Esser wrote:
> Sorry, this was my fault and I hope it is fixed with the follow-up commit
> to portmaster version 3.19-10.

Thanks! Works for me now.

-- 
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Why portmaster uses g++ not g++6 nor clang++?

[Koichiro Iwao]

Hi,

I'm building devel/qt5-make by portmaster. Somehow portmaster 
incorrectly detects gcc6 and
uses g++ despite it is actually installed as g++6. If I build it without 
portmaster, clang++

is used and build finishes successfully.

$ pkg info | grep gcc
gcc-ecj-4.5Eclipse Java Compiler used to build GCC 
Java

gcc6-6.4.0_7   GNU Compiler Collection 6
gcc6-aux-20170802_1Version of GCC 6 with full Ada support
gccmakedep-1.0.3   Create dependencies in makefiles using 
'gcc -M'


# portmaster devel/qt5-qmake
(snip)
===>  License LGPL21 accepted by the user
===>   qt5-qmake-5.10.1 depends on file: /usr/local/sbin/pkg - found
===> Fetching all distfiles required by qt5-qmake-5.10.1 for building
===>  Extracting for qt5-qmake-5.10.1
=> SHA256 Checksum OK for 
KDE/Qt/5.10.1/qtbase-everywhere-src-5.10.1.tar.xz.

===>  Patching for qt5-qmake-5.10.1
===>  Applying extra patch 
/usr/ports/devel/qt5/files/extrapatch-configure
===>  Applying extra patch 
/usr/ports/devel/qt5/files/extrapatch-mkspecs_features_create__cmake.prf
===>  Applying extra patch 
/usr/ports/devel/qt5/files/extrapatch-mkspecs_features_qt__module.prf
===>  Applying extra patch 
/usr/ports/devel/qt5/files/extrapatch-mkspecs_common_bsd_bsd.conf

===>  Applying FreeBSD patches for qt5-qmake-5.10.1
/usr/bin/sed -i "" -e "/DEFAULT_LIBDIRS=/ 
s,\"n,n/usr/local/lib&,"  
/ssd/tmp/ports/usr/ports/devel/qt5-qmake/work/qtbase-everywhere-src-5.10.1/configure

===>   qt5-qmake-5.10.1 depends on executable: gmake - found
===>   qt5-qmake-5.10.1 depends on package: pkgconf>=1.3.0_1 - found
===>   qt5-qmake-5.10.1 depends on file: /usr/local/bin/python2.7 - 
found

===>   qt5-qmake-5.10.1 depends on executable: gcc6 - found
===>   qt5-qmake-5.10.1 depends on file: /usr/local/bin/as - found
===>  Configuring for qt5-qmake-5.10.1
/bin/mkdir -p 
/ssd/tmp/ports/usr/ports/devel/qt5-qmake/work/qtbase-everywhere-src-5.10.1
echo 'CMAKE_MODULE_TESTS = -' > 
/ssd/tmp/ports/usr/ports/devel/qt5-qmake/work/qtbase-everywhere-src-5.10.1/.qmake.cache
echo 'QMAKE_LIBDIR_FLAGS = 
-L/ssd/tmp/ports/usr/ports/devel/qt5-qmake/work/qtbase-everywhere-src-5.10.1/lib' 
>> /ssd/tmp/ports/usr/ports/devel/qt5-qmake/work/qtbase-everywhere-src-5.10.1/.qmake.cache

Creating qmake...
===>  Building for qt5-qmake-5.10.1
gmake[1]: Entering directory 
'/ssd/tmp/ports/usr/ports/devel/qt5-qmake/work/qtbase-everywhere-src-5.10.1/qmake'
g++ -c -o main.o   -std=c++11 -ffunction-sections -g -g  
-I/ssd/tmp/ports/usr/ports/devel/qt5-qmake/work/qtbase-everywhere-src-5.10.1/qmake 
-I/ssd/tmp/ports/usr/ports/devel/qt5-qmake/work/qtbase-everywhere-src-5.10.1/qmake/library 
-I/ssd/tmp/ports/usr/ports/devel/qt5-qmake/work/qtbase-everywhere-src-5.10.1/qmake/generators 
-I/ssd/tmp/ports/usr/ports/devel/qt5-qmake/work/qtbase-everywhere-src-5.10.1/qmake/generators/unix 
-I/ssd/tmp/ports/usr/ports/devel/qt5-qmake/work/qtbase-everywhere-src-5.10.1/qmake/generators/win32 
-I/ssd/tmp/ports/usr/ports/devel/qt5-qmake/work/qtbase-everywhere-src-5.10.1/qmake/generators/mac 
-I/ssd/tmp/ports/usr/ports/devel/qt5-qmake/work/qtbase-everywhere-src-5.10.1/include 
-I/ssd/tmp/ports/usr/ports/devel/qt5-qmake/work/qtbase-everywhere-src-5.10.1/include/QtCore 
-I/ssd/tmp/ports/usr/ports/devel/qt5-qmake/work/qtbase-everywhere-src-5.10.1/include/QtCore/5.10.1 
-I/ssd/tmp/ports/usr/ports/devel/qt5-qmake/work/qtbase-everywhere-src-5.10.1/include/QtCore/5.10.1/QtCore 
-I../src/corelib/global 
-I/ssd/tmp/ports/usr/ports/devel/qt5-qmake/work/qtbase-everywhere-src-5.10.1/mkspecs/freebsd-g++ 
-DQT_VERSION_STR=\"5.10.1\" -DQT_VERSION_MAJOR=5 -DQT_VERSION_MINOR=10 
-DQT_VERSION_PATCH=1 -DQT_BUILD_QMAKE -DQT_BOOTSTRAPPED 
-DPROEVALUATOR_FULL -DQT_NO_FOREACH 
/ssd/tmp/ports/usr/ports/devel/qt5-qmake/work/qtbase-everywhere-src-5.10.1/qmake/main.cpp
gmake[1]: Leaving directory 
'/ssd/tmp/ports/usr/ports/devel/qt5-qmake/work/qtbase-everywhere-src-5.10.1/qmake'

===> Compilation failed unexpectedly.
Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure 
to

the maintainer.
*** Error code 1

# make -C /usr/ports/devel/qt5-make
-> builds successfully using clang++

--
meta
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Dropping maintainership for pydio / softether / wmconfig

[Koichiro IWAO]

I'll take the maintainership if nobody wants however
I think security/softether and security/softether-devel
should be maintained by the same maintainer.

Sato-san, would you like to maintain net/softether as well?

2018-02-22 05:50 に Tobias Kortkamp さんは書きました:

On Wed, Feb 21, 2018, at 21:23, n...@arrishq.net wrote:

Hello,

I've stopped using FreeBSD (and now enjoy meltdown and spectre patches
in time) and would - of course - like to drop maintainership for:

security/softether
www/pydio
x11-wm/wmconfig


Done.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to 
"freebsd-ports-unsubscr...@freebsd.org"


--
`whois vmeta.jp | nkf -w`
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Xrdp help needed

[Koichiro IWAO]

How xorgxrdp doesn't work?

--
`whois vmeta.jp | nkf -w`
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: MP3 licensing over - can we remove LAME restrictions?

[Koichiro IWAO]

Hi,

FYI, MP3 is coming back to Fedora. I think FreeBSD may able to do that.
https://fedoramagazine.org/full-mp3-support-coming-soon-to-fedora/

--
`whois vmeta.jp | nkf -w`
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Xrdp help needed

[Koichiro IWAO]

Hi,

Try net/xrdp-devel port. It should work well.
I'm planning to update net/xrdp port to the latest release but try 
-devel until it will be updated.


2017-05-01 02:11 に Wojciech Puchar さんは書きました:

installed xrdp from ports, done basic config and it works - i can
connect to FreeBSD server with Wyse terminal using RDP protocol. And
it works very well.

Except - no polish characters

adding
param5=-xkbmap
param6=pl

to section X11rdp in sessman - no change

right-alt+A behaves like CTRL-A not polish a-ogonek
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to 
"freebsd-ports-unsubscr...@freebsd.org"


--
`whois vmeta.jp | nkf -w`
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: devel/gvfs fails to build on 11-stable and ports r436799

[Koichiro IWAO]

It helped me too, thanks!

--
`whois vmeta.jp | nkf -w`
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: latest rust fails to install

[Koichiro IWAO]

I would also need their approval to revert anything. We are all doing
this on our spare time and bapt@ and antoine@ are very busy with many
tasks. Let's give them some more time :)


That's too bad. Reverting to unbroken state should be done quickly.
We get stuck, cannot go forward or backward for now.  Anyway, I
understand the only thing we can do is to keep waiting, thanks.

I have another question. Did the breakage commit pass review?
I can't believe such easy mistakes were overlooked.

--
`whois vmeta.jp | nkf -w`
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: latest rust fails to install

[Koichiro IWAO]

Hi,


Hi!

A patch to fix this error is being reviewed:
https://reviews.freebsd.org/D9816

Sorry for the breakage.


When will it be committed? It is still broken.
If it takes time, the breakage commit should be reverted.

--
`whois vmeta.jp | nkf -w`
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

any ssl port required, but not base

[Koichiro IWAO]

Hi,

if a port requires openssl or alternative from any port, how can I write 
Makefile?
Whichever openssl, openssl-devel, libress, and libressl-devel are ok but 
base openssl is not ok.


Regards,
--
`whois vmeta.jp | nkf -w`
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: xorg-server 1.18.4 segfaults

[Koichiro IWAO]

Konstantin,

Deinstalling llvm37 helped, thanks!


P.S.

I actually deinstalled all older versions of llvm, llvm36, llvm37.

--
`whois vmeta.jp | nkf -w`
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: xorg-server 1.18.4 segfaults

[Koichiro IWAO]

Konstantin,

Deinstalling llvm37 helped, thanks!

--
`whois vmeta.jp | nkf -w`
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

xorg-server 1.18.4 segfaults

[Koichiro IWAO]

Hi,

After recent update of xorg-server, the new xorg-server segfaults.
I'm using FreeBSD in VirtualBox so the video driver is vboxvideo.
I've already rebuilt virtualbox-ose-additions.

What can I do? I attach the xorg log.

--
`whois vmeta.jp | nkf -w`
meta [180360.851] 
X.Org X Server 1.18.4
Release Date: 2016-07-19
[180360.852] X Protocol Version 11, Revision 0
[180360.853] Build Operating System: FreeBSD 11.0-RELEASE-p2 amd64 
[180360.854] Current Operating System: FreeBSD graphite.local.haw.jp 
11.0-RELEASE-p2 FreeBSD 11.0-RELEASE-p2 #0: Mon Oct 24 06:55:27 UTC 2016 
r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64
[180360.854] Build Date: 15 February 2017  05:31:30AM
[180360.855]  
[180360.855] Current version of pixman: 0.34.0
[180360.856]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[180360.856] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[180360.867] (==) Log file: "/var/log/Xorg.20.log", Time: Wed Feb 15 11:36:51 
2017
[180360.868] (==) Using config file: "/etc/X11/xorg.conf"
[180360.868] (==) Using system config directory 
"/usr/local/share/X11/xorg.conf.d"
[180360.869] (==) No Layout section.  Using the first Screen section.
[180360.869] (==) No screen section available. Using defaults.
[180360.869] (**) |-->Screen "Default Screen Section" (0)
[180360.869] (**) |   |-->Monitor ""
[180360.870] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[180360.871] (**) Option "AutoAddDevices" "true"
[180360.871] (**) Option "AutoEnableDevices" "true"
[180360.871] (**) Automatically adding devices
[180360.871] (**) Automatically enabling devices
[180360.871] (==) Not automatically adding GPU devices
[180360.871] (==) Max clients allowed: 256, resource mask: 0x1f
[180360.871] (==) FontPath set to:
/usr/local/share/fonts/misc/,
/usr/local/share/fonts/TTF/,
/usr/local/share/fonts/OTF/,
/usr/local/share/fonts/Type1/,
/usr/local/share/fonts/100dpi/,
/usr/local/share/fonts/75dpi/
[180360.871] (==) ModulePath set to "/usr/local/lib/xorg/modules"
[180360.871] (II) The server relies on devd to provide the list of input 
devices.
If no devices become available, reconfigure devd or disable 
AutoAddDevices.
[180360.871] (II) Loader magic: 0x813b80
[180360.871] (II) Module ABI versions:
[180360.871]X.Org ANSI C Emulation: 0.4
[180360.871]X.Org Video Driver: 20.0
[180360.872]X.Org XInput driver : 22.1
[180360.872]X.Org Server Extension : 9.0
[180360.872] (--) PCI:*(0:0:2:0) 80ee:beef:: rev 0, Mem @ 
0xe000/33554432, BIOS @ 0x/65536
[180360.872] (II) "glx" will be loaded by default.
[180360.872] (II) LoadModule: "kbd"
[180360.874] (II) Loading /usr/local/lib/xorg/modules/input/kbd_drv.so
[180360.874] (II) Module kbd: vendor="X.Org Foundation"
[180360.874]compiled for 1.18.4, module version = 1.9.0
[180360.874]Module class: X.Org XInput Driver
[180360.874]ABI class: X.Org XInput driver, version 22.1
[180360.874] (II) LoadModule: "synaptics"
[180360.875] (II) Loading /usr/local/lib/xorg/modules/input/synaptics_drv.so
[180360.875] (II) Module synaptics: vendor="X.Org Foundation"
[180360.875]compiled for 1.18.4, module version = 1.9.0
[180360.876]Module class: X.Org XInput Driver
[180360.876]ABI class: X.Org XInput driver, version 22.1
[180360.876] (II) LoadModule: "glx"
[180360.876] (II) Loading /usr/local/lib/xorg/modules/extensions/libglx.so
[180360.880] (II) Module glx: vendor="X.Org Foundation"
[180360.880]compiled for 1.18.4, module version = 1.0.0
[180360.880]ABI class: X.Org Server Extension, version 9.0
[180360.880] (==) AIGLX enabled
[180360.880] (==) Matched vboxvideo as autoconfigured driver 0
[180360.880] (==) Matched modesetting as autoconfigured driver 1
[180360.880] (==) Matched scfb as autoconfigured driver 2
[180360.880] (==) Matched vesa as autoconfigured driver 3
[180360.880] (==) Assigned the driver to the xf86ConfigLayout
[180360.880] (II) LoadModule: "vboxvideo"
[180360.881] (II) Loading /usr/local/lib/xorg/modules/drivers/vboxvideo_drv.so
[180360.882] (II) Module vboxvideo: vendor="Oracle Corporation"
[180360.882]compiled for 1.18.0, module version = 1.0.1
[180360.882]Module class: X.Org Video Driver
[180360.882]ABI class: X.Org Video Driver, version 20.0
[180360.882] (**) Load address of symbol "VBOXVIDEO" is 0x80710e600
[180360.882] (II) LoadModule: "modesetting"
[180360.882] (II) Loading /usr/local/lib/xorg/modules/drivers/modesetting_drv.so
[180360.883] (II) Module modesetting: vendor="X.Org Foundation"
[180360.883]compiled for 1.18.4, module version = 1.18.4
[180360.883]Module class: X.Org Video Driver
[180360.883]ABI class: 

net/tigervnc: call for committer

[Koichiro IWAO]

Hi,

can someone grab bug 216387? it's a security update to fix memory 
overflow.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216387

I'd appreciate if you grab other bugs which I submitted.

--
`whois vmeta.jp | nkf -w`
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

dns/cli53: maintainership request

[Koichiro IWAO]

Hi,

Would someone please look at this? I'm willing to grab maintainership.
No response from maintainer more than 4 months.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214800

--
`whois vmeta.jp | nkf -w`
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: usage of openssl command in ports

[Koichiro IWAO]

Then you can just use:

${OPENSSLBASE}/bin/openssl

to run the appropriate binary.  You'ld have to use the SUB_LIST and
SUB_FILES mechanism to get the resulting value substituted into
pkg-install.in


This is what I wanted, thanks!

--
`whois vmeta.jp | nkf -w`
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

usage of openssl command in ports

[Koichiro IWAO]

Hi,

I have a question about usage of openssl command in ports.

If a port uses openssl command for example in pkg-install, how can I 
determine which openssl to use?
I think if ssl=base, /usr/bin/openssl should be used.  If ssl=openssl, 
${PREFIX}/bin/openssl should be used.

And other ssl ports.

Is there something like ${OPENSSL_CMD} or do I have to do manually like 
this?


.if ${SSL_DEFAULT} == base
OPENSSL_CMD= /usr/bin/openssl
.endif

.if ${SSL_DEFAULT} == openssl
OPENSSL_CMD= ${PREFIX}/bin/openssl
.endif

.if ${SSL_DEFAULT} == libressl
OPENSSL_CMD= "i don't know"
.endif

--
`whois vmeta.jp | nkf -w`
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

looking for a committer

[Koichiro IWAO]

Can someone look at these?

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212625
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213150

--
`whois vmeta.jp | nkf -w`
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Remmina ported to FreeBSD

[Koichiro IWAO]

Nice,

Once I've been worked on remmina port but not a former maintainer.  I 
noticed
remmina repository has freebsd branch and someone's working on remmina 
on FreeBSD.

Thanks for your great work.

BTW, avahi-gtk3 is missing in the build instruction.

--
`whois vmeta.jp | nkf -w`
meta 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: please merge www/speedtest-mini quarterly

[Koichiro IWAO]

It's done now (r395451), thanks for pointing this out.


Thanks for your quick response.


Is there any specific reason that the upstream are not willing to use
versioned distfiles?  It could be challenging for those who have never
installed this to figure out what have been changed, etc.

Cheers,


They don't disclose the reason not to use versioned distfile.
I also suffer distfile is not versioned but we still have to make an
ad hoc patch.

They just say:

Ookla Speedtest Mini application is offered as is, free of charge and
without any support. Ookla will introduce new features to it every so 
often.

This may mean that you will need to download it again periodically.
It is up to you to keep the application updated.


--
`whois vmeta.jp | nkf -w`
meta m...@vmeta.jp
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

please merge www/speedtest-mini quarterly

[Koichiro IWAO]

Hi,

I'm receiving notification of distfile checksum mismatch from 
pkg-fallout.

This is already fixed at head. Please apply the fix to quarterly.

http://beefy2.nyi.freebsd.org/data/101amd64-quarterly/395341/logs/speedtest-mini-2.1.8.20150114,1.log
http://beefy2.nyi.freebsd.org/build.html?mastername=101amd64-quarterlybuild=395341

--
`whois vmeta.jp | nkf -w`
meta m...@vmeta.jp
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: how to fetch multiple distfiles with USE_GITHUB?

[Koichiro IWAO]

Yes, I found and read that documentation soon after my first post.
Thanks for your work on documentation.

2015-08-22 08:54 に Mathieu Arnold さんは書きました:

Hi,

+--On 21 août 2015 06:29:38 + Koichiro IWAO m...@vmeta.jp wrote:
| Hello,
|
| If a port requires to fetch multiple distfiles from GitHub,
| what is the bestpractice? For example, equivalent to like this
| MASTER_SITES expression.
|
| MASTER_SITES= http://foo.example.com/distfile1.tar.gz:foo \
|http://bar.example.com/distfile2.tar.gz:bar
|
|
| AFAIK, this does not work but what I want is like this.
|
| USE_GITHUB= yes
| GH_ACCOUNT= fooproject:foo barproject:bar
| GH_PROJECT= foo:foo bar:bar
| GH_COMMIT=  deadbeef:foo deadbabe:bar

Have you tried reading our documentation ? Especially the 5.4.3.1.
Fetching Multiple Files From GitHub section from [1].

1:
https://www.freebsd.org/doc/en/books/porters-handbook/makefile-distfiles.html


--
`whois vmeta.jp | nkf -w`
meta m...@vmeta.jp
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

how to fetch multiple distfiles with USE_GITHUB?

[Koichiro IWAO]

Hello,

If a port requires to fetch multiple distfiles from GitHub,
what is the bestpractice? For example, equivalent to like this
MASTER_SITES expression.

MASTER_SITES= http://foo.example.com/distfile1.tar.gz:foo \
  http://bar.example.com/distfile2.tar.gz:bar


AFAIK, this does not work but what I want is like this.

USE_GITHUB= yes
GH_ACCOUNT= fooproject:foo barproject:bar
GH_PROJECT= foo:foo bar:bar
GH_COMMIT=  deadbeef:foo deadbabe:bar


--
`whois vmeta.jp | nkf -w`
meta m...@vmeta.jp
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Bug/199258 [new port] japanese/uim-mozc: Mozc engine for uim

[Koichiro IWAO]

Hi,

Could anyone please look at this?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199258


--
`whois vmeta.jp | nkf -w`
meta m...@vmeta.jp
___
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

devel/ruby-build call for committer

[Koichiro IWAO]

Hi,

I'm looking for a committer for this.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199436

Thanks,
--
`whois vmeta.jp | nkf -w`
meta m...@vmeta.jp
___
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: rubygems not working with ruby 2.2?

[Koichiro IWAO]

Reproduced in clean environment.

I think devel/ruby-gems is too old and needs updating.
ports version is 1.8.30 and the latest rubygems release is 2.4.6[1].

[1] https://github.com/rubygems/rubygems/releases

# confirm default ruby version is set to 2.2
grep DEFAULT_VERSIONS /etc/make.conf
DEFAULT_VERSIONS=   ruby=2.2 perl5=5.20

# remove all pkgs
pkg remove -fa

# update ports tree
portsnap fetch update

# install ruby and some rubygem- ports
make -C /usr/ports/lang/ruby22
make -C /usr/ports/devel/rubygem-rake
(snip)
===   rubygem-rake-10.4.2 depends on file: /usr/local/bin/gem22 - found
===   rubygem-rake-10.4.2 depends on file: /usr/local/bin/ruby22 - 
found

===  Configuring for rubygem-rake-10.4.2
===  Building for rubygem-rake-10.4.2
/usr/local/lib/ruby/site_ruby/2.2/rubygems/specification.rb:1960:in 
`block (2 levels) in to_yaml': stack level too deep (SystemStackError)

from /usr/local/lib/ruby/2.2/psych/coder.rb:36:in `map'
	from 
/usr/local/lib/ruby/site_ruby/2.2/rubygems/specification.rb:1959:in 
`block in to_yaml'

from /usr/local/lib/ruby/2.2/psych/deprecated.rb:19:in `call'
	from /usr/local/lib/ruby/2.2/psych/deprecated.rb:19:in `block in 
quick_emit'
	from 
/usr/local/lib/ruby/site_ruby/2.2/rubygems/specification.rb:1960:in 
`block (2 levels) in to_yaml'

from /usr/local/lib/ruby/2.2/psych/coder.rb:36:in `map'
	from 
/usr/local/lib/ruby/site_ruby/2.2/rubygems/specification.rb:1959:in 
`block in to_yaml'

from /usr/local/lib/ruby/2.2/psych/deprecated.rb:19:in `call'
 ... 9619 levels...
	from 
/usr/local/lib/ruby/site_ruby/2.2/rubygems/command_manager.rb:147:in 
`process_args'
	from 
/usr/local/lib/ruby/site_ruby/2.2/rubygems/command_manager.rb:117:in 
`run'
	from /usr/local/lib/ruby/site_ruby/2.2/rubygems/gem_runner.rb:65:in 
`run'

from /usr/local/bin/gem22:30:in `main'
=== Compilation failed unexpectedly.
Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure 
to

the maintainer.
*** Error code 1

--
`whois vmeta.jp | nkf -w`
meta m...@vmeta.jp
___
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: rubygems not working with ruby 2.2?

[Koichiro IWAO]

Does someone confirm rubygems working with ruby 2.2?

--
`whois vmeta.jp | nkf -w`
meta m...@vmeta.jp
___
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

rubygems not working with ruby 2.2?

[Koichiro IWAO]

Hello,

I switched ruby version 2.1 - 2.2 but rubygems seem not working.
I performed upgrade like ports/UPDATING 20141008.

Writing make.conf.
DEFAULT_VERSIONS= ruby=2.2

and then
portmaster -o lang/ruby22 lang/ruby21 # successfully finished
portmaster -R -r ruby-2.2 # failed with following message

===  Configuring for rubygem-activesupport-3.2.19
===  Building for rubygem-activesupport-3.2.19
/usr/local/lib/ruby/site_ruby/2.2/rubygems/specification.rb:1960:in 
`block (2 levels) in to_yaml': stack level too deep (SystemStackError)

from /usr/local/lib/ruby/2.2/psych/coder.rb:36:in `map'
from 
/usr/local/lib/ruby/site_ruby/2.2/rubygems/specification.rb:1959:in 
`block in to_yaml'

from /usr/local/lib/ruby/2.2/psych/deprecated.rb:19:in `call'
from /usr/local/lib/ruby/2.2/psych/deprecated.rb:19:in `block in 
quick_emit'
from 
/usr/local/lib/ruby/site_ruby/2.2/rubygems/specification.rb:1960:in 
`block (2 levels) in to_yaml'

from /usr/local/lib/ruby/2.2/psych/coder.rb:36:in `map'
from 
/usr/local/lib/ruby/site_ruby/2.2/rubygems/specification.rb:1959:in 
`block in to_yaml'

from /usr/local/lib/ruby/2.2/psych/deprecated.rb:19:in `call'
 ... 9619 levels...
from 
/usr/local/lib/ruby/site_ruby/2.2/rubygems/command_manager.rb:147:in 
`process_args'
from 
/usr/local/lib/ruby/site_ruby/2.2/rubygems/command_manager.rb:117:in 
`run'
from 
/usr/local/lib/ruby/site_ruby/2.2/rubygems/gem_runner.rb:65:in `run'

from /usr/local/bin/gem22:30:in `main'
=== Compilation failed unexpectedly.
Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure 
to

the maintainer.
*** Error code 1

Any ideas?
--
`whois vmeta.jp | nkf -w`
meta m...@vmeta.jp
___
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

question about PORTVERSIONing

[Koichiro IWAO]

Hi,

I have a question about determining PORTVERSION.

I was told to correct PORTVERSION 0.0..mm.dd style [1] by a 
committer.
devel/ruby-build port now has mmdd style PORTVERSION like 20141028 
and
mmdd is the upstream's official versioning system.  I'm not using 
date

instead of version number since upstream has no version information but
just using through upstream version to PORTVERSION.

Do I have to use 0.0..mm.dd in such case?

[1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194646

--
`whois vmeta.jp | nkf -w`
meta m...@vmeta.jp
___
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: question about PORTVERSIONing

[Koichiro IWAO]

I use upstream version as it is, thanks!

2014-11-13 12:04 Bryan Drewery wrote:

On 11/12/2014 8:16 PM, Koichiro IWAO wrote:

Hi,

I have a question about determining PORTVERSION.

I was told to correct PORTVERSION 0.0..mm.dd style [1] by a 
committer.
devel/ruby-build port now has mmdd style PORTVERSION like 20141028 
and
mmdd is the upstream's official versioning system.  I'm not using 
date
instead of version number since upstream has no version information 
but

just using through upstream version to PORTVERSION.

Do I have to use 0.0..mm.dd in such case?

[1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194646



Use whatever you want as long as it is monotonically increasing. No
requirement for 0.0. You can use MMDD or .MM. if you 
wish.
If upstream tags their releases like this it is even better to follow 
it.


The idea of using 0.0. in front is a just in case upstream follows 
a

new tag scheme, but we already have PORTEPOCH for those situations. Why
add an arbitrary 0.0 into the tag if upstream doesn't use that?


--
`whois vmeta.jp | nkf -w`
meta m...@vmeta.jp
___
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: bash velnerability

[Koichiro IWAO]

I think not yet[1]. But it will be shortly updated to patched version because
the vulnerability is already documented written in security/vuxml [2]. That
means port committer(s) already aware of the bash vulnerability.

[1] 
http://svnweb.freebsd.org/ports/head/shells/bash/Makefile?revision=369185view=markup
[2] http://svnweb.freebsd.org/ports?view=revisionrevision=369192


On Thu, Sep 25, 2014 at 11:58:30AM +0530, Riyaz T.K wrote:
 Hi,
 
 https://www.freebsd.org/cgi/ports.cgi?query=The+GNU+Project%27s+Bourne+Again+SHellstype=textsektion=all
 
 Is this version patched from the bash vulnerability?
 
 https://access.redhat.com/articles/1200223
 
 
 
 
 -- 
 Riyaz T K
 Admod Technologies
 ___
 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

-- 
`whois vmeta.jp | nkf -w`
meta m...@vmeta.jp
___
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: bash velnerability

[Koichiro IWAO]

Please let me make corrections.  The shellshock bash vulnerabilities are 
described by 2 CVEs.
 - CVE-2014-6271
 - CVE-2014-7169

The first CVE is already fixed in latest freebsd ports tree (r369185),
so far the second CVE is not fixed yet.

On Thu, Sep 25, 2014 at 11:58:30AM +0530, Riyaz T.K wrote:
 Hi,
 
 https://www.freebsd.org/cgi/ports.cgi?query=The+GNU+Project%27s+Bourne+Again+SHellstype=textsektion=all
 
 Is this version patched from the bash vulnerability?
 
 https://access.redhat.com/articles/1200223
 
 
 
 
 -- 
 Riyaz T K
 Admod Technologies
 ___
 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

-- 
`whois vmeta.jp | nkf -w`
meta m...@vmeta.jp
___
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

pkg-fallout USE_PACKAGE_DEPENDS_ONLY and SIGERR?

[Koichiro IWAO]

Hello,

How can I fix following two pkg-fallout notifications?  The one of them 
is about
dependency, another one is SIGERR.  I have no idea how to fix it.  
Please help.


===   USE_PACKAGE_DEPENDS_ONLY set - not building missing dependency 
from source

*** Error code 1

Stop.
make: stopped in /usr/ports/japanese/font-ricty



==  Building for ja-font-ricty-discord-3.2.3
cd 
/wrkdirs/usr/ports/japanese/font-ricty-discord/work/yascentur-Ricty-0fd7047 

/bin/sh 
/wrkdirs/usr/ports/japanese/font-ricty-discord/work/yascentur-Ricty-0fd7047/ricty_generator.sh
/usr/local/lib/X11/fonts/OTF/Inconsolata.otf  
/usr/local/lib/X11/fonts/TTF/migu-1m-regular.ttf

/usr/local/lib/X11/fonts/TTF/migu-1m-bold.ttf
Ricty Generator 3.2.3b

Author: Yasunori Yusa lastname at save.sys.t.u-tokyo.ac.jp

This script is to generate ``Ricty'' font from Inconsolata and Migu 1M.
It requires 2-5 minutes to generate Ricty. Owing to SIL Open Font 
License
Version 1.1 section 5, it is PROHIBITED to distribute the generated 
font.


trap: bad signal ERR
*** Error code 2

Stop in /usr/ports/japanese/font-ricty-discord.
*** Error code 1


http://beefy2.isc.freebsd.org/data/10amd64-quarterly/2014-08-27_15h21m01s/logs/ja-font-ricty-3.2.3.log
http://beefy1.isc.freebsd.org/data/84i386-default/2014-08-15_14h18m35s/logs/ja-font-ricty-discord-3.2.3.log

--
`whois vmeta.jp | nkf -w`
meta m...@vmeta.jp
___
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.3.5.1 -1.3.6: Repository has incompatible checksum format, need to re-create database

[Koichiro IWAO]

Try `pkg update`. It might be `pkg update -f`.

On Wed, Aug 13, 2014 at 05:30:08PM -0700, Russell L. Carter wrote:
 Greetings,
 
 I just upgraded pkg, and see this:
 
 $ pkg clean
 pkg: Repository pinyon has incompatible checksum format, need to
 re-create database
 Nothing to do.
 
 How do I recreate the database?  This is a poudriere version
 3.0.17 maintained pkg repo.
 
 On a different system, using the same poudriere maintained
 repo, with pkg 1.3.5.1 I don't see the re-create notice.
 
 Both systems fairly fresh currents.
 
 Russell
 ___
 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

-- 
`whois vmeta.jp | nkf -w`
meta m...@vmeta.jp
___
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: archivers/rpm build problem

[Koichiro IWAO]

On Wed, Jul 02, 2014 at 08:25:50AM +0200, Baptiste Daroussin wrote:
 I can confirm the problem and will see if I can fix, I was wondering why do 
 you
 or other people use rpm for? I am planning to remove archivers/rpm and
 recommanding using archivers/rpm4 instead, so I need to need any corner case
 where rpm4 cannot do rpm3 job.
 
 btw the linux ports now directly use plain bsdtar :)

Can't argue with migrating rpm from 3 to 4.
At least I still use rpm. Not for extracting rpms but evaluating
rpm macros like 'rpm --eval %_bindir'.

-- 
`whois vmeta.jp | nkf -w`
meta m...@vmeta.jp
___
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: archivers/rpm build problem

[Koichiro IWAO]

I also met the same failure. Not resolved yet.

--
`whois vmeta.jp | nkf -w`
meta m...@vmeta.jp
___
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: bugzilla auto committer assignment?

[Koichiro IWAO]

I'm not a perl specialist but I'd like to help something I can do.

It looks someone already works on auto assignment.  I'll wait for that
and help something else as much as I can do.

Thanks,

On Tue, Jun 10, 2014 at 10:23:17PM -0700, Eitan Adler wrote:
 On 10 June 2014 18:47, Koichiro IWAO m...@vmeta.jp wrote:
  Hi,
 
  I know bug tracking system moved to bugzilla but have some questions.
  Is automatic committer assignment implemented?  Is notification email
  sent to the maintainer when someone opened a new bug?
 
 Not yet.  Want to help!?
 
 
  GNATS assigned a committer automatically in a few minutes when I submit
  a PR but bugzilla looks no.  My bugs status are still Needs Triage [1].
  I don't want to overlook patches sent to the ports I maintain.
 
 Its on the list of things we want to get done ASAP.  The requirements
 are simple but someone that knows perl needs to volunteer to help :)
 
 
 -- 
 Eitan Adler
 ___
 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

-- 
`whois vmeta.jp | nkf -w`
meta m...@vmeta.jp
___
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 ports that you maintain require staging updates

[Koichiro IWAO]

I'll take japanese/font-ricty and sysutils/jfbterm.

On Mon, Jun 09, 2014 at 11:48:02AM -0500, Bryan Drewery wrote:
 If you see a port in here that you use and wish to keep working please
 consider becoming maintainer of it. Submit a PR with a patch to stage it
 and take maintainership of it.
 
 We need all the help we can get. It's easy to get involved. I myself 
 started
 by sending a PR here and there.
 
 Bryan
 

-- 
`whois vmeta.jp | nkf -w`
meta m...@vmeta.jp
___
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

bugzilla auto committer assignment?

[Koichiro IWAO]

Hi,

I know bug tracking system moved to bugzilla but have some questions.
Is automatic committer assignment implemented?  Is notification email
sent to the maintainer when someone opened a new bug?

GNATS assigned a committer automatically in a few minutes when I submit
a PR but bugzilla looks no.  My bugs status are still Needs Triage [1].
I don't want to overlook patches sent to the ports I maintain.


[1] 
https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=Needs%20Triagecomponent=Individual%20Port%28s%29email1=vmeta.jpemailreporter1=1emailtype1=substringlist_id=3718order=Importanceproduct=Ports%20Treequery_format=advancedresolution=---

Rgds,
-- 
`whois vmeta.jp | nkf -w`
meta m...@vmeta.jp
___
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

update linux-sun-j{dk,re}17 to update 60

[Koichiro IWAO]

Would you please update linux-sun-jdk17 to update 60?
linux-sun-jdk17 port says:

===  linux-sun-jre17-7.55 You must manually fetch the J2SE RE download
for the Linux platform (jre-7u60-linux-i586.tar.gz) from
http://www.oracle.com/technetwork/java/javase/downloads/index.html,
place it in /usr/ports/distfiles and then run make again.
*** Error code 1

but jdk-7u55-linux-i586.tar.gz is unavailable. Only the latest
jre-7u60-linux-i586.tar.gz is available on the Oracle site.

-- 
`whois vmeta.jp | nkf -w`
meta m...@vmeta.jp
___
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: archivers/rpm fails to build probably due to my local issue

[Koichiro IWAO]

I still fails to build today but thanks. I will look for my
envitonment again.

On Fri, May 09, 2014 at 11:58:12AM +0200, Alex Dupre wrote:
 Koichiro IWAO ha scritto:
  archivers/rpm fails to build around aclocal macro.
 
 Same issue yesterday, today it builds fine.
 
 -- 
 Alex Dupre
 ___
 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
 

-- 
`whois vmeta.jp | nkf -w`
meta m...@vmeta.jp
___
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 java/linux-sun-jdk18 added?

[Koichiro IWAO]

I read commit message and got what happened, thanks.

On Thu, Apr 10, 2014 at 10:40:24AM +0200, Alex Dupre wrote:
 Koichiro IWAO ha scritto:
  java/linux-sun-jdk18 was added just now but isn't it identical to
  java/linux-oracle-jdk18 ? Why -sun- port is needed?
 
 It was removed 30 minutes after the commit :-)
 
 -- 
 Alex Dupre
 

-- 
`whois vmeta.jp | nkf -w`
meta m...@vmeta.jp
___
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

Why java/linux-sun-jdk18 added?

[Koichiro IWAO]

java/linux-sun-jdk18 was added just now but isn't it identical to
java/linux-oracle-jdk18 ? Why -sun- port is needed?

% sha256 linux-oracle-jdk1.8.0/bin/java linux-sun-jdk1.8.0/bin/java
SHA256 (linux-oracle-jdk1.8.0/bin/java) = 
1067e37067c2b98ea9166d80b4f0c598e17cf4376e620cfd4141eee7e3b1c4ce
SHA256 (linux-sun-jdk1.8.0/bin/java) = 
1067e37067c2b98ea9166d80b4f0c598e17cf4376e620cfd4141eee7e3b1c4ce

-- 
`whois vmeta.jp | nkf -w`
meta m...@vmeta.jp
___
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

annoying pkg-fallout notices, how can I stop it?

[Koichiro IWAO]

I receive following pkg-fallout notices and they're annoying.
It says failed in checksums but I fixed checksums weeks ago.
Why pkg-fallout notices such old checksum mismatches?
How can I stop it?

Maintainer: meta+po...@vmeta.jp
Last committer: swi...@freebsd.org
Ident:  $FreeBSD: branches/2014Q1/net/xrdp/Makefile 333810 
2013-11-15 01:26:42Z swills $
Log URL:
http://beefy1.isc.freebsd.org/bulk/10i386-quarterly/2014-03-12_01h01m59s/logs/xrdp-0.6.1_1,1.log
Build URL:  
http://beefy1.isc.freebsd.org/bulk/10i386-quarterly/2014-03-12_01h01m59


Maintainer: meta+po...@vmeta.jp
Last committer: swi...@freebsd.org
Ident:  $FreeBSD: branches/2014Q1/net/xrdp/Makefile 333810 
2013-11-15 01:26:42Z swills $
Log URL:
http://beefy1.isc.freebsd.org/bulk/10i386-quarterly/2014-03-12_01h01m59s/logs/xrdp-0.6.1_1,1.log
Build URL:  
http://beefy1.isc.freebsd.org/bulk/10i386-quarterly/2014-03-12_01h01m59s


Maintainer: meta+po...@vmeta.jp
Last committer: swi...@freebsd.org
Ident:  $FreeBSD: branches/2014Q1/net/xrdp-devel/Makefile 333912 
2013-11-15 19:10:29Z swills $
Log URL:
http://beefy1.isc.freebsd.org/bulk/10i386-quarterly/2014-03-12_01h01m59s/logs/xrdp-devel-0.7.0.b20130912_1,1.log
Build URL:  
http://beefy1.isc.freebsd.org/bulk/10i386-quarterly/2014-03-12_01h01m59s


Maintainer: meta+po...@vmeta.jp
Last committer: swi...@freebsd.org
Ident:  $FreeBSD: branches/2014Q1/net/xrdp-devel/Makefile 333912 
2013-11-15 19:10:29Z swills $
Log URL:
http://beefy2.isc.freebsd.org/bulk/10amd64-quarterly/2014-03-12_01h01m40s/logs/xrdp-devel-0.7.0.b20130912_1,1.log
Build URL:  
http://beefy2.isc.freebsd.org/bulk/10amd64-quarterly/2014-03-12_01h01m40s


--
`whois vmeta.jp | nkf -w`
meta m...@vmeta.jp
___
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: annoying pkg-fallout notices, how can I stop it?

[Koichiro IWAO]

On Wed, Mar 12, 2014 at 02:12:21PM +0100, John Marino wrote:
 You get the idea.
 You fixed head, you didn't fix the quarterly branches.
 How you can stop it?
 MFC your fix to quarterly branch.

OK, I was blind. Very similar question has been posted hours ago.
Then, how do I request merge from head to the branch? May I ask you to
do that via this e-mail or should I send-pr? or other way?

-- 
`whois vmeta.jp | nkf -w`
meta m...@vmeta.jp
___
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/182294: sysutils/fsc not forked to background at start

[Koichiro IWAO]

Would someone please commit ports/182294?
sysutils/fsc is a useful tool except for its poor rc script.
http://www.freebsd.org/cgi/query-pr.cgi?pr=182294

--
`whois vmeta.jp | nkf -w`
meta m...@vmeta.jp
___
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: graphics/libjpeg-turbo in place of graphics/jpeg

[Koichiro IWAO]

+1

On Tue, Feb 11, 2014 at 5:27 AM, Jakub Lach jakub_l...@mailplus.pl 
wrote:

Currently, I reckon that libjpeg-turbo is a drop in replacement
for graphics/jpeg. Unfortunately, most ports have a direct
dependency on graphics/jpeg and will complain if it is missing[1].

Is there any way to achieve that and keep pkng happy?


See PR 180159

http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/180159

This PR adds a new USES feature for jpeg allowing the appropriate jpeg
port to be selected.

Then all jpeg using ports would need to be modified as stated in the 
PR.


Could someone commit this PR.

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


--
`whois vmeta.jp | nkf -w`
meta m...@vmeta.jp
___
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: net/tightvnc: taking maintainership

[Koichiro IWAO]

delphij@ quickly did. I submit a PR for the next time.

Thanks,

On Tue, Jan 21, 2014 at 09:48:51AM +0900, Koichiro IWAO wrote:
 I do maintain net/tightvnc. Please set the maintainer to 
 meta+po...@vmeta.jp.
 
 Thanks,
 -- 
 `whois vmeta.jp | nkf -w`
 meta m...@vmeta.jp
 

-- 
`whois vmeta.jp | nkf -w`
meta m...@vmeta.jp
___
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

net/tightvnc: taking maintainership

[Koichiro IWAO]

I do maintain net/tightvnc. Please set the maintainer to 
meta+po...@vmeta.jp.


Thanks,
--
`whois vmeta.jp | nkf -w`
meta m...@vmeta.jp
___
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

working on gnome-rdp port, please update wiki

[Koichiro IWAO]

I'm porting gnome-rdp listed on wanted ports.
Would someone please update the wiki page?

https://wiki.freebsd.org/WantedPorts

--
`whois vmeta.jp | nkf -w`
meta m...@vmeta.jp
___
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