Bug#497042: mediawiki: populateCategory.php script fails with PostgreSQL
Package: mediawiki Version: 1:1.13.0-1 Severity: grave Justification: renders package unusable Using PostgreSQL 8.3.3 and Mediawiki 1.13. Upgraded from Mediawiki 1.12 to 1.13. Had to execute the populateCategory.php script inside maintenance due to the changes made by upstream in the software, so that new category and categorylinks tables are populated. When doing so, it fails and leaves the pages plenty of corrupted information, displaying tons of links/pages that should not be there. Please note the segmentation fault at the end. The update.php executed before also ended in a segmentation fault error, but seemed to work fine. These are the errors that the script return when executing from the console: php maintenance/populateCategory.php Warning: Invalid argument supplied for foreach() in /usr/share/mediawiki/includes/db/DatabasePostgres.php on line 106 Warning: array_key_exists(): The second argument should be either an array or an object in /usr/share/mediawiki/includes/db/DatabasePostgres.php on line 122 Warning: array_key_exists(): The second argument should be either an array or an object in /usr/share/mediawiki/includes/db/DatabasePostgres.php on line 124 Warning: Invalid argument supplied for foreach() in /usr/share/mediawiki/includes/db/DatabasePostgres.php on line 106 Warning: array_key_exists(): The second argument should be either an array or an object in /usr/share/mediawiki/includes/db/DatabasePostgres.php on line 122 Warning: array_key_exists(): The second argument should be either an array or an object in /usr/share/mediawiki/includes/db/DatabasePostgres.php on line 124 Warning: Invalid argument supplied for foreach() in /usr/share/mediawiki/includes/db/DatabasePostgres.php on line 106 Warning: array_key_exists(): The second argument should be either an array or an object in /usr/share/mediawiki/includes/db/DatabasePostgres.php on line 122 Warning: array_key_exists(): The second argument should be either an array or an object in /usr/share/mediawiki/includes/db/DatabasePostgres.php on line 124 Warning: Invalid argument supplied for foreach() in /usr/share/mediawiki/includes/db/DatabasePostgres.php on line 106 Warning: array_key_exists(): The second argument should be either an array or an object in /usr/share/mediawiki/includes/db/DatabasePostgres.php on line 122 Warning: array_key_exists(): The second argument should be either an array or an object in /usr/share/mediawiki/includes/db/DatabasePostgres.php on line 124 Warning: Invalid argument supplied for foreach() in /usr/share/mediawiki/includes/db/DatabasePostgres.php on line 106 Warning: array_key_exists(): The second argument should be either an array or an object in /usr/share/mediawiki/includes/db/DatabasePostgres.php on line 122 Warning: array_key_exists(): The second argument should be either an array or an object in /usr/share/mediawiki/includes/db/DatabasePostgres.php on line 124 Warning: Invalid argument supplied for foreach() in /usr/share/mediawiki/includes/db/DatabasePostgres.php on line 106 Warning: array_key_exists(): The second argument should be either an array or an object in /usr/share/mediawiki/includes/db/DatabasePostgres.php on line 122 Warning: array_key_exists(): The second argument should be either an array or an object in /usr/share/mediawiki/includes/db/DatabasePostgres.php on line 124 Warning: Invalid argument supplied for foreach() in /usr/share/mediawiki/includes/db/DatabasePostgres.php on line 106 Warning: array_key_exists(): The second argument should be either an array or an object in /usr/share/mediawiki/includes/db/DatabasePostgres.php on line 122 Warning: array_key_exists(): The second argument should be either an array or an object in /usr/share/mediawiki/includes/db/DatabasePostgres.php on line 124 Warning: Invalid argument supplied for foreach() in /usr/share/mediawiki/includes/db/DatabasePostgres.php on line 106 Warning: array_key_exists(): The second argument should be either an array or an object in /usr/share/mediawiki/includes/db/DatabasePostgres.php on line 122 Warning: array_key_exists(): The second argument should be either an array or an object in /usr/share/mediawiki/includes/db/DatabasePostgres.php on line 124 Warning: Invalid argument supplied for foreach() in /usr/share/mediawiki/includes/db/DatabasePostgres.php on line 106 Warning: array_key_exists(): The second argument should be either an array or an object in /usr/share/mediawiki/includes/db/DatabasePostgres.php on line 122 Warning: array_key_exists(): The second argument should be either an array or an object in /usr/share/mediawiki/includes/db/DatabasePostgres.php on line 124 Warning: Invalid argument supplied for foreach() in /usr/share/mediawiki/includes/db/DatabasePostgres.php on line 106 Warning: array_key_exists(): The second argument should be either an array or an object in /usr/share/mediawiki/includes/db/DatabasePostgres.php on line 122 Warning: array_key_exists(): The second argument sh
Bug#366809: firefox-locale-ca: Uninstallable in sid, due to error in versioned dependencies
Package: firefox-locale-ca Version: 1.5.0.3-1 Severity: grave Justification: renders package unusable Dear Debian Developer, The new version of firefox-locale-ca in sid (1.5.0.3-1), cat not be installed, due to an error in the versioned dependence on firefox. It depends on firefox versions: firefox (>= 1.5.0.3) firefox (< 1.5.0.4) (UNAVAILABLE) firefox < 1.5.0.4 is not available due to the firefox versioning scheme in Debian. The available version of firefox in Debian is: 1.5.dfsg+1.5.0.3-2(testing,unstable) (I use the one from backports.org: 1.5.dfsg+1.5.0.3-1bpo1) The dependence should probably be: firefox (>= 1.5.dfsg+1.5.0.3) firefox (< 1.5.dfsg+1.5.0.4) (UNAVAILABLE) Best regards, and thank you for your work Jaume -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (400, 'testing'), (110, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.15-1-686-smp Locale: LANG=C, [EMAIL PROTECTED] (charmap=UTF-8) Versions of packages firefox-locale-ca depends on: ii firefox 1.5.dfsg+1.5.0.3-1bpo1 lightweight web browser based on M -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#306981: rsync: Patch for 306981
2.6.4-2 0 500 ftp://ftp.de.debian.org sarge/main Packages $ find . ./client ./client/a ./client/b ./server ./server/a $ rsync -a -b --delete --delete-after localhost:$PWD/server/ client/ $ find . ./client ./client/a ./client/b~ ./server ./server/a (WORKS: a backup copy "b~" exists) == I also checked that the above tests give the same results when adding --suffix="~2005-05-03" . Hope this helps. Best regards, and thank you for your work, Jaume -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing'), (110, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.11-1-686-smp Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages rsync depends on: ii libc6 2.3.2.ds1-21 GNU C Library: Shared libraries an ii libpopt01.7-5lib for parsing cmdline parameters -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#306981: rsync -b --sufix does not keep a copy of deleted files
Package: rsync
Version: 2.6.4-2
Severity: grave
Justification: causes non-serious data loss
Dear Debian Developers
With (old) rsync 2.6.3-2 I used the following options to syncronize
different computers:
DATA=`date '+%Y-%m-%d'`
RSYNCGET="rsync -abxHzu --progress -v --suffix=.~${DATA} --exclude="*.a"
--exclude="*.o" --exclude="*~*" --exclude="*.exe" --exclude=".nfs*"
--exclude="msg.*" --exclude="lock" --exclude="*\#" --exclude=".\#*"
--exclude="Backup" --exclude="pine-bin.linux" --delete --delete-after -e
ssh "
${RSYNCGET} server:dir dir
This makes a full copy, and leaves a backup copy of every changed and
deleted file in the client, with a name which contains the date
of the transfer.
Since I installed 2.6.4, the same command does not perform the
same:
If a file is deleted in the server, it will be deleted in the client,
WITHOUT leaving a backup copy.
Expected behaviour: a backup copy should be left in the client
I have checked that the same behaviour happens with sid 2.6.4-4.
The files disapear from the client, therefore it causes data loss.
Best regards, and thank you for your work.
Jaume
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (500, 'testing'), (110, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.11-1-686-smp
Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15)
Versions of packages rsync depends on:
ii libc6 2.3.2.ds1-21 GNU C Library: Shared libraries an
ii libpopt01.7-5lib for parsing cmdline parameters
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
