Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.rc > #363794 > unrolled thread

Bug#1071317: intel-mkl: FTBFS: error: can't create transaction lock on /var/lib/rpm/.rpm.lock (No such file or directory)

Back to article view | Back to linux.debian.bugs.rc

Contents

  Bug#1071317: intel-mkl: FTBFS: error: can't create transaction lock on /var/lib/rpm/.rpm.lock (No such file or directory) Santiago Vila <sanvila@debian.org> - 2024-05-17 22:50 +0200
    Bug#1071317: marked as done (intel-mkl: FTBFS: error: can't  create transaction lock on /var/lib/rpm/.rpm.lock (No such file or  directory)) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2024-06-12 13:00 +0200

#363794 — Bug#1071317: intel-mkl: FTBFS: error: can't create transaction lock on /var/lib/rpm/.rpm.lock (No such file or directory)

Package: src:intel-mkl
Version: 2020.4.304-4
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:

--------------------------------------------------------------------------------
[...]
  debian/rules binary
dh binary
    dh_update_autotools_config
    dh_autoreconf
    debian/rules override_dh_auto_configure
make[1]: Entering directory '/<<PKGBUILDDIR>>'
../intel-mkl_2020.4.304.orig.tar.gz: OK
rpm --rebuilddb
error: can't create transaction lock on /var/lib/rpm/.rpm.lock (No such file or directory)
make[1]: *** [debian/rules:35: extract-rpms] Error 255
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:27: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--------------------------------------------------------------------------------

The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:

https://people.debian.org/~sanvila/build-logs/202405/

About the archive rebuild: The build was made on virtual machines
of type m6a.large and r6a.large from AWS, using sbuild and a
reduced chroot with only build-essential packages.

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.

Thanks.

[toc] | [next] | [standalone]

#365045 — Bug#1071317: marked as done (intel-mkl: FTBFS: error: can't create transaction lock on /var/lib/rpm/.rpm.lock (No such file or directory))

[Multipart message — attachments visible in raw view] — view raw

Your message dated Wed, 12 Jun 2024 10:51:14 +0000
with message-id <E1sHLZS-0099bX-Gq@fasolo.debian.org>
and subject line Bug#1071317: fixed in intel-mkl 2020.4.304-5
has caused the Debian Bug report #1071317,
regarding intel-mkl: FTBFS: error: can't create transaction lock on /var/lib/rpm/.rpm.lock (No such file or directory)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1071317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071317
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.rc

csiph-web