# Os-release Debian 11

**URL:** <https://discourse.pi-hole.net/t/os-release-debian-11/54779>\
**Category:** Help\
**Created:** [April 8, 2022, 10:38am UTC](https://discourse.pi-hole.net/t/os-release-debian-11/54779 "2022-04-08T10:38:18Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![MichaIng](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/michaing/32/13351_2.png) [@MichaIng](https://discourse.pi-hole.net/u/MichaIng)\
**Post date:** [April 13, 2022, 7:13pm UTC](https://discourse.pi-hole.net/t/os-release-debian-11/54779/9 "2022-04-13T19:13:47Z")

</div>

Thanks for the info. Interesting, I have quite some Bookworm systems, even 2 production servers here, and haven't faced any issues with whiptail yet.

I'll just try it in general and then with the Pi-hole installer in particular, after lastest `apt full-upgrade`: Interesting, the regular message box works:

```sh
whiptail --msgbox test 20 70

```

The DietPi wrapper works:

```sh
G_WHIP_MSG test

```

Running the DietPi installer however does not work:

```sh
curl -sSL https://install.pi-hole.net | PIHOLE_SKIP_OS_CHECK=true sudo -E bash

```

I have such a guess that it is due to STDIN being overwritten by the pipe (just verified this being the issue, indeed), similar how `stty size` cannot work when being called from a bash shell with a pipe, and why the idea came up to switch to static 70x20 whiptail dimensions in the Pi-hole installer, as with the pipe, terminal dimensions cannot be obtained anyway: [Hardcode whiptail dimensions to 20 rows and 70 chars width by MichaIng · Pull Request #4229 · pi-hole/pi-hole · GitHub](https://github.com/pi-hole/pi-hole/pull/4229)

Now `whiptail` seems to suffer from a similar issue. Probably there is a workaround possible to bind STDIN of the whiptail calls again to the actual input console, but otherwise the installer instead can be called like this, avoiding the pipe:

```bash
bash -c "$(curl -sSL https://install.pi-hole.net)"

```

respectively including sudo and skipping the OS check on Bookworm:

```bash
sudo PIHOLE_SKIP_OS_CHECK=true bash -c "$(curl -sSL https://install.pi-hole.net)"

```

EDIT: I'm actually wondering what caused this change. There was no upstream release but only a Debian build update since Bullseye: [https://metadata.ftp-master.debian.org/changelogs//main/n/newt/newt\_0.52.21-5\_changelog](https://metadata.ftp-master.debian.org/changelogs//main/n/newt/newt_0.52.21-5_changelog)

```auto
newt (0.52.21-5) unstable; urgency=medium

  * Standards-Version: 4.6.0
  * Use debhelper-compat 13
  * Use dh-sequence-python3 instead of --with python3, dh-python
  * Point Vcs-Git to debian/latest branch for DEP-14
  * Add d/gbp.conf to point to DEP-14 branches
  * Drop custom 'xz' compression d/source/options
  * Change stage1 build profile to nopython. Closes: #949721
  * B-D on python3-all-dbg
  * python.patch: Drop refs to obsolete pyversions

 -- Alastair McKinstry <mckinstry@debian.org> Tue, 07 Sep 2021 10:59:05 +0100

```

---

_[View the full topic](https://discourse.pi-hole.net/t/os-release-debian-11/54779)._