Your message dated Fri, 17 Nov 2017 18:47:00 -0800
with message-id <[email protected]>
and subject line Re: Bug#842681: mediawiki: upgraded wiki (from squeeze) fails 
due to missing PSR-3
has caused the Debian Bug report #842681,
regarding mediawiki: upgraded wiki (from squeeze) fails due to missing PSR-3
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.)


-- 
842681: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842681
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mediawiki
Version: 1:1.27.1-2~bpo8+1
Severity: normal

Hi, I've just upgraded the Debian package from the oldstable version to the
backports version (upgrade mediawiki:all 1:1.19.20+dfsg-2.3 1:1.27.1-2~bpo8+1)

After doing so, our wiki says the following

> MediaWiki requires the PSR-3 logging library to be present. This library is
> not embedded directly in MediaWiki's git repository and must be installed
> separately by the end user. Please see mediawiki.org for help on installing
> the required components.

There is no mention of this PSR-3 library in UPGRADING.gz and no obvious match
for it when searching the Debian package archives.

--- End Message ---
--- Begin Message ---

On Tue, 18 Jul 2017 19:49:14 +0900
=?UTF-8?Q?Marc_Dequ=C3=A8nes_=28duck=29?= <[email protected]> wrote:
> Quack,
> 
> When upgrading to Stretch I saw the same message.
> 
> Kunal, what you're suggesting is fine for a single website, not for 
> multiple instance. Unlike a package like Redmine I don't see any 
> multi-site support in your package. But honestly this is pretty easy to 
> do, so I don't think it is needed.

I run multiple instances of MediaWiki by altering the database and paths
used for the wiki based on the hostname in LocalSettings.php, instead of
setting up extra symlinks. But your approach works fine as well.

> After updating the symlinks after upgrade I don't this error message 
> anymore.

Yep, the cause is most likely just a missing vendor/ symlink. Closing as
that should work.

Jonathan, feel free to email me with more details about your file layout
if you still can't get this to work, I'm happy to help you out.

-- Kunal

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---

Reply via email to