Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1707342 - kdesvn-2.0.95 snapshot missing translations
Summary: kdesvn-2.0.95 snapshot missing translations
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kdesvn
Version: 29
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Vasiliy Glazov
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-07 10:47 UTC by Kevin Kofler
Modified: 2019-05-22 11:31 UTC (History)
2 users (show)

Fixed In Version: kdesvn-2.0.95-2.fc30 kdesvn-2.0.95-2.fc29
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-22 01:39:29 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Kevin Kofler 2019-05-07 10:47:50 UTC
Description of problem:
The packaged kdesvn snapshot is not translated.

Version-Release number of selected component (if applicable):
kdesvn-2.0.95-1.fc29

How reproducible:
Always

Steps to Reproduce:
1. Start kdesvn.

Actual results:
Almost everything is in English, only global Qt/KF5 translations are applied.

Expected results:
The application is translated.

Additional info:
When packaging snapshots from git.kde.org, it is NOT enough to take a regular git snapshot, you must instead use the upstream releaseme tool that grabs the translations from the translators' SVN repository.

Comment 1 Vasiliy Glazov 2019-05-07 10:54:47 UTC
Can you help me with this tool?

Comment 2 Vasiliy Glazov 2019-05-13 06:49:10 UTC
Spec must contain link to source tarball. I must not download translations or build tarball during package building.

Comment 3 Kevin Kofler 2019-05-13 09:08:55 UTC
Of course you don't download the source DURING the package building!

The way it is done is that you clone git://anongit.kde.org/releaseme.git or https://anongit.kde.org/releaseme.git locally, run tarme.rb (which will generate a tarball):
./tarme.rb --version 2.0.95 --origin trunk kdesvn
and then upload that tarball and use it as Source0.

Instead of a link, you put just the file name as Source0, and above it, you add a comment how you generated it:

# git clone https://anongit.kde.org/releaseme.git
# cd releaseme
# ./tarme.rb --version 2.0.95 --origin trunk kdesvn
Source0: kdesvn-2.0.95.tar.xz

This is compliant to the guidelines as per: https://docs.fedoraproject.org/en-US/packaging-guidelines/SourceURL/#_using_revision_control

Comment 4 Kevin Kofler 2019-05-13 09:10:35 UTC
Oops, this probably needs to be:
./tarme.rb --version 2.0.95 --origin master kdesvn
(We need the origin of the code, which is in git and uses master, not trunk, as the branch name. The translations are in SVN, but those are located automatically using the metadata from https://phabricator.kde.org/source/sysadmin-repo-metadata/browse/master/projects/extragear/sdk/kdesvn/ .)

I hope this helps.

Comment 5 Vasiliy Glazov 2019-05-13 09:26:52 UTC
It can't access to data:

$ LANG=C ./tarme.rb --version 2.0.95 --origin trunk kdesvn
Logging colors are not available. Install logger-colors gem if desired
INFO -- ReleaseMe::Release: Getting CI states.
INFO -- ReleaseMe::Release: Getting source (git - git.org:kdesvn [master])
Traceback (most recent call last):
        6: from ./tarme.rb:85:in `<main>'
        5: from ./tarme.rb:85:in `collect'
        4: from ./tarme.rb:93:in `block in <main>'
        3: from /home/vascom/releaseme/lib/releaseme/release.rb:88:in `get'
        2: from /home/vascom/releaseme/lib/releaseme/source.rb:45:in `get'
        1: from /home/vascom/releaseme/lib/releaseme/git.rb:51:in `get'
/home/vascom/releaseme/lib/releaseme/git.rb:83:in `run': Cloning into 'kdesvn-2.0.95'... (ReleaseMe::Git::CloneError)
git.org: Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
        7: from ./tarme.rb:85:in `<main>'
        6: from ./tarme.rb:85:in `collect'
        5: from ./tarme.rb:93:in `block in <main>'
        4: from /home/vascom/releaseme/lib/releaseme/release.rb:88:in `get'
        3: from /home/vascom/releaseme/lib/releaseme/source.rb:39:in `get'
        2: from /home/vascom/releaseme/lib/releaseme/source.rb:47:in `rescue in get'
        1: from /home/vascom/releaseme/lib/releaseme/git.rb:51:in `get'
/home/vascom/releaseme/lib/releaseme/git.rb:83:in `run': Cloning into 'kdesvn-2.0.95'... (ReleaseMe::Git::CloneError)
git.org: Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Comment 6 Vasiliy Glazov 2019-05-13 09:27:12 UTC
$ LANG=C ./tarme.rb --version 2.0.95 --origin master kdesvn
Logging colors are not available. Install logger-colors gem if desired
Traceback (most recent call last):
./tarme.rb:53:in `<main>': invalid argument: --origin master (OptionParser::InvalidArgument)

Comment 7 Kevin Kofler 2019-05-13 09:42:32 UTC
It has been a while since I last used releaseme, and some things have changed (in particular, https://phabricator.kde.org/source/sysadmin-repo-metadata/ is new, the information used to be part of releaseme itself).

Looking through the code (in particular https://cgit.kde.org/releaseme.git/tree/lib/releaseme/origin.rb ), "-origin trunk" seems to be the correct option.

There used to be some flag to force releaseme to use anongit instead of authenticated git (which needs a KDE developer account) to clone the sources, I am looking for the way to do it now that everything changed.

Comment 8 Kevin Kofler 2019-05-13 09:48:52 UTC
Try:
RELEASEME_READONLY=1 ./tarme.rb --version 2.0.95 --origin trunk kdesvn

Comment 10 Vasiliy Glazov 2019-05-13 11:09:08 UTC
Thanks.

Comment 11 Fedora Update System 2019-05-13 11:36:49 UTC
kdesvn-2.0.95-2.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-5d910b79a6

Comment 12 Fedora Update System 2019-05-13 11:36:53 UTC
kdesvn-2.0.95-2.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-c80d57bd2c

Comment 13 Fedora Update System 2019-05-14 01:53:37 UTC
kdesvn-2.0.95-2.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-c80d57bd2c

Comment 14 Fedora Update System 2019-05-14 04:26:03 UTC
kdesvn-2.0.95-2.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-5d910b79a6

Comment 15 Fedora Update System 2019-05-22 01:39:29 UTC
kdesvn-2.0.95-2.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.

Comment 16 Fedora Update System 2019-05-22 11:31:13 UTC
kdesvn-2.0.95-2.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.