If repos are not compatible in a release upgrade, tell the client which repos are broken

[pop-os]

If repos are not compatible in a release upgrade, tell the client which repos are broken

[brs17]

I had added pop-os/session#7 which should be a ppa that only exists in cosmic and not disco. I was never prompted about this ppa being disabled and when I finished the upgrade, sources were not updated. Checking repoman, most of the settings were still unchecked and there were some Ubuntu repos I'd never seen before:

[mmstick]

Do you have logs from journalctl -u pop-upgrade?

[mmstick]

This is what I get with the firmware remote:

[brs17]

I do not have the system in that state anymore, I will (attempt) to recreate the issue again.

[brs17]

I now see the error as well by adding staging/firmware.

[brs17]

@mmstick testing upgrade from 18.04->19.04 via gnome-control-center, I am prompted twice(for the same repository) with the "Unsupported repository" pop-up. I was not selecting the checkbox.

Logs:
journal.log

[mmstick]

The logs detail that it never received the RepoModify signal. Client say anything?

[brs17]

All I did was press Accept. Next time I'm going through the upgrade, I'll show you.

[mmstick]

Running GCC from a terminal with env G_MESSAGES_DEBUG=all gnome-control-center will give useful logs for client-side interactions.

[mmstick]

If building from source, running it through valgrind is also useful for detecting memory leaks / bad allocations and frees.

[brs17]

I had added pop-os/session#7 which should be a ppa that only exists in cosmic and not disco. I was never prompted about this ppa being disabled and when I finished the upgrade, sources were not updated. Checking repoman, most of the settings were still unchecked and there were some Ubuntu repos I'd never seen before:

This still seems to be an issue after the upgrade I just did (through the recovery partition)

[brs17]

Going to close this as discussion has moved to #34