Bug#876478: ben tracker --global-conf <path> ignores settings

[Mehdi Dogguy <mehdi@dogguy.org>]

Hi Sebastiaan,

On 2018-05-13 14:13, Sebastiaan Couwenberg wrote:
> On 05/13/2018 01:59 PM, Mehdi Dogguy wrote:
> > On 2018-05-13 13:51, Sebastiaan Couwenberg wrote:
> > > On 05/13/2018 01:25 PM, Mehdi Dogguy wrote:
> > > > On 2017-09-22 18:37, Bas Couwenberg wrote:
> > > > > Package: ben
> > > > > Version: 0.7.4+b4
> > > > > Severity: important
> > > > >
> > > > > Dear Maintainer,
> > > > >
> > > > > Since the upgrade to stretch my ben setup no longer works as 
> > > > > before.
> > > > >
> > > > > The `ben tracker --global-conf <path>/global.conf` commands don't 
> > > > > use
> > > > > the cache file as configured in the global.conf file, and instead
> > > > > download the Sources & Packages files again (which were downloaded
> > > > > before
> > > > > using `ben download -c <path>/global.conf`).
> > > > >
> > > > > The downloaded files also use the current working directory instead 
> > > > > of
> > > > > the cache-dir configured in global.conf
> > > >
> > > > Do you have "use-cache = true;" in your global.conf file?
> > >
> > > Yes.
> >
> > Can you please share your setup so that I can reproduce it and debug 
> > it?
> > (scripts, configuration files)
>
> https://linuxminded.nl/tmp/ben.tar.gz
>
> That contains my entire ben directory.

Great, thanks!

I noticed you had the following line at the beginning of your 
ben-tracker-*.sh
scripts:

  rm -f ben.cache Packages_* Sources

Since those scripts are executed after ben-download-*.sh scripts, it may 
explain
the behaviour your are experiencing.

Regards,

--
Mehdi