# Upgrade to Bullseye

**URL:** https://discuss.freedombox.org/t/upgrade-to-bullseye/1664
**Category:** Support
**Created:** [August 16, 2021, 2:39pm UTC](https://discuss.freedombox.org/t/upgrade-to-bullseye/1664 "2021-08-16T14:39:31Z")
**Posts on this page:** 6
**Page:** 2

<div class="post-metadata">

### Author: ![jvalleroy](https://discuss.freedombox.org/user_avatar/discuss.freedombox.org/jvalleroy/32/331_2.png) [@jvalleroy](https://discuss.freedombox.org/u/jvalleroy)
#### Post date: [August 26, 2021, 11:55am UTC](https://discuss.freedombox.org/t/upgrade-to-bullseye/1664/21 "2021-08-26T11:55:54Z")

</div>

> [@Avron](#):
>
> Should I do something to avoid the “no such file or directory” that sounds a little worrying?

I think these locale errors are harmless. If you want to avoid them, you can run `sudo dpkg-reconfigure locales` and select the locale(s) you want to generate.

[https://wiki.debian.org/Locale#Standard](https://wiki.debian.org/Locale#Standard)

---

<div class="post-metadata">

### Author: ![dgj](https://discuss.freedombox.org/letter_avatar_proxy/v4/letter/d/7c8e57/32.png) [@dgj](https://discuss.freedombox.org/u/dgj)
#### Post date: [September 2, 2021, 12:24pm UTC](https://discuss.freedombox.org/t/upgrade-to-bullseye/1664/22 "2021-09-02T12:24:23Z")

</div>

I had the same problem and ran the following command:

`$ sudo apt remove fuse && sudo apt install fuse3 && sudo apt upgrade`

Although I got the same warnings about locales, everything went smoothly, so I ran unattended-upgrade:

`$ sudo unattended-upgrade -d`

As a result, `libntfs-3g883` was removed, and several packages are kept back.

> Package at-spi2-core has a higher version available, checking if it is from an allowed origin and is not pinned down.  
> Package batctl has a higher version available, checking if it is from an allowed origin and is not pinned down.  
> Package cockpit has a higher version available, checking if it is from an allowed origin and is not pinned down.  
> Package cockpit-bridge has a higher version available, checking if it is from an allowed origin and is not pinned down.  
> Package cockpit-networkmanager has a higher version available, checking if it is from an allowed origin and is not pinned down.  
> Package cockpit-packagekit has a higher version available, checking if it is from an allowed origin and is not pinned down.  
> Package cockpit-pcp has a higher version available, checking if it is from an allowed origin and is not pinned down.  
> Package cockpit-storaged has a higher version available, checking if it is from an allowed origin and is not pinned down.  
> Package cockpit-system has a higher version available, checking if it is from an allowed origin and is not pinned down.  
> Package cockpit-ws has a higher version available, checking if it is from an allowed origin and is not pinned down.  
> Package freedombox-doc-en has a higher version available, checking if it is from an allowed origin and is not pinned down.  
> Package freedombox-doc-es has a higher version available, checking if it is from an allowed origin and is not pinned down.  
> Package guile-2.2-libs has a higher version available, checking if it is from an allowed origin and is not pinned down.  
> Package guile-2.2-libs is kept back because a related package is kept back or due to local apt\_preferences(5).  
> Package libatspi2.0-0 has a higher version available, checking if it is from an allowed origin and is not pinned down.  
> Extracting content from /var/log/unattended-upgrades/unattended-upgrades-dpkg.log since 2021-09-02 14:21:30

Nevertheless, it appears I am now running v. 21.7. Should there be any cause for concern?

---

<div class="post-metadata">

### Author: ![njoseph](https://discuss.freedombox.org/user_avatar/discuss.freedombox.org/njoseph/32/17_2.png) [@njoseph](https://discuss.freedombox.org/u/njoseph)
#### Post date: [September 2, 2021, 3:10pm UTC](https://discuss.freedombox.org/t/upgrade-to-bullseye/1664/23 "2021-09-02T15:10:35Z")

</div>

My Pioneer FreedomBox is not upgrading beyond `21.4.4~bpo10+1` though it managed to dist-upgrade to Bullseye successfully.

```auto
The following packages have been kept back:
  freedombox guile-2.2-libs sshfs zile

```

I wonder if this is also related to fuse3.

---

<div class="post-metadata">

### Author: ![Avron](https://discuss.freedombox.org/letter_avatar_proxy/v4/letter/a/a9adbd/32.png) [@Avron](https://discuss.freedombox.org/u/Avron)
#### Post date: [September 2, 2021, 8:52pm UTC](https://discuss.freedombox.org/t/upgrade-to-bullseye/1664/24 "2021-09-02T20:52:42Z")

</div>

> [@njoseph](#):
>
> I wonder if this is also related to fuse3.

For freedombox, guile-2.2-libs and sshfs, probably. For zile I don’t know, I don’t have it. You can check with “apt -s install packageX” for each upgradable package.

---

<div class="post-metadata">

### Author: ![lifeform](https://discuss.freedombox.org/letter_avatar_proxy/v4/letter/l/7ab992/32.png) [@lifeform](https://discuss.freedombox.org/u/lifeform)
#### Post date: [September 2, 2021, 9:32pm UTC](https://discuss.freedombox.org/t/upgrade-to-bullseye/1664/25 "2021-09-02T21:32:16Z")

</div>

Regarding packages kept back after upgrade to bullseye, see [issue #2103](https://salsa.debian.org/freedombox-team/freedombox/-/issues/2103)

---

<div class="post-metadata">

### Author: ![dgj](https://discuss.freedombox.org/letter_avatar_proxy/v4/letter/d/7c8e57/32.png) [@dgj](https://discuss.freedombox.org/u/dgj)
#### Post date: [September 3, 2021, 8:06am UTC](https://discuss.freedombox.org/t/upgrade-to-bullseye/1664/26 "2021-09-03T08:06:41Z")

</div>

@lifeform thanks! Is it recommended then to run `sudo apt full-upgrade`? Also, no where does it mention `libntfs-3g883` being removed as it was on my installation 😕

I am hesitant to upgrade from the command line unless necessary. In the past I have had prompts regarding configuration files and I did not know how to answer, resulting in a broken installation.

[Previous page](https://discuss.freedombox.org/t/upgrade-to-bullseye/1664.md?page=1)
