pbuilder-dist bullseye create fails

[Christophe Prud'homme]

the command

pbuilder-dist bullseye create

fails with the following error at the very end

I: redirecting /dev/ptmx to /dev/pts/ptmx
I: installing dummy policy-rc.d
Ign:1 http://security.debian.org bullseye/updates InRelease
Err:2 http://security.debian.org bullseye/updates Release
  404 Not Found [IP: 151.101.130.132 80]
Get:3 http://deb.debian.org/debian bullseye-proposed-updates InRelease [39.4 kB]
Hit:4 http://deb.debian.org/debian bullseye InRelease
Get:5 http://deb.debian.org/debian bullseye/non-free amd64 Packages [98.7 kB]
Get:6 http://deb.debian.org/debian bullseye/contrib amd64 Packages [51.0 kB]
Reading package lists...
E: The repository 'http://security.debian.org bullseye/updates Release' does not have a Release file.
I: unmounting dev/ptmx filesystem
I: unmounting dev/pts filesystem
I: unmounting dev/shm filesystem
I: unmounting proc filesystem
I: unmounting sys filesystem
I: cleaning the build env
I: removing directory /var/cache/pbuilder/build/2585888 and its subdirectories

[Mattia Rizzolo (mapreri)]

that's because starting with bullseye the security suite is named bullseye-security instead of bullseye/updates.

(not planning to write a patch myself in the short time, hopefully somebody else will…)

[Launchpad Janitor (janitor)]

This bug was fixed in the package ubuntu-dev-tools - 0.181

---------------
ubuntu-dev-tools (0.181) unstable; urgency=medium

  [ Logan Rosen ]
  * Fix a couple of remaining issues from the py2→py3 move.

  [ Krytarik Raido ]
  * Fix typo in the logging configuration.

  [ Dan Streetman ]
  * pbuilder: Handle debian change from /updates to -security. LP: #1916633
    Starting in bullseye, the security suite is -security instead of /updates.
  * backportpackage: Don't use SourcePackage() directly. Closes: #983854
    As the warning from 2010 says, don't use this class directly.

  [ Balint Reczey ]
  * mk-sbuild:
    + Use eatmydata only with the dpkg command.
      Eatmydata wrapping the build as well could break tests.
      Thanks to Julian Andres Klode for suggesting this solution
    + Use eatmydata by default.
      Since only the dpkg is wrapped in eatmydata it should be the safe and
      fast default. Eatmydata is widely used around apt thus it should be a
      serious bug if a package can't be installed with eatmydata in use.

  [ Marco Trevisan (Treviño) ]
  * doc/mk-sbuild.1: Add documentation for --debootstrap-proxy and
    DEBOOTSTRAP_PROXY. LP: #1926166

 -- Mattia Rizzolo <email address hidden> Sun, 02 May 2021 19:56:48 +0200