On Wed, 8 Jul 2020 15:44:21 +0200, Christoph Moench-Tegeder stated:
>## Carmel NY (carmel...@outlook.com):
>
>> The entire build log, what there is of it, is available here:
>> https://seibercom.net/logs/qt5-network_build.log
>
>And there's your problem:
>: /usr/local/etc/poudriere.d/make.co
## Carmel NY (carmel...@outlook.com):
> The entire build log, what there is of it, is available here:
> https://seibercom.net/logs/qt5-network_build.log
And there's your problem:
: /usr/local/etc/poudriere.d/make.conf
:
: LICENSES_ACCEPTED+= PDFlib
: DEFAULT_VERSIONS=samba=4.11
: DEFAU
updated ports tree, when I attempt to run
>> >> poudriere to update the installed ports, I am greeted with this
>> >> warning:
>> >>
>> >> [00:00:21] Ignoring net/qt5-network | qt5-network-5.15.0: is
>> >> marked as broken: Qt5
I am greeted with this warning:
> >>
> >> [00:00:21] Ignoring net/qt5-network | qt5-network-5.15.0: is marked
> >> as broken: Qt5 requires Openssl 1.1.1, upgrade to FreeBSD 12.x/13.x
> >> or add DEFAULT_VERSIONS+=ssl=[openssl|libressl*] to /etc/make.conf
> &
>On Wed, 8 Jul 2020 at 13:10, Carmel NY wrote:
>>
>> FreeBSD 11.4-RELEASE
>>
>> With a freshly updated ports tree, when I attempt to run poudriere to
>> update the installed ports, I am greeted with this warning:
>>
>> [00:00:21] Ignoring net/qt5-
led ports, I am greeted with this warning:
>
> [00:00:21] Ignoring net/qt5-network | qt5-network-5.15.0: is marked as
> broken: Qt5 requires Openssl 1.1.1, upgrade to FreeBSD 12.x/13.x or add
> DEFAULT_VERSIONS+=ssl=[openssl|libressl*] to /etc/make.conf
>
> Subsequently, 339 ports
FreeBSD 11.4-RELEASE
With a freshly updated ports tree, when I attempt to run poudriere to
update the installed ports, I am greeted with this warning:
[00:00:21] Ignoring net/qt5-network | qt5-network-5.15.0: is marked as broken:
Qt5 requires Openssl 1.1.1, upgrade to FreeBSD 12.x/13.x or add
On Tue, Nov 05, 2019 at 09:27:58AM +0900, Koichiro Iwao wrote:
> I'm not familiar with golang build system. I'm not sure why this happens
> and the differences between golang apps use network and don't. I'd
> appreciate if you give me some advice how do golang folks
Hi,
Thank you both. I'll give it a try.
--
meta
___
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"
poudriere
Reply-To:
X-Operating-System: FreeBSD 12.1-STABLE amd64
Hi,
I recently noticed some golang apps (recent vewsion?) try to use network
during build. As we know, this causes build error on poudriere.
I'm not familiar with golang build system. I'm not sure why this happe
On 3/30/19 10:49 PM, Davide Beatrici wrote:
> Greetings,
>
> I would like to inform you
> about https://bugreports.qt.io/browse/QTBUG-74844.
>
> A patch is attached to the bug report.
>
> Best regards,
> Davide
Thanks for the heads-up. Please note that you are a lot more likely to
get your patc
of it.
>
> This is something that's going to need .. well, preferably Pjotr Kubaj who
> has
> access to suitable machines .. someone to chase the build and figure out what
> is #defined exactly and which (qmake) configurations are in use.
>
Looking, I can confirm QT_NO_B
On Monday, 11 March 2019 13:01:43 CET freebsd-ports-requ...@freebsd.org wrote:
> ../qbearerengine_impl.h:48:1: error: expected class-name before '{' token
I *imagine* (since I don't have anything that can try to reproduce this build
sensibly) that you're hitting a case where QT_NO_BEARERMANAGEMEN
ports-mgmt/poudriere-devel got:
[06:34:26] [02] [00:00:00] Building net/qt5-network | qt5-network-5.12.1
. . .
[06:47:03] [02] [00:12:37] Saved net/qt5-network | qt5-network-5.12.1 wrkdir
to:
/usr/local/poudriere/data/wrkdirs/FBSDpowerpc-default/default/qt5-network-5.12.1.tbz
[06:47:03] [02
On Monday, 24 December 2018 18:14:51 CET Michael Butler wrote:
> As follows:
.. and here I had tested on 11.2 with base SSL, openssl, openssl111, .. and
not considered that 12.0 would remove the definition of IFM_FDDI entirely.
Fixed, I hope, in r488281 (which built for me in a 12.0-RC3 VM).
[a
As follows:
--- .obj/qudpsocket.o ---
c++ -c -O2 -pipe -march=ivybridge -fstack-protector -fno-strict-aliasing
-DOPENSSL_API_COMPAT=0x1010L -std=c++1z -fvisibility=hidden
-fvisibility-inlines-hidden -fno-exceptions -Wall -W -Wdate-time
-Winconsistent-missing-override -pthread -fPIC -DQT_OPENSS
On 22/09/2018 19:13, Ruslan Makhmatkhanov wrote:
> As for your question:
> pbr is set in molecule's setup.py as setup_depends, so it should go to
> BUILD_DEPENDS in Makefile. Also make sure that you list all the
> dependencies from the molecule's requirements.txt as RUN_DEPENDS.
That's fixed it, t
This one should work: http://dpaste.com/0P2SBMM.txt
but it wouldn't, because of pbr's dependency on broken devel/py-pip (it
requires previous version of dns/py-idna, that we no more have in ports
tree).
As for your question:
pbr is set in molecule's setup.py as setup_depends, so it should go t
So, I've been working on porting molecule
(https://pypi.org/project/molecule/), and I have a port that /almost/
works. I can compile and run molecule from my shell prompt using the
port. Everything seems fine.
Except when I try and build the port inside poudriere. It seems that
python setuptool
On 08/17/16 00:59, Sascha Holzleiter wrote:
On 2016-08-17 00:51, Russell L. Carter wrote:
Hi,
For about a week now I have been having some build failures
that cause a lot of dependent port builds in poudriere
to get skipped.
Focusing on one of the first ones, net/qt5-network fails
in '
Hi,
For about a week now I have been having some build failures
that cause a lot of dependent port builds in poudriere
to get skipped.
Focusing on one of the first ones, net/qt5-network fails
in 'build'.
poudriere tells me it saved the wrkdir to:
/ssd1/poudriere/data/wrkdirs/10-st
SD
>>>> 10.2-RELEASE-p8 (amd64).
>>>>
>>>> Access via web interface on port 8200 is working fine. But the MiniDLNA
>>>> server is not seen in my network and correspondingly I cannot access
>>>> any of my FLAC audio files. I do not host any other medi
ess via web interface on port 8200 is working fine. But the MiniDLNA
>>> server is not seen in my network and correspondingly I cannot access
>>> any of my FLAC audio files. I do not host any other media besides the
>>> FLAC files.
>>>
>>> I strongly assume
>> server is not seen in my network and correspondingly I cannot access
>> any of my FLAC audio files. I do not host any other media besides the
>> FLAC files.
>>
>> I strongly assume this is related to upgrading to version 1.1.5.
>>
>> Can anyone reproduce
On 19.12.15 00:03, Dr. Peter Voigt wrote:
Today I have upgraded net/minidlna to latest version. I am on FreeBSD
10.2-RELEASE-p8 (amd64).
Access via web interface on port 8200 is working fine. But the MiniDLNA
server is not seen in my network and correspondingly I cannot access
any of my FLAC
On Fri, 18 Dec 2015 23:03:40 +0100
"Dr. Peter Voigt" wrote:
> Today I have upgraded net/minidlna to latest version. I am on FreeBSD
> 10.2-RELEASE-p8 (amd64).
>
> Access via web interface on port 8200 is working fine. But the
> MiniDLNA server is not seen in my netw
Today I have upgraded net/minidlna to latest version. I am on FreeBSD
10.2-RELEASE-p8 (amd64).
Access via web interface on port 8200 is working fine. But the MiniDLNA
server is not seen in my network and correspondingly I cannot access
any of my FLAC audio files. I do not host any other media
Hello.
I'm looking for a centralized backup solution with the following
requirements:
_ server (FreeBSD) side storage and/or NAS storage;
_ Windows and Mac client support;
_ "push model" (meaning a client will initiate a backup when it is
powered up/connected);
_ ability to run script on the c
On 9/9/2014 13:49, O. Hartmann wrote:
> In the strain of a bug I reported I also tried to fix this port, since the
> prior
> maintainer seems to have abandonded this great port.
>
> I'm a bit pissed off about the rude tune I feel treated!
I don't know why you brought the contents of a PR to the
Am Tue, 09 Sep 2014 06:35:29 +
bugzilla-nore...@freebsd.org schrieb:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=144203
>
> --- Comment #8 from John Marino ---
> FYI, I'm removing this port tonight. We've waited long enough.
>
In the strain of a bug I reported I also tried to fi
Op vrijdag 13 december 2013 schreef Erich Dollansky (
erichsfreebsdl...@alogt.com):
> Hi,
>
> I have had once an application installed that showed the current
> network connections as a graph in an X11 window.
>
> Does anybody know the name of such an application?
>
Hi,
I have had once an application installed that showed the current
network connections as a graph in an X11 window.
Does anybody know the name of such an application?
Thanks!
Erich
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org
14.05.2013 01:50, Beeblebrox пишет:
> Printer1: Officejet_4500_G510n-z. This connects to network with wireless and
> I use hplip for this printer.
OK, but for now let's make another one to print.
> Printer2: HP_LaserJet_2100. This uses jetdirect wired connection and setup
> is
Printer1: Officejet_4500_G510n-z. This connects to network with wireless and
I use hplip for this printer.
Printer2: HP_LaserJet_2100. This uses jetdirect wired connection and setup
is directly through cups (does not use hplip).
The log output I posted is for Printer2 (no hplip). Also all updates
13.05.2013 20:01, Beeblebrox пишет:
> I have 2 HP printers on my network. I have
> print/cups & print/hplip
[1]
> installed. Before a recent cups update (or re-compile by poudriere) I was
> printing to both f my HP printers without problem. After the update (2-3
> days ago
I have 2 HP printers on my network. I have print/cups & print/hplip
installed. Before a recent cups update (or re-compile by poudriere) I was
printing to both f my HP printers without problem. After the update (2-3
days ago) I cannot print to either.
After I give the print command (from a si
On Wed, Mar 27, 2013 at 04:03:09AM -0700, Beeblebrox wrote:
> Sorry for the late reply, everyone - I was distracted with some other things
> for a while.
>
> PATCHING:
> I'll probably have to look through the syntax of "OPTIONS" in the Makefiles
> of other KDE / CMAKE ports to get a handle on how
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/Ports-should-provide-knobs-disabling-unwanted-network-services-tp5798581p5799340.html
Sent from the freebsd-ports mailing list archive at Nabble.com.
___
freebsd-port
On Tue, Mar 26, 2013 at 07:15:24PM +0100, Wojciech Puchar wrote:
> On Sun, 24 Mar 2013, Beeblebrox wrote:
>
> > Many ports, (specially the KDE-related ones) provide no option to disable
> > network-related options. Usually these are things like samba-client,
> > Avahi-mD
On Sun, 24 Mar 2013, Beeblebrox wrote:
Many ports, (specially the KDE-related ones) provide no option to disable
network-related options. Usually these are things like samba-client,
Avahi-mDNS* (with variants), and the like. Gnome usually provides a choice
to disable gnome-vfs.
I really don&#
Le 26/03/2013 10:00, Peter Pentchev a écrit :
> On Tue, Mar 26, 2013 at 09:13:38AM +0100, Florent Peterschmitt wrote:
>> Le 25/03/2013 04:40, Scot Hetzel a écrit :
>>> On Sun, Mar 24, 2013 at 10:33 PM, Florent Peterschmitt
>>> wrote:
Le 24/03/2013 17:34, Scot Hetzel a écrit :
> On Sun, Ma
On Tue, Mar 26, 2013 at 09:13:38AM +0100, Florent Peterschmitt wrote:
> Le 25/03/2013 04:40, Scot Hetzel a écrit :
> > On Sun, Mar 24, 2013 at 10:33 PM, Florent Peterschmitt
> > wrote:
> >> Le 24/03/2013 17:34, Scot Hetzel a écrit :
> >>> On Sun, Mar 24, 2013 at 7:00 AM, Beeblebrox wrote:
>
Le 25/03/2013 04:40, Scot Hetzel a écrit :
> On Sun, Mar 24, 2013 at 10:33 PM, Florent Peterschmitt
> wrote:
>> Le 24/03/2013 17:34, Scot Hetzel a écrit :
>>> On Sun, Mar 24, 2013 at 7:00 AM, Beeblebrox wrote:
I would be very happy to submit a patch, if I actually knew how to write
one.
On Sun, Mar 24, 2013 at 10:33 PM, Florent Peterschmitt
wrote:
> Le 24/03/2013 17:34, Scot Hetzel a écrit :
>> On Sun, Mar 24, 2013 at 7:00 AM, Beeblebrox wrote:
>>> I would be very happy to submit a patch, if I actually knew how to write
>>> one...
>>>
>>
>> It is quite simple to create the patch
Le 24/03/2013 17:34, Scot Hetzel a écrit :
> On Sun, Mar 24, 2013 at 7:00 AM, Beeblebrox wrote:
>> I would be very happy to submit a patch, if I actually knew how to write
>> one...
>>
>
> It is quite simple to create the patch.
>
> If you have a working copy checked out with svn, then it would
On Sun, Mar 24, 2013 at 7:00 AM, Beeblebrox wrote:
> I would be very happy to submit a patch, if I actually knew how to write
> one...
>
It is quite simple to create the patch.
If you have a working copy checked out with svn, then it would be:
cd /usr/ports/[category]/[port]
- Make the necessar
te
> one...
>
>
>
> --
> View this message in context:
> http://freebsd.1045724.n5.nabble.com/Ports-should-provide-knobs-disabling-unwanted-network-services-tp5798581p5798594.html
> Sent from the freebsd-ports mailing list archive at Nabble.com.
>
I would be very happy to submit a patch, if I actually knew how to write
one...
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/Ports-should-provide-knobs-disabling-unwanted-network-services-tp5798581p5798594.html
Sent from the freebsd-ports mailing list archive at
ovide no option to disable
> network-related options. Usually these are things like samba-client,
> Avahi-mDNS* (with variants), and the like. Gnome usually provides a choice
> to disable gnome-vfs.
>
> I really don't understand why such ports enable those services by defau
Many ports, (specially the KDE-related ones) provide no option to disable
network-related options. Usually these are things like samba-client,
Avahi-mDNS* (with variants), and the like. Gnome usually provides a choice
to disable gnome-vfs.
I really don't understand why such ports enable
On Thu, May 31, 2012 at 6:52 PM, Per olof Ljungmark wrote:
> BTW, if KDE3 is unmaintained and this gous for FreeBSD too, perhaps it
> should be mentioned in the Handbook?
I submitted these lines for the Handbook some time ago:
There are two versions of KDE available on FreeBSD. Version 3 has bee
ous for FreeBSD too, perhaps it
>>> should be mentioned in the Handbook?
>>>
>>
>> There is very little software that is unmaintained upstream and is
>> maintained here-- it is strongly discouraged. Such a declaration
>> would be therefore redundant; EOL upstr
gly discouraged. Such a declaration
would be therefore redundant; EOL upstream means unsupported in
FreeBSD.
Chris
Hi Chris,
I don't know really for kde3-network specifically but I managed to
compile on a kde-lite without much problems on 8-STABLE after having
deleted openssl port.
On 31 May 2012 17:52, Per olof Ljungmark wrote:
> On 05/31/12 14:16, Chris Rees wrote:
>>
>> On May 31, 2012 12:39 PM, "Per olof Ljungmark" wrote:
>>>
>>>
>>> I find KDE4 unusable and xfce a bit weak for my purposes so I'm trying to
>>
>> stick to KDE3.
>>>
>>>
>>
>> Just a reminder that although
On 05/31/12 14:16, Chris Rees wrote:
On May 31, 2012 12:39 PM, "Per olof Ljungmark" wrote:
I find KDE4 unusable and xfce a bit weak for my purposes so I'm trying to
stick to KDE3.
Just a reminder that although people may try to help you, kde3 is
unmaintained.
BTW, if KDE3 is unmaintaine
On 05/31/12 14:32, Alberto Villa wrote:
On Thu, May 31, 2012 at 2:24 PM, Per olof Ljungmark wrote:
I heard from somewhere that there is a fork of KDE3 maintained by folks that
just like me finds KDE4 unusable. Perhaps someone on the list knows more?
http://www.trinitydesktop.org
Ah, yes. Bu
On Thu, May 31, 2012 at 2:24 PM, Per olof Ljungmark wrote:
> I heard from somewhere that there is a fork of KDE3 maintained by folks that
> just like me finds KDE4 unusable. Perhaps someone on the list knows more?
http://www.trinitydesktop.org
--
Alberto Villa, FreeBSD committer
http://people.F
On 2012-05-31 14:16, Chris Rees wrote:
On May 31, 2012 12:39 PM, "Per olof Ljungmark" wrote:
I find KDE4 unusable and xfce a bit weak for my purposes so I'm trying to
stick to KDE3.
Recent 9-STABLE amd64
Just a reminder that although people may try to help you, kde3 is
unmaintained.
On May 31, 2012 12:39 PM, "Per olof Ljungmark" wrote:
>
> I find KDE4 unusable and xfce a bit weak for my purposes so I'm trying to
stick to KDE3.
>
> Recent 9-STABLE amd64
>
> mv -f .deps/talkconn.Tpo .deps/talkconn.Po
> rm -f libmach.a
> ar cru libmach.a answmach.o forwmach.o talkconn.o
> ranlib
I find KDE4 unusable and xfce a bit weak for my purposes so I'm trying
to stick to KDE3.
Recent 9-STABLE amd64
mv -f .deps/talkconn.Tpo .deps/talkconn.Po
rm -f libmach.a
ar cru libmach.a answmach.o forwmach.o talkconn.o
ranlib libmach.a
gmake[4]: Leaving directory
`/usr/ports/net/kdenetwork3/w
On 02/07/12 18:40, O. Hartmann wrote:
We use a bunch of HP and Xerox printers across our network, all capable
of being accessed via network over IPP protocoall (so they claim).
Printing worked for me flawless on FreeBSD 8.2-STABLE, 9.0-CURRENT, now
9.0-STABLE on all boxes in question. Since
We use a bunch of HP and Xerox printers across our network, all capable
of being accessed via network over IPP protocoall (so they claim).
Printing worked for me flawless on FreeBSD 8.2-STABLE, 9.0-CURRENT, now
9.0-STABLE on all boxes in question. Since updating cups to revision
1.5.0 (this is
ding for bigreqsproto-1.1.1
Making all in specs
GENbigreq.html
xmlto:
/usr/ports/x11/bigreqsproto/work/bigreqsproto-1.1.1/specs/bigreq.xml
does not validate (status 3)
xmlto: Fix document syntax or use --skip-validation option
I/O error : Attempt to load network entity
http://www.oasis-open.org
Elib.xml does not
validate (status 3)
xmlto: Fix document syntax or use --skip-validation option
I/O error : Attempt to load network entity
http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd
/usr/ports/x11/libICE/work/libICE-1.0.7/doc/ICElib.xml:3: warning:
failed to load external entit
[1]To view this invitation online click here
You are subscribed to this mailing list as freebsd-ports@freebsd.org.
Please [2]click here to modify your message preferences or to
unsubscribe from any future mailings. We will respect all unsubscribe
reque
=-m64
See if your 'network i/o' test case now passes.
Makes no difference - it *doesn't fail* for network I/O (it completes
fine) - it just dumps a single line to stderr at the start, which says:
"
mbuffer: warning: unable to set socket buffer size: No buffer space
availabl
--On 23 September 2010 16:49 +0400 Ruslan Mahmatkhanov
wrote:
Hi Karl,
sorry about webmail formatting.
Yeah, it certainly mangled the original mail when quoting it!
Try to add this line into port's Makefile, and then reinstall mbuffer:
CFLAGS+=-m64
See if your 'network i/o&
r you. -- Regards, RuslanHi,The patch/updated version seems to
> work fine - there's a couple of compile time warnings, and when you run it
> using 'network' I/O you still get:"mbuffer: warning: unable to set socket
> buffer size: No buffer space available"But i
seems to work fine - there's a couple of compile
time warnings, and when you run it using 'network' I/O you still get:
"
mbuffer: warning: unable to set socket buffer size: No buffer space
available
"
But it does appear to work - network mode works, and when using anoth
22.09.2010 18:06, Karl Pielorz пишет:
Hi,
I've got the port of mbuffer (/usr/ports/misc/mbuffer) installed on a
number of machines (amd64/FreeBSD 6.4-S, 7.2-S and 8.1-R) - but it seems
to have issues...
Firstly - any attempt to use the 'network' options of it, fail miserably
Hi,
I've got the port of mbuffer (/usr/ports/misc/mbuffer) installed on a
number of machines (amd64/FreeBSD 6.4-S, 7.2-S and 8.1-R) - but it seems to
have issues...
Firstly - any attempt to use the 'network' options of it, fail miserably
(this is where mbuffer sends t
Hi guy(s)
I have FreeBSD 7.2
#uname -a
FreeBSD alpha.company.com 7.2-RELEASE-p2 FreeBSD 7.2-RELEASE-p2 #2:
Sat Jul 4 12:17:17 COT 2009
an...@alpha.company.com:/usr/obj/usr/src/sys/MYKERNEL amd64
#ls /var/db/pkg
---
apache-2.2.14_6
nut-2.4.1_3
nmap-5.21_1
---
# ls /usr/local/etc/nut/
cmdvartab
Diogo Coimbra convida-o a entrar no Viadeo Bom dia,
Gostaria de apresentar-lhe a empresa Viadeo.com, uma plataforma de networking
ao nível profissional, disponivel em Português, onde pode:
Encontrar potenciais colaboradores
; get the error message:
>>
>> TreeList failed: Network write failure: Connection closed
>>
>> after a couple of seconds. This doesn't occur when I am connected
>> through a cable ethernet device.
>
> OK, this just means your system was unable to maintain the netw
On Tue, Mar 14, 2006 at 07:37:56PM +0100, [LoN]Kamikaze wrote:
> That would mean that ipw is broken. I never had such problems when I was
> using 5-stable with ipw from the ports.
OK.
Kris
pgpXJoywrkH5y.pgp
Description: PGP signature
Hi all,
XMLSysInfo (xsi) is asystem monitoring daemon which returns system
information in response to network queries. The author asked me on IRC
if I could test FreeBSD support for it. So far everything looks to be
good and working fine for me. You can see the output from my laptop
(formatted
Siju George wrote:
> I installed Subversion on FreeBSD 6.1 from ports.
> Started svnserve to listen on 3690
> How do I make it listen on tcp4.
You can add the option --listen-host=0 to listen on IPv4 only.
Greetings,
Johan
pgpaeaEpCbpGo.pgp
Description: PGP signature
-an |grep 3690
tcp6 0 0 *.3690 *.*LISTEN
Any Idea why it is listening on tcp6 and not tcp4?
How do I make it listen on tcp4. I cannot access the repositories now
from the network :-(
Thankyou so much
Kind Regards
Siju
On Fri, Jun 30, 2006 at 03:59:48PM -0700, Mihir Sanghavi wrote:
> hi,
> I want to set up my network but donot know how to do. Can some explain me
> in detail please.thanks
>
Is FreeBSD handbook not useful for you?
--
Best regards,
Ar
hi,
I want to set up my network but donot know how to do. Can some explain me
in detail please.thanks
--
What we see depends mainly on what we look for.
-MIHIR
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd
80 matches
Mail list logo
