From nobody Wed Jan 15 22:08:14 2025 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4YYKrm4wbQz5kk6m for ; Wed, 15 Jan 2025 22:08:40 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from www121.sakura.ne.jp (www121.sakura.ne.jp [153.125.133.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4YYKrl3xhwz3lym for ; Wed, 15 Jan 2025 22:08:38 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Authentication-Results: mx1.freebsd.org; none Received: from kalamity.joker.local (124-18-43-234.area1a.commufa.jp [124.18.43.234]) (authenticated bits=0) by www121.sakura.ne.jp (8.17.1/8.17.1/[SAKURA-WEB]/20201212) with ESMTPA id 50FM8EMA022806; Thu, 16 Jan 2025 07:08:15 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dec.sakura.ne.jp; s=s2405; t=1736978901; bh=SxeCd1gR4XOPIXakVYWeGrtDOUyM7wuPUR8jX5rYyfE=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=Eap4llYetRscfIHoa5ctN+nEFaZOgiHDvfyJamvPc5PgZ5JVxYdD8hPalfNPMUFGn QdllDXFfyVkpTPozNNzXVOrMO/tuyxdQ1z5M3skb72QEdCjt6FhlmX2ob/fUSlDA8e fA+S1FZMgMRiGHnYr0535X8Jd/zLxe4PXiWtK5Mc= Date: Thu, 16 Jan 2025 07:08:14 +0900 From: Tomoaki AOKI To: Rainer Duffner Cc: John Nielsen , Current FreeBSD , Dennis Clarke Subject: Re: poudriere and the user ... is it mostly a lost idea? Message-Id: <20250116070814.49005cec8d50b99636a4b03e@dec.sakura.ne.jp> In-Reply-To: <477ED13E-453B-4F64-856C-D433812EDA5D@ultra-secure.de> References: <4187986C-3986-4813-91CE-3DA9F599BFC8@jnielsen.net> <477ED13E-453B-4F64-856C-D433812EDA5D@ultra-secure.de> Organization: Junchoon corps X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.2) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4YYKrl3xhwz3lym X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:7684, ipnet:153.125.128.0/18, country:JP] On Wed, 15 Jan 2025 21:33:55 +0100 Rainer Duffner wrote: > > > Am 15.01.2025 um 20:30 schrieb John Nielsen : > > > > > > If you want to get a desktop up and running quickly then you can use the pre-built packages (which are signed and verified by default, clouds and unicorns notwithstanding). > > > > If you choose to build all of your software locally that is 100% a supported option but it does put more responsibility on you, the user. When you get a build failure you are welcome to report it to the maintainer (listed in every single port file) and/or the appropriate mailing list (which -current is not, btw). Include the commands you are running and other configuration details as well as the exact error output. > > > > Note, however, that the automated package build system already emails port maintainers on build failures and, choosing xfce as an example, I don’t see any such reports in the mailing list archives (https://lists.freebsd.org/archives/freebsd-xfce/). You can even view the results of the project’s package build system (which also uses poudriere) by following the instructions here: https://people.freebsd.org/~grahamperrin/pkg-status/ > > > > On a recent quarterly build I don’t see any failed or skipped ports related to the desktop environments you mentioned. (https://pkg-status.freebsd.org/beefy20/build.html?mastername=141amd64-quarterly&build=7b2027223baa) > > > > I’d advise you to do more troubleshooting on your local system and provide some better details if you decide to ask for help in an appropriate forum, such as the freebsd-questions mailing list or the online forums at https://forums.freebsd.org/ or the mailing list(s) listed as maintainers for the ports you are having problems building. > > > > Good luck, > > > > JN > > > Recently, chromium got pulled in on my poudriere build as a dependency of some icinga sub-package. > > That pulled in llvm19, which took I think 18 or 22 hours on the meager HP Gen 8 that poudriere is running on. > > Then, after 24h, the build of chromium was erroring out. > > I think you need to have reasonably recent and powerful hardware to do a build of a „full“ desktop. > > My normal build is 20 hours for 2200 or so packages. Most time is spent on compiling llvm compilers…. And succeed/failure of builds strongly depends on which options are selected. If you've changed something, consider restoring them to default as much as possible. More, you'd better look for PRs on Bugzilla for ports failing for you. If you're lucky enough, someone already filed PR and patch and/or preferred options are already proposed (but not yet landed). And in some (limited, though) cases, bare-metal builds (with ports-mgmt/pkg_replace etc.) succeeds but fails on poudriere jails, usually caused by somewhat dependency issue. FYI: x11/mate and x11-wm/xfce4 succeed both poudriere (stable/14) and pkg_replace (main) for me. Some options are changed (or forgotton to chase default option changes as of overlooking), though. The ports tree is on main (aka latest) branch. The hardware probe is as below (old probe, though, so at stable/13 ATM). http://bsd-hardware.info/?probe=676f16ac86 -- Tomoaki AOKI