[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#978323: marked as done (gdb-bpf: FTBFS: tar: /usr/src/gdb.tar.*: Cannot open: No such file or directory)

Your message dated Sun, 3 Jan 2021 15:34:00 +0100
with message-id <ae5ddcff-23ea-ef5f-f6db-5bb1c4ca2913@debian.org>
and subject line Re: gdb-bpf: FTBFS: tar: /usr/src/gdb.tar.*: Cannot open: No such file or directory
has caused the Debian Bug report #978323,
regarding gdb-bpf: FTBFS: tar: /usr/src/gdb.tar.*: Cannot open: 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.)


-- 
978323: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978323
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: gdb-bpf
Version: 2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> tar xf /usr/src/gdb.tar.*
> tar: /usr/src/gdb.tar.*: Cannot open: No such file or directory
> tar: Error is not recoverable: exiting now
> make[1]: *** [debian/rules:34: unpack-stamp] Error 2

The full build log is available from:
   http://qa-logs.debian.net/2020/12/26/gdb-bpf_2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

--- End Message ---
--- Begin Message --- 
closing, that was fixed in src:gdb.

--- End Message ---
Reply to: