Your message dated Sat, 29 Sep 2012 17:15:43 +0000 (UTC) with message-id <[email protected]> and subject line closing bugs against mw-extensions that are fixed in sid has caused the Debian Bug report #687641, regarding mediawiki-extensions-base: Fatal error: Call to a member function isContentPage() on a non-object to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 687641: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687641 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: mediawiki-extensions-base Version: 2.6+wheezy1 Severity: important Dear Maintainer, When I went from stable (squeeze) to testing (wheezy) my mediawiki wiki stopped showing its content. Nowadays, when I turn on the option to show error messages, I see the following messages: Notice: Undefined property: SkinMonoBook::$mTitle in /usr/share/mediawiki-extensions/base/Cite/SpecialCite.php on line 39 Fatal error: Call to a member function isContentPage() on a non-object in /usr/share/mediawiki-extensions/base/Cite/SpecialCite.php on line 39 Cheers, Anye Li -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash mediawiki-extensions-base depends on no packages. Versions of packages mediawiki-extensions-base recommends: ii mediawiki 1:1.19.1-1 mediawiki-extensions-base suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---fixed 687641 2.7 fixed 686190 2.7 thanks Adam D. Barratt dixit: >Please don't do that. Everyone's unblock request is important to them, >and many of them also fix RC bugs. unblock bugs are "normal" at most, >unless the release team choose to make them otherwise. Okay, sorry. >If the bug is fixed in 2.8, surely the correct method of indicating that >would be to close it with an appropriate fixed version? Hm okay. It was almost certainly fixed with 2.7 already, so I’m using that as fixed version (the bugs stem from an incompatibility between core and extensions versions). bye, //mirabilos -- “It is inappropriate to require that a time represented as seconds since the Epoch precisely represent the number of seconds between the referenced time and the Epoch.” -- IEEE Std 1003.1b-1993 (POSIX) Section B.2.2.2
--- End Message ---
