# Switching to rolling (testing) release

**URL:** https://discuss.freedombox.org/t/switching-to-rolling-testing-release/222
**Category:** Hardware Owners Support
**Created:** [June 22, 2019, 5:05pm UTC](https://discuss.freedombox.org/t/switching-to-rolling-testing-release/222 "2019-06-22T17:05:32Z")
**Posts on this page:** 1
**Showing post:** 7

<div class="post-metadata">

### Author: ![Sunil](https://discuss.freedombox.org/user_avatar/discuss.freedombox.org/sunil/32/8_2.png) [@Sunil](https://discuss.freedombox.org/u/Sunil)
#### Post date: [July 8, 2019, 6:29pm UTC](https://discuss.freedombox.org/t/switching-to-rolling-testing-release/222/7 "2019-07-08T18:29:24Z")

</div>

> I have three follow-up questions:
> 
> (1) When manually running updates (via ssh),
> 
> $ sudo apt update && sudo apt upgrade
> 
> I get the following message:
> 
> […]  
> E: The repository ‘tor+http://security.debian.org/debian-security  
> testing/updates Release’ no longer has a Release file.  
> N: Updating from such a repository can’t be done securely, and is  
> therefore disabled by default.  
> […]
> 
> Is not having a Release file for debian-security an issue? If yes, can  
> you provide some instructions for how to fix it? If not, can I safely  
> ignore the message?

I believe this security release file will become available eventually  
(in perhaps a few days). For now, it is best to keep the line and  
continue with upgrade (if the upgrade itself does not fail). This way  
you won’t forget to add it back when it does become available.

BTW, you may have to run (instead of regular apt update):

apt --allow-releaseinfo-change update

> (2) I noticed that buster-backports was enabled in  
> /etc/apt/sources.list.d/freedombox2.list, and since I want to have a  
> rolling release I have commented it out.
> 
> $ sudo nano /etc/apt/sources.list.d/freedombox2.list
> 
> # This file is managed by FreedomBox, do not edit.  
> # Allow carefully selected updates to ‘freedombox’ from backports.
> 
> #deb tor+http://deb.debian.org/debian buster-backports main  
> #deb-src tor+http://deb.debian.org/debian buster-backports main
> 
> Is this correct?

Yes. If you are going to be using ‘testing’ you won’t need the backports  
repositories. Testing will always contain same or later versions of  
FreedomBox and other software it depends on. Keeping those should be  
entirely harmless too.

> (3) Now that Buster has moved to stable, when can users expect that  
> Plinth will update beyond v. 19.2?

Sometime soon, automatic transition of packages will allowed from  
unstable to testing. When that happens, freedombox (and transitional  
plinth package) 19.2 will become available in testing (or perhaps it  
might take 2 days).

For beyond, here is the plan:

- freedombox 19.11 will be uploaded tomorrow to experimental only (for now).
- freedombox 19.2 to become available in testing (very soon).
- freedombox 19.2 will be uploaded to backports.
- freedombox 19.11 will be uploaded to unstable.
- freedombox 19.11 to become available in testing 2 days after that.
- freedombox 19.11 may be uploaded to backports based on confidence.

Last two steps will repeat every 3 weeks for each release.

---

_[View the full topic](https://discuss.freedombox.org/t/switching-to-rolling-testing-release/222)._