Re: Port upgrade: dead in the water
On Friday, 15 January 2021 at 22:16:44 -0600, Kyle Evans wrote: > On Fri, Jan 15, 2021 at 10:00 PM Greg 'groggy' Lehey wrote: >> >> After years I have finally got round to upgrading my main computer. >> My intention is to upgrade the ports as well, but pkg doesn't want to >> play nice: >> >> # pkg-static install -f pkg >> pkg-static: Warning: Major OS version upgrade detected. Running >> "pkg-static install -f pkg" recommended >> ... >> I'm happy to blow everything away, but is there a way to extract >> something that pkg can use to determine which packages to install? > > `pkg bootstrap -f` should recover pkg to something usable Thanks. That seems to help. Greg -- Sent from my desktop computer. See complete headers for address and phone numbers. This message is digitally signed. If your Microsoft mail program reports problems, please read http://lemis.com/broken-MUA signature.asc Description: PGP signature
Re: CMAKE_PREFIX_PATH and /usr/local
On Fri, 15 Jan 2021, Gleb Popov wrote:
+if (CMAKE_SYSTEM_NAME MATCHES "BSD")
+include_directories("/usr/local/include")
This is most certainly a wrong thing to do. Instead of simply adding
-I/usr/local/include everywhere, you should fix problems for each
dependency that the software requires.
What's the problem, exactly? Ports have always installed themselves under
/usr/local, and I refuse to overwrite the base system (as Penguin/OS does;
well, Debian anyway), and the Mac ports system uses /opt/local.
I generally regard the base system i.e. that as distributed as being
non-userland, and overwritten only with updates. Backups are much more
manageable, as I don't have to worry about /bin, /lib etc.
-- 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"
Re: Port upgrade: dead in the water
On Fri, Jan 15, 2021 at 10:00 PM Greg 'groggy' Lehey wrote: > > After years I have finally got round to upgrading my main computer. > My intention is to upgrade the ports as well, but pkg doesn't want to > play nice: > > # pkg-static install -f pkg > pkg-static: Warning: Major OS version upgrade detected. Running > "pkg-static install -f pkg" recommended > Updating FreeBSD repository catalogue... > pkg-static: repository meta /var/db/pkg/FreeBSD.meta has wrong version 2 > pkg-static: Repository FreeBSD load error: meta cannot be loaded No error: 0 > Fetching meta.txz: 100%916 B 0.9kB/s00:01 > pkg-static: repository meta /var/db/pkg/FreeBSD.meta has wrong version 2 > repository FreeBSD has no meta file, using default settings > Fetching packagesite.txz: 100%6 MiB 582.8kB/s00:11 > pkg-static: repository meta /var/db/pkg/FreeBSD.meta has wrong version 2 > pkg-static: Repository FreeBSD load error: meta cannot be loaded No error: 0 > Unable to open created repository FreeBSD > Unable to update repository FreeBSD > Error updating repositories! > > I'm happy to blow everything away, but is there a way to extract > something that pkg can use to determine which packages to install? `pkg bootstrap -f` should recover pkg to something usable ___ 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"
Port upgrade: dead in the water
After years I have finally got round to upgrading my main computer. My intention is to upgrade the ports as well, but pkg doesn't want to play nice: # pkg-static install -f pkg pkg-static: Warning: Major OS version upgrade detected. Running "pkg-static install -f pkg" recommended Updating FreeBSD repository catalogue... pkg-static: repository meta /var/db/pkg/FreeBSD.meta has wrong version 2 pkg-static: Repository FreeBSD load error: meta cannot be loaded No error: 0 Fetching meta.txz: 100%916 B 0.9kB/s00:01 pkg-static: repository meta /var/db/pkg/FreeBSD.meta has wrong version 2 repository FreeBSD has no meta file, using default settings Fetching packagesite.txz: 100%6 MiB 582.8kB/s00:11 pkg-static: repository meta /var/db/pkg/FreeBSD.meta has wrong version 2 pkg-static: Repository FreeBSD load error: meta cannot be loaded No error: 0 Unable to open created repository FreeBSD Unable to update repository FreeBSD Error updating repositories! I'm happy to blow everything away, but is there a way to extract something that pkg can use to determine which packages to install? Greg -- Sent from my desktop computer. See complete headers for address and phone numbers. This message is digitally signed. If your Microsoft mail program reports problems, please read http://lemis.com/broken-MUA signature.asc Description: PGP signature
Re: Testing official self-extract makeself .run fails to extract / anyone could test it?
Thank you for testing. I will do further tests with older releases too and hope that upstream fixes it. Thanks DutchDaemon - FreeBSD Forums Administrator escreveu no dia sexta, 15/01/2021 à(s) 11:52: > On 15/01/2021 12:38, Nuno Teixeira wrote: > > Hello, > > > > I need that someone test official archivers/makeself self-extratable bin > to > > see if error is the same: > > > > https://github.com/megastep/makeself/issues/238 > > > > Download link: > > > https://github.com/megastep/makeself/releases/download/release-2.4.2/makeself-2.4.2.run > > > > Run: sh makeself-2.4.2.run > > > > Thanks, > > > > Nuno Teixeira > > # ./makeself-2.4.2.run > Creating directory makeself-2.4.2 > Verifying archive integrity... 100% MD5 checksums are OK. All good. > Uncompressing Makeself v2.4.2 100% ... Extraction failed. > Terminated > > -- > > # sh -x makeself-2.4.2.run > + umask > + ORIG_UMASK=0022 > + test n '=' n > + umask 077 > + CRCsum=3945225848 > + MD5=6ec4e617e8ed15e4612e05e0a8ad18cd > + SHA= > + TMPROOT=/tmp > + USER_PWD=/tmp/test > + export USER_PWD > + ARCHIVE_DIR=. > + export ARCHIVE_DIR > + label='Makeself v2.4.2' > + script=echo > + scriptargs='Makeself has extracted itself' > + cleanup_script='' > + licensetxt='' > + helpheader='' > + targetdir=makeself-2.4.2 > + filesizes=31397 > + keep=y > + nooverwrite=n > + quiet=n > + accept=n > + nodiskspace=n > + export_conf=n > + decrypt_cmd='' > + skip=668 > + print_cmd_arg='' > + type printf > + print_cmd=printf > + test -d /usr/xpg4/bin > + test -d /usr/sfw/bin > + unset CDPATH > + finish=true > + xterm_loop='' > + noprogress=n > + nox11=n > + copy=none > + ownership=n > + verbose=n > + cleanup=y > + cleanupargs='' > + initargs='' > + true > + break > + test xn '=' xy -a xn '=' xy > + id -u > + test xn '=' xy -a 0 -ne 0 > + test xnone '!=' xphase2 > + MS_PrintLicense > + test x '!=' x > + test xn '=' xn > + tty -s > + : > + test xmakeself-2.4.2 '=' x. > + test xy '=' xy > + test xn '=' xy > + test xn '=' xn > + echo 'Creating directory makeself-2.4.2' > Creating directory makeself-2.4.2 > + tmpdir=makeself-2.4.2 > + dashp=-p > + mkdir -p makeself-2.4.2 > + pwd > + location=/tmp/test > + test x '!=' x1 > + MS_Check makeself-2.4.2.run > + > > OLD_PATH=/techsupp/scripts/BLACKHOLES:/techsupp/scripts/GREYLIST:/techsupp/scripts/MCP:/techsupp/scripts:/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/root/bin: > + > > PATH=/techsupp/scripts/BLACKHOLES:/techsupp/scripts/GREYLIST:/techsupp/scripts/MCP:/techsupp/scripts:/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/root/bin::/bin:/usr/bin:/sbin:/usr/local/ssl/bin:/usr/local/bin:/opt/openssl/bin > + MD5_ARG='' > + exec > + MD5_PATH='' > + test -x '' > + exec > + MD5_PATH=/sbin/md5 > + test -x /sbin/md5 > + > > PATH=/techsupp/scripts/BLACKHOLES:/techsupp/scripts/GREYLIST:/techsupp/scripts/MCP:/techsupp/scripts:/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/root/bin: > + exec > + SHA_PATH=/usr/local/bin/shasum > + test -x /usr/local/bin/shasum > + test xn '=' xn > + MS_Printf 'Verifying archive integrity...' > + printf 'Verifying archive integrity...' > Verifying archive integrity...+ head -n 668 makeself-2.4.2.run > + wc -c > + tr -d ' ' > + offset=16914 > + verb='' > + i=1 > + echo 3945225848 > + cut '-d ' -f1 > + crc=3945225848 > + test -x /usr/local/bin/shasum > + basename /usr/local/bin/shasum > + test xshasum '=' xshasum > + SHA_ARG='-a 256' > + echo > + cut '-d ' -f1 > + sha= > + test x > '=' x > + test x '=' xy > + test -x /sbin/md5 > + basename /sbin/md5 > + test xmd5 '=' xdigest > + echo 6ec4e617e8ed15e4612e05e0a8ad18cd > + cut '-d ' -f1 > + md5=6ec4e617e8ed15e4612e05e0a8ad18cd > + test x6ec4e617e8ed15e4612e05e0a8ad18cd '=' > x > + MS_dd_Progress makeself-2.4.2.run 16914 31397 > + test xn '=' xy > + file=makeself-2.4.2.run > + offset=16914 > + length=31397 > + pos=0 > + bsize=4194304 > + test 4194304 -gt 31397 > + expr 4194304 / 4 > + eval '/sbin/md5 ' > + /sbin/md5 > + cut -b-32 > + bsize=1048576 > + test 1048576 -gt 31397 > + expr 1048576 / 4 > + bsize=262144 > + test 262144 -gt 31397 > + expr 262144 / 4 > + bsize=65536 > + test 65536 -gt 31397 > + expr 65536 / 4 > + bsize=16384 > + test 16384 -gt 31397 > + expr 31397 / 16384 > + blocks=1 > + expr 31397 % 16384 > + bytes=15013 > + dd 'ibs=16914' 'skip=1' 'count=0' > + expr 0 + 16384 > + pos=16384 > + MS_Printf ' 0%% ' > + printf ' 0%% ' > 0% + test 1 -gt 0 > + test 16384 -le 31397 > + dd 'bs=16384' 'count=1' > + expr 31397 / 100 > + pcent=313 > + expr 16384 / 313 > + pcent=52 > + test 52 -lt 100 > +
Re: CMAKE_PREFIX_PATH and /usr/local
On Fri, Jan 15, 2021 at 10:05 AM Gleb Popov wrote:
> On Fri, Jan 15, 2021 at 12:50 AM Tomasz CEDRO wrote:
>> Hello world :-)
>> I am porting LimeSuite to FreeBSD. Local patch fixes missing
>> "/usr/local/" path in CMakeLists.txt so the package now builds fine on
>> FreeBSD. On Linux probably most of the libraries and includes are
>> located in /usr/ do problem does not exist.
>> Upstream has some objections to accept this patch and considers
>> "/usr/local" a non-standard path [1]. But they propose to use
>> CMAKE_PREFIX_PATH to add "/usr/local". This however does not seem to
>> be supported in Ports (yet?).
>> The question is how to tell CMake about "/usr/local/include" without
>> source code modification? :-)
>> Below is the proposed patch:
>> > @@ -171,6 +171,11 @@ if (ENABLE_NEW_GAIN_BEHAVIOUR)
>> add_definitions(-DNEW_GAIN_BEHAVIOUR)
>> endif()
>> +if (CMAKE_SYSTEM_NAME MATCHES "BSD")
>> +include_directories("/usr/local/include")
>
> This is most certainly a wrong thing to do. Instead of simply adding
> -I/usr/local/include everywhere, you should fix problems for each dependency
> that the software requires.
>
> What error do you get without your patch?
Hello Gleb :-) This seems the LimeSuite CMake issue not to use
/usr/local/include where some GL includes are located. Without it
there is a build problem as GL.h (something like this) is not found. I
am not sure it this is the only occurrence of this symptom. Simply
adding /usr/local/include solves the problem.
Accorging to cmake 3.19 documentation CMAKE_PREFIX_PATH is empty by
default and it needs to be filled with search paths by the project:
CMAKE_PREFIX_PATH is empty by default, so the project sets the value,
so the /usr/local is missing now and should be put here (but still in
the source code so the patch seems unavoidable):
https://cmake.org/cmake/help/latest/variable/CMAKE_PREFIX_PATH.html?highlight=cmake_prefix_path
We are back in the point either to fix the upstream and add
"/usr/local" into CMAKE_PREFIX_PATH or propagate is somehow from a
port anyhow..?
Thanks :-)
Tomek
--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
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: Testing official self-extract makeself .run fails to extract / anyone could test it?
On 15/01/2021 12:38, Nuno Teixeira wrote: Hello, I need that someone test official archivers/makeself self-extratable bin to see if error is the same: https://github.com/megastep/makeself/issues/238 Download link: https://github.com/megastep/makeself/releases/download/release-2.4.2/makeself-2.4.2.run Run: sh makeself-2.4.2.run Thanks, Nuno Teixeira # ./makeself-2.4.2.run Creating directory makeself-2.4.2 Verifying archive integrity... 100% MD5 checksums are OK. All good. Uncompressing Makeself v2.4.2 100% ... Extraction failed. Terminated -- # sh -x makeself-2.4.2.run + umask + ORIG_UMASK=0022 + test n '=' n + umask 077 + CRCsum=3945225848 + MD5=6ec4e617e8ed15e4612e05e0a8ad18cd + SHA= + TMPROOT=/tmp + USER_PWD=/tmp/test + export USER_PWD + ARCHIVE_DIR=. + export ARCHIVE_DIR + label='Makeself v2.4.2' + script=echo + scriptargs='Makeself has extracted itself' + cleanup_script='' + licensetxt='' + helpheader='' + targetdir=makeself-2.4.2 + filesizes=31397 + keep=y + nooverwrite=n + quiet=n + accept=n + nodiskspace=n + export_conf=n + decrypt_cmd='' + skip=668 + print_cmd_arg='' + type printf + print_cmd=printf + test -d /usr/xpg4/bin + test -d /usr/sfw/bin + unset CDPATH + finish=true + xterm_loop='' + noprogress=n + nox11=n + copy=none + ownership=n + verbose=n + cleanup=y + cleanupargs='' + initargs='' + true + break + test xn '=' xy -a xn '=' xy + id -u + test xn '=' xy -a 0 -ne 0 + test xnone '!=' xphase2 + MS_PrintLicense + test x '!=' x + test xn '=' xn + tty -s + : + test xmakeself-2.4.2 '=' x. + test xy '=' xy + test xn '=' xy + test xn '=' xn + echo 'Creating directory makeself-2.4.2' Creating directory makeself-2.4.2 + tmpdir=makeself-2.4.2 + dashp=-p + mkdir -p makeself-2.4.2 + pwd + location=/tmp/test + test x '!=' x1 + MS_Check makeself-2.4.2.run + OLD_PATH=/techsupp/scripts/BLACKHOLES:/techsupp/scripts/GREYLIST:/techsupp/scripts/MCP:/techsupp/scripts:/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/root/bin: + PATH=/techsupp/scripts/BLACKHOLES:/techsupp/scripts/GREYLIST:/techsupp/scripts/MCP:/techsupp/scripts:/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/root/bin::/bin:/usr/bin:/sbin:/usr/local/ssl/bin:/usr/local/bin:/opt/openssl/bin + MD5_ARG='' + exec + MD5_PATH='' + test -x '' + exec + MD5_PATH=/sbin/md5 + test -x /sbin/md5 + PATH=/techsupp/scripts/BLACKHOLES:/techsupp/scripts/GREYLIST:/techsupp/scripts/MCP:/techsupp/scripts:/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/root/bin: + exec + SHA_PATH=/usr/local/bin/shasum + test -x /usr/local/bin/shasum + test xn '=' xn + MS_Printf 'Verifying archive integrity...' + printf 'Verifying archive integrity...' Verifying archive integrity...+ head -n 668 makeself-2.4.2.run + wc -c + tr -d ' ' + offset=16914 + verb='' + i=1 + echo 3945225848 + cut '-d ' -f1 + crc=3945225848 + test -x /usr/local/bin/shasum + basename /usr/local/bin/shasum + test xshasum '=' xshasum + SHA_ARG='-a 256' + echo + cut '-d ' -f1 + sha= + test x '=' x + test x '=' xy + test -x /sbin/md5 + basename /sbin/md5 + test xmd5 '=' xdigest + echo 6ec4e617e8ed15e4612e05e0a8ad18cd + cut '-d ' -f1 + md5=6ec4e617e8ed15e4612e05e0a8ad18cd + test x6ec4e617e8ed15e4612e05e0a8ad18cd '=' x + MS_dd_Progress makeself-2.4.2.run 16914 31397 + test xn '=' xy + file=makeself-2.4.2.run + offset=16914 + length=31397 + pos=0 + bsize=4194304 + test 4194304 -gt 31397 + expr 4194304 / 4 + eval '/sbin/md5 ' + /sbin/md5 + cut -b-32 + bsize=1048576 + test 1048576 -gt 31397 + expr 1048576 / 4 + bsize=262144 + test 262144 -gt 31397 + expr 262144 / 4 + bsize=65536 + test 65536 -gt 31397 + expr 65536 / 4 + bsize=16384 + test 16384 -gt 31397 + expr 31397 / 16384 + blocks=1 + expr 31397 % 16384 + bytes=15013 + dd 'ibs=16914' 'skip=1' 'count=0' + expr 0 + 16384 + pos=16384 + MS_Printf ' 0%% ' + printf ' 0%% ' 0% + test 1 -gt 0 + test 16384 -le 31397 + dd 'bs=16384' 'count=1' + expr 31397 / 100 + pcent=313 + expr 16384 / 313 + pcent=52 + test 52 -lt 100 + MS_Printf '\b\b\b\b\b\b\b' + printf '\b\b\b\b\b\b\b' + test 52 -lt 10 + MS_Printf ' 52%% ' + printf ' 52%% ' 52% + expr 16384 + 16384 + pos=32768 + test 32768 -le 31397 + test 15013 -gt 0 + dd 'bs=15013' 'count=1' + MS_Printf '\b\b\b\b\b\b\b' + printf '\b\b\b\b\b\b\b' + MS_Printf ' 100%% ' + printf ' 100%% ' 100% + md5sum=6ec4e617e8ed15e4612e05e0a8ad18cd + test x6ec4e617e8ed15e4612e05e0a8ad18cd '!=' x6ec4e617e8ed15e4612e05e0a8ad18cd + test xn '=' xn + MS_Printf ' MD5 checksums are OK.' + printf ' MD5 checksums are OK.' MD5 checksums are OK.+ crc=00 + verb=n + test
Testing official self-extract makeself .run fails to extract / anyone could test it?
Hello, I need that someone test official archivers/makeself self-extratable bin to see if error is the same: https://github.com/megastep/makeself/issues/238 Download link: https://github.com/megastep/makeself/releases/download/release-2.4.2/makeself-2.4.2.run Run: sh makeself-2.4.2.run Thanks, Nuno Teixeira ___ 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"
Removing sysutils/polkit dependency from sysutils/libudisks?
Several months ago, someone (swills@ IIRC) asked me to look into removing the sysutils/polkit dependency from sysutils/libudisks which I maintain. I just had a chance to look at that request and it would require at least removing the udisksctl utility from the default options and possibly removing it from the build altogether. However, its presence in the default options was expressly requested in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240138#c18 when I was initially porting libudisks. Is the request for removal still relevant? I think it was made with an eye toward removing sysutils/polkit altogether. If it is relevant, does it warrant removing udisksctl, which I found useful for port smoke testing and troubleshooting, in addition to the reasons for its presence listed in the Bugzilla comment linked above? ___ 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 you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ science/afni| 21.0.02 | afni_21.0.03 +-+ sysutils/snooze | 0.4 | v0.5 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Reported by:portscout! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: CMAKE_PREFIX_PATH and /usr/local
On Fri, Jan 15, 2021 at 12:50 AM Tomasz CEDRO wrote:
> Hello world :-)
>
> I am porting LimeSuite to FreeBSD. Local patch fixes missing
> "/usr/local/" path in CMakeLists.txt so the package now builds fine on
> FreeBSD. On Linux probably most of the libraries and includes are
> located in /usr/ do problem does not exist.
>
> Upstream has some objections to accept this patch and considers
> "/usr/local" a non-standard path [1]. But they propose to use
> CMAKE_PREFIX_PATH to add "/usr/local". This however does not seem to
> be supported in Ports (yet?).
>
> The question is how to tell CMake about "/usr/local/include" without
> source code modification? :-)
>
> Below is the proposed patch:
>
> > @@ -171,6 +171,11 @@ if (ENABLE_NEW_GAIN_BEHAVIOUR)
> add_definitions(-DNEW_GAIN_BEHAVIOUR)
> endif()
>
> +if (CMAKE_SYSTEM_NAME MATCHES "BSD")
> +include_directories("/usr/local/include")
>
This is most certainly a wrong thing to do. Instead of simply adding
-I/usr/local/include everywhere, you should fix problems for each
dependency that the software requires.
What error do you get without your patch?
___
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"
