Dear port maintainer,
The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
The 2020Q3 branch has been created. It means that the next update on the
quarterly packages will be on the 2020Q3 branch.
A lot of things happened in the last three months:
- - pkg 1.14.6
- - Default version of Lazarus switched to 2.0.8
- - New
Hi!
Trying to upgrade on a machine recently upgraded from 11.1 to 11.3,
this happens:
pkg upgrade -f pkg
Updating ... repository catalogue...
... repository is up to date.
All repositories are up to date.
The following 1 package(s) will be affected (of 0 checked):
Installed packages to be DOWNGR
## Kurt Jaeger (p...@opsec.eu):
> pkg upgrade -f pkg
> Updating ... repository catalogue...
> ... repository is up to date.
> All repositories are up to date.
So what repo is that and what does it offer?
> Installed packages to be DOWNGRADED:
> pkg: 1.14.6 -> 1.10.5_1
>
> Why does pkg i
On Sat, Jul 4, 2020 at 20:12 Kurt Jaeger wrote:
> Hi!
>
> Trying to upgrade on a machine recently upgraded from 11.1 to 11.3,
> this happens:
>
> pkg upgrade -f pkg
> Updating ... repository catalogue...
> ... repository is up to date.
> All repositories are up to date.
> The following 1 package(
Hi!
> > pkg upgrade -f pkg
> > Updating ... repository catalogue...
> > ... repository is up to date.
> > All repositories are up to date.
>
> So what repo is that and what does it offer?
That's repo.nepustil.net, which is mostly up2date.
> > Installed packages to be DOWNGRADED:
> > pkg
Hi!
> > Trying to upgrade on a machine recently upgraded from 11.1 to 11.3,
> > this happens:
> >
> > pkg upgrade -f pkg
> > Updating ... repository catalogue...
> > ... repository is up to date.
> > All repositories are up to date.
> > The following 1 package(s) will be affected (of 0 checked):
>
## Kurt Jaeger (p...@opsec.eu):
> > So what repo is that and what does it offer?
>
> That's repo.nepustil.net, which is mostly up2date.
Are you sure you got the right path there? Any leftovers in /etc/pkg/
or /usr/local/etc/pkg/ ?
You could grab packagesite.txz from your repo, untar that and the
Hi!
> > > So what repo is that and what does it offer?
> > That's repo.nepustil.net, which is mostly up2date.
> Are you sure you got the right path there?
Yes.
> Any leftovers in /etc/pkg/ or /usr/local/etc/pkg/ ?
None that I'm aware of.
> You could grab packagesite.txz from your repo, untar
I use 'poudriere' to maintain my ports. I still have a few ports that
depend on the depreciated py27. What is the recommended method to
update these ports? I was thinking of placing this in the
"poudriere.d/make.conf" file:
DEFAULT_VERSIONS+=python=3.7
DEFAULT_VERSIONS+=python2=3.7
DEFAULT_VERSION
Hi!
> I use 'poudriere' to maintain my ports. I still have a few ports that
> depend on the depreciated py27. What is the recommended method to
> update these ports? I was thinking of placing this in the
> "poudriere.d/make.conf" file:
>
> DEFAULT_VERSIONS+=python=3.7
> DEFAULT_VERSIONS+=python2=
On Sat, 4 Jul 2020 16:11:29 +0200, Kurt Jaeger stated:
>Hi!
>
>> I use 'poudriere' to maintain my ports. I still have a few ports that
>> depend on the depreciated py27. What is the recommended method to
>> update these ports? I was thinking of placing this in the
>> "poudriere.d/make.conf" file:
>
Hi!
> >> update these ports? I was thinking of placing this in the
> >> "poudriere.d/make.conf" file:
[...]
> What I have never been able to get a definitive answer to is exactly
> what the "+" does or if it is even needed, I have seen
> 'default_versions" both with and without it.
The file is re
On 2020-07-04 16:30, Carmel wrote:
What I have never been able to get a definitive answer to is exactly
what the "+" does or if it is even needed, I have seen
'default_versions" both with and without it.
The way I understand it, += appends. Thus:
FOO=bar
FOO+=quux
will result in FOO having the
## Kurt Jaeger (p...@opsec.eu):
> > You could grab packagesite.txz from your repo, untar that and then
> > grep '"name":"pkg"' packagesite.yaml
> > Any brokenness in /var/db/pkg/ ?
>
> How would I recognize brokenness ? The files that should be there
> are there.
I'm afraid I have to go full Ann
## Carmel (carmel...@outlook.com):
> DEFAULT_VERSIONS+=python2=3.7
Forcing python 2 to be python 3.7 will probably break - as far as I can
see, there're safeguards in place which will prevent this. In most cases,
the python2 dependency is there because upstream hasn't updated their
code yet. (Tha
On 04 Jul 2020, at 08:30, Carmel wrote:
> I see that you are putting it all on one line. That is probably easier.
> I like the separate entries technique simply because I find it easier
> to read myself or quickly comment out an entry.
I agree that separate lines have advantages. When making chan
Hello.
As for packages that require py27-*, I think it's better to leave it to
poudriere.
Then I think the py27-* package can be cleaned up with the following
command.
# If you are running poudriere bulk as follows.
# poudriere bulk -f ~/pkglist -j name
poudriere pkgclean -f ~/pkglist -j name
I have gotten a couple of emails from portscout about ports that need updated
and maintained. Before I go about updating and maintaining these ports I wanted
to do some practice on a couple that I use like x11/nvidia-settings. I have
recieved alot of help on the forums and from the documentation
On Sun, 5 Jul 2020 at 12:47, Brandon helsley
wrote:
>
> I have gotten a couple of emails from portscout about ports that need updated
> and maintained. Before I go about updating and maintaining these ports I
> wanted to do some practice on a couple that I use like x11/nvidia-settings. I
> have
This is my personal workflow:
1. Take a simple copy of the port into my working directory
2. Get the port working in my working directory.
3. cd my-working-directory
4. diff -ruN /usr/ports/x11/nvidia-settings . > /tmp/nvidia-settings.patch
5. submit patch onto bugs
Hi.
It has been a while since seamonkey was removed from ports.
I attempted to build latest seamonkey but it fails with compiler error.
I'm wondering if anyone keeping up to date local seamonkey port and also
wishing to share.
Hiro
___
freebsd-ports@f
On Sun, 5 Jul 2020 at 14:06, Brandon helsley
wrote:
[...]
>
> Yes it does, I understand how it works now, I just needed an example, and I
> can compare this with other methods to figure it out. How do you get the port
> working in your directory?
In general:
1. extract the original sources els
23 matches
Mail list logo
