FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed 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 +-+ lang/opencoarrays | 2.7.1 | 2.9.0 +-+ textproc/libextractor | 1.9 | 1.10 +-+ 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! ___ 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"
New 2020Q3 branch
-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 default version for Java: 8 - - Firefox 78.0.1 - - Firefox-esr 68.10.0 - - Chromium 83.0.4103.116 - - Ruby 2.5.8, 2.6.6, 2.7.1 - - Qt5 5.14.2 - - CHANGES entries 20200414, 20200514, 20200531 Next quarterly package builds will start on Saturday 2020-07-04 01:00 UTC and should be available on your closest mirrors few days later. For those stat nerds out there, here's what happened during the last 3 months on head: Number of commits: 10315 Number of committers: 178 Most active committers: 3557 sunpoet 757 yuri 448 jbeich 285 tcberner 224 tobik 197 dbaio 182 amdmi3 161 tagattie 157 pkubaj 154 fernape Diffstat: 21847 files changed, 532252 insertions(+), 311634 deletions(-) and on the 2020Q2 branch: Number of commits: 476 Number of committers: 65 Most active committers: 106 jbeich 40 linimon 28 rene 25 pkubaj 20 mandree 18 joneum 18 dbaio 11 tcberner 10 sunpoet 10 kai Diffstat: 1539 files changed, 45748 insertions(+), 14012 deletions(-) Regards, René -BEGIN PGP SIGNATURE- iQGyBAEBCgCcFiEE+zdFyG8V6O2sgTL82ClOw7vE19UFAl8AV0pfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEZC Mzc0NUM4NkYxNUU4RURBQzgxMzJGQ0Q4Mjk0RUMzQkJDNEQ3RDUeHHBvcnRtZ3It c2VjcmV0YXJ5QGZyZWVic2Qub3JnAAoJENgpTsO7xNfVHvUH/jouOAb5MXu/5iW5 ws4e9n8QoEHvd4ux8RsjUi/ZsHk8NbIpAWAN7q8n+eLnQBD4VKXyhIDpjmsrVyc8 N+95gfHMsTCrdpVe8W+fx2pppgj9B8Cg9K8Li9JO6wqxd/8SMI9a+k5HiUTciwkR Nzu57XVU8U7JFI1AKWI5ZagFIJHz4BqAL6e2+VfyE9vqxhUAk9YRbkDPRUpf75MT 6iA2PAPcOjj41T8Hxd971RTMJ7AaguqJ6VtCk62Th41XkRlpB3aZkMTQQ7ntwxp5 kHHY+xgXX0ZIeFJ6nBj64/DihWF/ZXTGVzaHbg6DygoGOG/XOK9ZmWOwiNsiloOc WqVWTHU= =Rl39 -END PGP SIGNATURE- ___ 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 does pkg try to install an older version of 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): Installed packages to be DOWNGRADED: pkg: 1.14.6 -> 1.10.5_1 Why does pkg insist on downgrading pkg ? How can this be fixed ? -- p...@opsec.eu+49 171 3101372Now what ? ___ 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 does pkg try to install an older version of pkg ?
## 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 insist on downgrading pkg ? How can this be fixed ? You are forcing "reinstallation or upgrade" (pkg-upgrade(8)) and if you have a stale repo which only offers that old pkg (is that perchance a 11.1 repo?)... that's what you get. Regards, Christoph -- Spare Space ___ 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 does pkg try to install an older version of pkg ?
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(s) will be affected (of 0 checked): > > Installed packages to be DOWNGRADED: > pkg: 1.14.6 -> 1.10.5_1 > > Why does pkg insist on downgrading pkg ? How can this be fixed ? Is the pkg branch used changed from latest to quarterly? Li-Wen > ___ 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 does pkg try to install an older version of pkg ?
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: 1.14.6 -> 1.10.5_1 > > > > Why does pkg insist on downgrading pkg ? How can this be fixed ? > > You are forcing "reinstallation or upgrade" (pkg-upgrade(8)) and > if you have a stale repo which only offers that old pkg (is that > perchance a 11.1 repo?)... that's what you get. It's a 11.3 repo, that's why I'm wondering... -- p...@opsec.eu+49 171 3101372Now what ? ___ 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 does pkg try to install an older version of 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): > > > > Installed packages to be DOWNGRADED: > > pkg: 1.14.6 -> 1.10.5_1 > > Why does pkg insist on downgrading pkg ? How can this be fixed ? > Is the pkg branch used changed from latest to quarterly? It's our own repo, which regularly rebuilds all the ports we use... That's what is so surprising to me. The previous pkg version was indeed 1.10.5_1, but I do not understand why pkg insists to install this. I've already replaced it with a copy of pkg-1.14.6, via: pkg add -f pkg-1.14.6.txz but when I then try to upgrade the whole pkg-tree from the repo, it insists to go back to 1.10.5_1. -- p...@opsec.eu+49 171 3101372Now what ? ___ 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 does pkg try to install an older version of pkg ?
## 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 then grep '"name":"pkg"' packagesite.yaml Any brokenness in /var/db/pkg/ ? There's a per-repo sqlite3 database which you could query like this: select name, origin, version from packages where name = 'pkg'; Regards, Christoph -- Spare Space ___ 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 does pkg try to install an older version of pkg ?
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 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. > There's a per-repo sqlite3 database which you could query like this: > select name, origin, version from packages where name = 'pkg'; I've tried, and it showed pkg-1.14.6 as it should be. Status-update: Our package builder (repo.nepustil.net) finished build for a new pkg-repo, and now the upgrade went through without regression to pkg-1.10.5_1 8-} -- p...@opsec.eu+49 171 3101372Now what ? ___ 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"
Updating py27-* ports
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_VERSIONS+=python3=3.7 and then rebuild all of my ports. Would that be sufficient, or even correct? Thanks! -- Carmel pgpF26xWJ1z3w.pgp Description: OpenPGP digital signature
Re: Updating py27-* ports
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=3.7 > DEFAULT_VERSIONS+=python3=3.7 > > and then rebuild all of my ports. Would that be sufficient, or even > correct? I used this in poudriere: DEFAULT_VERSIONS=python=3.7 python3=3.7 So I did not use python2=3.7 -- which will probably not work. That worked good enough that I did not investigate any further. -- p...@opsec.eu+49 171 3101372Now what ? ___ 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: Updating py27-* ports
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: >> >> DEFAULT_VERSIONS+=python=3.7 >> DEFAULT_VERSIONS+=python2=3.7 >> DEFAULT_VERSIONS+=python3=3.7 >> >> and then rebuild all of my ports. Would that be sufficient, or even >> correct? > >I used this in poudriere: > >DEFAULT_VERSIONS=python=3.7 python3=3.7 > >So I did not use python2=3.7 -- which will probably not work. > >That worked good enough that I did not investigate any further. 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. 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. Thanks! -- Carmel pgpAqUzgXWw1M.pgp Description: OpenPGP digital signature
Re: Updating py27-* ports
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 read by make during the build, so it's just part of the make syntax: man make says: += Append the value to the current value of the variable. -- p...@opsec.eu+49 171 3101372Now what ? ___ 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: Updating py27-* ports
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 value bar quux. Sometimes you will see += used even for what looks like the first of a series of assignments. This works because the initial value is the empty string, and is usually done to add to any non-empty default or initial value the variable may be getting elsewhere (now or later) or to future-proof against needing to add something before the first assignment and forgetting to change it from = to +=. See also, "Variable assignment modifiers" in the make manual page. ___ 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 does pkg try to install an older version of pkg ?
## 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 Anna Karenina here: all happy machines are alike, each unhappy machine is unhappy in it's own way. I was thinking along the lines of left over files (yeah, that's a recurring theme here, I've spent way to much time chasing problems and finding editor backup files and the like in "include directory"/ "conf.d" like settings). Perhaps truncated files, broken sqlite database files, that stuff. > Status-update: Our package builder (repo.nepustil.net) finished > build for a new pkg-repo, and now the upgrade went through without > regression to pkg-1.10.5_1 8-} Then I'll assume that your repo was more stale than you thought :) Regards, Christoph -- Spare Space ___ 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: Updating py27-* ports
## 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. (That's the case for the build systems of firefox/thunderbird and chromium - all of them are work in progress upstream - and Gimp's python bindings, which are planned to be python-3-compatible with Gimp 3 expected later this year (at least it was, last time I checked)). Regards, Christoph -- Spare Space ___ 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: Updating py27-* ports
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 changes I tend to go to multiple lines, then collapse back to a single line when I have a stable set. > 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. += adds the option, = set it. DEFAULT_VERSIONS=foo bar sing $DEFAULT_VERSIONS foo bar sing DEFAULT_VERSIONS+=max $DEFAULT_VERSIONS foo bar sing max DEFAULT_VERSIONS=sam $DEFAULT_VERSIONS sam -- Please to meet you, Rose. Now run for your life! ___ 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: Updating py27-* ports
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 Regards. ___ 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"
Porting Practice
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, but i'm still at a loss as to how the diff process works. Also, i've gotten stuck at a few spots along the way. I use svn to checkout a copy of the nvidia-settings port which has no maintainer. The copy goes into my root directory either in a work directory or not. After I make the changes to the files and issue the command... MAKE CONFIG:root@machine17:/usr/ports/x11/nvidia-settings # make config ===> No options to configure make patch and make configure both work. PORTLINT:root@machine17:/usr/ports/x11/nvidia-settings # portlint WARN: Makefile: Consider adding support for a NLS knob to conditionally disable gettext support. 0 fatal errors and 1 warning found. So once I get past this point and have succesfully tested the port with portlint and poudriere testport, I'm confused as to how I am supposed to build the package, and create a suitable diff to patch the port either with svn or diff -u. The documentation for (diff -u) says "To create a suitable diff for a single patch, copy the file that needs patching to something.orig, save the changes to something and then create the patch:" % diff -u something.orig something > something.diff Im not sure really the meaning of this documentation. What file needs patching, which file to copy, where to save changes to exactly, and how and why the svn method is different. Which method should I choose? I know it says that unified diff and svn are preffered but since I am new maybe the (diff -u) command would be easier to begin with? Please help and include anything that's relevant even if i didn't mention it. I'm really excited to get started and will absorb like a sponge any know how that's offered!!! One last thing. I have not attempted a poudriere testport today but for the last ten or so times I have tried, my computer shuts down after a few minutes of testing. Is this a overheating or is it some kind of another problem? ___ 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: Porting Practice
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 recieved alot of help on the forums and from the documentation, but i'm > still at a loss as to how the diff process works. [...] 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.freebsd.org Hope that helps. -- 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"
Re: Porting Practice
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.freebsd.org Hope that helps. 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? Is it poudriere testport? Thanks a ton. > > On Jul 4, 2020 at 7:08 PM, Jonathan Chenwrote: > > > 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 recieved alot of help on the forums and from the > documentation, but i'm still at a loss as to how the diff process works. > [...] 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.freebsd.org Hope that > helps. -- Jonathan Chen chen.org.nz> > ___ 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"
Anyone building Seamonkey locally?
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@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Porting Practice
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 elsewhere 2. hack it to compile 3. compare the hacks against the original sources again to generate diffs. 4. put the diffs into the files/ directory of the port 5. Tweak the Makefile for all targets (fetch, extract, build, stage, etc) Cheers. -- 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"
