When trying to update to 0.10.9-1, logseq-desktop-debug
has a conflict with pulsar-desktop-debug
.
error: failed to commit transaction (conflicting files)
logseq-desktop-debug: /usr/lib/debug/.build-id/08/05eac40eca021940fba86362246c391d52c5d1 exists in filesystem (owned by pulsar-bin-debug)
logseq-desktop-debug: /usr/lib/debug/.build-id/08/05eac40eca021940fba86362246c391d52c5d1.debug exists in filesystem (owned by pulsar-bin-debug)
logseq-desktop-debug: /usr/lib/debug/.build-id/2f/33078e6a1afa933d498dbc1ddba2954c80a969 exists in filesystem (owned by pulsar-bin-debug)
logseq-desktop-debug: /usr/lib/debug/.build-id/2f/33078e6a1afa933d498dbc1ddba2954c80a969.debug exists in filesystem (owned by pulsar-bin-debug)
logseq-desktop-debug: /usr/lib/debug/.build-id/54/ec801d25cfdd9e8e9647390ad4b878a30c9a74 exists in filesystem (owned by pulsar-bin-debug)
logseq-desktop-debug: /usr/lib/debug/.build-id/54/ec801d25cfdd9e8e9647390ad4b878a30c9a74.debug exists in filesystem (owned by pulsar-bin-debug)
logseq-desktop-debug: /usr/lib/debug/.build-id/80/4d27ab6ea5f4e51fdb2a42cf621db79a4ce34b exists in filesystem (owned by pulsar-bin-debug)
logseq-desktop-debug: /usr/lib/debug/.build-id/80/4d27ab6ea5f4e51fdb2a42cf621db79a4ce34b.debug exists in filesystem (owned by pulsar-bin-debug)
logseq-desktop-debug: /usr/lib/debug/.build-id/93/399ebc639a43226f8348722c39f9d36f5f87b1 exists in filesystem (owned by pulsar-bin-debug)
logseq-desktop-debug: /usr/lib/debug/.build-id/93/399ebc639a43226f8348722c39f9d36f5f87b1.debug exists in filesystem (owned by pulsar-bin-debug)
logseq-desktop-debug: /usr/lib/debug/.build-id/ad/bc37dbdae4f661213461904c0f01e005904b80 exists in filesystem (owned by pulsar-bin-debug)
logseq-desktop-debug: /usr/lib/debug/.build-id/ad/bc37dbdae4f661213461904c0f01e005904b80.debug exists in filesystem (owned by pulsar-bin-debug)
logseq-desktop-debug: /usr/lib/debug/.build-id/c3/ab3bd2f454c29415f4288c342d597be40b9cf3 exists in filesystem (owned by pulsar-bin-debug)
logseq-desktop-debug: /usr/lib/debug/.build-id/c3/ab3bd2f454c29415f4288c342d597be40b9cf3.debug exists in filesystem (owned by pulsar-bin-debug)
logseq-desktop-debug: /usr/lib/debug/.build-id/c6/abc02ed033ae5743b649be6f164afb007f2c2c exists in filesystem (owned by pulsar-bin-debug)
logseq-desktop-debug: /usr/lib/debug/.build-id/c6/abc02ed033ae5743b649be6f164afb007f2c2c.debug exists in filesystem (owned by pulsar-bin-debug)
logseq-desktop-debug: /usr/lib/debug/.build-id/d4/1fe579bed152666214ab352bddb7c03610b59a exists in filesystem (owned by pulsar-bin-debug)
logseq-desktop-debug: /usr/lib/debug/.build-id/d4/1fe579bed152666214ab352bddb7c03610b59a.debug exists in filesystem (owned by pulsar-bin-debug)
logseq-desktop-debug: /usr/lib/debug/.build-id/f6/294e6fc2647a8e507b42b1b0f9e8ab0afd06cb exists in filesystem (owned by pulsar-bin-debug)
logseq-desktop-debug: /usr/lib/debug/.build-id/f6/294e6fc2647a8e507b42b1b0f9e8ab0afd06cb.debug exists in filesystem (owned by pulsar-bin-debug)
Pinned Comments
xiota commented on 2024-01-15 00:17 (UTC) (edited on 2024-01-15 00:19 (UTC) by xiota)
This package sets
HOME=${SRCDEST:-$startdir}/node-home
to avoid cluttering the user home directory, while allowing data (over 4GB) to be reused between builds.$srcdir
is not used for this purpose because it can be wiped between runs.xiota commented on 2023-09-11 03:34 (UTC) (edited on 2024-01-14 17:37 (UTC) by xiota)
This is interesting. I have different results on two different computers. (AMD vs Intel?) Will go ahead and bump versions. Any users who have the same build failure, try rolling back to 0.9.13 or use the
-bin
package.No need to re-report the same issue. I'll update if I find a solution.
Note: No solution as of Jan 2024.
xiota commented on 2023-08-23 07:46 (UTC) (edited on 2023-12-03 06:07 (UTC) by xiota)
Clean chroot. Attempting to build after bumping to 0.9.14 or later results in error. Possibly related to AMD processors. Anyone know how to fix?