Source: fusionforge-plugin-blocks Version: 5.2.2+20130802-1 Severity: normal
Hi. Trying to install the plugin, on a test machine, I get : Unpacking fusionforge-plugin-blocks (from .../fusionforge-plugin-blocks_5.2.2+20130802-1+fusionforgeint1_all.deb) ... Setting up fusionforge-plugin-blocks (5.2.2+20130802-1+fusionforgeint1) ... You'll see some debugging info during this installation. Do not worry unless told otherwise. Creating plugin_blocks_meta_data table. Inserting first data into plugin_blocks_meta_data table. Processing /usr/share/gforge/plugins/blocks/db/blocks-init.sql DBD::Pg::st execute failed: ERROR: relation "plugin_blocks_pk_seq" already exists at /usr/share/gforge/plugins/blocks/bin/db-upgrade.pl line 61. Transaction aborted because DBD::Pg::st execute failed: ERROR: relation "plugin_blocks_pk_seq" already exists at /usr/share/gforge/plugins/blocks/bin/db-upgrade.pl line 61. Transaction aborted because DBD::Pg::st execute failed: ERROR: relation "plugin_blocks_pk_seq" already exists at /usr/share/gforge/plugins/blocks/bin/db-upgrade.pl line 61. Last SQL query was: CREATE SEQUENCE plugin_blocks_pk_seq START WITH 1 INCREMENT BY 1 MAXVALUE 2147483647 NO MINVALUE CACHE 1; (end of query) My suspicion is that the plugin was installed previously and its removal didn't cleanup everything, which, then blocks a later install. Purging the not configured package doesn't help, if I try a second time. As you can see, this is a modified package rebuild with custom patches, but I guess this applies to stock package too. Hope this helps. Best regards, -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing') Architecture: i386 (i686) Kernel: Linux 3.10-2-686-pae (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
