#963545 aptitude-create-state-bundle can't deal with no $HOME/.aptitude present

Package:
aptitude-common
Source:
aptitude
Submitter:
積丹尼 Dan Jacobson
Date:
2025-03-18 13:48:03 UTC
Severity:
minor
Tags:
#963545#5
Date:
2020-06-23 13:30:08 UTC
From:
To:
# aptitude-create-state-bundle /tmp/z
tar: .//root/.aptitude: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors

Well the man page says $HOME/.aptitude, which looks different than the
above.

But what's the big deal? Why can't the program proceed if it isn't
present?

Aptitude itself can still run, why not aptitude-create-state-bundle?

P.S., why not also grab a apt-config dump too?
#963545#10
Date:
2020-08-16 01:42:32 UTC
From:
To:
Dear Jidanni,

積丹尼 Dan Jacobson wrote:

Not really. Depending on the user and the current working directory,
this is (and from my point of view also looks) the same.

Because tar trips over it.

Passing --ignore-failed-read to tar should suffice.

Because aptitude doesn't call tar.

Why should we? We already have that data by including /etc/apt/ in the
tar ball. Using "apt-config dump" whould just add completely
unnecessary complexity.

		Regards, Axel
#963545#19
Date:
2020-08-16 04:16:52 UTC
From:
To:
Dear Jidanni,

Axel Beckert wrote:

Actually, aptitude-create-state-bundle still exits with 0 and the file
is still generated. So it's a really, really minor and cosmetic issue.

Done that now in the master branch. It actually has no impact on the
resulting file. It just downgrades tar's output from "error" to
"warning".

It will be fixed in the next aptitude upstream release. This will
probably be 0.8.14. It is not fixed in the 0.8.13-2 package I just
uploaded with a patch to fix a FTBFS.

		Regards, Axel
#963545#26
Date:
2020-08-18 15:17:55 UTC
From:
To:
Glad it will be fixed soon. Thanks.
#963545#31
Date:
2025-03-18 13:44:34 UTC
From:
To:
Hi,

I don't know when 0.8.14 is planned, but that's almost 5 years
since this message was posted.

Regards,