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 +-+ devel/aws-sdk-cpp | 1.4.10 | 1.4.11 +-+ devel/distcc| 3.1 | v3.3 +-+ graphics/icoutils | 0.32.2 | 0.32.3 +-+ x11/nxcomp | 3.5.0.32| 3.5.99.15 +-+ 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: DoveCot 2.3
On 7 Mar, 2018, at 15:18, Dewayne Geraghtywrote: Thanks Adam, its very reassuring to know that you'll "dogfood" the update prior to releasing to FreeBSD ports users. This is one of those high impact updates that need it - like sendmail, samba, heimdal, squid, nginx, apache ... ;) Kind regards, Dewayne PS dogfood is a peculiar term where, typically a supplier, uses what they provide to others. As an example: I first came across the term when HP Management wanted to demonstrate to their external customers that they use the same services internally as supplied externally. (I could write a short-story...) Thanks Dewayne, Dogfooding is why 2.3 wasn't committed. Larry didn't have problems with the upgrade, but I ran into a number of them on my own server, including some showstoppers (especially one that caused all incoming attachments to get mangled). I have every intention of committing 2.3.1 once it gets released, though if it happens right at the end of the month, I may wait a few days for 2018Q2 to get branched beforehand---I'd like for the kinks to be worked out in head before it hits quarterly. # Adam -- Adam Weinberger ad...@adamw.org http://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: Exim and CVE-2018-6789
On Wed, Mar 07, 2018 at 02:39:58PM -0700, The Doctor wrote: > On Wed, Mar 07, 2018 at 02:13:00PM -0600, Bob Willcox wrote: > > Hi All, > > > > What is the status of FreeBSD's exim port regarding the CVE-2018-6789 > > vulnerability? Has it been fixed or is the fix in the works? > > > > Check exim. > > I believe Exim 4.90_1 answers this. Thanks, I wasn't sure since the log update didn't spell out that it addressed CVE-2018-6789, nor could I find it on the web page that 316b3c3e-0e98-11e8-8d41-97657151f8c2 took me to (via google). Bob > > > Thanks, > > Bob > > > > -- > > Bob Willcox| The amount of flak received on any subject is inversely > > b...@immure.com | proportional to the subject's true value. > > Austin, TX | > > ___ > > 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" > > -- > Member - Liberal International This is doctor@@nl2k.ab.ca Ici > doctor@@nl2k.ab.ca > Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist > rising! > https://www.empire.kred/ROOTNK?t=94a1f39b Look at Psalms 14 and 53 on Atheism > To make pleasures pleasant, shorten them. -Charles Buxton -- Bob Willcox| The amount of flak received on any subject is inversely b...@immure.com | proportional to the subject's true value. Austin, TX | ___ 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: Exim and CVE-2018-6789
On Wed, Mar 07, 2018 at 02:13:00PM -0600, Bob Willcox wrote: > Hi All, > > What is the status of FreeBSD's exim port regarding the CVE-2018-6789 > vulnerability? Has it been fixed or is the fix in the works? > Check exim. I believe Exim 4.90_1 answers this. > Thanks, > Bob > > -- > Bob Willcox| The amount of flak received on any subject is inversely > b...@immure.com | proportional to the subject's true value. > Austin, TX | > ___ > 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" -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising! https://www.empire.kred/ROOTNK?t=94a1f39b Look at Psalms 14 and 53 on Atheism To make pleasures pleasant, shorten them. -Charles Buxton ___ 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: DoveCot 2.3
On Wed, Mar 07, 2018 at 05:11:05PM +, Matt Smith wrote: > On Mar 07 09:17, The Doctor wrote: > >What are the hold ups for Dovecot 2.3 ? > > > > You, constantly asking this list why they haven't upgraded any ports to > the latest versions but not actually providing any patches yourself to > help the volunteers do this more quickly. > I thought the hold up was with the extra certitification step. > -- > Matt > ___ > 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" -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising! https://www.empire.kred/ROOTNK?t=94a1f39b Look at Psalms 14 and 53 on Atheism To make pleasures pleasant, shorten them. -Charles Buxton ___ 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: DoveCot 2.3
On Wed, Mar 07, 2018 at 10:15:30AM -0700, Adam Weinberger wrote: > > On 7 Mar, 2018, at 9:17, The Doctorwrote: > > > > What are the hold ups for Dovecot 2.3 ? > > There are simply a lot of regressions in 2.3. Many of them have been fixed > upstream, but only the showstoppers made it into 2.3.0.1. The rest of the > fixes will be released with 2.3.1 later this month. 2.2.x is stable and > reliable, so I decided to stay on 2.2 until 2.3.1 is released. > > Once 2.3.1 and the next pigeonhole are released, ler and I will dogfood > them, and if they're solid then we'll commit the updates. > Got you. > # Adam > > > -- > Adam Weinberger > ad...@adamw.org > http://www.adamw.org > -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising! https://www.empire.kred/ROOTNK?t=94a1f39b Look at Psalms 14 and 53 on Atheism To make pleasures pleasant, shorten them. -Charles Buxton ___ 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"
archivers/liblz4 help needed with cross-compiling (PR 225377)
Hi all, If someone with knowledge on cross-compiling could have a look at PR 225377, I would be very grateful. I am the maintainer of the port concerned) and I understand the concern of the reporter. For all I know, the solution proposed in the PR is just a band-aid that would hide the issue (and possible create new ones) instead of solving it. However, having failed to really grasp how a port *should* behave when it comes to cross-compiling, I might be utterly mistaken and thus I am reaching out to you all in the hopes that someone can help resolve this. Thanks for any and all help. Martin ___ 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: Exim and CVE-2018-6789
On 07/03/2018 20:13, Bob Willcox wrote: > Hi All, > > What is the status of FreeBSD's exim port regarding the CVE-2018-6789 > vulnerability? Has it been fixed or is the fix in the works? > > Thanks, > Bob > According to exim.org CVE-2018-6789 was fixed in 4.90.1. The port version is 4.90.1 so yes it should be fixed. see https://www.freshports.org/mail/exim/ for a handy overview. Looks like the quarterly pkg repo is also up to date from a quick glance. Vince ___ 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: net/viamillipede seeks commiter
Hi! > > If there are no objections I'll commit this tonight. > > The bad_ideas target at the end of the Makefile needs to go before this > is committed. > > There still is a superfluous space at the start of a line in pkg-descr. > > The pkg-plist file should probably be removed in favor of using > PLIST_FILES in the Makefile. > > There is a file containing the license in the software's git repository, > so using LICENSE_FILE would probably be a good idea too. > > The file named LICENSE in that repository must not be committed. My current version is available as http://people.freebsd.org/~pi/via.shar and should cover all of this. If no-one beats me to it, I'll commit it tomorrow in the evening 8-} -- p...@opsec.eu+49 171 3101372 2 years 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"
Re: net/viamillipede seeks commiter
On 07/03/2018 20:37, Vincent Hoffman-Kazlauskas wrote: > > > On 07/03/2018 17:08, Ash Gokhale wrote: >> On Wed, Mar 7, 2018 at 6:51 AM, Kurt Jaegerwrote: >> >>> Hi! >>> > I've made peace with poudriere in 10.4, 11.1 and 12 current jails with > USES= uidfix, and also fixed the spurious pthreads cast that was >>> choking > gcc. Would you all try it again please? > https://github.com/agokhale/freebsd-port-net-viamillipede/ >>> commits/master I've tested it on 10.3-i386, same build error as before. Maybe the problem happens with 10.3, but not with 10.4. I'll retest with 10.4. >>> >>> Yes, builds with 10.4, fails with 10.3. >>> >>> -- >>> p...@opsec.eu+49 171 3101372 2 years to >>> go ! >>> >> >> >> >> mat@'s feedback accepted, >> >> This is the error from 10.3 release via poudriere jail: >> >> === >> ===> Building for viamillipede-0.7 >> make[1]: "/usr/share/mk/bsd.own.mk" line 505: MK_DEBUG_FILES can't be set >> by a user. >> *** Error code 1 >> >> >> I'm not sure where to go from this; can I fence the port to build only on >> 10.4+ ? >> >> I'll poke around in the jail for clues. > > > Been a while but I think its something like > > Something like this in the makefile > > .if ${OSVERSION} > 1004000 > BROKEN= Needs features from at least 10.4 > .endif > > Doh .if ${OSVERSION} < 1004000 of course. > > Vince > >> ___ >> 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" > ___ 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"
Exim and CVE-2018-6789
Hi All, What is the status of FreeBSD's exim port regarding the CVE-2018-6789 vulnerability? Has it been fixed or is the fix in the works? Thanks, Bob -- Bob Willcox| The amount of flak received on any subject is inversely b...@immure.com | proportional to the subject's true value. Austin, TX | ___ 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: net/viamillipede seeks commiter
On 07/03/2018 17:08, Ash Gokhale wrote: > On Wed, Mar 7, 2018 at 6:51 AM, Kurt Jaegerwrote: > >> Hi! >> I've made peace with poudriere in 10.4, 11.1 and 12 current jails with USES= uidfix, and also fixed the spurious pthreads cast that was >> choking gcc. Would you all try it again please? https://github.com/agokhale/freebsd-port-net-viamillipede/ >> commits/master >>> >>> I've tested it on 10.3-i386, same build error as before. Maybe >>> the problem happens with 10.3, but not with 10.4. I'll retest with 10.4. >> >> Yes, builds with 10.4, fails with 10.3. >> >> -- >> p...@opsec.eu+49 171 3101372 2 years to >> go ! >> > > > > mat@'s feedback accepted, > > This is the error from 10.3 release via poudriere jail: > > === > ===> Building for viamillipede-0.7 > make[1]: "/usr/share/mk/bsd.own.mk" line 505: MK_DEBUG_FILES can't be set > by a user. > *** Error code 1 > > > I'm not sure where to go from this; can I fence the port to build only on > 10.4+ ? > > I'll poke around in the jail for clues. Been a while but I think its something like Something like this in the makefile .if ${OSVERSION} > 1004000 BROKEN= Needs features from at least 10.4 .endif Vince > ___ > 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: DoveCot 2.3
On 7 Mar, 2018, at 9:17, The Doctorwrote: What are the hold ups for Dovecot 2.3 ? There are simply a lot of regressions in 2.3. Many of them have been fixed upstream, but only the showstoppers made it into 2.3.0.1. The rest of the fixes will be released with 2.3.1 later this month. 2.2.x is stable and reliable, so I decided to stay on 2.2 until 2.3.1 is released. Once 2.3.1 and the next pigeonhole are released, ler and I will dogfood them, and if they're solid then we'll commit the updates. # Adam -- Adam Weinberger ad...@adamw.org http://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: DoveCot 2.3
On Mar 07 09:17, The Doctor wrote: What are the hold ups for Dovecot 2.3 ? You, constantly asking this list why they haven't upgraded any ports to the latest versions but not actually providing any patches yourself to help the volunteers do this more quickly. -- Matt ___ 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: net/viamillipede seeks commiter
On Wed, Mar 7, 2018 at 6:51 AM, Kurt Jaegerwrote: > Hi! > > > > I've made peace with poudriere in 10.4, 11.1 and 12 current jails with > > > USES= uidfix, and also fixed the spurious pthreads cast that was > choking > > > gcc. Would you all try it again please? > > > https://github.com/agokhale/freebsd-port-net-viamillipede/ > commits/master > > > > I've tested it on 10.3-i386, same build error as before. Maybe > > the problem happens with 10.3, but not with 10.4. I'll retest with 10.4. > > Yes, builds with 10.4, fails with 10.3. > > -- > p...@opsec.eu+49 171 3101372 2 years to > go ! > mat@'s feedback accepted, This is the error from 10.3 release via poudriere jail: === ===> Building for viamillipede-0.7 make[1]: "/usr/share/mk/bsd.own.mk" line 505: MK_DEBUG_FILES can't be set by a user. *** Error code 1 I'm not sure where to go from this; can I fence the port to build only on 10.4+ ? I'll poke around in the jail for clues. ___ 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"
DoveCot 2.3
What are the hold ups for Dovecot 2.3 ? -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising! https://www.empire.kred/ROOTNK?t=94a1f39b Look at Psalms 14 and 53 on Atheism To make pleasures pleasant, shorten them. -Charles Buxton ___ 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: net/viamillipede seeks commiter
Hi! > I've made peace with poudriere in 10.4, 11.1 and 12 current jails with > USES= uidfix, and also fixed the spurious pthreads cast that was choking > gcc. Would you all try it again please? > https://github.com/agokhale/freebsd-port-net-viamillipede/commits/master I've tested it on 10.3-i386, same build error as before. Maybe the problem happens with 10.3, but not with 10.4. I'll retest with 10.4. -- p...@opsec.eu+49 171 3101372 2 years 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"
Re: net/viamillipede seeks commiter
On Tue, Mar 06, 2018 at 09:50:04PM +, Josh Paetzel wrote: > > > On Tue, Mar 6, 2018, at 10:19 AM, Mathieu Arnold wrote: > > On Tue, Mar 06, 2018 at 07:34:39AM -0500, Ash Gokhale wrote: > > > gcc. Would you all try it again please? > > > https://github.com/agokhale/freebsd-port-net-viamillipede/commits/master > > > > > > > Add to the top block DISTVERSIONPREFIX=v and change the version to 0.7. > > > > Remove MASTER_SITES. > > > > Remove GH_TAGNAME= v0.7 > > > > BINS seems to not be used, remove it. > > > > pkg-descr needs a big cleanup. > > > > -- > > Mathieu Arnold > > Email had 1 attachment: > > + signature.asc > > 1k (application/pgp-signature) > > It looks like all the changes suggested have been done, both poudriere and > portlint are happy. > > If there are no objections I'll commit this tonight. The bad_ideas target at the end of the Makefile needs to go before this is committed. There still is a superfluous space at the start of a line in pkg-descr. The pkg-plist file should probably be removed in favor of using PLIST_FILES in the Makefile. There is a file containing the license in the software's git repository, so using LICENSE_FILE would probably be a good idea too. The file named LICENSE in that repository must not be committed. -- Mathieu Arnold signature.asc Description: PGP signature