Re: Large builds with poudriere
On Thu, May 20, 2021 at 12:48 PM Mark Millard wrote: > Kevin Oberman rkoberman at gmail.com wrote on > Thu May 20 19:21:24 UTC 2021 : > > > You can greatly reduce the build-time for devel/llvm* by changing the > > config to BE_NATIVE to avoid building backends for all FreeBSD supported > > platforms. Obviously this is not acceptable for many cases, but if you > > never cross-compile for other platforms, it's a really big win. > > > Unfortunately, using something like (llvm10 is just one example, > llvm11 showed the same sort of problem at the time): > > /usr/local/etc/poudriere.d/options/devel_llvm10/options:_FILE_COMPLETE_OPTIONS_LIST=BE_AMDGPU > CLANG DOCS EXTRAS LIT LLD LLDB LLD_LINK OPENMP PYCLANG BE_FREEBSD BE_NATIVE > BE_STANDARD > > /usr/local/etc/poudriere.d/options/devel_llvm10/options:OPTIONS_FILE_SET+=BE_AMDGPU > > /usr/local/etc/poudriere.d/options/devel_llvm10/options:OPTIONS_FILE_UNSET+=BE_FREEBSD > > /usr/local/etc/poudriere.d/options/devel_llvm10/options:OPTIONS_FILE_SET+=BE_NATIVE > > /usr/local/etc/poudriere.d/options/devel_llvm10/options:OPTIONS_FILE_UNSET+=BE_STANDARD > > does not work for all platforms/targets. On a Cortex-A57 > this lead to: > > Registered Targets: > amdgcn - AMD GCN GPUs > r600 - AMD GPUs HD2XXX-HD6XXX > > In other words, aarch64 was missing. I had to pick > BE_STANDARD or BE_FREEBSD to get something that > would target aarch64 on aarch64. > > === > Mark Millard > marklmi at yahoo.com > ( dsl-only.net went > away in early 2018-Mar) > Looks like the Makefile might need some work. I see stuff for handling aach64/arm64, so it SHOULD work, but there are things I don't understand about AARCH64 to figure it all out. Still, it should be detected. Out of curiosity, if you do a "make -C /usr/ports/devel/llvm10 config", the line for BE_NATIVE should show the architecture you are running on. If it's missing/something else, maybe you should ask brooks@ about it. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: Large builds with poudriere
On Thu, May 20, 2021 at 8:08 AM Chris wrote: > On 2021-05-20 06:15, Ronald Klop wrote: > > On 5/20/21 2:47 PM, Fernando Apesteguía wrote: > >> El jue., 20 may. 2021 14:45, Alexis Praga > >> escribió: > >> > >>> > >>> Hi guys, > >>> > >>> I've recently been using poudriere to test news ports but this > resulted in > >>> building two large ports, namely: > >>> - devel/llvm [1] > >>> - lang/rust [2] > >>> > >>> Now, lang/rust takes 2 hourse to compile. So testing for 13.0, 12.2 and > >>> 11.4 means around 6 hours in total, a lot of time for my desktop > >>> computer. Especially if the dependencies are upgraded later on. > >>> > >>> Do you have any tips to deal with such long build time ? Apart from > >>> have a dedicated server :) > >>> > >> > >> Patience :-) > >> > >> Package seeding in poudriere is a long awaited feature. > >> > > > > > > You can manually put the rust/llvm package in the All packages directory > and > > poudriere will use that. It is a manual repeating task though. So the > > package > > seeding is indeed a nice feature. > I can't believe I didn't already know that. :-/ > Thanks, Ronald. Today you are a hero! :-) > > --Chris > > > > Ronald. > > > > > > > > > > > >>> Thanks, > >>> > >>> > >>> [1] For https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233010 > >>> [2] For https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255233 > >>> > >>> -- > >>> Alexis Praga > You can greatly reduce the build-time for devel/llvm* by changing the config to BE_NATIVE to avoid building backends for all FreeBSD supported platforms. Obviously this is not acceptable for many cases, but if you never cross-compile for other platforms, it's a really big win. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: Quarterly reports?
Thanks. I found it in the archives, but did not receive it at all. Not in spam. Just no sign of it. I should have received it on current, stable, and announce. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 On Sun, May 9, 2021 at 12:38 PM Freddie Cash wrote: > On Sun., May 9, 2021, 12:29 p.m. Kevin Oberman, > wrote: > >> Did I somehow miss it or is the first quarter report MIA? I don't think >> I've ever seen it posted more than a month after the start of the new >> quarter. >> > > It hit the mailing lists and website on May 5. > > Cheers, > Freddie > > Typos due to smartphone keyboard. > >> ___ 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"
Quarterly reports?
Did I somehow miss it or is the first quarter report MIA? I don't think I've ever seen it posted more than a month after the start of the new quarter. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: pkg builders order of jobs
On Sun, May 9, 2021 at 3:40 AM Stefan Esser wrote: > Am 09.05.21 um 12:22 schrieb Ronald Klop: > > Hi, > > > > On the pkg builders the list of builds is ordered on git hash. > > http://beefy18.nyi.freebsd.org/jail.html?mastername=main-amd64-default > > (NB: ipv6 only) > > > > This ordering is totally random to me. With svn the list was naturally > ordered > > because of the incremental commit id. > > > > Is it possible to add the commit count to the job-name like > sys/conf/newvers.sh > > in base? > > git_cnt=$($git_cmd rev-list --first-parent --count HEAD 2>/dev/null) > > Adding the start-time of the build in ISO format would also be highly > appreciated, at least by me ;-) > > The date should reflect the time of the last commit that has been > considered. Such a time stamp would let me see with little effort > whether a failure is due to a long running build job that did not > catch-up with the latest fixes to a port, or whether there still is > an issue with a port (especially for the "exotic" architectures that > I do not test on my system and that often need a lot longer to complete > a build job). > > Regards, STefan > I would suggest doing some optimization. Too often a very time consuming build is started well into the process. I mean things that take over 24 hours to build like chromium or electron11. Otherwise on smaller builds, a lot of time can be wasted as one or two slots on the build machines finishing one of the big builds and the other 15 slots idle. This does not happen frequently, but it does happen. With many build cycles exceeding 90 hours, any optimization would be helpful. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: Access to detailed status info on package build servers
On Tue, Apr 13, 2021 at 11:02 PM Simon Wright wrote: > Hi all, > > As detailed in other threads, I have been tracking the latest complete > build information on the package build servers (actually on > beefy6.ny.freebsd.org) in order to synchronise my ports tree with the > ports tree used by the build servers. This is so that the packages that > I build locally are as far as possible in sync with the packages > available from the freebsd mirrors. > > I use a script to pull down this file: > > http://beefy6.nyi.freebsd.org/data/122amd64-default/.data.json > > and extract the builds.latest field from it for the jail. Since the move > to git I can no longer access this file. Curl fails with an error 7 > which is a permission denied error. > > This is the command line I have been using: > /sbin/curl -so - > http://beefy6.nyi.freebsd.org/data/122amd64-default/.data.json > > Can anyone suggest another source for this data? Does the pkg-status > server have this info in a JSON file somewhere? It is on the status page > for the build here: > > > https://pkg-status.freebsd.org/builds/default:default:122amd64:4c2cc95952a6:beefy6 > > Build 4c2cc95952a6 > Serverbeefy6 > Statusstopped:done: > Jail 122amd64 > Set default > Ports Tree default > Build type Package > Start time 2021-04-10 01:01 > Elapsed 99:04:36 > SVN > > Or is it possible to return the access permissions for this > server/directory/file to what they were last week? > > Thanks for any guidance. > > Simon Wright. > ___ > 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" > This is likely not your problem, but Is it possible that you have an IPv6 issue? As of a few days ago, beefy6 is IPv6 only. For me, it means no access unless I bring up a tunnel as Frontier does not support IPv6. Next week I'll be moving to Comcast and that will fix the problem. Since it appears that Frontier has no plans to ever support IPv6 on fiber, or at least not for several years, I guess an HE tunnel is the only fix if I want 500 Mbps FIOS. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: Proposed ports git transition schedule
On Fri, Apr 2, 2021 at 7:36 AM Michael Gmelin wrote: > > > On 2. Apr 2021, at 16:27, Kevin Oberman wrote: > > On Fri, Apr 2, 2021 at 4:53 AM Robert Huff wrote: > > >The transition has happened. > >Where do I find the authoritative guide for non-committers? > > > >Respectfully, > > > >Robert Huff > > > -- > > Hello ... my name is SARS-CoV-2. > > You are not wearing a mask? > > Prepare to die! > > > And where do I find the repository? I look at https://cgit.freebsd.org and > see only doc and src. Is there a delay in the move of the repo? Or, am I > looking in the wrong place? > > > According to https://wiki.freebsd.org/git the final run of subversion-git > conversion hasn’t started yet (was planned for yesterday). So I guess we > just have to be patient. > > -m > Thanks! I suspect I've seen pointers to that wiki page as it looks very familiar, but forgot about it since the src conversion. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: Proposed ports git transition schedule
On Fri, Apr 2, 2021 at 4:53 AM Robert Huff wrote: > > The transition has happened. > Where do I find the authoritative guide for non-committers? > > > Respectfully, > > > Robert Huff > > -- > Hello ... my name is SARS-CoV-2. > You are not wearing a mask? > Prepare to die! > And where do I find the repository? I look at https://cgit.freebsd.org and see only doc and src. Is there a delay in the move of the repo? Or, am I looking in the wrong place? -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: On 14-CURRENT: no ports options anymore?
On Sat, Mar 13, 2021 at 2:51 PM Dan Mahoney (Ports) wrote: > If this isn’t at least in /usr/ports/UPDATING it sure should be. > > -Dan > Ditto! While it did not take me long to discover that the ncurses shareable had bumped the version, I wasted a lot of time rebuilding ports one by one. At least a heads-up would have been nice. The way to do this is unclear, though, as it was a base library update. I assume that it only bit those running current or 13. Those running 13-STABLE, as I was, had no warning. I'm not sure a note in UPDATING would have been appropriate, but a post to stable@ and current@ would have been nice. Or, did I miss them? This would also be made VERY clear in the 13.0 Release Notes. I suspect installing misc/compat12x would have worked. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: Problems with updating a port due to top directory in tarball
On Wed, Mar 3, 2021 at 10:15 PM Hiroo Ono wrote: > > On 2021年3月4日木曜日 9時00分32秒 JST, Kevin Oberman wrote: > > I'm trying to update a port I maintain. Since I last updated, it moved > from > > ISC to github and it uses unusual naming conventions. > > > > The distfile is "irrtoolset/archive/release-5.1.3.tar.gz". I can work > > around this with a DIST_SUBDIR and DISTNAME, but when the extract takes > > place, the top directory in the tarball is "irrtoolset-release-5.1.3". > > Since this is not expected, patch fails. > > If it is same as what is tagged as "release-5.1.3", > > DISTVERSIONPREFIX= release- > DISTVERSION=5.1.3 > USE_GITHUB= yes > GH_ACCOUNT= irrtoolset > GH_PROJECT= irrtoolset > > should work. > cf. > > https://docs.freebsd.org/en_US.ISO8859-1/books/porters-handbook/makefile-distfiles.html#makefile-master_sites-github-description > > Thanks you very much! The update to the port has been submitted and is awaiting a committer. Looking at the Porter's Handbook, I now understand how it works, but it would have taken a VERY long time to figure it all out without your help! (Might have taken until the heat death of the universe.) -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: Problems with updating a port due to top directory in tarball
Thanks to both of you. Looks like I can continue working on the port, now! -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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"
Problems with updating a port due to top directory in tarball
I'm trying to update a port I maintain. Since I last updated, it moved from ISC to github and it uses unusual naming conventions. The distfile is "irrtoolset/archive/release-5.1.3.tar.gz". I can work around this with a DIST_SUBDIR and DISTNAME, but when the extract takes place, the top directory in the tarball is "irrtoolset-release-5.1.3". Since this is not expected, patch fails. Is there a way to specify the name of the restore directory? Or to rename it after the extract phase? Since loading the "Porter's Handbook" as a single file seems to not be an option any longer, it is harder to search through the whole thing, I may have missed an simple way to deal with this. Thanks, -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: bogus warning from pkg
On Mon, Feb 15, 2021 at 11:10 AM Steve Kargl < s...@troutmask.apl.washington.edu> wrote: > I have a system installed from late January FreeBSD-current > sources and at that point an up-to-date ports tree. All > installed ports where builtin after I installed FreeBSD. So, > I am running FreeBSD-14.0. For some reason, I am getting > bogus warnings from pkg. > > % pkg info > /dev/null > pkg: Warning: Major OS version upgrade detected. Running \ > "pkg bootstrap -f" recommended > > Short of running the bootstrap command, how do I get > rid of these messages, which are clearly bogus. > > -- > Steve > Are you sure that you reinstalled pkg since the move to 14? That message means that pkg was built on a prior version of FreeBSD. As you build ports and don't do packages, just build and install pkg and that should do the trick. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: portmaster new development
On Mon, Dec 28, 2020 at 6:04 AM abi via freebsd-ports < freebsd-ports@freebsd.org> wrote: > On 28.12.2020 16:16, Stefan Esser wrote: > > Am 28.12.20 um 11:11 schrieb abi via freebsd-ports:> I build my ports > > in poudriere in VM without zfs or ssd on pre-Sandy > >> Bridge CPU. I don't have enough memory or disk space, so I don't use > >> tmpfs or ccache either. I migrated from portmaster when it was > >> abandoned several years ago and don't think I'll come back, > >> especially if new portmaster will be written on bash. The idea behind > >> portmaster was zero dependencies, so it doesn't brake after major > >> upgrades. > > > > You are free to use poudriere and it definitely is the official tool > > for FreeBSD package building (and I have to use it myself and it has > > cost me a lot of time rebuilding broken poudriere jails and keeping > > them in state that I can use them to test new ports on a number of > > different releases as well as i386 plus amd64). > > > > And while you are free to never again use portmaster, telling people > > that it has been abandoned is just a _lie_ and I'd want to ask you to > > stop telling it. It has been continuously maintained for decades. > > > I remember portmaster marked as deprecated in 2016. I've switched to > poudriere because of that. So, it _was_ abandoned when I migrated. It is > good that it is not, the more options - the better. But some people here > telling that poudriere requires ZFS and powerful dedicated hardware, I > just pointed that they are wrong. > I'm afraid your recollection is in error. While there was a lot of talk of deprecating it after Doug stopped supporting it. there was only discussion. Check the history in svn and it simply never happened. Getting rid of it was heavily pushed by a few people of the "poudreire is the solution to all port updating issues and all other should be removed" stripe, but it is and was never the solution for many even though it is a great tool and should be considered the "standard" method of ports management. If Stefan had not stepped up, deprecation would have had to happen as bitrot would have required it. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: portsnap
On Mon, Dec 28, 2020 at 4:37 AM Patrick M. Hausen wrote: > Hi all, > > > Am 26.12.2020 um 20:04 schrieb LuMiWa via freebsd-ports < > freebsd-ports@freebsd.org>: > > ...and I will continue to use portmaster. But I don't understand why > > we should no keep portsnap. > > Kudos to Stefan for keeping portmaster relevant and up-to-date. > But I never understood the appeal of portsnap. What's the advantage over > > svnlite co ... > cd /usr/ports; make update > > This mechanism is in the base system, so an extra tool demands some > justification ;-) > > Kind regards, > Patrick > -- > punkt.de GmbH > Patrick M. Hausen > .infrastructure > > Kaiserallee 13a > 76133 Karlsruhe > > Tel. +49 721 9109500 > > https://infrastructure.punkt.de > i...@punkt.de > > AG Mannheim 108285 > Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein > > portsnap(8) predates svnlite by quite a bit, but you have just described why it is not really worth the overhead of maintaining it. As bugzilla describes many ticket closures, Overcome by events". -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: portsnap
On Sat, Dec 26, 2020 at 9:42 AM LuMiWa via freebsd-ports < freebsd-ports@freebsd.org> wrote: > Hi! > > Today I red again an email: > > Subject:[HEADS UP] Planned deprecation of portsnap > From: Steve Wills > Date: 2020-08-04 18:43:20 > > And as portsnap user I have a question: Do they planning deprecation of > portmaster too? > > Thank you. > -- > “Waiter! A cup of coffee without cream, please! > I’m sorry, sir, we have no cream, only milk, so can it be a coffee > without milk?” > > ― Ernst Lubitsch’s Ninotchka I'm confused. other than dealing with ports, I don't see any relation. One is a tool to update the ports tree on a system and the other is a tool to install or update installed ports, regardless of how the tree was updated. There are other non-deprecated ports that will continue to perform both functions. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: Stale pkg repo?
On Fri, Dec 11, 2020 at 10:56 PM Greg Rivers wrote: > On Saturday, 12 December 2020 00:10:04 CST Kevin Oberman wrote: > > A pkg build in 121amd64 latest was completed on 7-Dec after running for > > over 90 hours and another on 10-Dec that took a more typical 48 hours > > build. FWIW, gtk3 is hardly a big package. Try chromium, rust, llvm* or > > libreoffice. I've seen cases when multiple of these monsters are included > > in a single build of packages for amd64. My last chromium build took over > > 13 hours on my build system. > > > I have observed similar times. From the spot checks I've done, a full > build of all packages averages between 50 and 60 hours. > > > The pointis that 12.1 latest for amd64 has completed two big builds with > > the distribution system net getting the updated packages. > > > Which brings us back to my original point (for 12.1amd64/latest > specifically). Why have the repos still not caught up with the builds? If > rsync is proving unreliable, perhaps switching to replicating via > incremental ZFS send/receive would be better? Can anyone in the know give > an ETA on fixing the immediate problem? > > -- > Greg > The build of 121amd64 latest run started on 2-Dec ran for over 90 hours. That is the longest I've seen, but there may be longer cases. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: Stale pkg repo?
On Fri, Dec 11, 2020 at 4:58 PM Jan Beich wrote: > Tatsuki Makino writes: > > > It seems that just 1 package update ( gtk3? :) ) can cause the > > official poudriere to build a daunting amount of work. > > Pales in comparison to FreeBSD security advisiories which force rebuild > of all 33000 packages. Given package builds are not reproducibile yet[1] > rsync maybe wasting bandwidth on large packages. > A pkg build in 121amd64 latest was completed on 7-Dec after running for over 90 hours and another on 10-Dec that took a more typical 48 hours build. FWIW, gtk3 is hardly a big package. Try chromium, rust, llvm* or libreoffice. I've seen cases when multiple of these monsters are included in a single build of packages for amd64. My last chromium build took over 13 hours on my build system. The pointis that 12.1 latest for amd64 has completed two big builds with the distribution system net getting the updated packages. ___ 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: Stale pkg repo?
On Thu, Dec 10, 2020 at 10:21 PM Greg Rivers via freebsd-ports < freebsd-ports@freebsd.org> wrote: > It's been a while since the "latest" FreeBSD pkg repo has been updated. > For example, dns/bind916 was updated to 9.16.9 ~13 days ago, but has yet to > appear in the repo. > > Has the frequency of pkg builds changed, or is there a problem somewhere > that's preventing the repo from being updated? > > -- > Greg > You don't say which version or platform you are using. There have been two complete repo builds of 12.2amd latest since the last repo update. Looks like rsync to the distribution systems is hung (again). I dropped a note to one of the people who have taken care of this in the past yesterday evening and am hoping for a change tonight (UTC-8). Maybe this thread will get some notice, as well. I'd like to know the proper place to report this as it has happened several times in the past year. There really should be a watchdog on this. Should not be hard to do. I wish I know the longest time a package update might take after the run is finished before it indicates a problem. the build of latest can take from a few hours to nearly 4 days. I assume the rsync time varies by quite a bit, too. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: editors/openoffice-4 compile error
Try building with MAKE_JOBS_UNSAFE and the actual problem will be at the end. Of course, it will take a lot longer to get to the error as you will only compile on a single processor thread. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 On Sat, Nov 28, 2020 at 4:29 PM George Mitchell wrote: > On 11/28/20 7:19 PM, Don Lewis wrote: > > [...] > > Hmn ... > > > > The "infinite recursion" warnings have been around for a while. They > > don't seem to break the build, but have been fixed upstream for 4.2.0 > > whenever that gets released. I hadn't seen the "&& with constant > operand" > > warning before. It looks like a real bug, but it is also just a warning > > and doesn't break the build. I also don't see anything obvious in the > > logs. > > > > Is this repeatable? > > [...] > > Three times so far.-- George > > ___ 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: hyperlinks broken in mate terminal
Works again for me. Do you have all of the mate ports updated to 1.24? (Except atril which has not been updated.) -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 On Sun, Oct 18, 2020 at 1:23 PM AN wrote: > Hi Eric: > > Still not working. > > # pkg info | grep mate-terminal > mate-terminal-1.24.1 Terminal component for the MATE Desktop > > > On Sun, 18 Oct 2020, Eric Turgeon wrote: > > > Date: Sun, 18 Oct 2020 11:56:02 -0300 > > From: Eric Turgeon > > To: AN > > Cc: freebsd-gn...@freebsd.org, FreeBSD > > Subject: Re: hyperlinks broken in mate terminal > > > > It is fixed in mate-terminal-1.24.1 > > > > > > > > > > *Eric TurgeonFreeBSD ports committer* > > www.freebsd.org > > > > > > On Thu, Oct 1, 2020 at 3:11 PM AN wrote: > > > > > FreeBSD Free_BSD_13 13.0-CURRENT FreeBSD 13.0-CURRENT #3 r366314: Thu > Oct > > > 1 11:23:09 EDT 2020 > > > root@Free_BSD_13:/usr/obj/usr/src/amd64.amd64/sys/MYKERNEL.bak amd64 > > > 1300117 > > > > > > mate-1.22.2 > > > luit-20190106_1Locale and ISO 2022 support for Unicode > > > terminals > > > mate-terminal-1.24.0 Terminal component for the MATE Desktop > > > > > > > > > I would appreciate any help with the following issue. I use Alpine as > > > my mail client. When I receive an email with a hyperlink (url), I > could > > > right-click on the link and select open from the menu and that would > take > > > me to that page in Firefox. This functionality stopped working > recently > > > for no apparent reason, possibly after upgrading ports. Normally when > > > this is working correctly if you hover the mouse over a url it will get > > > underlined, now if you hover over a url it does not get underlined. > > > > > > I rebuilt luit-20190106_1 and mate-terminal-1.24.0 but it did not fix > the > > > issue. Does anyone have any idea what might have broken this > > > functionality? Any help would be appreciated. > > > > > > Thanks in advance. > > > ___ > > > freebsd-gn...@freebsd.org mailing list > > > https://lists.freebsd.org/mailman/listinfo/freebsd-gnome > > > To unsubscribe, send any mail to " > freebsd-gnome-unsubscr...@freebsd.org" > > > > > > ___ > freebsd-gn...@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-gnome > To unsubscribe, send any mail to "freebsd-gnome-unsubscr...@freebsd.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"
Re: FreeBSD Port: virtualbox-ose-5.2.44_4 error build
On Tue, Oct 13, 2020 at 12:14 AM Alex V. Petrov wrote: > kmk: *** > > [/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxOGLrenderspu/render/renderspu_init.o] > Error 1 > The failing command: > @cc -c -O2 -g -pipe -O2 -mtune=generic -fno-omit-frame-pointer > -fno-strict-aliasing -fvisibility=hidden -DVBOX_HAVE_VISIBILITY_HIDDEN > -DRT_USE_VISIBILITY_DEFAULT -fPIC -Wno-sign-compare > -Werror-implicit-functio > n-declaration -m64 > > -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/include/VBox/Graphics > -I/usr/local/include > > -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/src/VBox/GuestHost/OpenGL/ > include > > -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxOGLgen > > -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxOGLre > nderspu/dtrace > -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/include > > -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release > -DVBOX -DVBOX_OSE -DVBOX_WITH_64_BITS_G > UESTS -DVBOX_WITH_REM -DVBOX_WITH_RAW_MODE -DRT_OS_FREEBSD -D__FREEBSD__ > -DRT_ARCH_AMD64 -D__AMD64__ -DVBOX_WITH_DEBUGGER -DVBOX_WITH_HARDENING > -DRTPATH_APP_PRIVATE=\"/usr/local/share/virtualbox-ose\" -DRTPATH_ > APP_PRIVATE_ARCH=\"/usr/local/lib/virtualbox\" > -DRTPATH_SHARED_LIBS=\"/usr/local/lib/virtualbox\" > -DRTPATH_APP_DOCS=\"/usr/local/share/doc/virtualbox-ose\" > -DVBOX_WITH_HGCM -DUNPACKS -DIN_RING3 -DHC_ARCH_BITS=6 > 4 -DGC_ARCH_BITS=64 -DPIC -DVBOX_WITH_CRHGSMI -DVBOX_WITH_VDMA > -DFreeBSD=1 -D_GNU_SOURCE > > -Wp,-MD,/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxOGLrenderspu/render/ > renderspu_init.o.dep > > -Wp,-MT,/usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxOGLrenderspu/render/renderspu_init.o > -Wp,-MP -o /usr/ports/emulators/virtualbox-ose/work > > /VirtualBox-5.2.44/out/freebsd.amd64/release/obj/VBoxOGLrenderspu/render/renderspu_init.o > > /usr/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.44/src/VBox/HostServices/SharedOpenGL/render/renderspu_init.c > kmk: *** Exiting with status 2 > *** Error code 2 > > Stop. > make[1]: stopped in /usr/ports/emulators/virtualbox-ose > -- > - > Alex. > There is an open ticket on this. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250315 So far, no response or commit. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: gvfs-1.46.1
Oops! Can't read. Sorry! You have two files listed in the pkg-plist that were not found. make sure that you have the latest version of the file. If it is, open a bug report. Common causes include building with options that were not considered when the pkg-plist file was created. Or the porter just made a mistake. You can always delete those files manually, but please report it along with the build options you have selected (if any). -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 On Mon, Oct 12, 2020 at 5:03 PM Kevin Oberman wrote: > On Mon, Oct 12, 2020 at 3:53 PM LuMiWa via freebsd-ports < > freebsd-ports@freebsd.org> wrote: > >> Hi >> >> On FreeBSD 12.1-RELEASE I have a problem to install (it built without >> problem) gvfs 1.46.1: >> >> make install >> ===> Installing for gvfs-1.46.1 >> ===> Checking if gvfs is already installed >> ===> Registering installation for gvfs-1.46.1 >> pkg-static: Unable to access file >> >> >> /usr/ports/devel/gvfs/work/stage/usr/local/share/GConf/gsettings/gvfs-dns-sd.convert:No >> such file or directory pkg-static: Unable to access file >> >> >> /usr/ports/devel/gvfs/work/stage/usr/local/share/GConf/gsettings/gvfs-smb.convert:No >> such file or directory *** Error code 74 >> >> Stop. >> make[1]: stopped in /usr/ports/devel/gvfs >> *** Error code 1 >> >> Stop. >> make: stopped in /usr/ports/devel/gvfs >> >> Thank you. > > > Looks like you already have a version of gvfs installed. Tools like > portmaster usually deal with this fiune, but manual installations require: > # make deinstall > # make install > -- > Kevin Oberman, Part time kid herder and retired Network Engineer > E-mail: rkober...@gmail.com > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 > > ___ 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: gvfs-1.46.1
On Mon, Oct 12, 2020 at 3:53 PM LuMiWa via freebsd-ports < freebsd-ports@freebsd.org> wrote: > Hi > > On FreeBSD 12.1-RELEASE I have a problem to install (it built without > problem) gvfs 1.46.1: > > make install > ===> Installing for gvfs-1.46.1 > ===> Checking if gvfs is already installed > ===> Registering installation for gvfs-1.46.1 > pkg-static: Unable to access file > > > /usr/ports/devel/gvfs/work/stage/usr/local/share/GConf/gsettings/gvfs-dns-sd.convert:No > such file or directory pkg-static: Unable to access file > > > /usr/ports/devel/gvfs/work/stage/usr/local/share/GConf/gsettings/gvfs-smb.convert:No > such file or directory *** Error code 74 > > Stop. > make[1]: stopped in /usr/ports/devel/gvfs > *** Error code 1 > > Stop. > make: stopped in /usr/ports/devel/gvfs > > Thank you. Looks like you already have a version of gvfs installed. Tools like portmaster usually deal with this fiune, but manual installations require: # make deinstall # make install -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: mate 1.24.1 breaks some applets
On Sun, Oct 4, 2020 at 11:05 PM Kevin Oberman wrote: > On Sun, Oct 4, 2020 at 10:48 PM Jonathan Chen wrote: > >> Hi, >> >> I've updated to the latest version of mate, 1.24.1; but unfortunately, >> the following panel applets fail to load: >> 1. Window List >> 2. Window Selector >> 3. Workspace Switcher >> >> Cheers. >> -- >> Jonathan Chen > > > All three work fine for me. 12-Stable on amd64. > -- > Kevin Oberman, Part time kid herder and retired Network Engineer > E-mail: rkober...@gmail.com > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 > I just realized that I had only a partial installation of 1.24.1. Sorry for the erroneous information! I'm backing off to 1.24.0 for now. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: mate 1.24.1 breaks some applets
On Sun, Oct 4, 2020 at 10:48 PM Jonathan Chen wrote: > Hi, > > I've updated to the latest version of mate, 1.24.1; but unfortunately, > the following panel applets fail to load: > 1. Window List > 2. Window Selector > 3. Workspace Switcher > > Cheers. > -- > Jonathan Chen All three work fine for me. 12-Stable on amd64. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: grafana7-7.1.3
On Fri, Oct 2, 2020 at 7:35 AM Brandon McCorkle < brandon.mccor...@gahanna.gov> wrote: > Hi Robson, > > With phantomjs deprecated are you aware of anyone working > to get the Grafana image renderer plugin working on Freebsd? I've recently > updated our Icinga system been unable to find a way to render the graphs > without phantomjs. > > Thank you, > > Brandon McCorkle > I'm a bit confused as to the removal of phantomjs. I've read the author's statement of the halt in development in March, 2018, but there was no deprecation announced and he did clean up the damaged master repo and restore the 2.1 development branch. He did not in any way indicate that it should not be used and it is still being used fairly widely. After a bit of a break, he has continued to make commits, the most recent in July. He seems unaware that FreeBSD has deleted the port as he still lists its availability. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: What are my options regarding deprecated PyPy port?
On Mon, Aug 24, 2020 at 6:50 PM figosdev via freebsd-ports < freebsd-ports@freebsd.org> wrote: > Hi, I'm new to FreeBSD-- I installed it for the first time this week. > Honestly, so far it has exceeded expectations. > > I installed X11, but the first thing I installed was PyPy2. > > Unlike CPython2, which is EOL'd, PyPy2 does not to the best of my > knowledge depend on CPython. When I installed it with pkg, it said the port > was deprecated and will be removed from ports soon-- but it also said it > was based on Python 2.7 (which is EOLd). > > I think there is a misunderstanding there. PyPy states the intention to > continue to maintain that version. > > Removing this port is unnecessary. Aware of the politics around this > (which go way over FreeBSD anyway) I doubt I will convince someone to save > this port, sadly. > > I've used both Python 2.x and 3.x for years now. If this problem can't be > fixed, can I at least be put in touch with the current port maintainer so > that I can learn how to maintain this as a 3rd party package for my own use? > > I'm certain I'm not up to becoming an official port maintainer at this > stage, but I'd like to be able to at least compile and run PyPy2 on freebsd > without redoing the ports work that was already done on this. > Looks like the deprecation might have been in error. While I can't be sure, it looks like it is in no way dependent on python27 and, if it is maintained, it probably was deprecated in error. Probably someone in the python group saw the 2.7 references and tagged it for deprecation. You probably should start by contacting python@ and, if there is no response, open a ticket on bugzilla pointing this out and requesting that the deprecation be reversed. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: ln -s python3 python2 && ln -s python37 python27?
Short answer is NO. There were significant changes made in python3 that require significant changes in most programs written in python2. This has been a huge issue that will continue until at least the end of the year when python27 is scheduled for removal. Unless a few ports still requiring python2 get updated, the removal will almost certainly be delayed. For example, both chrome and firefox require python2. In most cases, the changes required are trivial, but not always. Since this is a change in the Python language, it applies to all operating systems... Linux, Windows, MacOS as well as FreeBSD. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 On Fri, Aug 7, 2020 at 8:04 PM Chris wrote: > I'm currently performing a big buildup for a large deployment. > I built world && kernel in the build jail, and performed the > install into another jail for the port/package buildup that > will in turn be used for the deployment STABLE-12@363918 && > PORTS@544342, respectively. > Problem _appears_ to be with Python as maintained in the ports > tree. make.conf(5) defines only: > DEFAULT_VERSIONS+=python=3.7 python3=3.7 > performing a make config-recursive in xorg-server/ until dialogs > no longer appear. Followed by a make package-recursive install clean > goes as anticipated, building python-3.7 && py-37 additions, llvm, > ... > But towards the end I'm greeted by a large python2.7 session with > all the expected warnings about EOL and installing to the same > place. > Can I simply avoid all this BS by deleting python2.7 and family, > and simply link all references to python3.7. This is quite maddening. > There must be a way out. No? > > Thank you in advance for any, and all clues to salvation! :-) > > --Chris > > > ___ > 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" > ___ 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: gpac-libgpac-1.0.0_1,1 error build
On Mon, Aug 3, 2020 at 10:37 AM Jung-uk Kim wrote:
> On 20. 8. 2., Kevin Oberman wrote:
> > On Sat, Aug 1, 2020 at 10:15 PM Alex V. Petrov
> > wrote:
> >
> >> CC ../modules/x11_out/x11_out.c
> >> ../modules/x11_out/x11_out.c:978:11: warning: implicit declaration of
> >> function 'glXMakeCurrent' is invalid in C99
> >> [-Wimplicit-function-declaration]
> >> if ( ! glXMakeCurrent(xWindow->display,
> >> xWindow->fullscreen ? xWindow->full_wnd : xWindow->wnd, xWindow->glx_...
> >>^
> >> ../modules/x11_out/x11_out.c:978:109: error: no member named
> >> 'glx_context' in 'XWindow'
> >> ...if ( ! glXMakeCurrent(xWindow->display, xWindow->fullscreen ?
> >> xWindow->full_wnd : xWindow->wnd, xWindow->glx_context) ) {
> >>
> >> ~~~ ^
> >> 1 warning and 1 error generated.
> >> gmake[3]: *** [../config.mak:147: ../modules/x11_out/x11_out.o] Error 1
> >> gmake[3]: Leaving directory
> >> '/usr/ports/multimedia/gpac-libgpac/work/gpac-1.0.0/src'
> >> gmake[2]: *** [Makefile:40: lib] Error 2
> >> gmake[2]: Leaving directory
> >> '/usr/ports/multimedia/gpac-libgpac/work/gpac-1.0.0'
> >> *** Error code 1
> >>
> >> Stop.
> >> make[1]: stopped in /usr/ports/multimedia/gpac-libgpac
> >> *** Error code 1
> >>
> >> Stop.
> >> --
> >> -
> >> Alex.
> >>
> > I opened bug id #248418 for this error earlier today,
> > --
> > Kevin Oberman, Part time kid herder and retired Network Engineer
> > E-mail: rkober...@gmail.com
> > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B05568
>
> I just committed a fix. Please try again.
>
> Jung-uk Kim
>
Success! Thanks for the quick fix!
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
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: gpac-libgpac-1.0.0_1,1 error build
On Sat, Aug 1, 2020 at 10:15 PM Alex V. Petrov
wrote:
> CC ../modules/x11_out/x11_out.c
> ../modules/x11_out/x11_out.c:978:11: warning: implicit declaration of
> function 'glXMakeCurrent' is invalid in C99
> [-Wimplicit-function-declaration]
> if ( ! glXMakeCurrent(xWindow->display,
> xWindow->fullscreen ? xWindow->full_wnd : xWindow->wnd, xWindow->glx_...
>^
> ../modules/x11_out/x11_out.c:978:109: error: no member named
> 'glx_context' in 'XWindow'
> ...if ( ! glXMakeCurrent(xWindow->display, xWindow->fullscreen ?
> xWindow->full_wnd : xWindow->wnd, xWindow->glx_context) ) {
>
> ~~~ ^
> 1 warning and 1 error generated.
> gmake[3]: *** [../config.mak:147: ../modules/x11_out/x11_out.o] Error 1
> gmake[3]: Leaving directory
> '/usr/ports/multimedia/gpac-libgpac/work/gpac-1.0.0/src'
> gmake[2]: *** [Makefile:40: lib] Error 2
> gmake[2]: Leaving directory
> '/usr/ports/multimedia/gpac-libgpac/work/gpac-1.0.0'
> *** Error code 1
>
> Stop.
> make[1]: stopped in /usr/ports/multimedia/gpac-libgpac
> *** Error code 1
>
> Stop.
> --
> -
> Alex.
>
I opened bug id #248418
<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248418>for this error
earlier today,
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B05568
___
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: www/py-html5lib with FLAVOR=py27 failed to build
Still confused at why you are insisting on py27. py37-html5lib should work fine. I use it. To be completely clear, python27 is approaching the end. While a few ports still require it, I can't imagine any reason for leaving it as default. It's time to bite the bullet and go to python. The transition is really pretty trivial. Having py27 as default is simply getting totally unworkable. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 On Sun, Jul 26, 2020 at 2:41 PM KIRIYAMA Kazuhiko wrote: > On Sun, 26 Jul 2020 06:51:07 +0900, > Kevin Oberman wrote: > > > > On Sat, Jul 25, 2020 at 7:40 AM Johan Hendriks > wro > > > > > > > > Op 25-07-2020 om 08:17 schreef KIRIYAMA Kazuhiko: > > > > Hi, all > > > > > > > > www/py-html5lib with FLAVOR=py27 had failed to build: > > > > > > > > running build > > > > running build_py > > > > running install_lib > > > > creating > > > > /var/ports/work/usr/ports/devel/py-pytest-runner/work-py27/stage/usr/local/lib/python2.7 > > > > creating > > > > /var/ports/work/usr/ports/devel/py-pytest-runner/work-py27/stage/usr/local/lib/python2.7/site-packages > > > > copying build/lib/ptr.py -> > > > > /var/ports/work/usr/ports/devel/py-pytest-runner/work-py27/stage/usr/local/lib/python2.7/site-packages > > > > byte-compiling > > > > /var/ports/work/usr/ports/devel/py-pytest-runner/work-py27/stage/usr/local/lib/python2.7/site-packages/ptr.py > > > to ptr.pyc > > > > writing byte-compilation script '/tmp/tmpw8WT4z.py' > > > > /usr/local/bin/python2.7 -O /tmp/tmpw8WT4z.py > > > > removing /tmp/tmpw8WT4z.py > > > > running install_egg_info > > > > running egg_info > > > > writing pytest_runner.egg-info/PKG-INFO > > > > writing namespace_packages to > > > pytest_runner.egg-info/namespace_packages.txt > > > > writing top-level names to pytest_runner.egg-info/top_level.txt > > > > writing dependency_links to > pytest_runner.egg-info/dependency_links.txt > > > > writing entry points to pytest_runner.egg-info/entry_points.txt > > > > reading manifest file 'pytest_runner.egg-info/SOURCES.txt' > > > > writing manifest file 'pytest_runner.egg-info/SOURCES.txt' > > > > Copying pytest_runner.egg-info to > > > > /var/ports/work/usr/ports/devel/py-pytest-runner/work-py27/stage/usr/local/lib/python2.7/site-packages/pytest_runner-2.11.1-py2.7.egg-info > > > > running install_scripts > > > > writing list of installed files to > > > > '/var/ports/work/usr/ports/devel/py-pytest-runner/work-py27/.PLIST.pymodtmp' > > > > > Compressing man pages (compress-man) > > > > ===> Building package for py27-pytest-runner-2.11.1 > > > > ===> py27-hypothesis-5.19.0 Unknown flavor 'py27', possible flavors: > > > py37. > > > > *** Error code 1 > > > > > > > > Stop. > > > > make[1]: stopped in /usr/ports/devel/py-hypothesis > > > > *** Error code 1 > > > > > > > > Stop. > > > > make: stopped in /usr/ports/www/py-html5lib > > > > > > > > In devel/py-hypothesis/Makefile, USES=python:3.6+ > > > > specified. Which wrong to depend devel/py-hypothesis to > > > > py27-hypothesis or to do not correspond devel/py-hypothesis > > > > to py27 ? > > > > > > > > root@jdtpkxb:~ # svnlite info /usr/ports > > > > Path: /usr/ports > > > > Working Copy Root Path: /usr/ports > > > > URL: http://svn.freebsd.org/ports/head > > > > Relative URL: ^/head > > > > Repository Root: http://svn.freebsd.org/ports > > > > Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 > > > > Revision: 542063 > > > > Node Kind: directory > > > > Schedule: normal > > > > Last Changed Author: glewis > > > > Last Changed Rev: 542063 > > > > Last Changed Date: 2020-07-12 11:13:27 +0900 (Sun, 12 Jul 2020) > > > > > > > > root@jdtpkxb:~ # uname -a > > > > FreeBSD jdtpkxb 13.0-CURRENT FreeBSD 13.0-CURRENT #0 r363381M: Thu > Jul > > > 23 22:48:19 JST 2020 root@msrvkxb > :/usr/obj/usr/src/amd64.amd64/sys/XIJ > > > amd64 > > > > root@jdtpkxb:~ # > > > > > > > > Regards > > > > ___ > > >
Re: www/py-html5lib with FLAVOR=py27 failed to build
On Sat, Jul 25, 2020 at 7:40 AM Johan Hendriks wro > > Op 25-07-2020 om 08:17 schreef KIRIYAMA Kazuhiko: > > Hi, all > > > > www/py-html5lib with FLAVOR=py27 had failed to build: > > > > running build > > running build_py > > running install_lib > > creating > /var/ports/work/usr/ports/devel/py-pytest-runner/work-py27/stage/usr/local/lib/python2.7 > > creating > /var/ports/work/usr/ports/devel/py-pytest-runner/work-py27/stage/usr/local/lib/python2.7/site-packages > > copying build/lib/ptr.py -> > /var/ports/work/usr/ports/devel/py-pytest-runner/work-py27/stage/usr/local/lib/python2.7/site-packages > > byte-compiling > /var/ports/work/usr/ports/devel/py-pytest-runner/work-py27/stage/usr/local/lib/python2.7/site-packages/ptr.py > to ptr.pyc > > writing byte-compilation script '/tmp/tmpw8WT4z.py' > > /usr/local/bin/python2.7 -O /tmp/tmpw8WT4z.py > > removing /tmp/tmpw8WT4z.py > > running install_egg_info > > running egg_info > > writing pytest_runner.egg-info/PKG-INFO > > writing namespace_packages to > pytest_runner.egg-info/namespace_packages.txt > > writing top-level names to pytest_runner.egg-info/top_level.txt > > writing dependency_links to pytest_runner.egg-info/dependency_links.txt > > writing entry points to pytest_runner.egg-info/entry_points.txt > > reading manifest file 'pytest_runner.egg-info/SOURCES.txt' > > writing manifest file 'pytest_runner.egg-info/SOURCES.txt' > > Copying pytest_runner.egg-info to > /var/ports/work/usr/ports/devel/py-pytest-runner/work-py27/stage/usr/local/lib/python2.7/site-packages/pytest_runner-2.11.1-py2.7.egg-info > > running install_scripts > > writing list of installed files to > '/var/ports/work/usr/ports/devel/py-pytest-runner/work-py27/.PLIST.pymodtmp' > > > Compressing man pages (compress-man) > > ===> Building package for py27-pytest-runner-2.11.1 > > ===> py27-hypothesis-5.19.0 Unknown flavor 'py27', possible flavors: > py37. > > *** Error code 1 > > > > Stop. > > make[1]: stopped in /usr/ports/devel/py-hypothesis > > *** Error code 1 > > > > Stop. > > make: stopped in /usr/ports/www/py-html5lib > > > > In devel/py-hypothesis/Makefile, USES=python:3.6+ > > specified. Which wrong to depend devel/py-hypothesis to > > py27-hypothesis or to do not correspond devel/py-hypothesis > > to py27 ? > > > > root@jdtpkxb:~ # svnlite info /usr/ports > > Path: /usr/ports > > Working Copy Root Path: /usr/ports > > URL: http://svn.freebsd.org/ports/head > > Relative URL: ^/head > > Repository Root: http://svn.freebsd.org/ports > > Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 > > Revision: 542063 > > Node Kind: directory > > Schedule: normal > > Last Changed Author: glewis > > Last Changed Rev: 542063 > > Last Changed Date: 2020-07-12 11:13:27 +0900 (Sun, 12 Jul 2020) > > > > root@jdtpkxb:~ # uname -a > > FreeBSD jdtpkxb 13.0-CURRENT FreeBSD 13.0-CURRENT #0 r363381M: Thu Jul > 23 22:48:19 JST 2020 root@msrvkxb:/usr/obj/usr/src/amd64.amd64/sys/XIJ > amd64 > > root@jdtpkxb:~ # > > > > 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" > > > > > Python2.7 has been removed from the ports tree. > The error message you get verify's that. > > py27-hypothesis-5.19.0 Unknown flavor 'py27', possible flavors: py37. > > So you need to update your ports to the python 3.7 flavor. > Ahh, no. Both python2 and python27 are very much alive, if not well. python27 will live until the end of the year. The problems that the latest version of py-hypothesis no longer builds for python-2.7. You really need to change your default python version to 3.7 and update a lot of ports that currently depend on python-2.7. As time passes, more and more stuff will lose 2.7 compatibility. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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
Please be aware that this port is maintained by x...@freebsd.org and anyone who is subscribed to the x11 mailing list will get the portscout messaged. This does not mean it is intended that aloof those who subscribe to x11 are responsible for making repaired. If you have not done so, check bugzilla for any existing PR and, if there is one, check it in case it is already being worked. If not, attach your patch to that PR with a description of the fix. If there is no PR, you should open a ticket in the bugzilla with a subject "[patch] x11/nvidea-settings Fix compilation errors". Attach the patch and select "Maintainer approval requested". Include a description of the problem and how you patch fixes it. The leader of the x11 project Nicklas Zeising, is responsible for approving it. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 On Sat, Jul 4, 2020 at 10:33 PM Jonathan Chen wrote: > 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" > ___ 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"
jsoncpp update breaks cmake
The update to jsoncpp pumped the version of the .so which requires a rebuild of cmake. This prevents building a LOT of ports. Could someone bump the PORT_REVISION for cmake? I have not checked whether other ports may need a bump, as well. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: Lsof port can't build (again)
On Fri, Jun 19, 2020 at 12:18 AM @lbutlr wrote: > On 16 Jun 2020, at 14:55, Larry Rosenman wrote: > > sysutils/lsof ABSOLUTELY REQUIRES /usr/src to be able to build. > > Is there a list of the files in src that it requires? > > Can I delete the rest? > > (Tranferring 1.5GB is far less of an issue than keeping 1.5GB around). > Unless something has changed fairly recently, /usr/src/sys should be all you need. N.B. I have not looked at this recently, so something may have changed, but you can give it a try and find out for sure. ___ 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: Which u-boot for rpi3? u-boot-rpi3-32 or the old one?
On Tue, Jun 16, 2020 at 10:22 PM bob prohaska wrote: > On Tue, Jun 16, 2020 at 09:59:24PM -0700, Mark Millard wrote: > > > > > > On 2020-Jun-16, at 21:34, bob prohaska wrote: > > > > > Just noticed there are now two u-boot ports for the RPi3, one > > > called u-boot-rpi3-32 and (the presumably original) u-boot-rpi3. > > > > > > The descriptions are equally bland, what's the difference? > > > The goal is to boot a recent snapshot of -current from USB > > > using a Pi3b (no +). Now it's suffering from cpu_reset failed. > > > > Looking, the check in history for sysutils/u-boot-rpi3-32 > > Could you write a few words about how one checks such history? > There doesn't seem to be anything in /usr/ports/UPDATING. > You need to go to the web interface to the SVN repo for FreeBSD, http://svnweb.freebsd.org and walk down the tree. For ports, you probably want the ports->head repo. Then select the group and port of interest. You probably want to select Makefile and you can scroll down to what you are looking for. You'll need to play around to get a hang of how to do various things, but every commit ever made to FreeBSD since at least version 2.2 and I think before that as well as all ports from their creation. The repo is an incredible resource for looking for reasons for changes and, especially, to track down the commit that introduced a bug. That's how I tracked down a recent issue with 12.1-Stable that was panicking my system when I started a VirtualBox VM. I had no idea of how to fix it, but I knew who made the commit and, when I contacted him, I had a workaround in less than an hour and a fix in about 4 hours. It didn't take that long, but I was away from my system for a while Sunday evening before seeing the response with the patch. Obviously, the committer was not taking the evening off. (Thanks again, Mark!) -- Kevin Oberman, retired Network Engineer ___ 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: might need to bump version of python ports after recent openssl changes
On Tue, May 26, 2020 at 11:09 PM Stefan Eßer wrote: > Am 27.05.20 um 04:24 schrieb Jan Beich: > > Pete Wright writes: > > > >> hello - on current i found myself in a situation where python37 was > >> unable to import ssl: > >> > >> $ python3.7 > >> Python 3.7.7 (default, May 9 2020, 01:37:42) > >> [Clang 10.0.0 (g...@github.com:llvm/llvm-project.git > >> llvmorg-10.0.0-0-gd32170dbd on freebsd13 > >> Type "help", "copyright", "credits" or "license" for more information. > >>>>> import ssl > >> Traceback (most recent call last): > >> File "", line 1, in > >> File "/usr/local/lib/python3.7/ssl.py", line 98, in > >> import _ssl # if we can't import it, let the error > >> propagate > >> ImportError: /usr/local/lib/python3.7/lib-dynload/_ssl.so: Undefined > >> symbol "SSLv3_method@OPENSSL_1_1_0" > >>>>> > >> > >> > >> after a little digging it looks like we recently disabled SSLv3 on > >> CURRENT (huzzah!): > >> https://reviews.freebsd.org/D24945 > >> > >> After forcing a re-install of python37 things are working again as it > >> looked like the pbuilder did rebuild python after this commit. But pkg > >> upgrade didn't detect a new version, so I think it might be helpful to > >> bump the python version's so that people on CURRENT don't end up in > >> the same situation I was in? Not sure what the usual process is for > >> stuff like this... > > > > OSVERSION was already bumped in base r361410, so poudriere will > > force-rebuild all packages. Those who hack .jailversion to avoid > > rebuilds can only blame themselves. > > OSVERSION bumps will be observed by poudriere, but not by other port > building tools. > > Did I miss an announcement that all other methods to keep your system > in a workable state are now considered obsolete and unsupported? > > A port version bump would have enabled rebuilding just the affected > ports, while a rebuild of all my ports based on OSVERSION will take > days to complete on my local build server. Even if the packages are updated in the repository, does pkg know it? It looks to me like pkg upgrade will simply not upgrade the port unless PORT_REVISION is bumped. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 > > ___ 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: Gratuitous port splitting (was: Port Avidemux)
On Sun, May 24, 2020 at 9:56 AM Freddie Cash wrote: > Perhaps the avidemux port should be renamed to avidemux-libs, and then a > new avidemux meta-port could be created with basically just an OPTIONS > screen where your pick which parts you want installed? > > Cheers, > Freddie > > Typos due to smartphone keyboard. > At a minimum, the base port (avidemux) and the plugins should be merged. You really must have both to do anything. I would like to see the CLI and GUI ports become options in a single port instead of separate ports. If the base port is renamed, I'd prefer avidemux-base. Since gtk and qt4 are no longer options, I'd suggest avidemux-gui until/unless they are merged into a single port. I have started re-writing the descriptions with my first attempt included. The current one is terribly old, not even mentioning the most popular muxes, MP4 and MKV. and mostly ignores the fact that it is now really an editor. Proposed pkg-descr: Avidemux is a free and open-source transcoding and video editing software designed for easy-to-use video editing and video processing. Avidemux also offers a command-line interface. Avidemux is capable of non-linear video editing, applying filters by to video, and transcoding video into various formats. Avidemux can also insert audio streams into a video file (muxing) and seperating streams (demuxing). Most popular codec and muxes are supported. Matroska (MKV) is the default. Most codecs allow full tuning capabilities for trading off between speed and accuracy via the GUI or CLI. At this time, you must install multimedia/avidemx, multimedia/avidemux-plugins, and multimedia/avidemux-cli and/or multimedia/avidemux-qt5, the latter two providing user interfaces. WWW: http://avidemux.sourceforge.net/ ___ 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: Gratuitous port splitting (was: Port Avidemux)
On Sat, May 23, 2020 at 8:27 PM Greg 'groggy' Lehey wrote: > On Friday, 22 May 2020 at 21:38:44 -0700, Kevin Oberman wrote: > > On Fri, May 22, 2020 at 1:55 PM Wiebe Pestman > wrote: > > > >> Dear maintainer(s), > >> Today I tried to install the port avidemux-2.7.4_1, but unfortunately > >> without success. > >> When running the command "make install" the whole process proceeds > >> without any error message. > >> But at the end there is no binary ... > >> Neither in /usr/local/bin, nor in > >> > >> /usr/ports/multimedia/avidemux/work/stage/usr/local/bin > >> > >> Am I overlooking something in the installation procedure? > >> The kernel on my machine is: > >> > >> FreeBSD zwaluw 12.1-RELEASE FreeBSD 12.1-RELEASE r354233 GENERIC amd64 > >> > >> Hope to get an answer from you :-) > >> Best regards from Holland, > >> Wiebe Pestman > > > > avidemux does not install any executable. Oddly, it just installs > libraries > > and the like. You must also install avidemux-plugins and either or both > > avidemux-cli and avidemux-qt5. If you only need the GUI, you can skip > > avidemux-cli. > > > > The command to run the GUI version of avidemux is avidemux3_qt5. The CLI > > interface is avidemux3_cli. > > Yes, I've run into this problem too. Arguably it's broken. The > official documentation expects it to be a single installation, and I > don't see any reason to split avidemux into five ports (there's also > avidemux-qt4). What good is the avidemux port on its own? Or the > combination of avidemux-qt5 without avidemux-plugins? Just finding > out that you need all this stuff is a pain. I'd recommend folding > both of these ports, and probably avidemux-cli, into the ports > avidemux-qt4 and avidemux-qt5. > > At the very least there should be a warning in avidemux/pkg-descr, but > I don't think that's the right approach. > > Thoughts? > You are completely right, but this application is weird. It a bear of a port because it used to include tar files of all of its dependencies due to ever changing APIs that kept breaking the build. It also makes for a very messy build that actually is separate builds with a bash script to drive it. As a result, the creation of four ports was probably somewhat natural. It's still a bad idea and I have twice worked with committers who wanted to rework it, but people are busy. Tobias was very helpful to get this port back into the system after it had been deleted. I will submit an updated pkg-descr that at least lets people know that they need to install at least three ports. I hope to do that tomorrow. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: Port Avidemux
On Fri, May 22, 2020 at 1:55 PM Wiebe Pestman wrote: > Dear maintainer(s), > Today I tried to install the port avidemux-2.7.4_1, but unfortunately > without success. > When running the command "make install" the whole process proceeds > without any error message. > But at the end there is no binary ... > Neither in /usr/local/bin, nor in > > /usr/ports/multimedia/avidemux/work/stage/usr/local/bin > > Am I overlooking something in the installation procedure? > The kernel on my machine is: > > FreeBSD zwaluw 12.1-RELEASE FreeBSD 12.1-RELEASE r354233 GENERIC amd64 > > Hope to get an answer from you :-) > Best regards from Holland, > Wiebe Pestman avidemux does not install any executable. Oddly, it just installs libraries and the like. You must also install avidemux-plugins and either or both avidemux-cli and avidemux-qt5. If you only need the GUI, you can skip avidemux-cli. The command to run the GUI version of avidemux is avidemux3_qt5. The CLI interface is avidemux3_cli. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: ports: Need new future
Yes, or, at least a notification that defaults have changed. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 On Tue, May 5, 2020 at 12:13 AM Alex V. Petrov wrote: > Hi All! > > I think that for the ports menu options need a new "default" button > (make rmconfig). > > -- > - > Alex. > ___ > 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" > ___ 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: python 2.7 marked as deprecated and EOL while 2.7.18 RC is available
I have submitted a bug, bugzilla/show_bug.cgi?id=245799 <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245799>, to update math/gnumeric to run with python3. It's a bit odd because the current version in ports builds and runs with either python 2 or 3 by default, but the FreeBSD port does not because it attempts to compile all the python modules which are only available when the port is built with python2. Simply eliminating the post-install compileall.py call allows it to build and run. Making that dependent on PYTHON_DEFAULT =2.7 would be the right thing to do and is easy, but I'm unsure how to make the packing list DTRT. Other than that, gnumric just works with any supported version of python. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: python 2.7 marked as deprecated and EOL while 2.7.18 RC is available
On Thu, Apr 23, 2020 at 1:12 PM ajtiM via freebsd-ports < freebsd-ports@freebsd.org> wrote: > On Thu, 23 Apr 2020 21:46:15 +0200 > Kurt Jaeger wrote: > > > Hi! > > > > > I clean almost everything except print/lyx which I am using and I > > > like it (with latex-beamer). I try to build with Python 3.7 but not > > > success. I do not now if I am one of the "rare" user or is port > > > dead. > > > > The port is up to date with version 2.3.4.2. > > > > Can you try to ask upstream ? In their bugtracker ? > > > > https://www.lyx.org/trac/wiki/BugTrackerHome > > > > There's a closed bug that tracked this topic: > > > > https://www.lyx.org/trac/ticket/9006 > > > > and it says that lyx after 2.3.0 should work with py3. > > > > It was solved long time ago but we have: > > > Build dependencies: > > update-desktop-database : devel/desktop-file-utils > gmake : devel/gmake > pkgconf>=1.3.0_1 : devel/pkgconf > python2.7 : lang/python27 > msgfmt : devel/gettext-tools > autoconf>=2.69 : devel/autoconf > automake>=1.16.1 : devel/automake > perl5>=5.30.r1<5.31 : lang/perl5.30 > moc : devel/qt5-buildtools > qmake : devel/qt5-qmake > xcb.pc : x11/libxcb > > Runtime dependencies: > > update-desktop-database : devel/desktop-file-utils > python2.7 : lang/python27 > perl5>=5.30.r1<5.31 : lang/perl5.30 > xcb.pc : x11/libxcb > > > > -- > Ernst Lubitsch’s Ninotchka: > Edit the Makefile, deleting :2.7 after python from the USES= lines. If that works, please open a ticket for this so the port can be fixed to use python3. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: python 2.7 marked as deprecated and EOL while 2.7.18 RC is available
If you actually use inkscape, can you try inkscape with python37 an confirm whether or not it works? My guess is that it does not, but it does run and at least works to some degree. Maybe everything works. (Hope springs eternal.) I suspect you know this, but you can just edit the Makefile to remove ":2.7" from the dependencies and then rebuild the port. As for gnumeric (which I actually care about), I think just deleting the post-install in the Makefile might do the trick. post-install will clearly fail with a non-python27 build. Again, scon is the big one and looks like a candidate for FLAVORS. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 On Sun, Apr 19, 2020 at 7:44 AM ajtiM via freebsd-ports < freebsd-ports@freebsd.org> wrote: > And how and when will be solved Inkscape which is part of the GNOME > group: > > Build dependencies: > > concept_check.hpp : devel/boost-libs > cmake : devel/cmake > ninja : devel/ninja > update-desktop-database : devel/desktop-file-utils > gtk-update-icon-cache : graphics/gtk-update-icon-cache > pkgconf>=1.3.0_1 : devel/pkgconf > python2.7 : lang/python27 > msgfmt : devel/gettext-tools > x11.pc : x11/libX11 > > Runtime dependencies: > > py27-numpy>=1.15,1<1.19,1 : math/py-numpy@py27 > py27-lxml>0 : devel/py-lxml@py27 > py27-scour>0 : textproc/py-scour@py27 > update-desktop-database : devel/desktop-file-utils > gtk-update-icon-cache : graphics/gtk-update-icon-cache > python2.7 : lang/python27 > x11.pc : x11/libX11 > > Thank you. > > -- > Ernst Lubitsch’s Ninotchka: > > “‘Waiter! A cup of coffee without cream, please!’ ‘I’m sorry, sir, we > have no cream, only milk, so can it be a coffee without milk?’” > ___ > 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" > ___ 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: BLENDER 2.79
On Sat, Apr 18, 2020 at 1:57 PM Marcin Cieslak wrote: > On Sat, 18 Apr 2020, Adam Weinberger wrote: > > > On Sat, Apr 18, 2020 at 2:31 PM Tomasz CEDRO wrote: > >> > > > > BGE is gone and done, and in most cases FreeBSD does not keep old > > versions of ports around, and that's especially true for massive and > > complex projects like Blender. > > But I think we keep different port version around on major API changes > for a while. Not to mention things like node that can have up to 4 versions > in the ports tree. > > Whatever is the future of BGE, one should simply not lose the functionality > by doing "pkg upgrade". Not sure this even made into UPDATING > > Marcin While a packaged blender-2.79 is unlikely, the port is still available from subversion. Just be sure you keep a copy of the distribution. Yes, it's a huge build, but you really only need to package it once. Unless it is forked, it's likely abandoned so bitrot will get it some day. At least it's unlikely to change a lot, so you would not have to package it often other than after major releases or when a shareable dependency is updated. Note, I don't use blender, though I find it impressive! -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: python 2.7 marked as deprecated and EOL while 2.7.18 RC is available
I see both mate-menu and mate-applets require python27, but both build fine and seem to be running well when built with py37. It is possible that one or more applets that I don't use do require py27, but I see no reason for that requirement on mate-menus. The menus seem to be fine. Inkscape is another. It builds and runs on py37, but I have no confidence that it runs properly. I have not used inkscape in years and I don't really know how to test it. I am dubious. math/gnumeric is one I use daily and it explicitly states in the build that 2.x is required and it is not yet compatible with python3+. It appears that the default is to simply build gnumeric without Python bindings in which case python2 is not required, but the port makes use of it, so it probably needs at least some massaging. The big one is scons. It is required by virtualbox-ose, and that is rather important. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 > ___ 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: hdf5 update and problem
On Sun, Mar 29, 2020 at 1:18 PM ajtiM via freebsd-ports < freebsd-ports@freebsd.org> wrote: > Hi! > > After update of hdf5 there are problems with blender which doesn't > build anymore: > executing: /usr/ports/graphics/blender/work/.build/bin/blender --help > ld-elf.so.1: Shared object "libhdf5.so.103" not found, required by > "libAlembic.so.1.7" Traceback (most recent call last): > File "blender.1.py", line 56, in > > Also there is a problem with graphics/vigra too, > > Thank you. > > > -- > Ernst Lubitsch’s Ninotchka: The source of libAlembic.so needs to be rebuilt to support the updated hdf5. I don't use blender, but the generic answer is: # pkg which libAlembic.so.1.7 The response is the port that is still linked to the hold hdf5 shareable. Rebuild it and that will fix this one. Also, notify whoever updated hdf5 that the port needs a PORT_REVISION bump so that the package gets updated. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: svn commit: r358166 - head
On Fri, Feb 21, 2020 at 8:38 AM Mark Millard via freebsd-ports < freebsd-ports@freebsd.org> wrote: > Based on the example from https://www.freebsd.org/cgi/man.cgi?ldd > there are commands such as the following that might help: > > # find /usr/local/bin* /usr/local/lib* -type f | xargs -n1 file -F ' ' | > grep 'ELF.*dynamically' | cut -f1 -d' ' | xargs ldd -f '%A %o\n' | grep > ncurses\.so\.8 | more > /usr/local/bin/xterm libncurses.so.8 > /usr/local/bin/msgattrib libncurses.so.8 > /usr/local/bin/msgcat libncurses.so.8 > /usr/local/bin/msgcmp libncurses.so.8 > /usr/local/bin/msgcomm libncurses.so.8 > /usr/local/bin/msgconv libncurses.so.8 > /usr/local/bin/msgen libncurses.so.8 > /usr/local/bin/msgexec libncurses.so.8 > /usr/local/bin/msgfilter libncurses.so.8 > /usr/local/bin/msgfmt libncurses.so.8 > /usr/local/bin/msggrep libncurses.so.8 > /usr/local/bin/msginit libncurses.so.8 > /usr/local/bin/msgmerge libncurses.so.8 > /usr/local/bin/msgunfmt libncurses.so.8 > /usr/local/bin/msguniq libncurses.so.8 > /usr/local/bin/xgettext libncurses.so.8 > /usr/local/bin/gdbmtool libncurses.so.8 > /usr/local/bin/bison libncurses.so.8 > /usr/local/bin/sqlite3 libncurses.so.8 > /usr/local/bin/resize libncurses.so.8 > /usr/local/bin/luac52 libncurses.so.8 > /usr/local/bin/lua52 libncurses.so.8 > /usr/local/bin/gnuplot libncurses.so.8 > /usr/local/bin/FileCheck80 libncurses.so.8 > /usr/local/bin/FileCheck10 libncurses.so.8 > /usr/local/lib/gettext/cldr-plurals libncurses.so.8 > > This can be a lot of files to go through (e.g., lib*) and so > can take a fair amount of time. > > === > Mark Millard > marklmi at yahoo.com > ( dsl-only.net went > away in early 2018-Mar) > You can feed that list into 'pkg which', awk that to remove all of the commands and then all but the last space delimited string of the remainder, and uniq. I also sorted. bison-3.5.2,1 gdbm-1.18.1_1 gettext-tools-0.20.1_1 gnuplot-5.2.8 llvm80-8.0.1_3 lua52-5.2.4 sqlite3-3.30.1,1 xterm-353_1 -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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 is pkg version taking so long?
Never mind. I had a corrupt /usr/ports/Makefile. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 On Mon, Feb 17, 2020 at 9:19 AM Kevin Oberman wrote: > Today I ran "pkg version -vl\<" to see what ports had been updated. This > usually ran in a few seconds. Today it had provided no output after a much > longer time and I noticed it was running a "make flavors-package-names" on > a large number of the ports installed; perhaps all of them. It ran for over > 2 minutes. > > Did I clobber a cache of some sort? Can it be fixed? Is this a bug? > -- > Kevin Oberman, Part time kid herder and retired Network Engineer > E-mail: rkober...@gmail.com > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 > ___ 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 is pkg version taking so long?
Today I ran "pkg version -vl\<" to see what ports had been updated. This usually ran in a few seconds. Today it had provided no output after a much longer time and I noticed it was running a "make flavors-package-names" on a large number of the ports installed; perhaps all of them. It ran for over 2 minutes. Did I clobber a cache of some sort? Can it be fixed? Is this a bug? -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: What is the actual syntax used to FLAVOR ports?
On Sat, Feb 8, 2020 at 1:27 PM Chris wrote: > OK I know FLAVOR is an evolving concept. But I can not find > the FLAVOR documentation. Only references in the porters > handbook. What I think needs to be available is an entire > list of flavor tags for all (port) categories. > For example; > make FLAVOR=python27 returns the error use py27. > OK now I know how to flavor, and build python flavors. > But what of Perl? > make FLAVOR=perl2.8. Nope. How about make FLAVOR=p5-28, > and so it goes... > Does there exist a definitive list of flavors? It'd > also be valuable for defining defaults in make.conf(5) > > Thanks! > > --Chris The problem is not having a clear understanding of what a FLAVOR is and when it is used. FLAVORS are generally a way to deal with the problem of incompatible versions and Python is the poster child. Python2 and Python3 are two version of a VERY popular language that have significant syntax incompatibilities. While a program written for gcc-4.2 should work fine when compiled with gcc-7, it is VERY unlikely that a program written for Python2 will work with Python3. While the changes needed are often fairly straight forward, they have to be made. The result is a requirement of having both interpreters installed and two packages of of most Python libraries built from a single source. Adding FLAVORS for a port is an expensive operation and is never lightly approved by the ports management team as it adds a great deal of complexity and both human and machine overhead. Requests to FLAVOR a port are carefully reviewed and will only be approved with adequate justification. In the case of Perl, no attempt to flavor it has been needed. Most Perl packages (p5-*) will work with any of the three available ports. In most cases they may be installed and continue to work across versions with no changes. Python (py-) ports MUST be reinstalled to move from Python2 to Python3. Some have not had required changes to work with Python3 made and, initially, almost none did. Some have now been written with no support for Python2. All of this has to be properly handled by the package building system and it is not at all trivial. As of today, I believe the only FLAVORed ports are those using emacs, lazarus, php, and, of course, python. By "using", I mean that the port Makefile includes "USE_PYTHON" or similar USE_ definitions of the other languages. (Yes, emacs is not a language, but elisp, the core of emacs, is and lazarus is an IDE for Pascal.) I'm sorry of this is not entirely clear, but I hope it helps and I hope it is all correct. I may have worded some of it poorly. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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
On Tue, Feb 4, 2020 at 9:48 PM Thomas Mueller wrote: > > This is getting a bit off-topic, but I use Firefox with User Agent > Switcher > > by Linder. (There are several Firefox extensions that have VERY similar > > names.) It works perfectly at Chase and also fixes several sites that > > insist on providing the mobile version to FreeBSD. It allows the > selection > > of both OS and browser to provide in the user agent ID on a per-site > basis. > > It fixes a lot of issues. > > -- > > Kevin Oberman, Part time kid herder and retired Network Engineer > > Where would I find User Agent Switcher by Linder? Would it be on a > Mozilla site, and would it work with SeaMonkey? > > Would the several Firefox or SeaMonkey extensions have similar > functionality? > > Better to reply to list only; copy that was sent to me off-list had the > same Message-ID but was in multipart/alternative. Maybe the list software > sanitized the message format? > > Tom > It's available through Firefox from about:addons. It is the one by Linder, one of at eat three extensions of the same name. I don't know about SeaMonkey. Does it support the extension interface like Firefox? If so, it will probably work. You might also check the website at http://mybrowseraddon.com/useragent-switcher.html -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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
On Tue, Feb 4, 2020 at 3:39 AM Thomas Mueller wrote: > > This is quite surprising as I have not seen this. I do get occasional > dead > > buttons due to all of the privacy add-ons I run, especially No-Script, > but > > also less intrusive ones like Privacy Badger. > > > I have seen a few issues with sites taking advantage of some JS functions > > outside of the standard that Chrome has added and Firefox has not yet > > picked up. This is the fault of Chrome playing the old IE game of making > > other browsers notwork correctly on some pages. I also have to fake the > UI > > identifier for some sites as they reject access from FreeBSD (Chase Bank, > > I'm looking at you!) or do the wrong thing. > > > As regards chromium, I have deleted it it and will not consider ever > using > > it due to it's massive data collection and its blocking privacy tools > like > > No-Script. > > > Kevin Oberman, Part time kid herder and retired Network Engineer > > I know from experience what you mean with Chase Bank blocking online > banking access if your user-agent string is not to the website server's > liking. > > Chase Bank is not the only offender. Some websites, without blocking > access, behave differently and wrongly depending on user-agent string. > > I got Chase Bank to work with an outdated version of Otter Browser and a > fudged user agent. > > Sometimes it's not what browser you're using, but what browser the website > software thinks you're using. > > I do find some scripts to cause problems and make some websites very slow. > > I had problems with Mozilla SeaMonkey on nfl.com when I was looking to > see highlights on the last Super Bowl (last Sunday night). > > I was glad to close that browser window! > > Since this problem with Chase, using Mozilla Seamonkey under FreeBSD, > affects me so directly, I could not resist making this response. > > Tom > This is getting a bit off-topic, but I use Firefox with User Agent Switcher by Linder. (There are several Firefox extensions that have VERY similar names.) It works perfectly at Chase and also fixes several sites that insist on providing the mobile version to FreeBSD. It allows the selection of both OS and browser to provide in the user agent ID on a per-site basis. It fixes a lot of issues. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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
This is quite surprising as I have not seen this. I do get occasional dead buttons due to all of the privacy add-ons I run, especially No-Script, but also less intrusive ones like Privacy Badger. I have seen a few issues with sites taking advantage of some JS functions outside of the standard that Chrome has added and Firefox has not yet picked up. This is the fault of Chrome playing the old IE game of making other browsers notwork correctly on some pages. I also have to fake the UI identifier for some sites as they reject access from FreeBSD (Chase Bank, I'm looking at you!) or do the wrong thing. As regards chromium, I have deleted it it and will not consider ever using it due to it's massive data collection and its blocking privacy tools like No-Script. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 On Mon, Feb 3, 2020 at 11:38 AM Dave Horsfall wrote: > On Mon, 3 Feb 2020, Christoph Moench-Tegeder wrote: > > > You're right. For some reason, firefox is not handling the additional > > compression correctly (I see Content-Encoding: gzip in the headers, so > > it's advertised, but not unzipped by the browser, so I get a double- > > compressed file. Oh tempora, oh mores). Not enough time to dig into that > > right now. > > FWIW, I find that Firefox is becoming increasingly unreliable, with "dead" > buttons etc (yes, I have JS enabled against my better judgement) and have > to use Safari/Chrome instead. This is a pity, as I find that FF is much > faster and I've used it for many years. > > -- Dave > ___ > 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" > ___ 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: openblas-0.3.7_1,1 error install
I can't say anything about the missing library issue as I have not seen it. It is true that cblas and openblas now conflict. That is because openblas added cblas emulation that duplicates the libraries cblas installed. It is important that openblas be re-installed after cblas is deleted as it probably will delete files that openblas installs. I deleted both cblas and openblas (pkg delete -f cblas openblas) and then installed openblas. When I tried installing py-numpy@py27, it still failed, still trying to link to cblas stuff. Something was cached somewhere. I tried a couple of days later, after a reboot, and it built perfectly. I don't know if it was the reboot or something else, but everything builds and works fine, now. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 On Sat, Feb 1, 2020 at 1:39 PM ajtiM wrote: > On Sat, 1 Feb 2020 12:20:10 -0800 > Kevin Oberman wrote: > > > That is a configuration option, but the default is to use openblas. > > The change was made a few months ago. > > > > If you have built py-numpy from ports in the past, use "make -C > > /usr/ports/math/py-numpy" to change the saved config to use > > math/openblas. (NETLIB was the previous default which used cblas.) > > -- > > Kevin Oberman, Part time kid herder and retired Network Engineer > > E-mail: rkober...@gmail.com > > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 > > > > > > On Sat, Feb 1, 2020 at 3:44 AM ajtiM via freebsd-ports < > > freebsd-ports@freebsd.org> wrote: > > > > > On Fri, 31 Jan 2020 18:49:39 -0500 > > > ajtiM wrote: > > > > > > > On Fri, 31 Jan 2020 18:29:10 -0500 > > > > Steve Wills wrote: > > > > > > > > > Hi, > > > > > > > > > > On 1/31/20 5:47 PM, ajtiM via freebsd-ports wrote: > > > > > > > > > > > > ls -al /usr/local/lib/libopenblas* > > > > > > -rw-r--r-- 1 root wheel 32273330 Jan 31 10:45 > > > > > > /usr/local/lib/libopenblas_nehalemp-r0.3.7.a -rwxr-xr-x 1 > > > > > > root wheel 15492200 Jan 31 10:45 > > > > > > /usr/local/lib/libopenblas_nehalemp-r0.3.7.so lrwxr-xr-x 1 > > > > > > root wheel29 Jan 31 10:45 > > > > > > /usr/local/lib/libopenblas.a -> libopenblas_nehalemp-r0.3.7.a > > > > > > lrwxr-xr-x 1 root wheel30 Jan 31 10:45 > > > > > > /usr/local/lib/libopenblas.so -> > > > > > > libopenblas_nehalemp-r0.3.7.so > > > > > > > > > > > > > > > > Are you seeing any other issues besides the complaint from > > > > > portmaster? > > > > > > > > > > Steve > > > > > > > > For now I do not have problem but also pkg check -d -n -a shows: > > > > > > > > Checking all packages: 100% > > > > py27-numpy is missing a required shared library: libopenblas.so > > > > py37-numpy is missing a required shared library: libopenblas.so > > > > py37-scipy is missing a required shared library: libopenblas.so > > > > suitesparse is missing a required shared library: libopenblas.so > > > > > > > > Thank you. > > > > > > > > > > Does py-numpy depends on math/cblas still? > > > Thank you. > > > > > Yes, I had default option NETLIB and cblas was installed but I have > installed also openblas at the same time, I do not have clbla installed. > Now, I cannot have both at the same time and I do not know why py-numpy > is missing shared libraries which are installed. > -- > “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"
Re: FreeBSD Port: openblas-0.3.7_1,1 error install
That is a configuration option, but the default is to use openblas. The change was made a few months ago. If you have built py-numpy from ports in the past, use "make -C /usr/ports/math/py-numpy" to change the saved config to use math/openblas. (NETLIB was the previous default which used cblas.) -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 On Sat, Feb 1, 2020 at 3:44 AM ajtiM via freebsd-ports < freebsd-ports@freebsd.org> wrote: > On Fri, 31 Jan 2020 18:49:39 -0500 > ajtiM wrote: > > > On Fri, 31 Jan 2020 18:29:10 -0500 > > Steve Wills wrote: > > > > > Hi, > > > > > > On 1/31/20 5:47 PM, ajtiM via freebsd-ports wrote: > > > > > > > > ls -al /usr/local/lib/libopenblas* > > > > -rw-r--r-- 1 root wheel 32273330 Jan 31 10:45 > > > > /usr/local/lib/libopenblas_nehalemp-r0.3.7.a -rwxr-xr-x 1 root > > > > wheel 15492200 Jan 31 10:45 > > > > /usr/local/lib/libopenblas_nehalemp-r0.3.7.so lrwxr-xr-x 1 root > > > > wheel29 Jan 31 10:45 /usr/local/lib/libopenblas.a -> > > > > libopenblas_nehalemp-r0.3.7.a lrwxr-xr-x 1 root wheel30 > > > > Jan 31 10:45 /usr/local/lib/libopenblas.so -> > > > > libopenblas_nehalemp-r0.3.7.so > > > > > > > > > > Are you seeing any other issues besides the complaint from > > > portmaster? > > > > > > Steve > > > > For now I do not have problem but also pkg check -d -n -a shows: > > > > Checking all packages: 100% > > py27-numpy is missing a required shared library: libopenblas.so > > py37-numpy is missing a required shared library: libopenblas.so > > py37-scipy is missing a required shared library: libopenblas.so > > suitesparse is missing a required shared library: libopenblas.so > > > > Thank you. > > > > Does py-numpy depends on math/cblas still? > 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" > ___ 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"
Tool to check for non-default options for installed ports
I should just write this as it looks very straight-forward but I'm lazy and hate reinventing wheels. On my development system I build from ports. An on-going issue is that ports frequently change options from non-default to default and I never see the change. The result is that every now and then a port won't build due to a change or a port runs with reduced capabilities or performance when a new option becomes the standard. Looking at the DEFAULT_OPTIONS in the port Makefile and comparing them with saved config is trivial and I suspect a tool for this has probably been written several times. Thanks! -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: firefox build broken by SVN r520537?
Yes, it is a known issue, but only shows up when gtk3 is built without Wayland support. See bug 242790. gecko@ is waiting for an upstream patch. Until then the recommendation is to remove the patch which looks like simply reverting to PORTREVISION 3. -- Kevin Oberman, Part time kid herder and retired Network Engineer. E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 On Sun, Dec 22, 2019 at 12:32 PM Michael Butler wrote: > Is noone else seeing .. > > In file included from Unified_cpp_toolkit_xre0.cpp:56: > /usr/ports/www/firefox/work/firefox-71.0/toolkit/xre/glxtest.cpp:39:10: > fatal error: 'mozilla/widget/mozwayland.h' file not found > #include "mozilla/widget/mozwayland.h" > ^ > > imb > ___ > 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" > ___ 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: Checking you the maintainer of a port?
On Wed, Nov 27, 2019 at 1:08 PM Brooks Davis wrote: > On Wed, Nov 27, 2019 at 02:05:56PM -0700, Janky Jay, III wrote: > > Hello, > > > > On 11/27/19 2:03 PM, @lbutlr wrote: > > > I thought that the maintainer of a port was listed somewhere in the > files at user/ports//portbase/ but evidently not. What is the > easiest way to find out, sitting in console on a server without a GUI, to > find out who the maintainer is? (On my desktop I can just google and launch > a browser, but that is not possible on most of the servers which do not > have web clients installed. > > > > > > (Right now I am looking for the maintainer of roundcube, but this is a > general question.) > > > > > > > Please see the "MAINTAINER=" line in the port's "Makefile". > > A slightly more general answer is: > > cd /usr/ports//; make -V MAINTAINER > > -- Brooks > Or: make -C /usr/ports// maintainer -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: Omg upgrade wants to install MySQL
Packages are built using default options and some package you installed defaults to MySQL. Many ports are installed with GUIs by default, so packages are as well. Some ports have nox11 versions but many do not. This is a limitation to most (all?) packaging systems, not just the one FreeBSD uses. The only way I know around this is to build your own packages for those using non-default options. The preferred way is to build them with port-mgmt/poudrerie though you can also build them manually or with portmaster but, for most cases, poudriere is easier. This is all described in the Handbook. Only ports with modified options need be built locally and the standard packages should be used for all standard ports. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 On Sat, Nov 2, 2019 at 12:37 PM @lbutlr wrote: > I have mariadb101 (client and server) installed, but when looking at what > pkg update will do, one of the things it will do is install MySQL. Is there > something I need to do to tell it to use MariaDB instead? > > Since I am here, it also wants to install a bunch of X11 packages, but I > neither want nor have any desktop environment installed, so similar > question, how can I tell pkg to run in “don’t enable GUIs” mode? > > > > -- > 'That's blasphemy,' said the vampire. He gasped as Vimes shot him a > glance like sunlight. 'That's what people say when the voiceless speak.’ > > ___ > 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" > ___ 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: [Circumvented] Problem updating gimp-app-2.10.12_2, 1 to gimp-app-2.10.12_3, 1
On Mon, Sep 2, 2019 at 4:41 AM David Wolfskill wrote: > On Mon, Sep 02, 2019 at 01:34:50PM +0200, Walter Schwarzenfeld wrote: > > Try recompile graphics/libspiro. > > > > Thanks. As noted, I did (along with graphics/gegl), and that appears to > have circumvented the problem. > > I wrote the note so that others might make use of my experience: the > issue is resolved for me. > > Peace, > david Actually, no need to rebuild libspiro. The problem is that libpiro was updated Aug. 19 and the shareable version was bumped from '0' to '1' making gegl fail to load. Rebuilding gegl allows it to run normally and gimp-app to build. The real problem is that the pkg database is not working "right". i looked at gegl dependencies, it showed libspiro: > pkg info -d gegl gegl-0.4.16_2: [...] openexr-2.3.0_2 libspiro-20190731,1 librsvg2-2.40.20 [...] But showing the "depends on" for libspiro showed: > pkg info -r libspiro libspiro-20190731,1: > So attempting to list dependencies on libspiro would not have flagged gegl s needing a PORT_REVISION bump to be rebuilt to catch the .so version bump of libspiro. This should not happen, but clearly did... and not just to me. I will also mention that the commit to libspiro did not mention the shareable version bump or bump PORT_REVISION on ny ports. So the committer perhaps did not realize that there was an issue. I will drop the committer a note. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: perl port updates
Will do. I was unaware of the "se@"address or I would have. I did complain about this a few years ago on the ports@ list and I never got a response. I you use '-f' in portmaster, it will rebuild all ports that use the library directly and any port that uses that port all the way up the tree. It's only when something rather disastrous happens that you need or want to use '-f'. Very few ports actually make use of the shareable library. Most are simply calling the perl interpreter and the perl executable which will use the shareable, but those programs don't link to it. In fact, very few 'p5-' programs do, either. The exceptions are the very few that include C code (a lot do) that call into the libperl.so (fairly uncommon)m and the "pkg shlib" does a very nice job of finding these. Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 On Fri, Aug 23, 2019 at 5:10 AM Adam Weinberger wrote: > On Fri, Aug 23, 2019 at 12:25 AM Kevin Oberman > wrote: > > > > On Thu, Aug 22, 2019 at 4:56 PM Paul Macdonald via freebsd-ports < > > freebsd-ports@freebsd.org> wrote: > > > > > > > > I wonder if i'm not alone in wishing the perl maintainer would update > > > UPDATING with the actual up to date commands to do an upgrade, instead > > > of referring to an entry from many moons ago > > > > > > I'm not lazy, but if it was done once, this would actually save effort > > > for 100 boxes for me, and i suspect save effort for 10's of thousands > > > of people ( and avoid easy to make mistakes) > > > > > > Please take the time to make UPDATING correct ( and actually up to > date) > > > , it'll save many man hours! > > > > > > ( i do appreciate their time is valuable too, but there is a > > > multiplication effect) > > > > > > > > > sincere thanks > > > > > > Paul. > > > > > > > It's also annoying that, if I followed the instructions in hte 3 year old > > entry, I would have re-installed about 400 ports which would have taken > > several hours. By removing the "-f" from the portmaster command reduced > the > > re-build to about 40 ports, most small p5- ports requiring less than a > > minute each. Whole process took under an hour... likely about 15 minutes. > > No idea why the portmaster command includes it. portmaster is smart > enough > > to figure it out correctly and not re-install a bunch of ports that don't > > need it. > > Nearly all committers use poudriere, so we rely on your input for > legacy tool instructions. If the commands should be different, please > run it through s...@freebsd.org (the portmaster maintainer) and give us > the correct commands. > > # Adam > > > -- > Adam Weinberger > ad...@adamw.org > https://www.adamw.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"
Re: perl port updates
On Thu, Aug 22, 2019 at 4:56 PM Paul Macdonald via freebsd-ports < freebsd-ports@freebsd.org> wrote: > > I wonder if i'm not alone in wishing the perl maintainer would update > UPDATING with the actual up to date commands to do an upgrade, instead > of referring to an entry from many moons ago > > I'm not lazy, but if it was done once, this would actually save effort > for 100 boxes for me, and i suspect save effort for 10's of thousands > of people ( and avoid easy to make mistakes) > > Please take the time to make UPDATING correct ( and actually up to date) > , it'll save many man hours! > > ( i do appreciate their time is valuable too, but there is a > multiplication effect) > > > sincere thanks > > Paul. > It's also annoying that, if I followed the instructions in hte 3 year old entry, I would have re-installed about 400 ports which would have taken several hours. By removing the "-f" from the portmaster command reduced the re-build to about 40 ports, most small p5- ports requiring less than a minute each. Whole process took under an hour... likely about 15 minutes. No idea why the portmaster command includes it. portmaster is smart enough to figure it out correctly and not re-install a bunch of ports that don't need it. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: firefox
On Thu, Aug 15, 2019 at 11:20 PM Jack L. wrote: > On Thu, Aug 15, 2019 at 10:51 AM Kevin Oberman > wrote: > > > > On Thu, Aug 15, 2019 at 1:29 AM Jack L. wrote: > >> > >> On Wed, Aug 14, 2019 at 1:32 PM Miroslav Lachman <000.f...@quip.cz> > wrote: > >> > > >> > @lbutlr wrote on 2019/08/12 07:08: > >> > > On 11 Aug 2019, at 20:29, bruce wrote: > >> > >> I have tried firefox. It crashes regularly > >> > > > >> > > That doesn’t sound right. If Firefox is crashing a lot there is > something not quite right with your system or install. > >> > > >> > I am using Seamonkey on everyday basis. Sometimes my computer is > running > >> > 20+ days without reboot and Seamonkey running all the time with 5 > >> > windows and total count of 200+ openned tabs. No crashes at all. > >> > Firefox crashes instantly after start (even if I delete its profile) > >> > Palemoon, Qupzilla, Iridium crashes few times a day. > >> > LibreOffice, Gimp and other apps are running fine. Only browsers are > so > >> > unstable these days. And as you can read I am not alone with this kind > >> > of experience so I don't think it's just my computer problem. > >> > > >> > Miroslav Lachman > >> > >> yup, they don't make browsers like they used to > > > > > > I'll probably regret opening this potential can of worms, but I find > these reports of instability in Firefox surprising. I have used Firfox as > my web browser on FreeBSD for many year, going back to at least Firefox v3 > and probably v2. I can't say I've never had it crash, but in the past year > I can't recall a single crash on FreeBSD. It has been rock solid. So why is > it failing or some people? (I'll note in passing that Firefox has been > somewhat less stable on Windows 7 where it seems to crash every couple of > weeks. > > > > Possibilities include hardware, especially graphics, web sites visited, > and Firefox configuration. Lots of tabs may be an issue as I try to keep my > open tabs under 20. > > I can't imagine trying to deal with 200+, but it must eat a lot of > resources. That may be tied to the failures reported. > > My experience with firefox is it gets slower and slower and slower > until it's practically unusable until it's restarted (even having only > the gmail tab open for days) > Try looking at the memory pressure on your system. Firefox, especially when running heavy-duty pages like gmail. I noticed that rss (res on top) would grow until swapping started. It would continue until my swap partition was full followed by the expected... the system grinding to a halt. I could usually catch it before swap was full and restarting firefox would fix it for a while. If you want to monitor memory use, I suggest sysutils/gkrellm2. To looks at firefox use, "ps -uc | grep firefox" provides the rss for all firefox processes. rss is hte 6th column. You could write a quick script to sum the numbers, but I have just added them up manually. I increased RAM from 4G to 8, the max for the hardware, and that improved things a lot. (If you add memory, don't forget to enlarge swap.) Firefox still is huge, but the system now handles it much better. I checked the INITIAL memory use by Firefox recently and it was nearly 3.7G. And it grows from there. I saw similar issues with chrome, but I no longer use it. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: [drugg...@apache.org: [ANNOUNCEMENT] Apache HTTP Server 2.4.41 Released]
On Thu, Aug 15, 2019 at 3:25 AM The Doctor via freebsd-ports < freebsd-ports@freebsd.org> wrote: > Heads up Apache porters! > > - Forwarded message from Daniel Ruggeri - > > Date: Wed, 14 Aug 2019 15:50:10 -0500 > From: Daniel Ruggeri > To: annou...@httpd.apache.org > Subject: [ANNOUNCEMENT] Apache HTTP Server 2.4.41 Released > > Apache HTTP Server 2.4.41 Released > [...] I think you are running a bit late. The 2.4.41 port was committed yesterday at 19:25 UTC... about 14 hours before this was sent out. So far, I have seen no issues. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: firefox
On Thu, Aug 15, 2019 at 1:29 AM Jack L. wrote: > On Wed, Aug 14, 2019 at 1:32 PM Miroslav Lachman <000.f...@quip.cz> wrote: > > > > @lbutlr wrote on 2019/08/12 07:08: > > > On 11 Aug 2019, at 20:29, bruce wrote: > > >> I have tried firefox. It crashes regularly > > > > > > That doesn’t sound right. If Firefox is crashing a lot there is > something not quite right with your system or install. > > > > I am using Seamonkey on everyday basis. Sometimes my computer is running > > 20+ days without reboot and Seamonkey running all the time with 5 > > windows and total count of 200+ openned tabs. No crashes at all. > > Firefox crashes instantly after start (even if I delete its profile) > > Palemoon, Qupzilla, Iridium crashes few times a day. > > LibreOffice, Gimp and other apps are running fine. Only browsers are so > > unstable these days. And as you can read I am not alone with this kind > > of experience so I don't think it's just my computer problem. > > > > Miroslav Lachman > > yup, they don't make browsers like they used to I'll probably regret opening this potential can of worms, but I find these reports of instability in Firefox surprising. I have used Firfox as my web browser on FreeBSD for many year, going back to at least Firefox v3 and probably v2. I can't say I've never had it crash, but in the past year I can't recall a single crash on FreeBSD. It has been rock solid. So why is it failing or some people? (I'll note in passing that Firefox has been somewhat less stable on Windows 7 where it seems to crash every couple of weeks. Possibilities include hardware, especially graphics, web sites visited, and Firefox configuration. Lots of tabs may be an issue as I try to keep my open tabs under 20. I can't imagine trying to deal with 200+, but it must eat a lot of resources. That may be tied to the failures reported. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: PHP version retirement
On Sun, Aug 11, 2019 at 4:23 PM Martin Waschbüsch wrote: > > > Am 11.08.2019 um 23:31 schrieb Wolfgang Zenker < > wolfg...@lyxys.ka.sub.org>: > > > > * Martin Waschbüsch [190811 20:41]: > >> [..] > >>> You could also have used the quarterly branch, which keeps software > till > >>> the end of the quarter. In the case of php 5.6 it would have given you > >>> time until March 31st, and would have included version 5.6.40 > > > >> 5.6.40 never made it into the main ports tree. Are you sure it was > available in the quarterly snapshot? > > > > I am sure. You can check for yourself using the svnweb interface at the > > FreeBSD website; php 5.6.40 was added to the 2019Q1 branch on Jan 26th > > Thanks, Wolfgang, for pointing that out. > > Up to now I always thought of quarterly as a static snapshot of the main > ports tree made at a given point in time. > OK. Where did 5.6.40 come from? I just looked at the ports repo and it was NEVER committed there. The very last commit to ports/head/lang/php56 was 5.6.39. Whil it has no impact on me, I find it very odd to find a package that never existed in ports. That makes it impossible for me to access the source for this package and recreate it for any reason. My gut feeling is that this is broken and should never happen. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: Possible issues with FreeBSD ports ML?
Philip, Thanks so much for your time. I don't know if anything was ever wrong or almost everyone on mailing lists just took a couple of days off, but traffic volume on the lists now looks completely normal and I received no responses of lost posts to ports. Thanks so much for taking the time to look at it and sorry for the noise. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 On Thu, Aug 1, 2019 at 12:00 AM Philip Paeps wrote: > On 2019-08-01 11:35:54 (+0530), Kevin Oberman wrote: > > Over the past dy and a half there have been no posts on the ports > > list. The last user-posted message was on July 29 at 23:30:51. There > > was a message from portscout about 14 yours later, but nothing else. > > This is based on the contents of the ML archive, not just what I have > > been seeing. Others of the dozen FreeBSD lists I read have also been a > > bit quiet with only a very small number of posts. > > postmas...@freebsd.org is aware of what I have seen but have not been > > able to confirm a problem. > > > > If this message actually got to you and you have sent a message to > > ports or some other list after 16:00 UTC on July 30, please DO NOT > > reply to the list, but send me a note with the ML to which the post > > was sent and the time the post was sent (or your best guess) and/or > > postmas...@freebsd.org. Mail log entries would be especially useful. > > > > Perhaps nothing is wrong, but to go two days with only about a dozen > > messages from several normally active lists like ports, current, > > stable, and x11. > > > > As I may be wrong and everyone who normally would post have all taken > > summer vacation at the same time. If so, I do apologize for wasting > > your time. > > As far as postmaster can tell, mail is flowing normally. > > If your messages to FreeBSD mailing lists are bouncing or being delayed, > please try to reach out to postmas...@freebsd.org so we can investigate. > Given the volume of mail that goes through FreeBSD.org, debugging > problems is difficult without at least some details about specific > messages or hosts to grep for. > > Philip [hat: postmaster] > > -- > Philip Paeps > Senior Reality Engineer > Alternative Enterprises > ___ > 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" > ___ 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"
Possible issues with FreeBSD ports ML?
Over the past dy and a half there have been no posts on the ports list. The last user-posted message was on July 29 at 23:30:51. There was a message from portscout about 14 yours later, but nothing else. This is based on the contents of the ML archive, not just what I have been seeing. Others of the dozen FreeBSD lists I read have also been a bit quiet with only a very small number of posts. postmas...@freebsd.org is aware of what I have seen but have not been able to confirm a problem. If this message actually got to you and you have sent a message to ports or some other list after 16:00 UTC on July 30, please DO NOT reply to the list, but send me a note with the ML to which the post was sent and the time the post was sent (or your best guess) and/or postmas...@freebsd.org. Mail log entries would be especially useful. Perhaps nothing is wrong, but to go two days with only about a dozen messages from several normally active lists like ports, current, stable, and x11. As I may be wrong and everyone who normally would post have all taken summer vacation at the same time. If so, I do apologize for wasting your time. Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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 packages being built with stale dependencies?
On Thu, Jul 25, 2019 at 10:52 AM Kevin Oberman wrote: > Today I tried updating llvm80 to the newest version, 8.0.1, using pkg. I > discovered that the package for llvm80 is built using the deprecated and > soon to expire sambe47. Last week, in preparation for the expiry , I > updated to samba48 and I assumed that any ports that were being packaged > for "latest" would also be built with the default versions of dependencies. > SAMBA_DEFAULT was changed to samba48 back on June 8, so why are "LATEST" > packages still being built with samba47? > Thanks to David's nudge I just learned something new about pkg upgrade. If there are any installed ports, whether built from source or installed from packages, that are missing dependencies, pkg will try to install them for any package upgrade even if the package being upgraded has no dependency on that port. Perhaps the --force option would have bypassed this. The man page is not clear. In any case, that was the problem and re-installing the two packages that the use of "portmaster -o" missed when updating samba47 to samba48. I probably did something wrong. I'm still confused, but things are now working and everything seems clean. -- > Kevin Oberman, Part time kid herder and retired Network Engineer > E-mail: rkober...@gmail.com > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 > ___ 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: Massive PORTS_REVISION bump after making gcc-9.1 default
Gerald,
Thanks for our excellent explanation. I must admit that I did not think
about various archs. So, now I understand why the PORTREVISION was bumped
and that I don't need to go back and build the ports that were rebuilt
prior to the gcc9-9.1 upgrade. I trust tat portmaster did hte right thing.
(Yes, I suppose that there is a slight risk, but I'll take it!)
Now, why the heck do rust and llvm both have packages that require samba47.
I don't see why they require samba at all, let alone a deprecated version
that will expire in about a week. Since I'm trying to upgrade a package for
amd64, I can't see archs being an issue, so I'm baffled. But that's a
different thread.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
On Sun, Jul 28, 2019 at 12:12 PM Lorenzo Salvadore via freebsd-ports <
freebsd-ports@freebsd.org> wrote:
>
> ‐‐‐ Original Message ‐‐‐
> On Sunday 28 July 2019 20:56, Gerald Pfeifer wrote:
>
> > On Sun, 28 Jul 2019, Kevin Oberman wrote:
> >
> > > The description of the commit states:
> > > This includes ports
> > >
> > > - with USE_GCC=yes or USE_GCC=any,
> > > - with USES=fortran,
> > > - using Mk/bsd.octave.mk which in turn features USES=fortran, and
> > > - with USES=compiler specifying openmp, nestedfct, c11, c++0x,
> c++11-lang,
> > > c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
> > > plus, everything INDEX-11 shows with a dependency on lang/gcc9 now.
> > >
> > >
> > > This would appear to me like it did catch a great many ports which are
> > > not build with or any anything to do will gcc, though I am not sure.
> >
> > These ports may not use GCC on your system, or even the majority of
> > systems, but there are systems and situations where they do, and bumping
> > PORTREVISION is a global binary decision for each port considered.
> >
> > > E.g. I thought that USES=compiler:c11 and similar were asking for
> > > c11 semantics from whatever compiler was used but
> >
> > Let's look at your example. ports/Mk/Uses/compiler.mk has the following
> > on USES=compiler:c11:
> >
> > .if ${_COMPILER_ARGS:Mc11}
> > .if !${COMPILER_FEATURES:Mc11}
> > .if (defined(FAVORITE_COMPILER) && ${FAVORITE_COMPILER} == gcc) ||
> > (${ARCH} != amd64 && ${ARCH} != i386) # clang not always supported on
> Tier-2
> > USE_GCC= yes
> > CHOSEN_COMPILER_TYPE= gcc
> > .elif ${COMPILER_TYPE} == gcc
> >
> > That is, if a user has set a preference for GCC or for non x86/x86-64
> > platforms, GCC is used.
> >
> > And if there is one legitimate configuration on the planet where a
> > PORTREVISION bump is required, we have to perform it in our repository.
> >
> > (This is not saying I may not have made a mistake somewhere, but in
> > general those bumps do appear necessary.)
> >
> > Gerald
>
> It might be useful to add a command to pkg that bumps PORTREVISION
> for installed packages without really building them again, for those cases
> when users know that they are not affected by the bump.
> I think at the moment this is possible only by manually modifying
> /var/db/pkg/local.sqlite (I never tried).
>
> Lorenzo Salvadore.
> ___
> 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"
>
___
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: Massive PORTS_REVISION bump after making gcc-9.1 default
On Sun, Jul 28, 2019 at 7:06 AM Stefan Esser wrote: > Am 28.07.19 um 01:26 schrieb Kevin Oberman: > > Today I was hit with 226 ports needing update. With one exception, all > were > > the result of the bump or the default gcc version to 9.1. The problem is > > that 9.1 was not installed first, so over 43 of these ports were rebuilt > > with the exact same compiler it was built with before the rebuild, eating > > up 2:45 of time on my build system. I'm sure if was less for many as my > > build system is over 8 years old. It was non-trivial in any case. > > Which port management tool did you use to rebuild the updated ports? > > I just checked what portmaster does, and it appears to build gcc-9.1 > before starting to update ports that depend on it. > > It was the 78th port out of 653 out-dated ports (most of them due to > a bumped port revision because of the gcc update), and I checked with > "make all-depends-list" that none of the first 77 ports depended on > gcc ... > > > Should an install of gcc9 preceded all updates? Perhaps a note in > UPDATING? > > I certainly looked there before I started when I saw 226 ports in the > list. > > Updating required build tools before ports that require them should > be automatic, if a tool like portmaster, portupgrade or poudriere is > used. > > Regards, STefan > I used "portmaster -a". The problem is that all ports compiled with gcc had PORTREVISION bumped. Most do not have a run-time dependency on gcc. I am pretty sure that gcc9 was updated prior to the build of any port that did have a run dependency, but that is a tiny minority of the ports that had PORTREVISION bumped. It deems likely that the code generated by gcc9 will be different from that generated by gcc8 and I admit that I lack the expertise to know whether this really justifies a port rebuild. The description of the commit states: This includes ports - with USE_GCC=yes or USE_GCC=any, - with USES=fortran, - using Mk/bsd.octave.mk which in turn features USES=fortran, and - with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang, c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib plus, everything INDEX-11 shows with a dependency on lang/gcc9 now. This would appear to me like it did catch a great many ports which are not build with or any anything to do will gcc, though I am not sure. E.g. I thought that USES=compiler:c11 and similar were asking for c11 semantics from whatever compiler was used but, again, I am not familiar enough with compilers to be clear on this. My days of serious coding ended back to the 80s and were generally focused on assembly language and several languages which have not been used this century. So, do I really need to re-install audio/faac which has "USES=compiler:c11 "? I seriously doubt it, but I'm just not sure, which is why I asked. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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"
Massive PORTS_REVISION bump after making gcc-9.1 default
Today I was hit with 226 ports needing update. With one exception, all were the result of the bump or the default gcc version to 9.1. The problem is that 9.1 was not installed first, so over 43 of these ports were rebuilt with the exact same compiler it was built with before the rebuild, eating up 2:45 of time on my build system. I'm sure if was less for many as my build system is over 8 years old. It was non-trivial in any case. Should an install of gcc9 preceded all updates? Perhaps a note in UPDATING? I certainly looked there before I started when I saw 226 ports in the list. Should I rebuild the ports that were rebuilt prior to the installation of gcc-9.1? -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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/llvm80 requires many python 2.7 ports?
Thanks, Brooks! Now if the package builder would use start using samba48 instead of 47, I'll be able to install the package. I'm really baffled why "LATEST" is still being built with a deprecated, nearly expired port almost two months after the default version was changed, but I'll admit to not being familiar with the package building system details. Still,things are going to break really soon when samba47 goes away. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 On Thu, Jul 25, 2019 at 3:07 PM Brooks Davis wrote: > On Thu, Jul 25, 2019 at 02:57:29PM -0700, Kevin Oberman wrote: > > I just went to build llvm80 after discovering that I could not install > the > > package without moving from the drfault samba48 back to the deprecated > > samba47. > > > > When I try to build the port, I get: > > Upgrade llvm80-8.0.0_2 to llvm80-8.0.1 > > Install textproc/py-recommonmark@py27 > > Install textproc/py-docutils@py27 > > Install textproc/py-sphinx@py27 > > Install devel/py-Jinja2@py27 > > Install devel/py-babel@py27 > > Install devel/py-pytz@py27 > > Install textproc/py-MarkupSafe@py27 > > Install devel/py-typing@py27 > > Install graphics/py-imagesize@py27 > > Install textproc/py-alabaster@py27 > > Install textproc/py-pygments@py27 > > Install textproc/py-snowballstemmer@py27 > > Install textproc/py-pystemmer@py27 > > Install textproc/py-sphinx_rtd_theme@py27 > > Install textproc/py-sphinxcontrib-websupport@py27 > > Install www/py-requests@py27 > > Install dns/py-idna@py27 > > Install net/py-urllib3@py27 > > Install net/py-ipaddress@py27 > > Install net/py-pysocks@py27 > > Install security/py-certifi@py27 > > Install security/py-cryptography@py27 > > Install devel/py-asn1crypto@py27 > > Install devel/py-cffi@py27 > > Install devel/py-pycparser@py27 > > Install security/py-openssl@py27 > > Install textproc/py-chardet@py27 > > Install devel/py-pytest-runner@py27 > > Install devel/py-setuptools_scm@py27 > > > > Is llvm80 really still stuck using v2 Python? I looked at the very > complex > > Makefile, and it's very clear: _USES_PYTHON?= python:2.7,build > > > > Will this going away some day soon? I know that end of 2.7 support is > > approaching and I have only a handfull of python 2.7 ports left, mostly > to > > support print/hplip (HP printer drivers for CUPS) and hope to get rid of > > them soime day soon. > > Historically LLVM has required Python v2. I've not checked if 8.0.1 can > be pinned to 3.6 like I've done with llvm-devel. llvm90 (coming soon) > will use python 3.6. I'll keep switching llvm80 in mind, but given that > such a change will require everyone to rebuild it I'll probably wait and > combine it with other changes. > > -- Brooks > ___ 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"
devel/llvm80 requires many python 2.7 ports?
I just went to build llvm80 after discovering that I could not install the package without moving from the drfault samba48 back to the deprecated samba47. When I try to build the port, I get: Upgrade llvm80-8.0.0_2 to llvm80-8.0.1 Install textproc/py-recommonmark@py27 Install textproc/py-docutils@py27 Install textproc/py-sphinx@py27 Install devel/py-Jinja2@py27 Install devel/py-babel@py27 Install devel/py-pytz@py27 Install textproc/py-MarkupSafe@py27 Install devel/py-typing@py27 Install graphics/py-imagesize@py27 Install textproc/py-alabaster@py27 Install textproc/py-pygments@py27 Install textproc/py-snowballstemmer@py27 Install textproc/py-pystemmer@py27 Install textproc/py-sphinx_rtd_theme@py27 Install textproc/py-sphinxcontrib-websupport@py27 Install www/py-requests@py27 Install dns/py-idna@py27 Install net/py-urllib3@py27 Install net/py-ipaddress@py27 Install net/py-pysocks@py27 Install security/py-certifi@py27 Install security/py-cryptography@py27 Install devel/py-asn1crypto@py27 Install devel/py-cffi@py27 Install devel/py-pycparser@py27 Install security/py-openssl@py27 Install textproc/py-chardet@py27 Install devel/py-pytest-runner@py27 Install devel/py-setuptools_scm@py27 Is llvm80 really still stuck using v2 Python? I looked at the very complex Makefile, and it's very clear: _USES_PYTHON?= python:2.7,build Will this going away some day soon? I know that end of 2.7 support is approaching and I have only a handfull of python 2.7 ports left, mostly to support print/hplip (HP printer drivers for CUPS) and hope to get rid of them soime day soon. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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"
Latest packages being built with stale dependencies?
Today I tried updating llvm80 to the newest version, 8.0.1, using pkg. I discovered that the package for llvm80 is built using the deprecated and soon to expire sambe47. Last week, in preparation for the expiry , I updated to samba48 and I assumed that any ports that were being packaged for "latest" would also be built with the default versions of dependencies. SAMBA_DEFAULT was changed to samba48 back on June 8, so why are "LATEST" packages still being built with samba47? -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: problem with bind911 or 914
On Wed, May 22, 2019 at 8:54 AM Wojciech Puchar wrote: > i've reinstalled bind914 (and then tried 911 too) after updating to latest > FreeBSD-11 > > and the problem is that bind cannot perform any TCP transfers > > in logs i'm getting like this > > May 22 20:50:55 <3.6> puchar named[67338]: transfer of > 'icetransport.pl/IN' from 84.10.41.58#53: connected using > 194.1.144.90#44228 > May 22 20:50:55 <3.3> puchar named[67338]: transfer of > 'icetransport.pl/IN' from 84.10.41.58#53: failed while receiving > responses: host > May 22 20:50:55 <3.6> puchar named[67338]: transfer of > 'icetransport.pl/IN' from 84.10.41.58#53: Transfer status: host > unreachable > May 22 20:50:55 <3.6> puchar named[67338]: transfer of > 'icetransport.pl/IN' from 84.10.41.58#53: Transfer completed: 0 messages, > 0 recor > > > while on 84.10.41.58 i see > > May 22 20:50:51 icetransport named[4479]: client @0x3bc271400 > 194.1.144.90#44228 (icetransport.pl): transfer of 'icetransport.pl/IN': > AXFR started (serial 3873) > May 22 20:50:51 icetransport named[4479]: client @0x3bc271400 > 194.1.144.90#44228 (icetransport.pl): transfer of 'icetransport.pl/IN': > AXFR ended > May 22 20:50:51 icetransport named[4479]: client @0x3c0129400 > 194.1.144.90#44231 (icetransport.pl): transfer of 'icetransport.pl/IN': > AXFR started (serial 3873) > May 22 20:50:51 icetransport named[4479]: client @0x3c0129400 > 194.1.144.90#44231 (icetransport.pl): transfer of 'icetransport.pl/IN': > AXFR ended > > > using FreeBSD base system host program i can transfer this domain without > problem too. > > > this way named now cannot update any of domains from master server. > > furthermore i see LOTS of things like this in log: > > May 22 20:51:10 <3.3> puchar named[67338]: dispatch 0x804544e00: shutting > down due to TCP receive error: 193.108.91.73#53: host unreachable > > > > seems like named connect properly over tcp and then reports error. > > Any idea what's this and how to fix it? > Looks to me like either a firewall or policy issue, not BIND. Back a decade ago, many firewalls defaulted to blocking tcp/53. This was based on the unfortunate decision to list the use of tcp/53 as "SHOULD" in the RFC instead of "MUST", but this should produce a timeout,not a host unreachable. "host unreachable" is should be the result of an ICMP message coming back from a router. Take a look at the traffic with tcpdump or wireshark and see if you are getting no response (firewall) or an ICMP Host Unreachable. If the latter, it is coming from a router between you and Akamai and is the result of policy; most likely of your ISP. In neither case is you local BIND at fault. Historically ISPs have loved to play rude games with DNS, either deliberately or due to software flaws in things like load balancers. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: portupgrade + FLAVORS
Oops. Disregard. Confusing portupgrade with portmaster.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
On Mon, May 6, 2019 at 6:03 PM Kevin Oberman wrote:
> Looks like the maintainer should be on the CC, so I added Stefan.
> --
> Kevin Oberman, Part time kid herder and retired Network Engineer
> E-mail: rkober...@gmail.com
> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
>
>
> On Mon, May 6, 2019 at 11:35 AM Bob Willcox wrote:
>
>> On Sun, Apr 07, 2019 at 08:51:57PM -0500, Matthew D. Fuller wrote:
>> > For any portupgrade users still out there wishing for FLAVOR support,
>> > I have patches to add it. I've been running them here locally for a
>> > few weeks without incident (apart from an extra upgrade or two
>> > actually working without manual intervention/resort to portmaster,
>> > that is). Dropping the attached patch into
>> > $PORTS/ports-mgmt/portupgrade/files/patch-flavors and rebuilding it is
>> > a simple shortcut to getting it in place.
>> >
>> > I haven't done any testing of using portupgrade with pre-built
>> > packages (is there even any reason to post-pkg?), or using portinstall
>> > (never saw the point), but it seems to handle the upgrading path just
>> > fine.
>> >
>> >
>> > Also sitting in a PR upstream at
>> > https://github.com/freebsd/portupgrade/pull/72
>> >
>> >
>> > --
>> > Matthew Fuller (MF4839) | fulle...@over-yonder.net
>> > Systems/Network Administrator | http://www.over-yonder.net/~fullermd/
>> >On the Internet, nobody can hear you scream.
>>
>> > --- bin/portupgrade.orig 2018-03-09 18:59:29 UTC
>> > +++ bin/portupgrade
>> > @@ -1147,6 +1147,11 @@ def get_make_args(origin, pkgname = nil)
>> >else
>> > args = $make_args.split(' ')
>> >end
>> > +
>> > + if flavor = origin[/@(.+)$/, 1]
>> > +args << 'FLAVOR=' + flavor
>> > + end
>> > +
>> >quoted = 0
>> >n = 0
>> >is_quoted = false
>> > --- lib/pkgtools/pkgdb.rb.orig2018-03-09 18:59:29 UTC
>> > +++ lib/pkgtools/pkgdb.rb
>> > @@ -425,10 +425,20 @@ class PkgDB
>> >@installed_pkgs = []
>> >@installed_ports = []
>> >@db = {}
>> > +
>> > + flavors = {}
>> > + pkg_flavors = xbackquote(PkgDB::command(:pkg), 'annotate', '-Sa',
>> > + 'flavor').split("\n")
>> > + pkg_flavors.each do |line|
>> > +pkg, flavor = line.sub(/: Tag: flavor Value: /, ':').split(':')
>> > +flavors[pkg] = flavor
>> > + end
>> > +
>> >pkg_origins = xbackquote(PkgDB::command(:pkg), 'query', '%n-%v
>> %o').split("\n")
>> >pkg_origins.each do |line|
>> > pkg, origin = line.split(' ')
>> > @installed_pkgs << pkg
>> > +origin << '@' + flavors[pkg] if flavors[pkg]
>> > add_origin(pkg, origin)
>> >end
>> >@installed_pkgs.freeze
>> > --- lib/pkgtools/portsdb.rb.orig 2018-03-09 18:59:29 UTC
>> > +++ lib/pkgtools/portsdb.rb
>> > @@ -325,6 +325,7 @@ class PortsDB
>> >end
>> >
>> >def portdir(port)
>> > +port = port.sub(/@.*$/, '')
>> > File.join(ports_dir, port)
>> >end
>> >
>>
>> > ___
>> > 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
>> "
>>
>> Hi Mathew,
>>
>> Thanks for the flavors patch to portupgrade. As with some others here it
>> is
>> still my preferred tool for keeping my ports up-to-date.
>>
>> Any word on when/if your patch will be integraded into the port proper?
>>
>> Thanks again,
>> Bob
>>
>>
>> --
>> Bob Willcox| "The only way to get rid of temptation is to yield to
>> it...
>> b...@immure.com | I can resist everything but temptation."
>> Austin, TX | - Oscar Wilde
>> ___
>> 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"
>>
>
___
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: portupgrade + FLAVORS
Looks like the maintainer should be on the CC, so I added Stefan.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
On Mon, May 6, 2019 at 11:35 AM Bob Willcox wrote:
> On Sun, Apr 07, 2019 at 08:51:57PM -0500, Matthew D. Fuller wrote:
> > For any portupgrade users still out there wishing for FLAVOR support,
> > I have patches to add it. I've been running them here locally for a
> > few weeks without incident (apart from an extra upgrade or two
> > actually working without manual intervention/resort to portmaster,
> > that is). Dropping the attached patch into
> > $PORTS/ports-mgmt/portupgrade/files/patch-flavors and rebuilding it is
> > a simple shortcut to getting it in place.
> >
> > I haven't done any testing of using portupgrade with pre-built
> > packages (is there even any reason to post-pkg?), or using portinstall
> > (never saw the point), but it seems to handle the upgrading path just
> > fine.
> >
> >
> > Also sitting in a PR upstream at
> > https://github.com/freebsd/portupgrade/pull/72
> >
> >
> > --
> > Matthew Fuller (MF4839) | fulle...@over-yonder.net
> > Systems/Network Administrator | http://www.over-yonder.net/~fullermd/
> >On the Internet, nobody can hear you scream.
>
> > --- bin/portupgrade.orig 2018-03-09 18:59:29 UTC
> > +++ bin/portupgrade
> > @@ -1147,6 +1147,11 @@ def get_make_args(origin, pkgname = nil)
> >else
> > args = $make_args.split(' ')
> >end
> > +
> > + if flavor = origin[/@(.+)$/, 1]
> > +args << 'FLAVOR=' + flavor
> > + end
> > +
> >quoted = 0
> >n = 0
> >is_quoted = false
> > --- lib/pkgtools/pkgdb.rb.orig2018-03-09 18:59:29 UTC
> > +++ lib/pkgtools/pkgdb.rb
> > @@ -425,10 +425,20 @@ class PkgDB
> >@installed_pkgs = []
> >@installed_ports = []
> >@db = {}
> > +
> > + flavors = {}
> > + pkg_flavors = xbackquote(PkgDB::command(:pkg), 'annotate', '-Sa',
> > + 'flavor').split("\n")
> > + pkg_flavors.each do |line|
> > +pkg, flavor = line.sub(/: Tag: flavor Value: /, ':').split(':')
> > +flavors[pkg] = flavor
> > + end
> > +
> >pkg_origins = xbackquote(PkgDB::command(:pkg), 'query', '%n-%v
> %o').split("\n")
> >pkg_origins.each do |line|
> > pkg, origin = line.split(' ')
> > @installed_pkgs << pkg
> > +origin << '@' + flavors[pkg] if flavors[pkg]
> > add_origin(pkg, origin)
> >end
> >@installed_pkgs.freeze
> > --- lib/pkgtools/portsdb.rb.orig 2018-03-09 18:59:29 UTC
> > +++ lib/pkgtools/portsdb.rb
> > @@ -325,6 +325,7 @@ class PortsDB
> >end
> >
> >def portdir(port)
> > +port = port.sub(/@.*$/, '')
> > File.join(ports_dir, port)
> >end
> >
>
> > ___
> > 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"
>
> Hi Mathew,
>
> Thanks for the flavors patch to portupgrade. As with some others here it is
> still my preferred tool for keeping my ports up-to-date.
>
> Any word on when/if your patch will be integraded into the port proper?
>
> Thanks again,
> Bob
>
>
> --
> Bob Willcox| "The only way to get rid of temptation is to yield to
> it...
> b...@immure.com | I can resist everything but temptation."
> Austin, TX | - Oscar Wilde
> ___
> 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"
>
___
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: gnupod - can't use hash as reference.
On Mon, Apr 29, 2019 at 1:17 PM Steve Roome wrote: > Here's patches to fix gnupod, as attachments, as they should have been. > > Sorry about that, > > Steve > Thanks for working on gunpod. This, however, is not the proper place for such proposals. Please submit a bug report to the FreeBSD bugzilla at https://bugs.freebsd.org/bugzilla/ Since the port is orphaned, I assume that the upstream is no longer maintained and may no longer available for download. If you are willing to maintain the source and can make it available. github and sourceforge are to of the many places that may be used for this. The FreeBSD Porter's Handbook goes into details on submitting the port. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: ltmain.sh not found
On Wed, Apr 24, 2019 at 9:05 AM Christoph Moench-Tegeder wrote: > ## Willem Offermans (wil...@offermans.rompen.nl): > > > Unfortunately it is probably not gawk in my case, which causes trouble. > > However, your response indicates that the problem will be solved after I > > have updated/reinstalled the guilty one. > > There's sysutils/bsdadminscripts, which provides pkg_libchk: that's a > tool for checking if any port misses a shared library. It has been > rather helpful back when I was using portupgrade... > > Regards, > Christoph > I believe bsdadminscripts has been withdrawn. You should use "pkg check -B" to check. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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"
devel/autogen upgrade will fail. UPDATING needs an entry
Upgrading devel/autogen will fail as the build procedure will attempt to run the new version, but will find the old library version and error. An entry in UPDATING to the effect that "pkg delete autogen" should by run and then autogen should be reinstalled. This does not apply up upgrading with pkg or building with poudriere. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: dns/dsc on FreeBSD 11.2-p9 and 12.0
On Thu, Apr 18, 2019 at 1:36 PM Kurt Jaeger wrote: > Hi! > > > Thank you for your reply and the check with poudriere > > > > I tried building the port with portmaster and from the ports tree > directly > > with make, make install > > If I build from the ports tree, I can reproduce the problem. > > I have no solution right now besides the suggestion to build > in poudriere 8-} > > -- > p...@opsec.eu+49 171 3101372One year to go ! > ___ > 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" > Taking a quick look, u_int and u_char are not defined POSIX types, but are BSD types defined in sys/types.h. /usr/include/arpa/nameser.h does include sys/types.h, so should be fine. This typically means that something, some dependency, is interfering and causing these types to not be found and poudriere, since it does a clean build, does not hit this issue. I did quickly look at the source files to see where sys/types.h or some other code that would define u_char and u_int might be found, but came up empty. I'd be curious there they are defined in a poudriere build. I see only . and /usr/local/include listed in the compile line. Tracking these things down can be painful. I'm afraid and I will not claim to be great at it. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: first attempt at porting something (fdkaac)
You might take a look at audio/fdk-aac/. Not only will it show you how to do it, it will save you the trouble. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 On Fri, Mar 29, 2019 at 1:23 PM Per Gunnarsson via freebsd-ports < freebsd-ports@freebsd.org> wrote: > Hello! > > I have been trying to create a port of fdkaac (a command line tool for > fdk-aac the library). > > When I compiled it first, I needed to run "autoreconf -i", after which > ./configure, make, make install worked. > > Now I have created a Makefile, distinfo, pkg-descr and pkg-plist. > > The download from github works, but the Makefile has a problem. I just > nicked a Makefile and modified it, that is the way I learn how things work. > > First it seems to find fdk-aac, but then after autoreconf is run it > doesn't find it any longer. > > The files for the port and the information I got about what went wrong > is available in the directory > > https://mustafejen.se/~per/tmp/debug/Myfirstport > > Cheers! > > Per Gunnarsson > ___ > 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" > ___ 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: databases/mongodb40 port proposal
On Thu, Feb 28, 2019 at 7:39 AM Matthias Fechner wrote: > Dear Andrew, > > Am 28.02.2019 15:48, schrieb Andrew Shevchuk: > > Latest stable MongoDB (4.0.6) port proposal: > > > https://raw.githubusercontent.com/ashevchuk/mongodb40-freebsd-port/master/mongodb40.patch > > thanks a lot for this patch! > I just tried to apply it so I can do some tests but I'm unable to apply > your patch. > I tested it with: > patch -i mongodb40.patch > > while beeing in the ports directory. > But it complains that it is not able to find the file to patch: > > # patch -i mongodb40.patch > Hmm... Looks like a normal diff to me... > The text leading up to this was: > -- > |diff -rNd databases/Makefile.orig databases/Makefile > -- > File to patch: > > > How to apply this patch? > > > -- > Gruß > Matthias > Most patches against ports, including this one, assume that the current directory is /usr/ports or whatever directory is your ports tree base directory. Alternatively, you can use '-s N' to ignore the first N directories in the path specified in the patch. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: vim - GTK2 or GTK3?
On Tue, Feb 19, 2019 at 4:26 AM David Demelier wrote: > Le 19/02/2019 à 04:44, Jan Beich a écrit : > > Adam Weinberger writes: > > > >> I'm curious whether the default Vim port should use GTK2 or GTK3 as > >> its UI toolkit, but I use neither so I need input from people here. > >> > >> Right now it defaults to GTK2, but I'm suspecting that more people use > >> GTK3 these days. I haven't run X in about 10 years, so I don't really > >> know one way or the other. If anybody on this list has thoughts about > >> GTK2 vs GTK3 (or something else!) as the default, I'd love to hear it. > > Gtk2 is deprecated and does not support high DPI displays, so it's > already a reason to not use it anymore. > > -- > David > When did that happen? I run Mate desktop which is gtk2 based as are a great many ports. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: Using LibreSSL with only one or a subset of all installed ports
On Wed, Feb 6, 2019 at 7:55 AM Nick Rogers wrote:
> I am wondering if it is wise or possible to use libressl for only a single
> installed port, while continuing to use OpenSSL from Base for all remaining
> installed ports. I would like to do this in order to get around the fact
> that lang/phantomjs does not compile against openssl 1.1.x due to API
> changes, and fixing it is less than trivial. However, I am not quite ready
> to switch other ports to LibreSSL.
>
> My thought was to use the following approach in make.conf when building via
> poudriere.
>
> .if ${.CURDIR:M*/lang/phantomjs}
> DEFAULT_VERSIONS+= ssl=libressl
> .endif
>
> I am hoping for some advice as to whether or not this will work, or if its
> a terrible idea, or if there is perhaps a better way to toggle libressl
> per-port. All the port documentation I can find suggests an outright switch
> to libressl for all ports, so I am concerned there is something I am
> missing that will not be happy?
>
Along this path lies madness! Not that it can't work, but it is very
dangerous and likely to get more complicated over time.
The problem is with having multiple sharable libraries (.so) of the same
name. The loader will refuse to load an executable if it attempts to load
two or more shareable libraries that have a common name as it is not
possible to determine which library to use for any reverence. If phantomjs
calls ssl routines directly and also is linked to a shareable that is
linked to either the openssl port installed shareable or the base system
shareable, the code will not load. As linkages grow more and more complex,
this tends to turn into a real rats nest.
I'm not saying that it can't be done, but you have to know all of the
linkages and be very sure that there are no conflicts.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
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: llvm60 required by ???
On Sat, Jan 12, 2019 at 12:36 AM Mark Millard via freebsd-ports < freebsd-ports@freebsd.org> wrote: > > Is there anything other than mesa-dri that requires this port? > > https://www.freshports.org/devel/llvm60/ shows: > > This port is required by: > > for Build > • devel/cpp2py > • devel/cquery > • devel/creduce > • devel/flang > • devel/flang-clang > • devel/gnome-builder > • devel/include-what-you-use > • devel/libclc > • devel/qt5-qdoc > • graphics/mesa-libs > • graphics/openshadinglanguage > • lang/beignet > • lang/crystal > • lang/ldc > • math/blis > • math/cvc4 > • math/libpgmath > • science/dft_tools > • science/triqs > • www/waterfox* > Collapse this list. > for Libraries > • audio/faust > • audio/faustlive > • devel/cquery > • devel/py-llvmlite > • devel/youcompleteme > • lang/crystal > for Run > • audio/csound > • audio/csound6* > • devel/cpp2py > • devel/creduce > • devel/flang > • devel/flang-clang > • devel/gnome-builder > • devel/include-what-you-use > • devel/qt5-qdoc > • devel/xtoolchain-llvm60 > • graphics/openshadinglanguage > • lang/beignet > • lang/ldc > • math/libpgmath > Collapse this list. > > > > === > Mark Millard > marklmi at yahoo.com > ( dsl-only.net went > away in early 2018-Mar) > While I can't go through all of them, but qr5-qdoc builds fine with llvm70, though I can't promise that it will work. I suspect that the port just needs updating to allow either port. Several of these are llvm related ports that are clearly version specific. I suspect many/most of the others simply need updating to work with llvm70. No, I'm not volunteering. Sorry, but the next few days look very busy. If I get time, I may see if I can check out a few. I don't actually use any of them, so I won't be testing them... only that they build. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: llvm60 required by ???
Try re-building these ports. They will probably re-build with 7.0. I got everything on my system moved to 7.0 except mesa-dri. Oddly, I see that there was a patch in the port to support 7.0. No idea why it still uses 6.0, but I sure would not mind getting rid of it. mesa-lib does not seem to depend on 6.0. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 On Fri, Jan 11, 2019 at 3:55 PM wrote: > On Fri, 11 Jan 2019 16:33:52 -0500 > Robert Huff wrote: > > > > > Is there anything other than mesa-dri that requires this port? > > > > > > Respectfully, > > > > > > Robert Huff > > > > ___ > > 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" > > On mine 12.0-RELEASE-p2 FreeBSD 12.0-RELEASE-p2 GENERIC amd64 > and everything built from ports I got: > > pkg delete llvm60 > Updating database digests format: 100% > Checking integrity... done (0 conflicting) > Deinstallation has been requested for the following 11 packages (of 0 > packages in the universe): > > Installed packages to be REMOVED: > llvm60-6.0.1_5 > libosmesa-18.1.9 > mesa-dri-18.1.9_3 > xorg-7.7_3 > xorg-server-1.18.4_11,1 > xf86-input-keyboard-1.9.0_3 > xf86-input-mouse-1.9.3_2 > xf86-video-scfb-0.0.4_7 > xf86-video-vesa-2.4.0_2 > xf86-video-ati-legacy-7.9.0_3,1 > xorg-drivers-7.7_5 > > Number of packages to be removed: 11 > > The operation will free 862 MiB. > > Proceed with deinstalling packages? [y/N]: n > > > ___ > 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" > ___ 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: Massive PORTREVSION bump for gcc8
On Sat, Dec 15, 2018, 6:32 PM Jan Beich Kevin Oberman writes: > > > This morning the PORTREVISION on at least hundreds of ports was bumped > > because gcc8 was declared as the "canonical" version. As a result, I will > > have about 300 ports to rebuild which will take many hours. > > Why? > > USE_GCC embeds RPATH during build where libgcc_s, libgfortran, > libstdc++, etc. can be found. Mixing different versions (e.g., libgcc_s > from lang/gcc7 with libgfortran from lang/gcc8) may destabilize > runtime. Rebuild is necessary to ensure the consistent state, mainly for > portmaster/portupgrade that don't rebuild every time dependency is > upgraded. > > USE_GCC is implicitly set by USES=compiler on architectures stuck with > GCC in base i.e., powerpc*/sparc64/mips*/riscv*. > > [..] Thanks, Jan. I must admit that I did not think of this, though I should have. Sorry about the noise. -- Kevin Oberman, Retired Network Engineer ___ 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: Massive PORTREVSION bump for gcc8
This really answers nothing. Comments below. On Thu, Dec 13, 2018 at 1:36 AM Mathieu Arnold wrote: > On Wed, Dec 12, 2018 at 10:29:59AM -0800, Kevin Oberman wrote: > > This morning the PORTREVISION on at least hundreds of ports was bumped > > because gcc8 was declared as the "canonical" version. As a result, I will > > have about 300 ports to rebuild which will take many hours. > > Why? > > Because they need to be rebuilt so that they use the new default of gcc8. > Why does this matter? They were already working fine with gcc7. Why is it of any significant benefit to the user to do this massive rebuild? I installed gcc8, and I assume some of the rebuilds are using it, though with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang, c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib leaves me mystified as several of those items will not result in the use of gcc, though there may be some reason I miss. Still, this is the cause of the bump for many of the ports that are being rebuilt with clang. But why is this better than just letting gcc8 build port as they otherwise need updating? Again, this build will typically run for hours on many systems, using a great deal of power and slowing other uses of the systems, if they are not dedicated build systems. > If a port is built and running properly with gcc7, I see no reason to > force > > the rebuild of all of the ports that are built with gcc7. > > If you do not want to upgrade, do not upgrade. Now, if you want to keep > up-to-date, well, you do have to rebuild everything with the new gcc > default. > Since PORTREVISION is bumped, there is no quick way to tell whether a port is showing an update because of the gcc8 bump or because of a real update. Yes, I could look through the ports repository for each port and confirm that it does or does not need a rebuild, but this is really not a practical solution. I normally update all ports to LATEST recularly. I know that I am not alone in doing periodic updates. I know that the FreeBSD package building systems will spend days building LATEST packages, again, to no purpose I can discern. After two days of building, with several failures. I still have 45 to go. The only good thing is that, since there are no real updates, the failures don't really impact the system operations. I'd really just like a real, valid reason that this is beneficial. Honestly, I see no benefit to anyone. -- > Mathieu Arnold > Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: Massive PORTREVSION bump for gcc8
No, it doesn't. The PORTREVISION in the individual ports were bumped, so they will get rebuilt with gcc7 if you set the DEFAULT_VERSION, but it will still show as dated and be rebuilt by any postmaster or poudriere general update. On Wed, Dec 12, 2018, 10:40 AM Steve Kargl On Wed, Dec 12, 2018 at 10:29:59AM -0800, Kevin Oberman wrote: > > This morning the PORTREVISION on at least hundreds of ports was bumped > > because gcc8 was declared as the "canonical" version. As a result, I will > > have about 300 ports to rebuild which will take many hours. > > Why? > > > > If a port is built and running properly with gcc7, I see no reason to > force > > the rebuild of all of the ports that are built with gcc7. This will lead > to > > a delay of probably several days in getting updated packages built for > > LATEST repos and will consume hours of CPU time for everyone using > > poudriere or building from ports. This even impacts (slightly) climate > > change with the extra energy used in rebuilding all of those ports across > > the globe. > > > > Perhaps there was a real reason this was required. I have certainly never > > seen it before for any new compiler version to either gcc or llvm. > > Does adding > > DEFAULT_VERSIONS+=GCC=7 > > to /etc/make.conf prevent the need to update 300 ports. > > -- > Steve > ___ 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"
Massive PORTREVSION bump for gcc8
This morning the PORTREVISION on at least hundreds of ports was bumped because gcc8 was declared as the "canonical" version. As a result, I will have about 300 ports to rebuild which will take many hours. Why? If a port is built and running properly with gcc7, I see no reason to force the rebuild of all of the ports that are built with gcc7. This will lead to a delay of probably several days in getting updated packages built for LATEST repos and will consume hours of CPU time for everyone using poudriere or building from ports. This even impacts (slightly) climate change with the extra energy used in rebuilding all of those ports across the globe. Perhaps there was a real reason this was required. I have certainly never seen it before for any new compiler version to either gcc or llvm. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: print/py27-reportlab still won't build
I have reproduced it and did so before the message, but I am not able to re-open as it is not my ticket. I just discovered that ticket when I was preparing to submit a ticket. It should be re-opened and set to "Affects some people". I have copied Rob Belica, the originator of the ticket. I added details of my configuration to the ticket. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 On Sun, Dec 2, 2018 at 5:46 PM Kubilay Kocak wrote: > On 3/12/2018 12:25 pm, Kevin Oberman wrote: > > I see that https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233323 was > > closed last week as "Overcome by events". How was the problem overcome > and > > by what event. I still am unable to build the port and, as a result, > can't > > upgrade hplip. What am I missing? > > Hi Kevin, > > After confirming the issue is still reproducible after the revision > (r486170) detailed in comment [1], re-open the Bugzilla issue with > details [2][3] of the reproduction case. > > I've corrected the resolution (Overcome By Events -> Unable to > Reproduce) to more accurately reflect the claimed resolution type. > > [1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233323#c1 > [2] System info (uname -a), ports/pkg (latest? quarterly? make.conf) > [3] Full build/error log as an attachment (including OPTIONS, etc) > > ./koobs > > > ___ 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"
print/py27-reportlab still won't build
I see that https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233323 was closed last week as "Overcome by events". How was the problem overcome and by what event. I still am unable to build the port and, as a result, can't upgrade hplip. What am I missing? -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: Resolving ports conflicts for ImageMagick6
On Sun, Nov 18, 2018 at 1:14 PM bob prohaska wrote: > On Sun, Nov 18, 2018 at 07:49:41PM +0100, Christoph Moench-Tegeder wrote: > > ## bob prohaska (f...@www.zefox.net): > > > > > Installing ImageMagick6-6.9.10.14,1... > > > pkg-static: ImageMagick6-6.9.10.14,1 conflicts with > ImageMagick-6.9.9.28_2,1 (installs files into the same place). Problematic > file: /usr/local/bin/Magick++-config > > > *** Error code 70 > > > > Make sure your installed packages are up-to-date with your ports tree. > > Using old packages with a new ports tree (or vice versa) results in... > this. > > I neglected to mention this in on an RPI3, so packages aren't available. > > It never crossed my mind that pkg could be used to remove a port compiled > from source. I tried "make deinstall", but by then the old ImageMagick > port had morphed into ImageMagick6 and deinstall didn't work. > > bob prohaska > While Warren's procedure clearly works, I believe the recommended procedure when a port is renamed is: # pkg set -o graphics/ImageMagick:graphics/ImageMagick6 # portmaster ImageMagick6 or # portmaster -o graphics/ImageMagick6 ImageMagick The '-o', in either case, builds the new port and updates all ports that depend on it with the replacement without trying to rebuild them. Of course, all of this working requires an up to date ports tree. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: Packages not updated?
On Sun, Oct 21, 2018 at 1:32 PM Kevin P. Neal wrote: > So I just saw another post on this list that mentioned the "pkg version > -vL=" > command. Now, I've got a /usr/ports tree used by poudriere and run on the > same machine. I svn updated my /usr/ports and kicked off poudriere. When it > was done I ran "pkg upgrade". But the "pkg version -vL=" still shows this: > > py27-ndg_httpsclient-0.4.2 < needs updating (port has 0.5.1) > py27-pbr-1.8.1_1 < needs updating (port has 3.1.1) > py27-pip-9.0.1 < needs updating (port has 9.0.3) > py27-psutil-5.2.2 < needs updating (port has 5.4.7) > py27-pyasn1-0.2.2 < needs updating (port has 0.4.2) > py27-python2-pythondialog-3.4.0< needs updating (port has 3.4.0_1) > py27-werkzeug-0.12.2 < needs updating (port has 0.14.1) > transmission-web-2.93_1< needs updating (port has 2.94) > > The question is: why are these packages not getting upgraded when I run > pkg upgrade? > > And, yes, pkg version is getting its info from my poudriere server. I'm > looking at the web server logs in real time. > > Any ideas? > -- > Kevin P. Nealhttp://www.pobox.com/~kpn/ > The packages get rebuilt by periodic batch jobs and always lag by about 2-4 days. This assumes that you are updating from head and not the quarterly. There have been issues where a package build run hung and had to be at least kicked and perhaps more that delayed things. It's been 10 days since the last head package update, so I suspect something is hung up. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: pkg-static: xorgproto-2018.4 conflicts with glproto-1.4.17
On Sun, Oct 7, 2018 at 11:33 AM bob prohaska wrote: > On Sun, Oct 07, 2018 at 07:52:48PM +0200, Walter Schwarzenfeld wrote: > > Recent version?? of glib20 is 2.56.1. > > > > > > Ahh! I knew the latest was 2.56.1 but failed to guess it was called > glib20. Tried > just about everything but > > Thank you! > > bob prohaska > Quick check for port names of installed ports: # pkg info -o glib-\* glib-2.56.1_1,1devel/glib20 glib-networking-2.56.1 net/glib-networking pkg info can supply a lot of information. Te man age is very worthwhile reading, though I do need to check it as I can't remember all of the options. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: pkg-static: xorgproto-2018.4 conflicts with glproto-1.4.17
On Sun, Oct 7, 2018 at 10:15 AM Walter Schwarzenfeld < w.schwarzenf...@utanet.at> wrote: > Here you can see which ports are merged: > > https://www.freshports.org/x11/xorgproto/ See the UPDATING entry 20180731 for the command to take care of this. It provides the proper command to do the trick. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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"
