Re: vulnerabilities bogus error
https://vuxml.freebsd.org/freebsd/vuln.xml.bz2 ___ 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"
vulnerabilities bogus error
Trying to update my port. During make install get a bunch of bogus error messages about the port having vulnerabilities. I know this to not be the case. The first message says pkg-static; unable to open vulnxml file (null): Invalid argument This is a new fresh install of RELEASE 12.0. How do I manually fetch this vulnxml file or where should I "touch" to create it? ___ 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"
PKGNAME of perl package
Just noticed that the package name of the perl ports does not match the PKGNAME variable: $ make -C /usr/ports/lang/perl5.26/ -V PKGNAME perl5-5.26.3 # make package ===> Building package for perl5.26-5.26.3 There is a mismatch of names perl5-5.26.3 vs. perl5.26-5.26.3 and this confuses (my version of) portmaster ... Is this by design and what use is the PKGNAME variable, if the package is actually created under another name? Which variable should I use to get the actual package name from the port's Makefile? STefan ___ 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: 12-stable, poudriere in jail
No matter what I tried, the python and ruby builds still are failing.
I’ve since changed the setup to a VIMAGE vnet jail, and that appears to be
working properly.
If there is a way to make the „classic“ inherited IPs setup work, I’d love to
learn how.
Stefan
> Am 10.12.2018 um 00:20 schrieb Stefan Bethke :
>
> I’ve made some progress fiddling with common.sh. If I hard-reset $localipargs
> to an empty string, I can run the build successfully. ATM for me,
> $localipargs is set to „ip4.addr=127.0.0.1 ip6.addr=::1“, which breaks the
> jail(8) invocation.
>
> I’ve opened an issue on GH: https://github.com/freebsd/poudriere/issues/657
>
>> Am 09.12.2018 um 21:17 schrieb Stefan Bethke :
>>
>> Since upgrading my machine to 12-stable a couple of days ago, my poudriere
>> jail is having trouble building python and ruby errors like:
>> checking getaddrinfo bug... yes
>> Fatal: You must get working getaddrinfo() function.
>> or you can specify "--disable-ipv6".
>> ===> Script "configure" failed unexpectedly.
>>
>>
>> compiling getaddrinfo.c
>> In file included from getaddrinfo.c:86:
>> ./addrinfo.h:165:12: error: conflicting types for 'getnameinfo'
>> extern int getnameinfo __P((
>> ^
>> /usr/include/netdb.h:251:6: note: previous declaration is here
>> int getnameinfo(const struct sockaddr *, socklen_t, char *,
>> ^
>> getaddrinfo.c:408:7: warning: add explicit braces to avoid dangling else
>> [-Wdangling-else]
>> } else if (strcmp(sp->s_proto, "tcp") == 0) {
>>
>>
>> My jail has a private IP assigned to an Ethernet interface, and a loopback
>> address. In 11-stable, I shared 127.0.0.1 with the host. Since upgrading to
>> 12-stable, I get
>> jail: IPv4 addresses clash
>>
>> If change the loopback IPs on the jail to .2/:2, I then get:
>> [00:00:00] Warning: No loopback address defined, consider setting
>> LOIP6/LOIP4 or assigning a loopback address to the jail.
>>
>> but I get the above build errors. Setting LOIP4/LOIP6 to .2/:2, I’m back at
>> the IPv4 addresses clash error. Setting LOIP4/LOIP6 to 3./:3, I get the
>> warning again, and the build errors.
>>
>> I can build python on the host just fine.
>>
>> I’m getting the build problems with both a 11.2-RELEASE and a 12.0-RC3 based
>> reference jail.
>>
>>
>> The relevant lines from jail.conf:
>> pkg {
>> path = "/jail/pkg.xxx.xxx";
>> host.hostname = „pkg.xxx.xx";
>> ip4.addr += "bridge1|44.128.xx.xx";
>> ip4.addr += "lo0|127.0.0.1";
>> ip6.addr += "lo0|::1";
>> children.max = 40;
>> exec.poststart += "zfs jail $name data/jail/${host.hostname}/poudriere";
>> exec.poststart += "jexec $name zfs mount -a";
>> #exec.prestop += "zfs unjail $name
>> data/jail/${host.hostname}/poudriere";
>> allow.mount;
>> allow.mount.devfs;
>> allow.mount.linprocfs;
>> allow.mount.nullfs;
>> allow.mount.procfs;
>> allow.mount.tmpfs;
>> allow.mount.zfs;
>> allow.socket_af;
>> allow.chflags;
>> enforce_statfs=1;
>> #ip6=inherit;
>> ip4=inherit;
>> }
>>
>>
>> --
>> Stefan BethkeFon +49 151 14070811
>>
>> ___
>> 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"
>
> --
> Stefan BethkeFon +49 151 14070811
>
> ___
> 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"
--
Stefan BethkeFon +49 151 14070811
___
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"
vector-maps not working in firefox
Hi, not sure if this is a problem of firefox or one of the components used. Vector-based maps display wrong in Firefox on FreeBSD (all of the Firefox versions that I have tested in the last year at least, on FreeBSD 10.x and 11.x). The same maps work fine in Firefox on Linux and in Chromium on FreeBSD. How would one identify the software that is actually at fault here? Or maybe its just a problem on my FreeBSD installations? A few example URLs: https://www.qwant.com/maps/#map=14.80/46.4354087/-109.8376529 https://www.google.com/maps/@46.435512,-109.8343499,15z https://duckduckgo.com/?q=harlowton+mt&atb=v128-4__&ia=web&iax=about&iaxm=about Wolfgang ___ 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 +-+ www/libjwt | 1.9.0 | v1.10.0 +-+ 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 Thanks. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Updating perl
On 14/12/2018 10:44, Carmel NY wrote:
> Using poudriere, I attempted to update my system to the new "perl 5.28". I
> made the necessary changes in the "make.conf" files and then attempted to run
> poudriere. At the very beginning of the run, poudriere issued a warning that
> "security/py-certbot | py36-certbot-0.29.1_1,1" failed. This is from the end
> of the log file:
>
> ===
> ===
> ===> Patching for py36-certbot-0.29.1_1,1
> ===> Applying FreeBSD patches for py36-certbot-0.29.1_1,1
> Ignoring previously applied (or reversed) patch.
> 2 out of 2 hunks ignored--saving rejects to certbot/compat.py.rej
> => FreeBSD patch patch-certbot_compat.py failed to apply cleanly.
> *** Error code 1
>
> Stop.
> make: stopped in /usr/ports/security/py-certbot
> =>> Cleaning up wrkdir
> ===> Cleaning for py36-certbot-0.29.1_1,1
> build of security/py-certbot | py36-certbot-0.29.1_1,1 ended at Fri Dec 14
> 05:35:15 EST 2018 build time: 00:00:05
> !!! build failure encountered !!!
>
> Has anyone else had this problem?
>
Yeah -- I just committed the fixes for py-certbot for which you had been
testing. What was committed was very slightly different to the patch
you tested.
You're seeing some sort of mismerge in your ports tree there. You
should be able to fix it by:
cd ${PORTSDIR}/security/py-certbot
svn revert -R .
and then try rebuilding. That is assuming you have the ports tree
checked out of SVN. Use something like 'git reset --hard' if you're a
git user. Anything else, I don't actually know, but the main aim would
be to get rid of any local changes and resynch to the primary repository
contents.
Cheers,
Matthew
signature.asc
Description: OpenPGP digital signature
Re: Updating perl
On 14/12/2018 9:44 pm, Carmel NY wrote: Using poudriere, I attempted to update my system to the new "perl 5.28". I made the necessary changes in the "make.conf" files and then attempted to run poudriere. At the very beginning of the run, poudriere issued a warning that "security/py-certbot | py36-certbot-0.29.1_1,1" failed. This is from the end of the log file: === === ===> Patching for py36-certbot-0.29.1_1,1 ===> Applying FreeBSD patches for py36-certbot-0.29.1_1,1 Ignoring previously applied (or reversed) patch. 2 out of 2 hunks ignored--saving rejects to certbot/compat.py.rej => FreeBSD patch patch-certbot_compat.py failed to apply cleanly. *** Error code 1 Stop. make: stopped in /usr/ports/security/py-certbot =>> Cleaning up wrkdir ===> Cleaning for py36-certbot-0.29.1_1,1 build of security/py-certbot | py36-certbot-0.29.1_1,1 ended at Fri Dec 14 05:35:15 EST 2018 build time: 00:00:05 !!! build failure encountered !!! Has anyone else had this problem? Hi Carmel, That was just reported here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234009 I'm trying to grok how this may be perl update related. Can you try what I suggested in comment #1 and let me know (in the issue) how that goes. ./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"
Re: Updating poudriere jail
On Fri 2018-12-14 11:13:16 UTC+, Carmel NY (carmel...@outlook.com) wrote: > ># build Postfix with Cyrus SASL support > >mail_postfix_SET=SASL > > > >Of course, be sure to point your FreeBSD 12.0-REL systems to your new 12.0 > >repo, instead of your old 11.x repo. > > > >Regards > >Andrew > > You know, that there are both a: > > Port: postfix-current-sasl-3.4.20181202,5 > Path: /usr/ports/mail/postfix-current-sasl > Info: Experimental Postfix version > > and > > Port: postfix-sasl-3.3.2_1,1 > Path: /usr/ports/mail/postfix-sasl > Info: Postfix with Cyrus SASL support > > Why not just use one of them? I had no idea until it was mentioned to me off-list earlier. You learn something new every day :-) Thanks, Regards Andrew ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Updating poudriere jail
On Fri, 14 Dec 2018 07:29:18 +1100, andrew clarke stated: >On Thu 2018-12-13 19:43:30 UTC+, Carmel NY (carmel...@outlook.com) wrote: > >> I am using FreeBSD 11.2-RELEASE-p6. If I use freebsd-update to install the >> new version 12, what do I have to do to update the poudriere jail? Plus, >> if I do update, will I have to rebuild all of my installed applications? >> >> Thanks :) > >I found it simplest to create a new poudriere jail named 12amd64 to coincide >with my existing 11amd64 jail. > >In my case the only port I build that needs non-standard options is >mail/postfix, to enable Cyrus SASL support. Consequently I have this setting >in /usr/local/etc/poudriere.d/make.conf (outside the jail) which from what I >understand applies to both my 11amd64 and 12amd64 (and future) poudriere >jails: > ># build Postfix with Cyrus SASL support >mail_postfix_SET=SASL > >Of course, be sure to point your FreeBSD 12.0-REL systems to your new 12.0 >repo, instead of your old 11.x repo. > >Regards >Andrew You know, that there are both a: Port: postfix-current-sasl-3.4.20181202,5 Path: /usr/ports/mail/postfix-current-sasl Info: Experimental Postfix version and Port: postfix-sasl-3.3.2_1,1 Path: /usr/ports/mail/postfix-sasl Info: Postfix with Cyrus SASL support Why not just use one of them? -- Carmel ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Updating perl
Using poudriere, I attempted to update my system to the new "perl 5.28". I made the necessary changes in the "make.conf" files and then attempted to run poudriere. At the very beginning of the run, poudriere issued a warning that "security/py-certbot | py36-certbot-0.29.1_1,1" failed. This is from the end of the log file: === === ===> Patching for py36-certbot-0.29.1_1,1 ===> Applying FreeBSD patches for py36-certbot-0.29.1_1,1 Ignoring previously applied (or reversed) patch. 2 out of 2 hunks ignored--saving rejects to certbot/compat.py.rej => FreeBSD patch patch-certbot_compat.py failed to apply cleanly. *** Error code 1 Stop. make: stopped in /usr/ports/security/py-certbot =>> Cleaning up wrkdir ===> Cleaning for py36-certbot-0.29.1_1,1 build of security/py-certbot | py36-certbot-0.29.1_1,1 ended at Fri Dec 14 05:35:15 EST 2018 build time: 00:00:05 !!! build failure encountered !!! Has anyone else had this problem? -- Carmel ___ 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: Request for commit approval (multimedia/webcamd)
On 12/13/18 10:38 PM, Kurt Jaeger wrote:
Hi!
Mine last version:
# Gamepad Logitech
notify 100 {
match "system""USB";
match "subsystem" "INTERFACE";
match "type" "ATTACH";
match "vendor""0x046d";
match "product" "0xc216|0xc219";
action "/usr/local/etc/rc.d/webcamd start $cdev $interface";
};
Can you submit this patch? Or do you want me to?
Please, just commit this fix (approved). Thanks!
--HPS
Index: files/webcamd.conf.in
===
--- files/webcamd.conf.in (revision 487369)
+++ files/webcamd.conf.in (working copy)
@@ -59,12 +59,8 @@
match "type" "ATTACH";
match "vendor""0x046d";
- match "product" "0xc216";
+ match "product" "0xc216|0xc219";
- match "intclass" "0x03";
- match "intsubclass" "0x00";
- match "intprotocol" "0x00";
-
action "%%PREFIX%%/etc/rc.d/webcamd start $cdev $interface";
};
Done.
--HPS
___
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
Thanks for your posts. I think the same as you. For me, I have to do the update of the defaul version of perl from today. It is not so big as the gcc8 "thing", but another 200 ports to build. This week I have build some ports three times. ___ 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: A potential new porter seeking some clarifications
On 14/12/2018 7:09 pm, Kubilay Kocak wrote: While special targets (check-plist) can be and are useful, the only form of QA we should be doing is 'all of it', and at the present moment, that is: 1) portlint -AC (or better) 2) poudriere testport (supported versions/archs, at least tier1 [1]) 3) make test for run-time QA [2] I forgot: 4) DEVELOPER=yes in /etc/make.conf for extra sanity checks Even (1) and (2) alone, while being the making up the bulk of our QA, which is notable not 'everything, everytime', is insufficient, as it mostly picks up only 'our' errors, not the softwares issues, which ultimately impact users. [1] non tier1 is not as trivial as it should be to setup in poudriere. [2] if test suites exist, TEST_DEPENDS and test: target should be hooked up ./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"
Re: A potential new porter seeking some clarifications
On 14/12/2018 2:11 am, Lars Engels wrote: On Thu, Dec 13, 2018 at 10:41:01PM +0800, Arthur Pirika wrote: Hi all! I’m hoping to get into porting for FreeBSD, right now just focusing on one package, a plugin for bitlbee, however I’d like to extend my hand to maintain other ports in the future once I have more knowledge and practice with the system. Welcome! :-) Before I start, though, I just need some clarifications of things from the porter’s handbook. 1. If I understand correctly, the version of the ports tree as fetched by portsnap isn’t the best for working on the tree. I should instead make another copy of the tree as an svn checkout? Distfiles, however, still go to /usr/ports/distfiles You can change this by setting DISTDIR variable in /etc/make.conf to a directory you like. See ports(7) manpage. 2. Is it absolutely necessary to use poudriere before submitting a port? I’m still getting to grips with how it works, and if I need to get comfortable with it first, I’ll do so. That really depends on the change's size. Trivial patches can often be sub-/committed without a poudriere run. portlint -ac, make check-plist and make package can find potential issues for you. Bigger changes should be build in poudriere. You don't need to attach the logs to the PR, though. tldr: It is absolutely necessary if we don't want to shuffle 'quality' work to "someone else" as a project/culture/community, we want to pick up issues as early as possible and if we want our contributions as committers and not-yet-committers alike to be taken seriously, hopefully resulting in quicker times to commit in the latter case. The degree of QA required, putting it gently, is not at all contingent on, or proportional to *change* size or "apparent" simplicity. That contention needs to go away. Note: Lars, I'm certainly not pointing the finger at you here, or anyone else in particular. The canonical example historically used, and sometimes (too often) described as 'simple' by both committers and contributors, mostly only ever used to imply that QA (or more of it) isn't necessary to get a Bugzilla issue assigned/closed more quickly, is the "minor PORTVERSION bump and a distinfo update". In the meantime along with that two line "simple" patch, upstream has added/removed dependencies, added or removed a few files (pkg-plist), or at worst, broken/regressed something entirely, to name only a few cases. While special targets (check-plist) can be and are useful, the only form of QA we should be doing is 'all of it', and at the present moment, that is: 1) portlint -AC (or better) 2) poudriere testport (supported versions/archs, at least tier1 [1]) 3) make test for run-time QA [2] Even (1) and (2) alone, while being the making up the bulk of our QA, which is notable not 'everything, everytime', is insufficient, as it mostly picks up only 'our' errors, not the softwares issues, which ultimately impact users. [1] non tier1 is not as trivial as it should be to setup in poudriere. [2] if test suites exist, TEST_DEPENDS and test: target should be hooked up ./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"
