Re: No update for a day on ports?
Citerar D'Arcy Cain : On 2021-04-01 4:55 a.m., Bob Eager wrote: I got a partial answer. There is a port, net/gitup, that will do an update of sorts. (Note: I was just told 'gitup' and there is an old port, now renamed 'git-up', which is not the right one). I just tried gitup and was told tha I had no permissions for /var/db/gitup. Can I not run gitup as a normal user? Trying to run the latest poudriere from ports (git) and that seems to still use the subversion variant, or do I need to reinitialize something? Have I missed some migration guide for this? Cheers, Jimmy ___ 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: No update for a day on ports?
Citerar Bob Eager :
On Thu, 1 Apr 2021 19:47:01 +1100
Dewayne Geraghty wrote:
Would appreciate if anyone can provide insight as to the 4 git
commands that I need to function, in a manner similar to the way I
use svnlite use. Git equivalents for:
svnlite update /usr/ports
svnlite update -r '{$-$MM-$DD}' /usr/ports/$category/$port
svnlite log -l $N /usr/ports/$category/$port
svnlite diff /usr/ports/$category/$port
I got a partial answer. There is a port, net/gitup, that will do an
update of sorts. (Note: I was just told 'gitup' and there is an old
port, now renamed 'git-up', which is not the right one).
I'm sure many other users would have a similar usage (and similar
non-knowledge of git)
Indeed. I feel this should have been done in advance. And been in
Appendix A of the Handbook in plenty of time.
As a minor aside, has anyone stated the reason why the user-base of
base or ports are moving to git?
Going with the fashion, IMO. But I will no doubt get shouted down.
If it is deprecated where do I find the information I need, this does
not help:
https://docs.freebsd.org/en_US.ISO8859-1/books/handbook/ports-using.html
Cheers, Jimmy
___
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"
Build failures for logitechmediaserver in poudriere
Hi, I'm getting some strange build failures for logitechmediaserver when building in poudriere. From ports everything is working fine, on the other hand the packaging step isn't done there :-) I get a lot of these in the build log: pkg-static: Unable to access file /wrkdirs/usr/ports/audio/logitechmediaserver/work/stage/usr/local/share/logitechmediaserver/CPAN/arch/5.28/Class/XSAccessor.pm:No such file or directory pkg-static: Unable to access file /wrkdirs/usr/ports/audio/logitechmediaserver/work/stage/usr/local/share/logitechmediaserver/CPAN/arch/5.28/Class/XSAccessor/Array.pm:No such file or directory pkg-static: Unable to access file /wrkdirs/usr/ports/audio/logitechmediaserver/work/stage/usr/local/share/logitechmediaserver/CPAN/arch/5.28/Class/XSAccessor/Heavy.pm:No such file or directory pkg-static: Unable to access file /wrkdirs/usr/ports/audio/logitechmediaserver/work/stage/usr/local/share/logitechmediaserver/CPAN/arch/5.28/DBI.pm:No such file or directory pkg-static: Unable to access file /wrkdirs/usr/ports/audio/logitechmediaserver/work/stage/usr/local/share/logitechmediaserver/CPAN/arch/5.28/DBI/Changes.pm:No such file or directory Anyone has any idea what's causing this. Been banging my head a couple of days and am running out of ideas. Thankful for any help / Jimmy ___ 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: Can't get Wordpress to install from poudriere
Hi all, Thanks Adam. I already got some quick, and almost the same, help from Kurt yesterday. So if someone else is as forgetful as me I forgot to change the path in the /usr/local/etc/pkg/repos file when I upgraded to 11.2 and then also created a new jail for 11.2. I changed to php72 at the same time so I got stuck thinking it was something wrong with that. Cheers, Jimmy Citerar Adam Weinberger : On Mon, Aug 20, 2018 at 3:22 AM Jimmy Renner wrote: Well, maybe it is not as simple. I have set up poudriere to build som packages locally, right now: graphics/pecl-imagick graphics/php72-gd audio/logitechmediaserver www/owncloud www/wordpress In my make.conf I have set: DEFAULT_VERSIONS+= php=72 So far, so good. Everything seems to build ok. But as soon as I try to install anything, the wordpress from poudriere is never picked up but the other packages are. I've obviously messed something up but I cannot find what. I've been scratching my head for days so any suggestions or hints would be good. Thanks, Jimmy Hi Jimmy, First place I'd look is the pkg conf. Have you made any modifications to /etc/pkg/FreeBSD.conf? Can you show us the files you have in /usr/local/etc/pkg/? Second place I'd look is making sure that pkg is using the generated catalogues: pkg update -f # 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"
Can't get Wordpress to install from poudriere
Well, maybe it is not as simple. I have set up poudriere to build som packages locally, right now: graphics/pecl-imagick graphics/php72-gd audio/logitechmediaserver www/owncloud www/wordpress In my make.conf I have set: DEFAULT_VERSIONS+= php=72 So far, so good. Everything seems to build ok. But as soon as I try to install anything, the wordpress from poudriere is never picked up but the other packages are. I've obviously messed something up but I cannot find what. I've been scratching my head for days so any suggestions or hints would be good. Thanks, Jimmy ___ 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: Mumble in pkg
Citerar Greg Byshenk : On Mon, Jan 23, 2017 at 09:05:19PM +0100, Jimmy Renner wrote: >>> On 2017/01/23 15:26, Jimmy Renner wrote: >>>> I might be totally off (and in the wrong forum) but I'm having problems >>>> running the mumble version fetched by pkg, if I try to build the same >>>> version in ports everything works fine. The failing one complains about >>>> "unable to allocate SSL_CTX". The big difference I see is that the pkg >>>> version is using /usr/lib/lbssl.so.8 and /lib/libcrypto.so.8 and the >>>> ports version is using /usr/local/lib/libcrypto.so.9 and >>>> /usr/local/lib/libssl.so.9. The odd thing is that both binaries are >>>> reporting to be version OpenSSL 1.0.2j though the one depending on the >>>> libs in /usr/lib says OpenSSL 1.0.2j-freebsd. Ok, openssl-1.0.2j_1,1 is installed, from pkg. Ok, so I think what's going on here is that: The pkg version of mumble uses the default system OpenSSL, but you've installed the OpenSSL port (via the package). This means that the port builds fine - using the non-system OpenSSL that you've installed. But the pkg conflicts, because it wants the system OpenSSL -- and /usr/local/lib/* is found first. There are probably other ways to fix this, but the easiest is to either a) remove the OpenSSL pkg, or b) build mumble as a port. [Corrections welcome if I have something wrong.] -- greg byshenk - gbysh...@byshenk.net - Leiden, NL I won't correct you :-) I thought as the binaries reported different things and that when doing ldd they pointed to different libraries that they shouldn't interfere with eachother but clearly I was wrong since temporarily moving the ports openssl files made the pkg version of mumble work. Now I just have to see if anything else is affected by removing the port openssl :-) Thanks! Cheers, Jimmy ___ 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: Mumble in pkg
Citerar Mathieu Arnold : Le 23/01/2017 à 17:20, Jimmy Renner a écrit : Citerar Matthew Seaman : On 2017/01/23 15:26, Jimmy Renner wrote: I might be totally off (and in the wrong forum) but I'm having problems running the mumble version fetched by pkg, if I try to build the same version in ports everything works fine. The failing one complains about "unable to allocate SSL_CTX". The big difference I see is that the pkg version is using /usr/lib/lbssl.so.8 and /lib/libcrypto.so.8 and the ports version is using /usr/local/lib/libcrypto.so.9 and /usr/local/lib/libssl.so.9. The odd thing is that both binaries are reporting to be version OpenSSL 1.0.2j though the one depending on the libs in /usr/lib says OpenSSL 1.0.2j-freebsd. What are the options settings for the instance of OpenSSL you built from ports? What version of SSL/TLS are you trying to use? Cheers, Matthew I'm using the default options, however if I build the port and then run "pkg upgrade" it wants to re-install mumble because "needed shared library changed". I haven't specified any SSL version anywhere, should I have? The port variant is the one working though. I would have understood if the port variant didn't work but I can't do much about the dependencies for the pre-built one from pkg, or can I? The "default" does not mean much, as there still are ports that force installing the ports version of OpenSSL, do you have openssl, or libressl installed ? -- Mathieu Arnold Ok, openssl-1.0.2j_1,1 is installed, from pkg. / Jimmy ___ 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: Mumble in pkg
Citerar Matthew Seaman : On 2017/01/23 15:26, Jimmy Renner wrote: I might be totally off (and in the wrong forum) but I'm having problems running the mumble version fetched by pkg, if I try to build the same version in ports everything works fine. The failing one complains about "unable to allocate SSL_CTX". The big difference I see is that the pkg version is using /usr/lib/lbssl.so.8 and /lib/libcrypto.so.8 and the ports version is using /usr/local/lib/libcrypto.so.9 and /usr/local/lib/libssl.so.9. The odd thing is that both binaries are reporting to be version OpenSSL 1.0.2j though the one depending on the libs in /usr/lib says OpenSSL 1.0.2j-freebsd. What are the options settings for the instance of OpenSSL you built from ports? What version of SSL/TLS are you trying to use? Cheers, Matthew I'm using the default options, however if I build the port and then run "pkg upgrade" it wants to re-install mumble because "needed shared library changed". I haven't specified any SSL version anywhere, should I have? The port variant is the one working though. I would have understood if the port variant didn't work but I can't do much about the dependencies for the pre-built one from pkg, or can I? Cheers, Jimmy ___ 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"
Mumble in pkg
I might be totally off (and in the wrong forum) but I'm having problems running the mumble version fetched by pkg, if I try to build the same version in ports everything works fine. The failing one complains about "unable to allocate SSL_CTX". The big difference I see is that the pkg version is using /usr/lib/lbssl.so.8 and /lib/libcrypto.so.8 and the ports version is using /usr/local/lib/libcrypto.so.9 and /usr/local/lib/libssl.so.9. The odd thing is that both binaries are reporting to be version OpenSSL 1.0.2j though the one depending on the libs in /usr/lib says OpenSSL 1.0.2j-freebsd. What have I messed up? :-) Any help or pointers would be much appreciated. Cheers, Jimmy ___ 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 lagging for 10.2
Citerar Mike Clarke :
On Tue, 08 Sep 2015 08:46:48 +0200
Jimmy Renner wrote:
I don't know if this is the right list to post to but for me lots (a
bit over 100) of ports are updated but if I do a pkg upgrade not much
is updated. This has been the case since I upgraded to 10.2. No
complaints, I was just wondering if I have done anything wrong :-)
10.2 now uses the quarterly repository by default but you can switch to
using the latest packages if you
create /usr/local/etc/pkg/repos/FreeBSD.conf as below:
FreeBSD: {
url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest";
}
This will override the url attribute in /etc/pkg/FreeBSD.conf
--
Mike Clarke
My bad. I have to admit I had stopped reading before that last line in
the realeas notes :-)
Thanks Mike!
/ Jimmy
___
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"
Packages lagging for 10.2
Hi, I don't know if this is the right list to post to but for me lots (a bit over 100) of ports are updated but if I do a pkg upgrade not much is updated. This has been the case since I upgraded to 10.2. No complaints, I was just wondering if I have done anything wrong :-) Cheers, Jimmy ___ 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 failure
Quoting Mark Linimon : On Wed, Dec 16, 2009 at 11:13:36PM -0500, Robert Huff wrote: The maintainer, ruby@, is aware of this; a check of the PR database shows multiple open PRs, none critical but many serious going back six months and more. As an aside, the Severity and Priority fields have been so often abused as to have become meaningless. Although I still try to groom the db for "critical" ones, and thus try to get those some attention, I really don't think the committers pay much attention. (In general I think those should be reserved for "data corruption" and "security".) The longer-term solution is to remove those as user-settable fields. This hard to understand given portupgrade is the recommended upgrade tool. Once the individual who was working on it gave it up to the mailing list, it became one of those "everyone is responsible so no one is responsible" problems. I don't have a recommended fix for this. Having said that, I have a ports tree as of a month ago and portupgrade was working ok for me. I don't have the cycles to go figure out where it fails to be able to fix it, sorry. I don't know if your issues are related but yesterday I managed to fix a ports tree that made portupgrade crash. I wasn't aware that portupgrade looks in the options files for dependencies. I think some ports, and my guess it is those who gave me the problem, blindly pulls in dependencies without checking if they are already installed or not and it is in those cases that portupgrade can get an incorrect cyclic dependencies list. Ok, enough of my strange unproven theories. I removed a lot of the options files from /var/db/ports/... and after some point, it was actually when removing them from all the p5-* ports, portupgrade started working again. When running portupgrade again I was more restrictive with what options to actually enable and after that everything works. Don't know if that will help anyone but I though I should at least put my ideas down somewhere. / Jimmy This message was sent using IMP, the Internet Messaging Program. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: PHP gd issues
Quoting Paul Macdonald : Hi, Sometime within the last week an upgrade has left some php gd functions non working on my systems, from imagecreatefrom png: gd-png: fatal libpng error: [00][00][00][00]: unknown critical chunk I don't recall any updates which might have affected this and can;t see anything in ports/UPDATING. A re-install of php5-extensions leaves in the same state... Has anyone else seen this and any suggestions for a fix? I've seen it too, haven't found out what causes it yet though. Is there a log of recently updated ports i can look at ( i stupidly don;t log this myself) Not that I know of and I'm at an equal stupidity level :-) / Jimmy This message was sent using IMP, the Internet Messaging Program. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
