On Wed, Jul 10, 2019 at 11:29:01 +0200, olivier sallou wrote: > Le mer. 10 juil. 2019 à 11:08, Andrey Rahmatullin <w...@debian.org> a > écrit : > > > On Wed, Jul 10, 2019 at 10:54:21AM +0200, olivier sallou wrote: > > > So, am I doing something wrong? > > You tried to install a package (what package? they don't exist) from a > > repo that doesn't exist. > > > > I tried a package that is not in backports, it was just for test (for an > automation tool I use) > It should fail with a *package not found* , but should not fail about > buster-backports being non available. > > Is the problem linked to buster-backports not existing yet ? Is backports > repo not created automatically on new releases? > buster-backports exists. AIUI this is an apt bug when dealing with empty repos. (Although why are you setting default-release to buster-backports?)
Cheers, Julien
