Mailinglist Archive: opensuse-buildservice (41 mails)

< Previous Next >
Re: [opensuse-buildservice] putting files to OTHER directory and its availability in the API
  • From: Adrian Schröter <adrian@xxxxxxx>
  • Date: Wed, 20 Mar 2019 19:34:15 +0100
  • Message-id: <35318879.8FThkxx6mJ@linux-ywca>
On Mittwoch, 20. März 2019, 19:11:16 CET Stanislav Brabec wrote:

I am trying to implement a new translation update process. I need to export
pot files from the build process.

I have been told that files copied into %{_topdir}/OTHER will become
available at after the build. But it is a half true. It
works only for i586 but not x86_64.

Is there any other step needed to get it working?
em/grub2/grub2.spec?expand=0 See %prep stage and the end of %install phase
just above %pre.

Log cleanly shows that it works correctly for x86_64:
enSUSE_Factory/x86_64/grub2/_log [ 589s] + tar -jcf
/home/abuild/rpmbuild/OTHER/pot.tar.bz2 po-suse/grub2-suse.pot [ 589s] +
ls -al /home/abuild/rpmbuild/OTHER
[ 589s] total 12
[ 589s] drwxr-xr-x 2 abuild abuild 4096 Mar 20 16:49 .
[ 589s] drwxr-xr-x 9 abuild abuild 4096 Mar 20 16:40 ..
[ 589s] -rw-r--r-- 1 abuild abuild 2312 Mar 20 16:49 pot.tar.bz2

ctory/x86_64/grub2 does not contain any reference to pot.tar.bz2
ctory/i586/grub2 does:
<binary filename="pot.tar.bz2" size="2315" mtime="1553100342" />

actually, it also gets copied on x86_64, but there is the second build step
run, which is needed for secure boot. And it gets not exported there.

one more example of conflicting hacks... but we can maybe export it also in
the second step. Will have a look tomorrow ...


Adrian Schroeter
SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
email: adrian@xxxxxxx

To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-buildservice+owner@xxxxxxxxxxxx

< Previous Next >