Re: Why builds use 13.0-RELEASE and not 13.1-RELEASE?

2022-07-28 Thread Yasuhiro Kimura 
From: Yuri 
Subject: Why builds use 13.0-RELEASE and not 13.1-RELEASE?
Date: Wed, 27 Jul 2022 23:26:07 -0700

> Shouldn't builds use the last released version?
> 
> 
> Thanks,
> 
> Yuri

It is because 13.0-RELEASE is still supported. official packages for
one major version are built on the system with the oldest minor
version of the same major version. 13.0-RELEASE reaches it EoL on
August 31th. So after that official packages will be built on
13.1-RELEASE.

---
Yasuhiro Kimura

Commit PR 264043

2022-07-28 Thread Osipov, Michael 
Guys,

please commit the supplied patch. devel/py-click is broken for months.

Michael

Re: Commit PR 264043

2022-07-28 Thread Kurt Jaeger 
Hi!

> please commit the supplied patch. devel/py-click is broken for months.

Done.

-- 
p...@opsec.eu+49 171 3101372Now what ?

make config stopped working

2022-07-28 Thread Daniel Braniss 
hi,
after todays’ git pull, for example if i do:

cd /usr/ports/editors/emacs
make config
i get

===> Options unchanged

tried make clean, but still the same. make show options
shows the options!

cheers,
danny

Re: make config stopped working

2022-07-28 Thread Kurt Jaeger 
Hi!

> after todays??? git pull, for example if i do:
> 
> cd /usr/ports/editors/emacs
> make config
> i get
> 
> ===> Options unchanged
> 
> tried make clean, but still the same. make show options
> shows the options!

I had a similar problem, and it turned out that

dialog4ports

was no longer working:

ld-elf.so.1: Shared object "libdialog.so.9" not found, required by 
"dialog4ports"

I fixed it with:

pkg install -f dialog4ports

-- 
p...@opsec.eu+49 171 3101372Now what ?

Re: Commit PR 265028 and PR 265025

2022-07-28 Thread Kurt Jaeger 
Hi!

> please commit both PRs for devel/maven and devel/maven-wrapper. All necessary
> data is provided in both issues.

Done, thanks for the patches.

-- 
p...@opsec.eu+49 171 3101372Now what ?

Re: make config stopped working

2022-07-28 Thread Daniel Braniss 



> On 28 Jul 2022, at 18:41, Kurt Jaeger  wrote:
> 
> Hi!
> 
>> after todays??? git pull, for example if i do:
>> 
>> cd /usr/ports/editors/emacs
>> make config
>> i get
>> 
>> ===> Options unchanged
>> 
>> tried make clean, but still the same. make show options
>> shows the options!
> 
> I had a similar problem, and it turned out that
> 
> dialog4ports
> 
> was no longer working:
> 
> ld-elf.so.1: Shared object "libdialog.so.9" not found, required by 
> "dialog4ports"
> 
> I fixed it with:
> 
> pkg install -f dialog4ports

BINGO!

now next problem:
pkg update
failes! i solved it by copying the sqlite file it from another host, but still 
a problem.

thanks,
danny

> 
> -- 
> p...@opsec.eu+49 171 3101372Now what ?
>

review needed for a manual Python port

2022-07-28 Thread Robert Clausecker 
Greetings!

I have tried to package uiCA, the uops.info Code Analyzer.  This is
a Python project, but without setuptools or anything.  Unfortunately
I don't know much about Python packaing and have just tried to wing
it.  I would appreciate some review on the port.

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

The port also seemingly exposes a bug in Portlint's PORTVERSION
checking regex (PR #265364).  Might need to be checked out, too.

Thank you for your help!

Yours,
Robert Clausecker

-- 
()  ascii ribbon campaign - for an 8-bit clean world 
/\  - against html email  - against proprietary attachments

Unmaintained FreeBSD ports which are out of date

2022-07-28 Thread portscout 
Dear port maintainers,

The portscout new distfile checker has detected that one or more
unmaintained ports appears to be out of date. Please take the opportunity
to check each of the ports listed below, and if possible and appropriate,
submit/commit an update. Please consider also adopting this port.
If any ports have already been updated, you can safely ignore the entry.

An e-mail will not be sent again for any of the port/version combinations
below.

Full details can be found at the following URL:
http://portscout.freebsd.org/po...@freebsd.org.html


Port| Current version | New version
+-+
finance/moneymanagerex  | 1.2.7   | v1.5.18
+-+
textproc/redisearch | 2.2.10  | v2.4.11
+-+


If any of the above results are invalid, please check the following page
for details on how to improve portscout's detection and selection of
distfiles on a per-port basis:

http://portscout.freebsd.org/info/portscout-portconfig.txt

Reported by:portscout!

Handling conflicts and cherry-pick to 2022Q3 issue

2022-07-28 Thread Nuno Teixeira 
Hello,

I'm trying to commit to 2022Q3 PR 265530
 and after
solving Makefile conflicts (PORTREVISIONs), git push gives the error:

---

remote: Some parts of your commit look suspiciously like merge
remote: conflict markers.  Please double-check your diff and try
remote: committing again.
remote: 
remote:
To gitrepo.freebsd.org:ports.git
 ! [remote rejected]   2022Q3 -> 2022Q3 (pre-receive hook declined)
error: failed to push some refs to 'gitrepo.freebsd.org:ports.git'
---

Any hints on how to solve it?

Thanks in advance,

Nuno Teixeira

Re: Handling conflicts and cherry-pick to 2022Q3 issue

2022-07-28 Thread Michael Gmelin 
Look at what you’re trying to commit and check if there are any conflict marker 
(>>>, <>, =).

> On 28. Jul 2022, at 23:44, Nuno Teixeira  wrote:
> 
> 
> Hello,
> 
> I'm trying to commit to 2022Q3 PR 265530 and after solving Makefile conflicts 
> (PORTREVISIONs), git push gives the error:
> 
> ---
> 
> remote: Some parts of your commit look suspiciously like merge
> remote: conflict markers.  Please double-check your diff and try
> remote: committing again.
> remote: 
> remote:
> To gitrepo.freebsd.org:ports.git
>  ! [remote rejected]   2022Q3 -> 2022Q3 (pre-receive hook declined)
> error: failed to push some refs to 'gitrepo.freebsd.org:ports.git'
> ---
> 
> Any hints on how to solve it?
> 
> Thanks in advance,
> 
> Nuno Teixeira
> 
> 
>

Re: Handling conflicts and cherry-pick to 2022Q3 issue

2022-07-28 Thread Nuno Teixeira 
yes it is

Michael Gmelin  escreveu no dia quinta, 28/07/2022 à(s)
23:35:

> Look at what you’re trying to commit and check if there are any conflict
> marker (>>>, <>, =).
>
> On 28. Jul 2022, at 23:44, Nuno Teixeira  wrote:
>
> 
> Hello,
>
> I'm trying to commit to 2022Q3 PR 265530
>  and after
> solving Makefile conflicts (PORTREVISIONs), git push gives the error:
>
> ---
> 
> remote: Some parts of your commit look suspiciously like merge
> remote: conflict markers.  Please double-check your diff and try
> remote: committing again.
> remote: 
> remote:
> To gitrepo.freebsd.org:ports.git
>  ! [remote rejected]   2022Q3 -> 2022Q3 (pre-receive hook declined)
> error: failed to push some refs to 'gitrepo.freebsd.org:ports.git'
> ---
>
> Any hints on how to solve it?
>
> Thanks in advance,
>
> Nuno Teixeira
>
>
>
>

Re: Handling conflicts and cherry-pick to 2022Q3 issue

2022-07-28 Thread Nuno Teixeira 
Fixed and committed, thanks

Nuno Teixeira  escreveu no dia quinta, 28/07/2022 à(s)
23:36:

> yes it is
>
> Michael Gmelin  escreveu no dia quinta, 28/07/2022
> à(s) 23:35:
>
>> Look at what you’re trying to commit and check if there are any conflict
>> marker (>>>, <>, =).
>>
>> On 28. Jul 2022, at 23:44, Nuno Teixeira  wrote:
>>
>> 
>> Hello,
>>
>> I'm trying to commit to 2022Q3 PR 265530
>>  and after
>> solving Makefile conflicts (PORTREVISIONs), git push gives the error:
>>
>> ---
>> 
>> remote: Some parts of your commit look suspiciously like merge
>> remote: conflict markers.  Please double-check your diff and try
>> remote: committing again.
>> remote: 
>> remote:
>> To gitrepo.freebsd.org:ports.git
>>  ! [remote rejected]   2022Q3 -> 2022Q3 (pre-receive hook
>> declined)
>> error: failed to push some refs to 'gitrepo.freebsd.org:ports.git'
>> ---
>>
>> Any hints on how to solve it?
>>
>> Thanks in advance,
>>
>> Nuno Teixeira
>>
>>
>>
>>