Bug#1058522: (no subject)
Hi Jeremy,
Сб 30 дек 2023 @ 11:28 Jeremy Sowden <jeremy@azazel.net>:
> On 2023-12-24, at 10:00:26 +0500, Lev Lamberov wrote:
>> Чт 21 дек 2023 @ 15:06 Jeremy Sowden:
>> > On 2023-12-21, at 11:21:48 +0000, Jeremy Sowden wrote:
>> >> On 2023-12-21, at 11:10:28 +0500, Lev Lamberov wrote:
>> >> > Since I cannot reproduce the bug, I'm downgrading the severity of
>> >> > this bug report.
>> >>
>> >> I cloned the git repo, ran `gbp buildpackage --git-pbuilder` and
>> >> reproduced it (log attached). I'll see if I can work out what's going
>> >> on.
>>
>> Thanks for your input. I double checked this bug report both under
>> git-pbuilder and sbuild. E. g., here is the sbuild environment:
>>
>> $ sudo sbuild-shell unstable
>> I: /bin/sh
>> # bash
>> (unstable-amd64-sbuild)root@shakva:/# du --version
>> du (GNU coreutils) 9.4
>> Copyright (C) 2023 Free Software Foundation, Inc.
>> License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>.
>> This is free software: you are free to change and redistribute it.
>> There is NO WARRANTY, to the extent permitted by law.
>>
>> Written by Torbjörn Granlund, David MacKenzie, Paul Eggert,
>> and Jim Meyering.
>> (unstable-amd64-sbuild)root@shakva:/# exit
>>
>> But I still cannot reproduce the bug. Don't know...
>
> First things first, do you see the following in your chroot?
>
> (unstable-amd64-sbuild)root@ulthar:~# d=$(mktemp -d)
> (unstable-amd64-sbuild)root@ulthar:~# du -sb $d
> 0 /tmp/tmp.qay80HZ09w
>
> This is the cause of the problem. If your du is not reporting zero size
> for an empty directory, that would explain the discrepancy and the rest
> of this e-mail is irrelevant. :)
It is zero for me.
I was able to reproduce the bug in a clean schroot environment. Will
figure out what to do next in the coming days.
Happy New Year!
Cheers!
Lev
Reply to: