Updating the pkgdb Free adult syber chat rooms

Fedora Infrastructure is composed of a number of services (koji, fedpkg, pkgdb, etc..) some of which are maintained outside the Fedora Project and some of which were built in-house by the infrastructure team. Think “how an upstream release becomes a package update”, “How a new source distribution becomes a package.” At present, many of the steps in this process require the maintainer to wait and watch for a previous step to complete. At Linux Fest Northwest (2009), jkeating gave a talk on the problem of complexity in the Fedora infrastructure and how this might be addressed with a message bus architecture.For instance once a branch of a package is successfully built in koji, the maintainer must submit their update to bodhi (See the new package process for more details). Each service in the infrastructure depends on many of the others.[2/8] Deleting files for gettext-0.18.3.1_1: 100% [3/8] Installing gettext-runtime-0.19.3...[6/8] Extracting subversion-1.8.11: 100% [7/8] Installing glib-2.42.1...We’ll occasionally send you account related emails. [2/8] Deleting files for gettext-0.18.3.1_1: 100% [3/8] Installing gettext-runtime-0.19.3...

pkg: sqlite error while executing UPDATE deps SET origin=? The following 4 packages will be affected (of 0 checked): New packages to be INSTALLED: glib: 2.42.1 gettext-runtime: 0.19.3 docbook: 1.5 Installed packages to be UPGRADED: subversion: 1.8.9_7 - 1.8.11 The process will require 18 MB more space. The following 8 packages will be affected (of 0 checked): Installed packages to be REMOVED: glib~pkg-renamed~3364-2.36.3_3 New packages to be INSTALLED: gettext-runtime: 0.19.3 gettext-tools: 0.19.3 gettext: 0.19.3 glib: 2.42.1 docbook: 1.5 Installed packages to be UPGRADED: subversion: 1.8.9_7 - 1.8.11 The process will require 11 MB more space. [y/N]: y [1/8] Deinstalling glib~pkg-renamed~3364-2.36.3_3... [1/8] Deleting files for glib~pkg-renamed~3364-2.36.3_3: 100% [2/8] Deinstalling gettext-0.18.3.1_1...

pkg-static: sqlite error while executing UPDATE deps SET origin=? pkg: sqlite error while executing UPDATE deps SET origin=? sqlite Registering installation for glib-2.42.1 Installing glib-2.42.1... 3; in file pkgdb.c:1619: UNIQUE constraint failed: deps.name, deps.version, deps.package_id *** Error code 70 Stop in /usr/ports/devel/glib20. Another variant, as package: [[email protected] /usr]# pkg add glib-2.36.3_2Installing glib-2.36.3_2... 3; in file pkgdb.c:1619: UNIQUE constraint failed: deps.name, deps.version, deps.package_id Failed to install the following 1 package(s): glib-2.36.3_2Query: [[email protected] /usr/ports/devel/glib20]# pkg shell SQLite version 3.8.7 2014-10-17 Enter ".help" for usage hints. [88/321] Upgrading freeglut from 2.8.1 to 2.8.1_3...

pkg-static: sqlite error while executing UPDATE deps SET origin=? pkg: sqlite error while executing UPDATE deps SET origin=? pkg: unlinkat(usr/local/lib/12): No such file or directory pkg: unlinkat(usr/local/share/licenses/freeglut-2.8.1/LICENSE): No such file or directory pkg: unlinkat(usr/local/share/licenses/freeglut-2.8.1/MIT): No such file or directory pkg: unlinkat(usr/local/share/licenses/freeglut-2.8.1/catalog.mk): No such file or directory pkg: unlinkat(usr/local/share/licenses/freeglut-2.8.1/): No such file or directory [88/321] Extracting freeglut-2.8.1_3: 100% [89/321] Reinstalling compositeproto-0.4.2...

pkg: sqlite error while executing UPDATE deps SET origin=?

Not so short investigation left me with an impression that gnome-software is too tightly integrated with GNOME (too many assumptions about the environment) to work in Qubes VM. It seems to me we would resolve a lot of issues by piecewise-replacement of core GNOME software packages (starting with @marmarek With all due respect, I think all GNOME software is too tightly integrated with GNOME to be useful outside that environment.

Search for updating the pkgdb:

updating the pkgdb-46

In your case I'd expect to see two packages (called either 'glib' or 'docbook') -- reducing that to one should solve your problem, but you should make sure that doesn't end up breaking any dependencies. done (0 conflicting) Conflicts with the existing packages have been found.

Leave a Reply

Your email address will not be published. Required fields are marked *

One thought on “updating the pkgdb”