Date: Wed, 10 May 2017 12:59:31 -0400 (EDT) From: Mike Andrews <mandrews@bit0.com> To: freebsd-ports@freebsd.org Subject: poudriere + bdb6 build issue (maybe newbie stupidity) Message-ID: <alpine.BSF.2.21.1705101258040.12354@beast.int.bit0.com>
next in thread | raw e-mail | index | archive | help
I¢m experimenting with poudriere for the first time and running into an issue with some ports that use BDB. With this in make.conf: DEFAULT_VERSIONS= bdb=6 I get this for four ports that use BDB 6: [00:00:47] ====>> [04][00:00:00] Finished build of databases/p5-BerkeleyDB: Ignored: cannot install: no eligible BerkeleyDB version. Requested: 6, incompatible: . Try: make debug-bdb [00:00:47] ====>> [03][00:00:00] Finished build of databases/ruby-bdb: Ignored: cannot install: no eligible BerkeleyDB version. Requested: 6, incompatible: . Try: make debug-bdb [00:00:48] ====>> [06][00:00:01] Finished build of www/webalizer: Ignored: cannot install: no eligible BerkeleyDB version. Requested: 6, incompatible: . Try: make debug-bdb [00:00:49] ====>> [01][00:00:01] Finished build of textproc/redland: Ignored: cannot install: no eligible BerkeleyDB version. Requested: 6, incompatible: . Try: make debug-bdb Installing the ports manually from source works just fine. Am I missing something stupid/obvious here, or is it an issue with those specific four ports? From owner-freebsd-ports@freebsd.org Wed May 10 17:23:09 2017 Return-Path: <owner-freebsd-ports@freebsd.org> Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 726C1D677AE for <freebsd-ports@mailman.ysv.freebsd.org>; Wed, 10 May 2017 17:23:09 +0000 (UTC) (envelope-from ultima1252@gmail.com) Received: from mail-yw0-x232.google.com (mail-yw0-x232.google.com [IPv6:2607:f8b0:4002:c05::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2FE251CDC for <freebsd-ports@freebsd.org>; Wed, 10 May 2017 17:23:09 +0000 (UTC) (envelope-from ultima1252@gmail.com) Received: by mail-yw0-x232.google.com with SMTP id b68so1153679ywe.3 for <freebsd-ports@freebsd.org>; Wed, 10 May 2017 10:23:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=lXmpAJ+v0ykEunCkquyw7eVwbTfx7PqxKgjqnsPs0yM=; b=vHJZRtWrl+NSW6JtBKQfTUFaoMva1xbb88vaQHnQY+3pgIRHI9G237NVGCjSg/pUn0 DlC3wqcfIAKDLZz+Ux4OxzyJ825nHz5EJTfMk7CGyXZW1DkLO1pAhxse6kQVtFALJG/v JY3pAAAZfklk8t1q1+OQzZbP4s8aatTks/4idf+2Ipzp898v9oXgaOk/Vxh/lMhwtj23 jJGIUE/57oxKfsj5IysStdTQs+I77KQo0qmZEznm6UBAvHwfs8V4hxyC3hc226/3E2Vi FJw7u09Ro0IqGgKNKS0N9Q7SIuOGfiGm+bx6PX1MFr3rVv60yf28purq9QE1HJ8H2JEL Movg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=lXmpAJ+v0ykEunCkquyw7eVwbTfx7PqxKgjqnsPs0yM=; b=HZ1rJu+rODmnw6bu49RP0Ixw/0c2fNmQ9UQcmiR0O8UW2oS5OWMUPDyw80KaSEQsz6 RiiZ11bIIRMUQ6Agv42T6u1XbY4M4DjiJEx9WP+aRxqnstOinWXH8JhCdAvB2pySS5Ox p11aT3b/QzLndU5JAhqPbbAQFdQMdJvCm9OM8YEX722eAjyJQ7/ar3E9XCaJNrF28+tE PSiuNYfWu1NOzIm3uZy+Im3ZnmUA7H+mBwfX7BSTwzXE8f9f9Zfw4yHKe9vX1b7vzfmn ZAfGSAjAbTWN2jmqcVQeL7VK0t+p8n9/gSjDgMgUd6o93Ykm3Yc/I9mnR2wqo6sx4ix3 2XPw== X-Gm-Message-State: AODbwcBf/NuwviCvlrDN8RQHtzOsMe95T7xhXpdjDBFk3KRWi4xJBPHD 0GmBQagAPrtr8TGo50pZX/id5tKKCY1D X-Received: by 10.129.106.7 with SMTP id f7mr5683012ywc.84.1494436988132; Wed, 10 May 2017 10:23:08 -0700 (PDT) MIME-Version: 1.0 Received: by 10.129.72.75 with HTTP; Wed, 10 May 2017 10:23:07 -0700 (PDT) In-Reply-To: <20170510114351.GA61453@nat.rebma.instinctive.eu> References: <20170510114351.GA61453@nat.rebma.instinctive.eu> From: Ultima <ultima1252@gmail.com> Date: Wed, 10 May 2017 13:23:07 -0400 Message-ID: <CANJ8om7_+jdCG2tTJTEn-5NVrxjjX4wAMjoBH4=VfBmmWYpKpw@mail.gmail.com> Subject: Re: Ada and GNAT maintainership proposition To: Natasha Kerensikova <natbsd@instinctive.eu> Cc: freebsd-ports@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports>, <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>; List-Post: <mailto:freebsd-ports@freebsd.org> List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>, <mailto:freebsd-ports-request@freebsd.org?subject=subscribe> X-List-Received-Date: Wed, 10 May 2017 17:23:09 -0000 The best way to get started with porting is reading the FreeBSD porters handbook. https://www.freebsd.org/doc/en/books/porters-handbook/ In order to take maintainership, a pr needs to be filled on bugzilla requesting the port. Porting on the most recent -RELEASE version is fine, however It is recommended to test on current as well. I don't think its a huge issue if you can't do this though. if it fails on current you will get fallout messages. It is important to test on all supported releases which can be found here. https://www.freebsd.org/releases/ The testing are needed on tier 1 supported architectures which currently are amd64/i386, of course more is better but not required. The tiers can be found here. https://www.freebsd.org/platforms/ All these tests aren't necessarily required by the port maintainer, but it wont be committed unless they pass these tests. So it is definitely easier and less time consuming for both committer and maintainer if tests are completed. Hope this helps, Ultima On Wed, May 10, 2017 at 7:43 AM, Natasha Kerensikova <natbsd@instinctive.eu> wrote: > Hello, > > I'm an insignificant FreeBSD user and Ada developer, and over the years > I've come to rely a lot of both technologies together. I'm very worried > now that I discovered that Ada-related ports no longer have a maintainer. > Having thought a lot about it in the past day, I don't have a workable > exit strategy for either technology, and I don't want to need one. > > So the whole point of this e-mail is, what happens now? > > > As far as I can tell, if nobody steps up to take over the > maintainership, the ports will eventually be considered dead and be > removed. I think I saw ports stay maintainerless for a long while before > being dropped, but here we have a lively compiler and a moving standard, > so it's likely things will break sooner rather than later. Once a port > is broken, even if it's not reported as broken, its days of > maintainerless existence are numbered. > > So, does anyone care? > > I do, but I mean, besides me? > > Is there anybody ready to step up and take maintainership and ensure > these ports continue to work? > (If there is, don't read the rest of the e-mail, it's moot.) > > > I'm afraid there isn't anybody, and that's why I'm asking here whether I > can be that somebody. > > It would be nice there was some way to make an official distinction > between standard maintainership and maintainership-by-default-because-I- > want-it-to-work-but-I-would-gladly-hand-it-to-anyone-interested. > > The problem is that Marino's shoes are difficult to fill. I'm basically > applying for a position while I have no experience (I only compiled gcc > three times in my life), no relevant skill (except reading C), and > almost no time. The only thing preventing me from being the most > ill-suited person for the role is that I care. Is it enough? > > I'm used to imposter's syndrome, but taking for example the recent thread > https://lists.freebsd.org/pipermail/freebsd-ports/2017-April/108130.html > that's already way beyond my league. > > On top of that, I'm only running recent -RELEASE, I'm not sure I can > find a box on which to run -CURRENT, and I don't hope having some > -STABLE or older -RELEASE available. That limits quite a bit my testing > capabilities. > > I think I can handle the load of being the contact person for these > ports and dealing with the bugtracker and things like that. So if there > is anyone reading this with a bit of technical expertise to help but who > doesn't want to deal with the communication part of the maintainership, > please let me know, so I can volunteer less shakily. > > > So at this point, is there anybody to talk me out of trying to maintain > gcc-aux and some of the Ada ports left behind? > > What is the procedure to ask for maintainership on these? > > I still haven't fully sketched the exact list of package I would try to > claim, but I use daily lang/gcc6-aux, www/aws, devel/florist-gpl, and > devel/gprbuild; I occasionally use devel/adacurses and devel/gnatcoll; > and I could easy integrate into my workflow lang/adacontrol and > lang/asis. I would take some more, going out of my way to test them, but > I'll have to think about which ones are within my reach. The gnatdroid > and gnatcross ones are almost certainly not. > > > Thanks for your patience, > Natasha > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.21.1705101258040.12354>