Package: google-sitemapgen
Version: 1.5-3
Severity: important

Dear Maintainer,

   * What led up to the situation?

The latest version of google-sitemapgen produces a sitemap index 
(for very large sites) starting with <urlset> rather than <sitemapindex>

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

Install a new version

   * What was the outcome of this action?

Google no longer understands the site map and ignores it.
As this render the package broken and this is its sole functionality
I'm marking it as important, but this will only affect sites with
more than 50,000 pages.

   * What outcome did you expect instead?

Working as before. There is a patch in SourceForge:

https://sourceforge.net/p/goog-sitemapgen/bugs/12/

that patch is somewhat applied (because the double _ is not
an issue), but the SITEMAP -> SITEINDEX bit is necessary


-- System Information:
Debian Release: 8.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages google-sitemapgen depends on:
ii  python  2.7.9-1

google-sitemapgen recommends no packages.

google-sitemapgen suggests no packages.

-- no debconf information

Reply via email to