[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#791678: marked as done (www.debian.org: recover website hit stats (and translations prioritization))

Your message dated Sat, 21 Nov 2015 10:18:41 +0000
with message-id <E1a05Fh-0007AR-SI@moszumanska.debian.org>
and subject line Debian WWW CVS commit by pabs fixes #791678
has caused the Debian Bug report #791678,
regarding www.debian.org: recover website hit stats (and translations prioritization)
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 owner@bugs.debian.org

791678: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791678
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
X-Debbugs-Cc: debian-admin@lists.debian.org
Package: www.debian.org
Severity: normal
Tags: l10n

Dear all

We used to have website hit counts gathered some website mirror, and
they were
used for ordering the webpages with translation pending (pages like this
https://www.debian.org/devel/website/stats/es#untranslated for Spanish), so
translators knew how to prioritize.

These stats were stored in DDE which is dead since some time (a year?

I am interested in getting the website hit stats back again (for translation

Maybe the stats file can be copied to another place instead of DDE?

The file http://anonscm.debian.org/viewvc/webwml/webwml/get-www-stats



# This program is run from a crontab on a Debian website mirror like this:
# MAILTO="porridge@debian.org"
# # Atomically and concurrent-safely create a stats.tgz
# 18 3   *   *   *     cd "$HOME" && d=$(mktemp -d stats-wip-XXXXXXXXXX)
&& printf '{"hostname":"\%s"}' $(hostname -f) > "$d/stats.meta.json" &&
./get-www-stats > "$d/stats.json" && tar zcf stats-wip.tgz "$d" && rm
-rf "$d" && mv stats-wip.tgz stats.tgz
# And the output is transferred to dde.debian.net like this:
# MAILTO="porridge@debian.org"
# # Atomically transfer stats and replace them.
# 18 4   *   *   *     cd $HOME && { [ ! -e stats-old ] ||
please_cleanup_failed_run ; } && cp -al stats-new stats-old && ln -s
stats-old stats-old.s && mv -T stats-old.s stats && { scp -q -i
.ssh/stats-transfer-nopass senfl.debian.org:stats.tgz stats.tgz ||
scp_failed ; } && rm -rf stats-new && mkdir stats-new && tar zxf
stats.tgz -C stats-new --strip-components=1 && rm stats.tgz && ln -s
stats-new stats-new.s && mv -T stats-new.s stats && rm -rf stats-old
# The output is then exported via DDE (see https://wiki.debian.org/DDE)
and used
# by the stattrans.pl script to sort the page lists in the Debian web site
# translation statistics pages.


I'd like to know if somebody from DSA may help with these:

1.- In which mirror is stored that cron job? (or should be stored)
2.- In order to create/modify the cron job, who do I need to talk to?
3.- Where should the cron job copy the stats file to?

After those issues are addressed, I can try to submit a patch against the
website script "stattrans.pl", so it gets
the file from the new location instead from DDE, and generates the
ordered list
of pending translation.

I've considered adopting the DDE service, but it's long time since no other
people use it, and I've encountered problems deploying it, and in the
case of
the website statistics no particular DDE feature was used, we could just
the file in other place and get it from there.

Laura Arjona

--- End Message ---
--- Begin Message ---
This bug was closed by pabs in the webwml CVS repository:


Note that it might take some time until www.debian.org has been updated.

CVSROOT:	/cvs/webwml
Module name:	webwml
Changes by:	pabs	15/11/21 10:18:41

Modified files:
	.              : get-www-stats stattrans.pl 

Log message:
	Fix website hit stats and translation prioritization (Closes: #791678)

--- End Message ---

Reply to: