Your message dated Sat, 12 Dec 2015 13:10:20 +0000
with message-id <20151212131020.ga26...@chase.mapreri.org>
and subject line Re: Bug#807728: Could not create directory: /home/jff/.cache
has caused the Debian Bug report #807728,
regarding Could not create directory: /home/jff/.cache
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 ow...@bugs.debian.org
immediately.)


-- 
807728: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807728
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pbuilder
Version: 0.221.1
Severity: grave

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hi,

since the last update I get allways:

[...]
Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ...
Reading package lists...
Building dependency tree...
Reading state information...
Initializing package states...
Writing extended state information...
Building tag database...
E: Could not create directory: /home/jff/.cache:
boost::filesystem::create_directory: No such file or directory:
"/home/jff/.cache"
E: pbuilder-satisfydepends failed.
[...]

The directory /home/jff/.cache exists:

ls -al
insgesamt 38248
drwxr-xr-x 71 jff  jff       4096 Dez 12 07:30 .
drwxr-xr-x  4 root root      4096 Okt  9  2014 ..
[...]
- -rw-r--r--  1 jff  jff      39261 Jan 26  2015 .bzr.log
drwx------ 55 jff  jff       4096 Dez 12 07:19 .cache
drwx------ 10 jff  jff       4096 Jul 26 20:16 .claws-mail
drwx------ 53 jff  jff       4096 Dez  8 06:14 .config
drwx------  2 jff  jff       4096 Jul 19 13:01 .cups
drwx------  3 jff  jff       4096 Okt  9  2014 .dbus






- -- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (500, 'testing-updates'), 
(1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-1-amd64 (SMP w/6 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages pbuilder depends on:
ii  debconf [debconf-2.0]  1.5.58
ii  debootstrap            1.0.75
ii  dpkg-dev               1.18.3
ii  wget                   1.17-1

Versions of packages pbuilder recommends:
ii  devscripts  2.15.9
ii  fakeroot    1.20.2-1
ii  iproute2    4.3.0-1
ii  net-tools   1.60+git20150829.73cef8a-2
ii  sudo        1.8.12-1

Versions of packages pbuilder suggests:
ii  cowdancer     0.75
ii  gdebi-core    0.9.5.7
pn  pbuilder-uml  <none>

- -- debconf information:
  pbuilder/rewrite: false
  pbuilder/mirrorsite: http://mirror.1und1.de/debian/
  pbuilder/nomirror:

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCgAGBQJWa8JzAAoJEAn4nzyModJdKJcQAIg7rf7JdR+OIldpLDOkBigN
GzRmai0waB3Wbvsl4H5dekxBNjAfW5UV6gS+ujX3c3uwgvXf29YS8BBn9V5a0gb/
r39txzdkJNXHA1UwNviH8N7MllsUoN+YAZ9/oOLak7uKYxggUYwncxBDWkZhJTGL
y2pamYf+ywbZ5bcqv/FuMP4hQq8ARO9DWxp0ehhjYXy+PX5rYu7OhOFJg3xKUch+
YECMo6Icf5qvcQieYO0M3QluU63NThBspYlKLo4349/MXvK3lh7MadRFSOFzgYh8
w8pcEQaL0Nsyg+P7Vk5QmtjhE1plR9tUzQP+q2WBYW7V4A/7PRqoKLgh+HOLAVrx
qDJU/MQ2rcNR07DgsSGdoU4KS+KfRNxWsiHAYkd3phGotLW8NUyw5dymcX2kujBv
df5B8nh82Ctcl+u7ShlZkHW0mBAi3XccpvXFMQ+mLP9vix/vFIKtXmIkOiUP5Zx9
WMRyEDLRZogQPNycKQ2X2XrkzZ/ZgiM6eAviGb+hJoRwOGSsvoKAA8xxadj362pi
zK2PRHxbhU39fpeeVqjBvL2ESQKDGyqGq6Z6pTF+4tfk1ptPJ5XGwzQZe6NW3lYA
VSk2h9+GQCY5TJAJHktWw2KEYlzNHHGUhjLYdXG4fZc/Hgg7vw64c6Z6l9rkLI2q
7SeBLo9n03DwK2LpqFSS
=1R+Y
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message ---
Version: 0.221.3

On Sat, Dec 12, 2015 at 07:45:07AM +0100, Jörg Frings-Fürst wrote:
> since the last update I get allways:
> 
> [...]
> Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ...
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Initializing package states...
> Writing extended state information...
> Building tag database...
> E: Could not create directory: /home/jff/.cache:
> boost::filesystem::create_directory: No such file or directory:
> "/home/jff/.cache"
> E: pbuilder-satisfydepends failed.
> [...]

This is due to yet another change in aptitude, but the kinda of
workaround I did in 0.221.3 should be sufficient for this too.

> The directory /home/jff/.cache exists:
> 
> ls -al
> insgesamt 38248
> drwxr-xr-x 71 jff  jff       4096 Dez 12 07:30 .
> drwxr-xr-x  4 root root      4096 Okt  9  2014 ..
> [...]
> - -rw-r--r--  1 jff  jff      39261 Jan 26  2015 .bzr.log
> drwx------ 55 jff  jff       4096 Dez 12 07:19 .cache
> drwx------ 10 jff  jff       4096 Jul 26 20:16 .claws-mail
> drwx------ 53 jff  jff       4096 Dez  8 06:14 .config
> drwx------  2 jff  jff       4096 Jul 19 13:01 .cups
> drwx------  3 jff  jff       4096 Okt  9  2014 .dbus

well, we're talking about inside the chroot, there most probably it
doesn't.

The issue is that /home/jff is not present in the chroot, and aptitude
won't create it.
Anyway, please try to upgrade to what is currently in unstable and
confirm it works :)

-- 
regards,
                        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540      .''`.
more about me:  http://mapreri.org                              : :'  :
Launchpad user: https://launchpad.net/~mapreri                  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-

Attachment: signature.asc
Description: PGP signature


--- End Message ---

Reply via email to