Hello,
I would like to provide translation memories for translators and measure localization progress over Fedora versions (Linux wide). I need to get upstream's content to get translation files such as po/gettext files. To do that, I need to learn how to interact with Fedora packages to reach the SRPM.
The easiest way would probably be to run `dnf list --all` in a virtual machine or container for each Fedora release. An alternative could be to use datagrepper using org.fedoraproject.prod.buildsys.build.state.change? Using this method would allow me to catch new changes, but how do I load previous events or do the first initialization? Is there other ways to get all the SRPM of a Fedora release?
thanks a lot for your help,
I had a discussion on fedora-i18n [0], and Ben Cotton suggested me to ask my question here. I tried to document what I want to do in this wiki page page [1]
[0] https://lists.fedoraproject.org/archives/list/i18n@lists.fedoraproject.org/t... [1] https://fedoraproject.org/wiki/User:Jibecfed/LinuxLocalizationMeasurement
On Mon, 31 Aug 2020 at 22:28, Jean-Baptiste Holcroft jibecfed@fedoraproject.org wrote:
Hello,
I would like to provide translation memories for translators and measure localization progress over Fedora versions (Linux wide). I need to get upstream's content to get translation files such as po/gettext files. To do that, I need to learn how to interact with Fedora packages to reach the SRPM.
The easiest way would probably be to run `dnf list --all` in a virtual machine or container for each Fedora release. An alternative could be to use datagrepper using org.fedoraproject.prod.buildsys.build.state.change? Using this method would allow me to catch new changes, but how do I load previous events or do the first initialization? Is there other ways to get all the SRPM of a Fedora release?
As an alternative approach, you could download https://src.fedoraproject.org/git-seed-latest.tar.xz and keep the git history fresh locally (won't catch the newly added packages though). then pull the needed data from the spec files.
clime
thanks a lot for your help,
I had a discussion on fedora-i18n [0], and Ben Cotton suggested me to ask my question here. I tried to document what I want to do in this wiki page page [1]
[0] https://lists.fedoraproject.org/archives/list/i18n@lists.fedoraproject.org/t... [1] https://fedoraproject.org/wiki/User:Jibecfed/LinuxLocalizationMeasurement _______________________________________________ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro...
Dne 31. 08. 20 v 22:50 clime napsal(a):
On Mon, 31 Aug 2020 at 22:28, Jean-Baptiste Holcroft jibecfed@fedoraproject.org wrote:
Hello,
I would like to provide translation memories for translators and measure localization progress over Fedora versions (Linux wide). I need to get upstream's content to get translation files such as po/gettext files. To do that, I need to learn how to interact with Fedora packages to reach the SRPM.
The easiest way would probably be to run `dnf list --all` in a virtual machine or container for each Fedora release. An alternative could be to use datagrepper using org.fedoraproject.prod.buildsys.build.state.change? Using this method would allow me to catch new changes, but how do I load previous events or do the first initialization? Is there other ways to get all the SRPM of a Fedora release?
As an alternative approach, you could download https://src.fedoraproject.org/git-seed-latest.tar.xz
You have meant https://src.fedoraproject.org/repo/git-seed-latest.tar.xz I guess.
Vít
and keep the git history fresh locally (won't catch the newly added packages though). then pull the needed data from the spec files.
clime
thanks a lot for your help,
I had a discussion on fedora-i18n [0], and Ben Cotton suggested me to ask my question here. I tried to document what I want to do in this wiki page page [1]
[0] https://lists.fedoraproject.org/archives/list/i18n@lists.fedoraproject.org/t... [1] https://fedoraproject.org/wiki/User:Jibecfed/LinuxLocalizationMeasurement _______________________________________________ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro...
infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro...
On Tue, 1 Sep 2020 at 09:33, Vít Ondruch vondruch@redhat.com wrote:
Dne 31. 08. 20 v 22:50 clime napsal(a):
On Mon, 31 Aug 2020 at 22:28, Jean-Baptiste Holcroft jibecfed@fedoraproject.org wrote:
Hello,
I would like to provide translation memories for translators and measure localization progress over Fedora versions (Linux wide). I need to get upstream's content to get translation files such as po/gettext files. To do that, I need to learn how to interact with Fedora packages to reach the SRPM.
The easiest way would probably be to run `dnf list --all` in a virtual machine or container for each Fedora release. An alternative could be to use datagrepper using org.fedoraproject.prod.buildsys.build.state.change? Using this method would allow me to catch new changes, but how do I load previous events or do the first initialization? Is there other ways to get all the SRPM of a Fedora release?
As an alternative approach, you could download https://src.fedoraproject.org/git-seed-latest.tar.xz
You have meant https://src.fedoraproject.org/repo/git-seed-latest.tar.xz I guess.
Yes, thanks.
Vít
and keep the git history fresh locally (won't catch the newly added packages though). then pull the needed data from the spec files.
clime
thanks a lot for your help,
I had a discussion on fedora-i18n [0], and Ben Cotton suggested me to ask my question here. I tried to document what I want to do in this wiki page page [1]
[0] https://lists.fedoraproject.org/archives/list/i18n@lists.fedoraproject.org/t... [1] https://fedoraproject.org/wiki/User:Jibecfed/LinuxLocalizationMeasurement _______________________________________________ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro...
infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro...
infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro...
On Tue, Sep 01, 2020 at 09:41:01AM +0200, clime wrote:
On Tue, 1 Sep 2020 at 09:33, Vít Ondruch vondruch@redhat.com wrote:
Dne 31. 08. 20 v 22:50 clime napsal(a):
On Mon, 31 Aug 2020 at 22:28, Jean-Baptiste Holcroft jibecfed@fedoraproject.org wrote:
Hello,
I would like to provide translation memories for translators and measure localization progress over Fedora versions (Linux wide). I need to get upstream's content to get translation files such as po/gettext files. To do that, I need to learn how to interact with Fedora packages to reach the SRPM.
The easiest way would probably be to run `dnf list --all` in a virtual machine or container for each Fedora release. An alternative could be to use datagrepper using org.fedoraproject.prod.buildsys.build.state.change? Using this method would allow me to catch new changes, but how do I load previous events or do the first initialization? Is there other ways to get all the SRPM of a Fedora release?
As an alternative approach, you could download https://src.fedoraproject.org/git-seed-latest.tar.xz
You have meant https://src.fedoraproject.org/repo/git-seed-latest.tar.xz I guess.
Yes, thanks.
For that you will then have to 'fedpkg srpm' in each packages git dir to make a src.rpm.
All the src.rpms are shipped on mirrors...
https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything...
for rawhide that changes usually daily.
For releases you could do the base repo + updates repo as it changes?
https://dl.fedoraproject.org/pub/fedora/linux/releases/32/Everything/source/...
Does that help any?
kevin
infrastructure@lists.fedoraproject.org