Date: Mon, 5 Aug 2013 12:59:19 -0700 (PDT) From: Jeffrey Bouquet <jeffreybouquet@yahoo.com> To: ports list <freebsd-ports@freebsd.org> Subject: Re: libpkg, sqlite and database problems prevent building any packages Message-ID: <1375732759.58715.YahooMailNeo@web164001.mail.gq1.yahoo.com> In-Reply-To: <322389.43675.bm@smtp105.sbc.mail.ne1.yahoo.com> References: <322389.43675.bm@smtp105.sbc.mail.ne1.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Bottom posting below; will reply in better format when/if I get another web= mail client maybe... the=0A=0Atext is below the next occurance of "bottom p= osting"=0A=0A=0A=0A________________________________=0A From: Thomas Mueller= <mueller6724@bellsouth.net>=0ATo: freebsd-ports@freebsd.org =0ASent: Monda= y, August 5, 2013 8:36 AM=0ASubject: Re: libpkg, sqlite and database proble= ms prevent building any packages=0A =0A=0AOn 05/08/2013 14:30, Thomas Muell= er wrote:=0A> I could see my pkg client is out of date, but how do I update= it?=0A>=0A> Attempts to update all gave me those error messages.=A0 Instal= lation fails.=0A=0AMatthew Seaman responded:=0A=0A> Your package database h= as got into an inconsistent state.=A0 pkg(8) is=0A> attempting to auto-upda= te the schema to the latest version, but failing=0A> because it's trying to= remove an 'infos' column from a table where that=0A> column has apparently= already been removed.=A0 (Likely this situation has=0A> come about because= pkg got killed in the middle of doing this update=0A> previously.)=0A=0A> = How happy are you to get down'n'dirty with the source code and running=0A> = SQL from the command line?=A0 If you look at the updates pkg is attempting= =0A> to run shown here:=0A=0A>=A0 =A0 https://github.com/freebsd/pkg/blob/m= aster/libpkg/private/db_upgrades.h=0A=0A> would you be capable of looking a= t the DB schema, working out which of=0A> those updates had been applied, a= plying any outstanding ones by hand and=0A> then setting the user version t= o 19 by:=0A=0A>=A0 =A0 sql> PRAGMA user_version =3D 19 ;=0A=0A?=0A=0A> If n= ot, check in /var/backups for a good copy of your local.sqlite=0A> database= and try and restore from there.=A0 Unfortunately, there's no=0A> guarantee= that any backup copy doesn't have the same inconsistencies as=0A> your liv= e copy.=0A=0A> We need to make pkg(8) databases more resilient to the effec= ts of SIGHUP=0A> or similar while they are elbows-deep in the bowels of the= DB schema...=0A=0ATrying to do what you suggest would in all likelihood be= an exercise in futility, especially when I am very tired from being unable= to sleep.=0A=0AI didn't realize pkgng was so non-sturdy.=0A=0AI wonder wha= t would happen if I delete /var/db/pkg/local.sqlite, or perhaps better, mov= e it to another location and name so as not to burn my bridges.=0A=0ABut an= ything so I can upgrade pkg.=0A=0ADoes pkgng have no means of recovery?=A0 = Can pkg regenerate a database, and from what?=0A=0AMy /var/backups on the U= SB-stick 9.2-BETA2 amd64 installation shows=0A=0A=0Atotal 280=0A-rw-r--r--= =A0 1 root=A0 wheel=A0 =A0 1674 Apr=A0 2=A0 2012 aliases.bak=0A-rw-r--r--= =A0 1 root=A0 wheel=A0 =A0 436 Apr=A0 2=A0 2012 group.bak=0A-rw-------=A0 = 1 root=A0 wheel=A0 =A0 1500 Apr=A0 2=A0 2012 master.passwd.bak=0A-rw-r--r--= =A0 1 root=A0 wheel=A0 269144 Dec 13=A0 2012 pkgdb.bak.tbz=0A-rw-r--r--=A0 = 1 root=A0 wheel=A0 =A0 129 Jul 16=A0 2012 pkgdb.bak.tbz.2=0A=0A=0Apkg.bak.= tbz looks like the database from the old format.=0A=0AMy /var/backups on th= e USB-stick 9.1-STABLE i386 installation shows=0A=0A=0Atotal 140=0A-rw-r--r= --=A0 1 root=A0 wheel=A0 =A0 1688 Jan 20=A0 2013 aliases.bak=0A-rw-r--r--= =A0 1 root=A0 wheel=A0 =A0 1674 Jun=A0 6=A0 2012 aliases.bak2=0A-rw-r--r--= =A0 1 root=A0 wheel=A0 =A0 481 Jan 17=A0 2013 group.bak=0A-rw-r--r--=A0 1 = root=A0 wheel=A0 =A0 449 Jul 13=A0 2012 group.bak2=0A-rw-------=A0 1 root= =A0 wheel=A0 =A0 1761 Jan 17=A0 2013 master.passwd.bak=0A-rw-------=A0 1 ro= ot=A0 wheel=A0 =A0 1500 Jun=A0 6=A0 2012 master.passwd.bak2=0A>-rw-r--r--= =A0 1 root=A0 wheel=A0 =A0 8524 May 28 03:01 pkgdb.bak.tbz=0A>-rw-r--r--=A0= 1 root=A0 wheel=A0 =A0 130 Jan 19=A0 2013 pkgdb.bak.tbz.2=0A>-rw-r--r--= =A0 1 root=A0 wheel=A0 100352 May 28 04:29 pkgng.db=0A=0A=0A>pkgng.db looks= like the new format, but that was before I built wine and dependencies.=0A= =0A......................................................=0A...............= .......................................=0ABottom posting...=A0=0A=0ANon-stu= rdy? , but this sort of showstopper is what IMHO =0Ashould necessite a huge= problem-resolving flowchart, =0Abefore pkg(ng) =A0fully obsoletes its lega= cy=0Aalternative... not to mention the possibility of =0Apkg(ng) not having= enough memory, =0Aon some installs where before /var/db/pkg would have eno= ugh.=0AJust a 2c. =A0 =A0As in, if I *have to* migrate to pkg/, I need some= thing from which to=0Acopy the succint parts to a few post-its on the monit= or... =A0(think HUGE...FLOWCHART...)=A0=0A=0AThanks.=A0=0A=0A=0A___________= ____________________________________=0Afreebsd-ports@freebsd.org mailing li= st=0Ahttp://lists.freebsd.org/mailman/listinfo/freebsd-ports=0ATo unsubscri= be, send any mail to "freebsd-ports-unsubscribe@freebsd.org" From owner-freebsd-ports@FreeBSD.ORG Mon Aug 5 20:04:24 2013 Return-Path: <owner-freebsd-ports@FreeBSD.ORG> Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 47B0C430 for <freebsd-ports@freebsd.org>; Mon, 5 Aug 2013 20:04:24 +0000 (UTC) (envelope-from naylor.b.david@gmail.com) Received: from mail-we0-x232.google.com (mail-we0-x232.google.com [IPv6:2a00:1450:400c:c03::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CD827247E for <freebsd-ports@freebsd.org>; Mon, 5 Aug 2013 20:04:23 +0000 (UTC) Received: by mail-we0-f178.google.com with SMTP id u57so2804501wes.23 for <freebsd-ports@freebsd.org>; Mon, 05 Aug 2013 13:04:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:date:message-id:user-agent:in-reply-to :references:mime-version:content-type:content-transfer-encoding; bh=cPZ7X31lcBfYwlYJa1vwa5ZC0SH25O9x68iWUyE1CAM=; b=FhRDNt4DGUgoseBHyM1d+JkDaFPzsuboe857TEEK97AjLH46hhl3EZha5mIhwcUbe6 Rh4eF67nztk+qshTIlnCLeKWLHuyLF0x0IgoHN65dbBiXrp9WPnAL2qmZ5IK3Y5XoOBz M6ZX4qJDoiQ7E1p2appCoaA1WHwgPmgGAdiLoRregIQsyHwLWB48/bKK8rOa7Hpf0027 tfd9pVpW3m4YZQfoDL3Fet1hxYO4pBQaIOsLIXqnUGLgPcH1i3qGFi7UespdUPWToMZi VNQsqFhmyJdCVFmOMrIp5lXfnV2G0oXaHZnbeX6gMZH0sM4oh7cZMc9Ou+8GOUzjgO9A cEyQ== X-Received: by 10.180.212.112 with SMTP id nj16mr7912875wic.31.1375733062177; Mon, 05 Aug 2013 13:04:22 -0700 (PDT) Received: from dragon.dg ([197.87.211.201]) by mx.google.com with ESMTPSA id nb12sm1073562wic.7.2013.08.05.13.04.17 for <multiple recipients> (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 05 Aug 2013 13:04:21 -0700 (PDT) From: David Naylor <naylor.b.david@gmail.com> To: "Sam Fourman Jr." <sfourman@gmail.com> Subject: Re: [REVIEW] Completing i386-wine Date: Mon, 05 Aug 2013 22:04:05 +0300 Message-ID: <2203305.4G4tg7geX1@dragon.dg> User-Agent: KMail/4.9.5 (FreeBSD/9.1-RELEASE; KDE/4.9.5; amd64; ; ) In-Reply-To: <CAOFF+Z0Wrd825DtVj3CVnO=T6HWDR2xWabgpQVyUq38Nc_y1EA@mail.gmail.com> References: <638991.76970.bm@smtp107.sbc.mail.bf1.yahoo.com> <CAOFF+Z0Wrd825DtVj3CVnO=T6HWDR2xWabgpQVyUq38Nc_y1EA@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2394712.3t5NgvUoLa"; micalg="pgp-sha1"; protocol="application/pgp-signature" Content-Transfer-Encoding: 7Bit Cc: Thomas Mueller <mueller6724@bellsouth.net>, freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 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: Mon, 05 Aug 2013 20:04:24 -0000 --nextPart2394712.3t5NgvUoLa Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="ISO-8859-1" On Monday, 5 August 2013 02:31:54 Sam Fourman Jr. wrote: > Would there also be the possibility to have i386-wine as a source-code > > > port, and build from i386 installation? That avoids cross-compiling. > > > > One could build an i386 installation either from amd64 or previous i386 > > installation, then build i386-wine and other desired ports when booted > > into > > the i386 installation. > > > > This i386 installation would be on another partition or another disk (USB > > 3.0 stick or USB 3.0 hard-drive partition?), and from the amd64 > > installation, the i386 installation could be mounted on /compat/i386. > > > > With a USB hard drive, if not directly bootable, the loader and kernel > > could be copied to another boot disk/partition, and root could be set for > > the USB hard-drive partition. My USB 3.0 hard drive, Western Digital My > > Book Essential, is not recognized by the BIOS/UEFI or GRUB2, but is > > accessible from Linux or FreeBSD. > > > > Tom-- > > Can't we just have the port build wine in a i386 jail? eg it would require > the FreeBSD sources, build the jail... etc.. it seems like a LOT, but > honestly whats wrong with it... ill do the testing Hi Sam / Thomas Well, when compiling on i386 the port is "source based". I am reluctant to bring in the i386 environment bootstrapping logic within the port (especially given there are so many different ways - and personal preferences - on how to do it). I also think it is not appropriate, in my opinion, for a port to do so much. Given that nothing stops an individual from setting up such an environment manually (such as how I do it to create the packages) I think the port offers enough functionality as is. I hope this clarifies my position on this, and thank you for your feedback :-) --nextPart2394712.3t5NgvUoLa Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEABECAAYFAlIABTcACgkQUaaFgP9pFrI4OwCdELz44IoqQsnbcKiM/czI4faV MusAni0a7bNXUKgVwvdoFq8hg24o+ZWY =Rn78 -----END PGP SIGNATURE----- --nextPart2394712.3t5NgvUoLa--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1375732759.58715.YahooMailNeo>