Date: Fri, 14 Feb 2014 06:07:50 -0800 (PST) From: Beeblebrox <zaphod@berentweb.com> To: freebsd-ports@freebsd.org Subject: Re: pkg upgrade breaks with mariadb migration Message-ID: <CAPSTsku-qubBW=UBW4TdjyTiRAcFsf%2BgTd5pVadY1P7th52fMg@mail.gmail.com> In-Reply-To: <1392385403.3697.83408689.3FA59E62@webmail.messagingengine.com> References: <1392315760107-5885723.post@n5.nabble.com> <1392319784.9544.83106817.53DEC381@webmail.messagingengine.com> <1392381083669-5885945.post@n5.nabble.com> <1392385403.3697.83408689.3FA59E62@webmail.messagingengine.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Although I suspect you could have a different problem. Are you mixing FreeBSD and your private repository? No. When I upgrade, I specify the repo: # pkg upgrade -r myrepo On the other hand, I'm merging gnome3 from the marcuscom-devel repo. It's possible those ports may have some hard-coded "mysql" reference in them... ----- FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS -- View this message in context: http://freebsd.1045724.n5.nabble.com/pkg-upgrade-breaks-with-mariadb-migration-tp5885723p5885967.html Sent from the freebsd-ports mailing list archive at Nabble.com. From owner-freebsd-ports@FreeBSD.ORG Fri Feb 14 14:17:46 2014 Return-Path: <owner-freebsd-ports@FreeBSD.ORG> Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CB6A4544 for <freebsd-ports@freebsd.org>; Fri, 14 Feb 2014 14:17:46 +0000 (UTC) Received: from mail-qc0-x22f.google.com (mail-qc0-x22f.google.com [IPv6:2607:f8b0:400d:c01::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 87FFF1B8F for <freebsd-ports@freebsd.org>; Fri, 14 Feb 2014 14:17:46 +0000 (UTC) Received: by mail-qc0-f175.google.com with SMTP id x13so20251240qcv.34 for <freebsd-ports@freebsd.org>; Fri, 14 Feb 2014 06:17:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=eWBPAFeMIIR07KUhcbaJj3E/r7R0gt8Qqwhzuv4nmbU=; b=yWo20bLHP9KYjrWlV3s9ZPz+PLW7SFWuvkrqZCVXgiduyNsUjiy6oJ7m7wBXk/q/AB tu8YLnQSLDXCz2m7FnmcnOQTpDnjy4cgnTgbArlITrA9rbFyBf+Btl0HLoYHTXeCsida +gwpRII8O7tfbB6c63psX16zmavpMBiwF6tIuJrI/wsH0FBXQP35chEws9OPZALh8aRo nlhRjnJeIEJWe0kL1ObHfo2Z2czlvfwAvBNgFrJAikNKWdcbL4iUBifZANtu7GYhTGR1 5aIMUXCxkS7mJq9TCcoHxlQ8M3PAxuCdnMXbEyATbRXd5PwPEC91pDqwpNy57TSxNaDr Dswg== X-Received: by 10.140.101.104 with SMTP id t95mr12573055qge.106.1392387465528; Fri, 14 Feb 2014 06:17:45 -0800 (PST) MIME-Version: 1.0 Received: by 10.229.241.198 with HTTP; Fri, 14 Feb 2014 06:17:25 -0800 (PST) In-Reply-To: <20140214135856.GB68773@shell.bebik.local> References: <CALSf6fQrMNXPcc+xFCs11nf6h5Zmh74KfWp-3icERcmdPQGc1w@mail.gmail.com> <20140214135856.GB68773@shell.bebik.local> From: "B. Estrade" <estrabd@gmail.com> Date: Fri, 14 Feb 2014 08:17:25 -0600 Message-ID: <CALSf6fSNWyEp5pLcMq2RansWre38KV4Xyc+nPQ_CVvmAF2OH9Q@mail.gmail.com> Subject: Re: Help with getting movement on "anomalous" port To: Rodrigo Osorio <rodrigo@bebik.net> Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org> List-Unsubscribe: <http://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: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>, <mailto:freebsd-ports-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 14 Feb 2014 14:17:46 -0000 Thank you. I have this information in the pkg-descr file, but I am happy to add it to the PR. It's a basic fork of litecoin (already in there) and very similar to the ever growing collection of crypto currency clients in net-p2p. https://www.feathercoin.com/ Brett On Fri, Feb 14, 2014 at 7:58 AM, Rodrigo Osorio <rodrigo@bebik.net> wrote: > > Hi, > > Thanks for your submition. > > Adding a little comment about what this port does (now I know is a bitcoin > stuff), > and why is it needed in the freebsd ports system usually helps a lot. > > Regards > - rodrigo > > > On 14/02/14 07:41 -0600, B. Estrade wrote: > > A couple of weeks ago I submitted a new port for net-p2p/feathercoin. > > Shortly thereafter, it was marked as miscategorized so I resubmitted > > thinking that this was the proper course of action. > > > > (at the bottom of: http://portsmon.freebsd.org/portsanomalies.py) > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=186324 > > http://www.freebsd.org/cgi/query-pr.cgi?pr=186493 > > > > It now seems that they are stuck in the queue since I have had another > port > > maintainer-update (lang/qore) go through without any problems. > > > > Please advise on the best way to make progress on this, either through > > fixing something missing in the new port or getting it pushed through. > > > > Thank you! > > Brett > > _______________________________________________ > > freebsd-ports@freebsd.org mailing list > > http://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?CAPSTsku-qubBW=UBW4TdjyTiRAcFsf%2BgTd5pVadY1P7th52fMg>