Date: Fri, 10 Jan 2020 07:15:02 +0000 From: bugzilla-noreply@freebsd.org To: pkg@FreeBSD.org Subject: [Bug 232350] periodic: pkg-checksum and pkg-backup interfere with 'overnight' port builds Message-ID: <bug-232350-32340-At1RT0Ca6M@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-232350-32340@https.bugs.freebsd.org/bugzilla/> References: <bug-232350-32340@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D232350 --- Comment #29 from Tatsuki Makino <tatsuki_makino@hotmail.com> --- (In reply to Matthew Seaman from comment #28) Thank you for answering my sqlite3 questions. However, I don't think the pkg_lock table is for pkg-lock. I have locked seamonkey-2.49.4_27, but when I run sqlite3 /var/db/pkg/local.sqlite .dump , I only get the following: CREATE TABLE pkg_lock (exclusive INTEGER(1),advisory INTEGER(1),read INTEGER(8)); INSERT INTO pkg_lock VALUES(0,0,0); And there is a column for the locked flag in the packages table. CREATE TABLE packages (id INTEGER PRIMARY KEY,origin TEXT NOT NULL,name TEXT NOT NULL,version TEXT NOT NULL,comment TEXT NOT NULL,desc TEXT NOT NULL,mtree_id INTEGER REFERENCES mtree(id) ON DELETE RESTRICT ON UPDATE CASCADE,message TEXT,arch TEXT NOT NULL,maintainer TEXT NOT NULL, www TEXT,prefix TEXT NOT NULL,flatsize INTEGER NOT NULL,automatic INTEGER NOT NULL,locked INTEGER NOT NULL DEFAULT 0, ...Omitted The column names in the pkg_lock table seem to allow simultaneous invocatio= n... --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-232350-32340-At1RT0Ca6M>