Menu

#1408 Namespace 104 and 105 on wikisource

closed-fixed
xqt
General (277)
5
2012-02-25
2012-02-17
No

Namespaces 104 and 105 do not exist on the following Wikibooks and should be removed from the family file: gl, sk mk, bg, fo, is, fi, cs, ko, ja, uk, sr, nl, az, el.

Output of version.py:
Pywikipedia trunk/pywikipedia <r9900, 2011/10/30, 15:03:29>
Python 2.7.2 <default, Jun 12 2011, 15:08:59> [MSC v.1500 32 bit <Intel>]
config settings:
use_api = True
use_api_login = True
unicode test: ok

Discussion

  • xqt

    xqt - 2012-02-20
    • assigned_to: nobody --> xqt
    • status: open --> pending-invalid
     
  • xqt

    xqt - 2012-02-20

    Are you really sure? wikibooks has only the following namespace aliases:

    self.namespaces[104] = {
    'az': u'Vikikitab',
    'he': u'מדף',
    'ka': u'თარო',
    'nl': u'Wikijunior',
    'pl': u'Wikijunior',
    'ro': u'Carte de bucate',
    'ru': u'Рецепт',
    }

     
  • Anonymous

    Anonymous - 2012-02-21

    Looks like I got confused between projects. It is supposed to be wikisource. Sorry.

    From the interwiki.log:
    WARNING: Family file wikisource includes namespace['is'][104], but it should be removed (namespace doesn't exist in the site)
    WARNING: Family file wikisource includes namespace['is'][105], but it should be removed (namespace doesn't exist in the site)
    WARNING: Family file wikisource includes namespace['fi'][104], but it should be removed (namespace doesn't exist in the site)
    WARNING: Family file wikisource includes namespace['fi'][105], but it should be removed (namespace doesn't exist in the site)
    ......and so on.

     
  • Anonymous

    Anonymous - 2012-02-21
    • summary: Namespace 104 and 105 on wikibooks --> Namespace 104 and 105 on wikisource
    • status: pending-invalid --> open-invalid
     
  • Anonymous

    Anonymous - 2012-02-22
    • status: open-invalid --> open
     
  • xqt

    xqt - 2012-02-25
    • status: open --> closed-fixed
     
  • xqt

    xqt - 2012-02-25

    done in r9925-9927. Thanks.

     

Log in to post a comment.

MongoDB Logo MongoDB