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
Hi,
It seems like the package and the port mail/milter-manager are broken
and it has no maintainer. To be more specific, I keep on getting a
"Segmentation fault (core dumped)" when executing the binary. I assume
it is being compiled against something which milter-manager is not
compatible yet, cau
Hi!
> It seems like the package and the port mail/milter-manager are broken
> and it has no maintainer. To be more specific, I keep on getting a
> "Segmentation fault (core dumped)" when executing the binary. I assume
> it is being compiled against something which milter-manager is not
> compatibl
Hello,
From: Leander Schäfer
Subject: FreeBSD 11.1-RELEASE - mail/milter-manager broken
Date: Sun, 18 Mar 2018 12:18:24 +0200
> It seems like the package and the port mail/milter-manager are broken
> and it has no maintainer. To be more specific, I keep on getting a
> "Segmentation fault (core d
Hi Yasuhiro,
Thank you for your feedback. I was about to file my bug report to
https://bugs.freebsd.org when I found your update. The Segmentation
fault (core dumped) appears already when you execute "milter-manager"
binary without any further options/flags or configuration file. I'm also
using po
Hi,
Current version of copyq if outdated - it is 2.7.1 and newest version is 3.3.0.
Could the port be updated, please?
Thanks
--
/*
* Serpent7776
*/
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
T
Trying to work up a development port of ufraw, fetching from
https://github.com/sergiomb2/ufraw.git
(or at least that's where I can get the source manually)
Going slowly, just trying to get the source fetched properly:
/!\ ufraw-devel-g20161113: Makefile warnings, please consider fixing /!\
No
Hi!
> Thank you for your feedback. I was about to file my bug report to
> https://bugs.freebsd.org when I found your update. The Segmentation
> fault (core dumped) appears already when you execute "milter-manager"
> binary without any further options/flags or configuration file. I'm also
> using p
Hi Kurt,
I'm most certain you did, but just to be safe: are you sure you used the
updated version 2.1.1 / patch from Yasuhiro? Cause the changes of
Yasuhiro did not reflect for my poudriere when it pulled the latest
ports tree. If you applied the changes manually to your poudriere, how
did you do
On Saturday, March 17, 2018 06:44:54 PM Serpent7776 wrote:
> On Sat, 17 Mar 2018 18:18:57 +0100
>
> Kurt Jaeger wrote:
> > > I created initial working qlipper port (a clipboard manager), but I will
> > > not maintain or improve it further. If anyone is interested in this
> > > port, just clone re
Gary Aitken wrote on 2018/03/18 20:04:
Trying to work up a development port of ufraw, fetching from
https://github.com/sergiomb2/ufraw.git
(or at least that's where I can get the source manually)
Going slowly, just trying to get the source fetched properly:
/!\ ufraw-devel-g20161113: Makefile
On Sun, 18 Mar 2018 21:30:29 +0100
Vidar Karlsen wrote:
> On Saturday, March 17, 2018 06:44:54 PM Serpent7776 wrote:
> > On Sat, 17 Mar 2018 18:18:57 +0100
> >
> > Kurt Jaeger wrote:
> > > > I created initial working qlipper port (a clipboard manager), but I will
> > > > not maintain or impro
> On 18 Mar 2018, at 22:33, Serpent7776 wrote:
>
> Just note your url is missing dash, here's corrected:
> https://github.com/vkarlsen/freebsd-ports/tree/master/deskutils/qlipper
Thanks, I must have fat-fingered it, “freebsd-ports” with the dash is indeed
correct.
--
Vidar Karlsen
signature
On Sun, Mar 18, 2018 at 08:10:14PM +0100 I heard the voice of
Kurt Jaeger, and lo! it spake thus:
>
> Tested it, seems to still dump core.
>
> Backtrace is at
>
> http://people.freebsd.org/~pi/logs/milter-backtrace.txt
I recall trying to build it on ruby 2.4 on a server some time back
(early la
FreeBSD BSD_12 12.0-CURRENT FreeBSD 12.0-CURRENT #12 r331138: Sun Mar 18
15:09:37 EDT 2018
root@BSD_12:/usr/obj/usr/src/amd64.amd64/sys/MYKERNEL amd64
I recently started to see strange behavior on 2 different machines and was
wondering if anyone else has run into it. Within the last few days
On 03/18/18 18:35, AN wrote:
Is there a way to restart the audio subsystem without rebooting the
machine?
Building kernel with sound and snd_* as loadable modules should enable
this to be accomplished with kldunload/kldload. In my experience though
all sound device files must be closed before
On 03/18/18 14:53, Miroslav Lachman wrote:
Gary Aitken wrote on 2018/03/18 20:04:
Trying to work up a development port of ufraw, fetching from
https://github.com/sergiomb2/ufraw.git (or at least that's where I
can get the source manually) Going slowly, just trying to get the
source fetched prop
Where did you get this version number? DISTVERSION= g20161113
I was trying to follow example 5.13 in the porter's handbook.
However, this particular git tree has only a main branch and no
tags, so it's not a perfect fit.
What about this
PORTNAME= ufraw-devel PORTVERSION= g201611
In message <764e2df5-613d-a131-5d7d-6df545995...@gmail.com>, Theron
Tarigo writ
es:
> On 03/18/18 18:35, AN wrote:
> > Is there a way to restart the audio subsystem without rebooting the
> > machine?
> Building kernel with sound and snd_* as loadable modules should enable
> this to be accomplish
Gary Aitken wrote on 2018/03/19 00:02:
fetch:
https://codeload.github.com/sergiomb2/ufraw/tar.gz/g20161113?dummy=/sergiomb2-ufraw-g20161113_GH0.tar.gz:
Not Found
=> Attempting to fetch
http://distcache.FreeBSD.org/ports-distfiles/ufraw-devel/sergiomb2-ufraw-g20161113_GH0.tar.gz
fetch:
ht
On 03/18/18 18:13, Miroslav Lachman wrote:
Gary Aitken wrote on 2018/03/19 00:02:
fetch:
https://codeload.github.com/sergiomb2/ufraw/tar.gz/g20161113?dummy=/sergiomb2-ufraw-g20161113_GH0.tar.gz:
Not Found
=> Attempting to fetch
http://distcache.FreeBSD.org/ports-distfiles/ufraw-devel/sergiom
Hi!
> I'm most certain you did, but just to be safe: are you sure you used the
> updated version 2.1.1 / patch from Yasuhiro? Cause the changes of
> Yasuhiro did not reflect for my poudriere when it pulled the latest
> ports tree. If you applied the changes manually to your poudriere, how
> did yo
22 matches
Mail list logo
