raulcd opened a new issue, #50358:
URL: https://github.com/apache/arrow/issues/50358

   ### Describe the bug, including details regarding any error messages, 
version, and platform.
   
   When executing the binary signing and upload of artifacts: 
`dev/release/05-binary-upload.sh 25.0.0 1` it fails with:
   ```bash
   Successfully uploaded 15 assets to apache-arrow-25.0.0-rc1
   31bd089f3983c13a5e74129a7f5d168be1d9f390aa880888d24fc903f3714933
   Pseudo-terminal will not be allocated because stdin is not a terminal.
   Warning: Permanently added '[127.0.0.1]:32768' (ED25519) to the list of 
known hosts.
   gpg: keybox '/home/arrow/.gnupg/pubring.kbx' created
   gpg: /home/arrow/.gnupg/trustdb.gpg: trustdb created
   gpg: key 9E922B2D60E9FD1C: public key "Raul Cumplido Dominguez (CODE SIGNING 
KEY) <[email protected]>" imported
   gpg: Total number processed: 1
   gpg:               imported: 1
   Warning: Permanently added '[127.0.0.1]:32768' (ED25519) to the list of 
known hosts.
   tar xf binary/tmp/artifacts/almalinux-10-amd64.tar.gz -C 
/tmp/rc/yum/repositories/incoming
   tar xf binary/tmp/artifacts/almalinux-10-arm64.tar.gz -C 
/tmp/rc/yum/repositories/incoming
   mv /tmp/rc/yum/repositories/incoming/almalinux/10/Source/Packages 
/tmp/rc/yum/repositories/incoming/almalinux/10/Source/SPackages
   tar xf binary/tmp/artifacts/almalinux-9-amd64.tar.gz -C 
/tmp/rc/yum/repositories/incoming
   tar xf binary/tmp/artifacts/almalinux-9-arm64.tar.gz -C 
/tmp/rc/yum/repositories/incoming
   mv /tmp/rc/yum/repositories/incoming/almalinux/9/Source/Packages 
/tmp/rc/yum/repositories/incoming/almalinux/9/Source/SPackages
   tar xf binary/tmp/artifacts/almalinux-8-amd64.tar.gz -C 
/tmp/rc/yum/repositories/incoming
   tar xf binary/tmp/artifacts/almalinux-8-arm64.tar.gz -C 
/tmp/rc/yum/repositories/incoming
   mv /tmp/rc/yum/repositories/incoming/almalinux/8/Source/Packages 
/tmp/rc/yum/repositories/incoming/almalinux/8/Source/SPackages
   tar xf binary/tmp/artifacts/amazon-linux-2023-amd64.tar.gz -C 
/tmp/rc/yum/repositories/incoming
   tar xf binary/tmp/artifacts/amazon-linux-2023-arm64.tar.gz -C 
/tmp/rc/yum/repositories/incoming
   mv /tmp/rc/yum/repositories/incoming/amazon-linux/2023/Source/Packages 
/tmp/rc/yum/repositories/incoming/amazon-linux/2023/Source/SPackages
   tar xf binary/tmp/artifacts/centos-9-stream-amd64.tar.gz -C 
/tmp/rc/yum/repositories/incoming
   tar xf binary/tmp/artifacts/centos-9-stream-arm64.tar.gz -C 
/tmp/rc/yum/repositories/incoming
   mv /tmp/rc/yum/repositories/incoming/centos/9-stream/Source/Packages 
/tmp/rc/yum/repositories/incoming/centos/9-stream/Source/SPackages
   Downloading: almalinux - 100.0% [63/63] 00:01:19 00:00:00  2/s
   Downloading: amazon-linux - 100.0% [42/42] 00:00:45 00:00:00  3/s
   Downloading: centos - 100.0% [63/63] 00:01:26 00:00:00  0/s
   error: Unable to open sqlite database /var/lib/rpm/rpmdb.sqlite: unable to 
open database file
   error: cannot open Packages index using sqlite - Operation not permitted (1)
   error: cannot open Packages database in /var/lib/rpm
   error: can't create transaction lock on /var/lib/rpm/.rpm.lock (No such file 
or directory)
   error: /tmp/apache-arrow-binary20260703-49-htq2me.asc: key 1 import failed.
   rake aborted!
   Command failed with status (1): [rpm --import 
/tmp/apache-arrow-binary20260703-49-htq2me.asc]
   /host/binary-task.rb:1933:in `rpm_sign'
   /host/binary-task.rb:2082:in `block (3 levels) in define_yum_rc_tasks'
   /usr/share/rubygems-integration/all/gems/rake-13.2.1/exe/rake:27:in `<top 
(required)>'
   Tasks: TOP => yum:rc => yum:rc:sign
   (See full trace by running task with --trace)
   ```
   
   This is potentially related to the update to the underlying image that 
uploads binaries:
   - https://github.com/apache/arrow/pull/50201
   
   ### Component(s)
   
   Release


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to