> MANY projects have not updated .po files (look on
> https://github.com/mesonbuild/meson/issues/11338)
Yes, and we don't believe you should be running update-po either.
--
Reply to this email directly or view it on GitHub:
Closed #2817 as completed.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2817#event-11508091602
You are receiving this because you are subscribed to this thread.
Message ID:
___
Rpm-maint
> MANY projects have not updated .po files
I fail to see any relevance to rpm.
In any case, this is supposedly fixed in
b4dc72f4b92489f77de9b0ae0bed754875d37ece.
--
Reply to this email directly or view it on GitHub:
> Well yes, it's not something you're expected to run on a release tarball. So
> this is really going in circles, again.
MANY projects have not updated .po files (look on
https://github.com/mesonbuild/meson/issues/11338)
--
Reply to this email directly or view it on GitHub:
Well yes, it's not something you're expected to run on a release tarball. So
this is really going in circles, again.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2817#issuecomment-1862283412
You are receiving this because you are
> (..) and for Fedora multiple times by different people and doesn't exhibit
> any such errors.
Because Fedora build procedure has no `update-pot` target execution.
--
Reply to this email directly or view it on GitHub:
Actually both of you: what exactly are you doing that you run into this?
Clearly, the paths in the rpm-l10n repo were wrong but the release tarball from
ftp.rpm.org has been built locally and for Fedora multiple times by different
people and doesn't exhibit any such errors.
Which makes me
> In first line of the provided output is ONE command which needs to be
> executed. It does not need anything build env specific biits.
It's one command run in some unspecific context. You've reported several
tickets where you've been using cmake in a very different manner than what we
do and
> I'm just making the changes where they are now. I can certainly see moving
> the CMake code out and file list out.
It is not possible to tag repo ans subrepo.
At the moment in https://github.com/rpm-software-management/rpm-l10n there is
no any tags.
--
Reply to this email directly or view
I'm just making the changes where they are now. I can certainly see moving the
CMake code out and file list out.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2817#issuecomment-1859000304
You are receiving this because you are
IMO all those changes should be part of rpm repo.
In this repo should be time to time (at least week before release) updated
po/rpm.pot file and that .pot files should be registered on one of the i18n
translation infras. Than time to time available updates should be pooled.
Really .. please have
The fix for this is going to be in
https://github.com/rpm-software-management/rpm-l10n.
I've opened a PR that allows the target to build on my system:
https://github.com/rpm-software-management/rpm-l10n/pull/1
--
Reply to this email directly or view it on GitHub:
> Why on earth are you specifically running 'update-pot' on a released rpm
> tarball in the first place?
Because .pot file used during build is ALWAYS not-up-to-date. `update-pot`
removes many translated entries which are no longer used (-> installed .mo
files are shorter).
As you see in this
Why on earth are you specifically running 'update-pot' in the first place?
And, if you expect somebody to look at this, supply the entire reproducer. Ie,
all the cmake commands on a pristine source tarball.
--
Reply to this email directly or view it on GitHub:
BTW: is it possible to change dist tar ball compression from .bz2 to .xz 樂
(xz produces shorter tar balls on archives with text files)
```console
[tkloczko@pers-jacek SOURCES]$ ls -l rpm-4.19.1.tar.xz rpm-4.19.1.tar.bz2
-rw-rw-r-- 1 tkloczko tkloczko 5940447 Dec 14 19:37 rpm-4.19.1.tar.bz2
It would be good to add checking that target to release procedure
```console
+ /usr/bin/cmake --build x86_64-redhat-linux-gnu -j48 --verbose --target
update-pot
Change Dir: '/home/tkloczko/rpmbuild/BUILD/rpm-4.19.1/x86_64-redhat-linux-gnu'
Run Build Command(s): /usr/bin/cmake -E env VERBOSE=1
16 matches
Mail list logo
