hi, everybody . . .
since pretty well forever i've had the TDE repos in my list such that updating has been no problem. but recently -- well, here:
E: The repository 'http://ppa.launchpad.net/frederik-elwert/transcribe/ubuntu bionic Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. E: Repository 'http://mirror.ppa.trinitydesktop.org/trinity/trinity-r14.0.0/ubuntu bionic InRelease' changed its 'Origin' value from 'LP-PPA-trinity-trinity-r14.0.0' to 'trinitydesktop.org' E: Repository 'http://mirror.ppa.trinitydesktop.org/trinity/trinity-r14.0.0/ubuntu bionic InRelease' changed its 'Label' value from 'Trinity Desktop Environment R14.0.0' to 'Trinity Desktop Environment R14.0.x' E: Repository 'http://mirror.ppa.trinitydesktop.org/trinity/trinity-r14.0.0/ubuntu bionic InRelease' changed its 'Suite' value from 'bionic' to '' N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details. E: Repository 'http://mirror.ppa.trinitydesktop.org/trinity/trinity-builddeps-r14.0.0/ubunt... bionic InRelease' changed its 'Origin' value from 'LP-PPA-trinity-trinity-builddeps-r14.0.0' to 'trinitydesktop.org' E: Repository 'http://mirror.ppa.trinitydesktop.org/trinity/trinity-builddeps-r14.0.0/ubunt... bionic InRelease' changed its 'Label' value from 'Trinity Build Dependencies R14.0.0' to 'Trinity Build Dependencies R14.0.x' E: Repository 'http://mirror.ppa.trinitydesktop.org/trinity/trinity-builddeps-r14.0.0/ubunt... bionic InRelease' changed its 'Suite' value from 'bionic' to '' N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
[end of quote]
has something changed? looking on the TDE website, i see that my repository listings appear to be correct.
On Saturday 01 February 2020 13:59:48 dep wrote:
hi, everybody . . .
since pretty well forever i've had the TDE repos in my list such that updating has been no problem. but recently -- well, here:
E: The repository 'http://ppa.launchpad.net/frederik-elwert/transcribe/ubuntu bionic Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. E: Repository 'http://mirror.ppa.trinitydesktop.org/trinity/trinity-r14.0.0/ubuntu bionic InRelease' changed its 'Origin' value from 'LP-PPA-trinity-trinity-r14.0.0' to 'trinitydesktop.org' E: Repository 'http://mirror.ppa.trinitydesktop.org/trinity/trinity-r14.0.0/ubuntu bionic InRelease' changed its 'Label' value from 'Trinity Desktop Environment R14.0.0' to 'Trinity Desktop Environment R14.0.x' E: Repository 'http://mirror.ppa.trinitydesktop.org/trinity/trinity-r14.0.0/ubuntu bionic InRelease' changed its 'Suite' value from 'bionic' to '' N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details. E: Repository 'http://mirror.ppa.trinitydesktop.org/trinity/trinity-builddeps-r14.0.0/ubu ntu bionic InRelease' changed its 'Origin' value from 'LP-PPA-trinity-trinity-builddeps-r14.0.0' to 'trinitydesktop.org' E: Repository 'http://mirror.ppa.trinitydesktop.org/trinity/trinity-builddeps-r14.0.0/ubu ntu bionic InRelease' changed its 'Label' value from 'Trinity Build Dependencies R14.0.0' to 'Trinity Build Dependencies R14.0.x' E: Repository 'http://mirror.ppa.trinitydesktop.org/trinity/trinity-builddeps-r14.0.0/ubu ntu bionic InRelease' changed its 'Suite' value from 'bionic' to '' N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
[end of quote]
has something changed? looking on the TDE website, i see that my repository listings appear to be correct.
Yup, problems here, as well. (But now they seem to have been resolved.) I tried to upgrade, got a BIG list of packages, mostly all TDE, along with some dependencies from Debian/Devuan; when I tried to download and install, I got some weird messages.
Just tried again (apt-get update && apt-get upgrade), and now it seems to be working again ... at least for me. Packages have all downloaded.
Bill
On Saturday 01 of February 2020 22:59:48 dep wrote:
hi, everybody . . .
since pretty well forever i've had the TDE repos in my list such that updating has been no problem. but recently -- well, here:
E: The repository 'http://ppa.launchpad.net/frederik-elwert/transcribe/ubuntu bionic Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. E: Repository 'http://mirror.ppa.trinitydesktop.org/trinity/trinity-r14.0.0/ubuntu bionic InRelease' changed its 'Origin' value from 'LP-PPA-trinity-trinity-r14.0.0' to 'trinitydesktop.org' E: Repository 'http://mirror.ppa.trinitydesktop.org/trinity/trinity-r14.0.0/ubuntu bionic InRelease' changed its 'Label' value from 'Trinity Desktop Environment R14.0.0' to 'Trinity Desktop Environment R14.0.x' E: Repository 'http://mirror.ppa.trinitydesktop.org/trinity/trinity-r14.0.0/ubuntu bionic InRelease' changed its 'Suite' value from 'bionic' to '' N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details. E: Repository 'http://mirror.ppa.trinitydesktop.org/trinity/trinity-builddeps-r14.0.0/ ubuntu bionic InRelease' changed its 'Origin' value from 'LP-PPA-trinity-trinity-builddeps-r14.0.0' to 'trinitydesktop.org' E: Repository 'http://mirror.ppa.trinitydesktop.org/trinity/trinity-builddeps-r14.0.0/ ubuntu bionic InRelease' changed its 'Label' value from 'Trinity Build Dependencies R14.0.0' to 'Trinity Build Dependencies R14.0.x' E: Repository 'http://mirror.ppa.trinitydesktop.org/trinity/trinity-builddeps-r14.0.0/ ubuntu bionic InRelease' changed its 'Suite' value from 'bionic' to '' N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
[end of quote]
has something changed? looking on the TDE website, i see that my repository listings appear to be correct.
I don't know if you're just waking up from winter sleep, but you can read:
http://trinity-devel.pearsoncomputing.net/?0::16128
Cheers :)
said Slávek Banko:
| I don't know if you're just waking up from winter sleep, but you can | read: | | http://trinity-devel.pearsoncomputing.net/?0::16128 | | Cheers :)
Thanks, I did. The judges would also have accepted "Use apt instead of apt-get, because apt prompts you to approve the repository changes unlike apt-get, which simply throws an error."
Another, weirder issue: after the upgrade and a reboot, the machine goes to GDM instead of TWM, which worked just fine before the upgrade.
On Monday 03 of February 2020 00:02:16 dep wrote:
said Slávek Banko: | I don't know if you're just waking up from winter sleep, but you can | read: | | http://trinity-devel.pearsoncomputing.net/?0::16128 | | Cheers :)
Thanks, I did. The judges would also have accepted "Use apt instead of apt-get, because apt prompts you to approve the repository changes unlike apt-get, which simply throws an error."
Another, weirder issue: after the upgrade and a reboot, the machine goes to GDM instead of TWM, which worked just fine before the upgrade.
Yes, for some reason not yet known, it may happen that during the upgrade it may switch to another DM if another DM is installed.
You can use dpkg-reconfigure tdm-trinity to switch back. Or uninstall another DM if not needed.
Cheers
said Slávek Banko:
| > Another, weirder issue: after the upgrade and a reboot, the machine | > goes to GDM instead of TWM, which worked just fine before the upgrade. | | Yes, for some reason not yet known, it may happen that during the | upgrade it may switch to another DM if another DM is installed. | | You can use dpkg-reconfigure tdm-trinity to switch back. Or uninstall | another DM if not needed.
Thanks again. That's what I did; mostly wanted to kind of report it in case a.) it's a strange bug or b.) I had broken something else! (And as always, the TWM/TDM confusion is mine.)
-
dep -
Slávek Banko -
William Morder via trinity-users