Hi,

I'm using `gbp buildpackage` with pbuilder, and I'm running into an
issue that I've seen a few times. The build fails because the build dependencies cannot be satisfied; looking at the failure:

Err http://deb.debian.org/debian sid/main amd64 python3-django all
2:4.0.5-2
404 Not Found [IP: 151.101.118.132 80]

but on my machine:

$ apt show python3-django
Package: python3-django
Version: 2:4.0.6-1

..it would seem that the pbuilder env is using an out of date package
index. I have tried 'pbuilder update', 'pbuilder create'.. with the
same results. The really odd thing is that if I use 'pbuilder login',
I can install python3-django (4.0.6-1) no problem.

I imagine I'm missing something simple wrt pbuilder.. any ideas where
to look?

Thanks!
Matt

-----BEGIN PGP SIGNATURE-----

iQJKBAABCgA0FiEEnnn62mSvqqi3CaOCyHh1RhnOe48FAmLQj24WHG1hdHRAaGF6 ZWxtb2xsdXNrLm9yZwAKCRDIeHVGGc57jzxND/4yzBApcsfHmeTAQE5NLKj6K7eU 0+i5EZMT8MtHPV24TTjDTcBU/ZvNJW50hVN4JvhRPabjvZRg+scnsvTJhsvze4Eq 5bejd2WbllbQY+AylTGnNVYLw6EpUH0OGtedzEX2MOzPKnHfrmHx+fwO9FJ+arIj BPQjyPDu05HDPWCqel4q2JqSjQGZesPdZL69B4sKBTFIVrCU5zZ1bGbcjOsC4paZ CmcPsIgeI+nnCPRtTUGrD+s4k06mBE3DR0aXA1+/uJnhfjaFwhWOBLBqwSvI8CcS aeyGOM7hopTj4ZGWjtz6krAODNhMM4espVEpB1gU2vr0T4bpn/nJkqOv6qF3luxm aKbsNhY1yDG8Qq7KJ0PXCIRWfAjNM34UPMhK67VLTSAZ6dL9BQ/b2ghbaiNfy+AH tTiW9hQfP9P/GxGWffOXISJ3JkDroKOoGTpmfvp/wU8nyEqekxxgsU8pg6NswF7X gH0cRTV+u4MEZqx8dRw4nssAXQqJO7Bzwc7UHMTK200MgxZMy85+sj0qz/ogPQoe fs9afs2m7DoBrije+UjVhrhCAQk3rzOblXLGLg0NbiMkuGVGb65Rusj18zko4Qbk XmEi0uVQatuOmPtVfvPQJ4q2KtQEnxNZm98EefRZB0sHv4qkZ50ozGE1+k8Deiz/ gNzUcO1CIcCStZoi7A==
=4OzL
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Thu, 2022-07-14 at 17:49 -0400, Matt Barry wrote:

I imagine I'm missing something simple wrt pbuilder.. any ideas where
to look?

Are you getting any errors from the pbuilder update command?

Are you updating the same chroot as you are building with?

You can also add a hook that does apt update before the build:

==> ~/.pbuilder/hooks/D01update <==
#!/bin/bash
exec apt-get update

Sometimes it is useful to have a shell during the build, which you
can use to do things you forgot to do in the packaging or elsewhere.

==> ~/.pbuilder/hooks/A00shell -> shell <==
==> ~/.pbuilder/hooks/B00shell -> shell <==
==> ~/.pbuilder/hooks/C00shell -> shell <==
==> ~/.pbuilder/hooks/D00shell -> shell <==
==> ~/.pbuilder/hooks/E00shell -> shell <==
==> ~/.pbuilder/hooks/G00shell -> shell <==
==> ~/.pbuilder/hooks/H00shell -> shell <==
==> ~/.pbuilder/hooks/I00shell -> shell <==
==> ~/.pbuilder/hooks/shell <==
#!/bin/bash
exec /bin/bash -i </dev/tty > /dev/tty 2> /dev/tty

There are various pbuilder hook examples here:

/usr/share/doc/pbuilder/examples

More pbuilder tips and tricks here:

https://wiki.debian.org/PbuilderTricks

--
bye,
pabs

https://wiki.debian.org/PaulWise

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEYQsotVz8/kXqG1Y7MRa6Xp/6aaMFAmLQuSwACgkQMRa6Xp/6 aaM2mRAAgwJVCGD5w2VNTnL2iB02T1qHBrX3pUfxwNMVgIjKCTxGAni9thrW4WOg hElJp5P4r9BVKGPn2ju9XM8UA4D8nP1F2z1w6oN6lx5DddbwHL2hPnjI5E29csuL YLVgBZkitT78N/riWtoDirrW8UUoCHUZ64QGl6lAzRxwD39EjCT/sJbuE0Aopryz CoLqUKedbAgID+u2JHDm0zR/s3BaCm8aSeMuy5Ti+lstu2SlyZgzh/3ymJiDs+T/ JiyDOHrxN3fJWtvIpX2DjsieU25K+tcLtAuq38x9bBdQNRYpTC9xu1rT6t6/7hBZ +kb7LMmFXyid5vfkiDn9+IYB+KVgH53mvjrRWBIqkOGWsGTIUDP/WNuRpvHoZOkF voB2iDA5J0sJcC3biBEg1Tev5/JWi76vehEEiF8Zj8o6cm4JpLqbPQ97Jf5AQ2Kr 8tcVe3sTrwuHNS6PNeOjXvlLGnlNelondJoTX2tNGtEEo5taIgwZMLnfC9FxqfaM MyriMF45VPSJrhpMdV+eBvOx/ZT3dy4YUzg279treN858f13jPbijW8kmHNf9Mex 008qGyrPWb1GKBVJ94M5VEw7E4At1AjkTB0VGZzWYsHXQZVIx+PcgXGsehzbxi2r EWI/DFYOzb/ExhuZ99Z2VBgeoAhddlL8i+jT2gwSZrs3P33ftqs=
=PNl/
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Fri, 2022-07-15 at 08:47 +0800, Paul Wise wrote:

On Thu, 2022-07-14 at 17:49 -0400, Matt Barry wrote:

I imagine I'm missing something simple wrt pbuilder.. any ideas
where
to look?

Are you getting any errors from the pbuilder update command?

No, however..

Are you updating the same chroot as you are building with?

No :)

I'll figure out which configs belong where, but long story short,
'pbuilder update' and 'git-pbuilder update' were working on two
different chroots.

Thanks!

You can also add a hook that does apt update before the build:

   ==> ~/.pbuilder/hooks/D01update <==
   #!/bin/bash
   exec apt-get update

Strangely this did not do anything.. hmm.

  
Sometimes it is useful to have a shell during the build, which you
can use to do things you forgot to do in the packaging or elsewhere.

   ==> ~/.pbuilder/hooks/A00shell -> shell <==
   ==> ~/.pbuilder/hooks/B00shell -> shell <==
   ==> ~/.pbuilder/hooks/C00shell -> shell <==
   ==> ~/.pbuilder/hooks/D00shell -> shell <==
   ==> ~/.pbuilder/hooks/E00shell -> shell <==
   ==> ~/.pbuilder/hooks/G00shell -> shell <==
   ==> ~/.pbuilder/hooks/H00shell -> shell <==
   ==> ~/.pbuilder/hooks/I00shell -> shell <==
   ==> ~/.pbuilder/hooks/shell <==
   #!/bin/bash
   exec /bin/bash -i </dev/tty > /dev/tty 2> /dev/tty

There are various pbuilder hook examples here:

   /usr/share/doc/pbuilder/examples

Cool, thanks!

Cheers,
Matt

-----BEGIN PGP SIGNATURE-----

iQJKBAABCgA0FiEEnnn62mSvqqi3CaOCyHh1RhnOe48FAmLQwDIWHG1hdHRAaGF6 ZWxtb2xsdXNrLm9yZwAKCRDIeHVGGc57j9zaD/4liOa+y/TAi7Do1Rpd1DGliqkA ycnl7LzHjOrB6NCZMEdXghCg2xzC88zhoGEvF5/k8oQgWDW1tQ42fCG3smvGBKDZ ygHPF/cWp6DC06ZL3Qg+njg9/rDAaSsREpCMNyhRYYer4OSdDfDuTJfGmU/AgkVi RrRbxngGAWmq4exKAi6xgy35Gq+pb+C2k397f7Mytu2qXh2g+M9aW+nwyLOmEaxa p6ohU2JQ68KnzXP9durq3pIk8gRMU7t1hOVEHeT+85pRtj0C+a6BCj1AAUUZZFhx JVDtkLY6lsvKw8hdFNQhD4wmHi6wABUdvWLBMyndDDjyg/RsuRkfsuIC5nzc6pCy 1rjvF9WGwc/NkN+sphpP6+zu1loviUVdxcE+npIf1Gn5tCUej1gryDcZr6O88OlM oynvwOO3HnvJAjHF7Wao43l+7b9Eo0MG2QMEccbPq0TlI9SdCMasDc7vn5qVJvmL /iUmMZIsHquGI7TMGEUDbcidsOoBW52yc2IvaeEUhCsr6gchuofycArljetCUMNz 3G0kmnpTfhTXaUzdO7V86relW/9BkmCeG32cyo5iLknav97ylwk1/yKcNJ5Zr56n L05qS+HfgSeXXTaM4UACQkLJXFgw5bGzbaCzDPgquHe0hGwsJnwK1/RknHl8VG/f gw2eydChgVgmnT1hLA==
=fgPQ
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)