Apt update warning in Parrotsec

I am using latest version of Parrotsec and while updating by using command apt update i found this error:
Get:1 https://deb.parrotsec.org/parrot parrot InRelease [14.6 kB]
E: Repository ‘https://deb.parrotsec.org/parrot parrot InRelease’ changed its ‘Suite’ value from ‘stable’ to ‘parrot’
E: Repository ‘https://deb.parrotsec.org/parrot parrot InRelease’ changed its ‘Codename’ value from ‘parrot’ to ‘stable’
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
Do you want to accept these changes and continue updating from this repository? [y/N]

Why is this happening? What is the actual reason behind it?

1 Like

Remove this repo & add from

I saw this about 10-hrs to late…

exactly what was changed by confirming this change and do we need to change anything back to fix it?

Can confirm I had the same message. The package manager seemed to work fine after that, but some tools were removed by autoremove

Could a dev please comment on this change?

Some tools removed by running apt autoremove

Because of ,i think you remove depend paclage of any meta package

But why is this happening? What’s the reason behind it? This didn’t used to happen before.

1 Like

accchech was removed during such an autoremove. acccheck is not a dependency on anything afaik.

@Dark_hunter is right, I’d also like to know what the reason is behind this change. For all we know someone may be tampering with the archives.


Actually codename changed in conf/distributions by palinuro
Wait for a while , merging with devuvan repo

Parrot dev teams ,planning for make repo for support

Accheck has been removed automatically long time ago. It has nothing to do with this repo change.

Hello all- new to the board.

Checking in on this issue before running updates- can anyone confirm if these changes were legitimate / intended?

Thanks in advance!

1 Like

Any news on this issue

I also have this problems and when i choose to accept the change and update now i got the rolling repo, and it constantly updating package for me so should i update it or just wait. oh and also it said that i have this:
Conflicting distribution: https://deb.parrotsec.org/parrot parrot InRelease (expected parrot but got rolling)

It is because the code name was changed on repository and it is not a bug so no need to care about this.

1 Like

buon giorno!

( thank you very much for the hard work and help on parrot os to every one )

but …same problem here : after updating with sudo parrot-upgrade… I got at first the ‘constantly updating package’ problem and then today an unexpected ‘synaptic’ error … please help me to understand what I should / can do , because one week ago everything was ok and working very well for me …

W: Distribution conflict: https://deb.parrotsec.org/parrot stable InRelease (stable expected, but getting rolling)

E: The value “parrot” is invalid for APT::Default-Release, because such a release is not available in the package sources.
E: _cache->open() failed, please report. <<

actually Synaptic keeps crashing and stopped working !
and furthermore I got quite confused about what to add or remove to the sources list now , beg your pardon, should I simply wait ??

└──╼ $inxi -Fxz
Host: parrot Kernel: 4.19.37-parrot1-amd64 x86_64
bits: 64 compiler: gcc v: 8.3.0 Desktop: MATE 1.20.4
Distro: Parrot GNU/Linux 4.7 base: Debian parrot

my best wishes to the team and community, I hope you have some good summerdays anyway.

I had the synaptic error as well, the solution I used was to uncheck the last three repos. Then change the Distribution value to “rolling” all my packages are still included in the repo and updates fine after that. I believe you can just change the values of the other repos as well (to what the error message specifies) if those are needed. The repo list is under setting->repositories. Hope that help!

Is it occur any problem if i change distribution value stabe to rolling?
What exactly mean by different distribution value like parrot stable and rolling?

No, from my understanding it is just a config change. The uri/url is still the same so it is getting the packages from the same server location just under a different distribution value. That is my understanding at least a dev might be able to tell you better. If you want to no more about the debian repositories in general I did a quick search in case you want to dig a little deeper. https://www.jfrog.com/confluence/display/RTF/Debian+Repositories

I don’t know why the change happened but you may want to hold off until there is an explanation of why this change was done as many on this thread have been asking. In case you have security concerns.

1 Like

Still waiting on a DEV to say something about this. I have the same issue and since this is my working OS I really need to know how to handle this issue…