Why does running "apug" offer to downgrade some packages?

No, I don't think I will:

The following packages will be DOWNGRADED:
  dolphin-compat-notinstalled elive-daemons elive-tools hebernate
  konqueror-compat-notinstalled nautilus-compat-notinstalled
  pcmanfm-compat-notinstalled smb-admin thunar-audio-converter
  usb-bootable-elive warning-messages
274 upgraded, 7 newly installed, 11 downgraded, 0 to remove and 0 not upgraded.
Need to get 615 MB of archives.
After this operation, 1,398 kB disk space will be freed.
Do you want to continue? [Y/n]

Updating eltrans (again) does the similar thing:

~ ❯❯❯ api elive-tools eltrans
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
  update-notifier-common
The following packages will be upgraded:
  eltrans
The following packages will be DOWNGRADED:
  elive-tools
1 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 284 not upgraded.
Need to get 709 kB of archives.
After this operation, 57.3 kB of additional disk space will be used.
Do you want to continue? [Y/n]

SHIT SHIT SHIT SHIT I accidentally pressed enter instead of typing n

Now elive-tools is down to 3.0.6

How can i fix this?!

dpkg: warning: downgrading elive-tools from 3.8.12+git21aae632a-6buster11 to 3.0.6+202006100517+git79675bf323-6buster11
(Reading database ... 202917 files and directories currently installed.)
Preparing to unpack .../elive-tools_3.0.6+202006100517+git79675bf323-6buster11_all.deb ...
Unpacking elive-tools (3.0.6+202006100517+git79675bf323-6buster11) over (3.8.12+git21aae632a-6buster11) ...
Setting up elive-tools (3.0.6+202006100517+git79675bf323-6buster11) ...
Processing triggers for mime-support (3.62) ...
Processing triggers for desktop-file-utils (0.23-4) ...

(EDIT: Eltrans actually seems to work with this downgrade, @Thanatermesis can you figure out why?)

EDIT 2: I got logged in all right, but this zenity box appeared when I tried to proofread original english sentences:

Sorry! At the moment only a few people is allowed to correct the original messages in English. We do this to simply ensure the best quality of the messages for the Elive applications. You can found more info about this topic in our Forums.

(EDIT 3: Which do i click: myspell-fr or myspell-fr-gut??)

The "downgrade" has to do with the version numbers used i.e a downgrade is an "upgrade".
So don't do N , just hit Enter for the defaults.

1 Like

ohhhhhh

thats what i did:

does anyone know?

Downgrades are configured to be perfectly safe in elive :slight_smile:

by other side I think you have a different issue @TheTechRobo , can you show me the result of this?:

grep "^deb" /etc/apt/sources.list.d/*

BTW: eltrans account is not yet enabled, which means still no login account for dev website, sorry, im very saturated of tasks while trying to finish eltrans, Im having other issues around that needs to be fixed too

I don't think it's a different issue. I see the same quite often with only the standard repos in use and mostly in relation to specific elive packages .... looks like the git numbering is confusing the repo data base but never really looked into it deeply.

yes I think it is :thinking:, in fact I just added an extra feature on elive-health that warns the user about a (this) specific issue, let's wait the answer of @TheTechRobo about the repos and i will tell more about that :happy:

~ ❯❯❯     grep "^deb" /etc/apt/sources.list.d/*
/etc/apt/sources.list.d/aaa-elive.list:deb http://repo.buster.elive.elivecd.org/ buster main elive efl games ports fixes drivers multimedia non-free
/etc/apt/sources.list.d/aaa-elive.list.save:deb http://repo.buster.elive.elivecd.org/ buster main elive efl games ports fixes drivers multimedia non-free
/etc/apt/sources.list.d/audio-recorder-ubuntu-ppa-focal.list:deb http://ppa.launchpad.net/audio-recorder/ppa/ubuntu focal main
/etc/apt/sources.list.d/audio-recorder-ubuntu-ppa-focal.list.save:deb http://ppa.launchpad.net/audio-recorder/ppa/ubuntu focal main
/etc/apt/sources.list.d/debian.list:deb http://deb.debian.org/debian buster main contrib non-free
/etc/apt/sources.list.d/debian.list:deb http://deb.debian.org/debian-security buster/updates main contrib non-free
/etc/apt/sources.list.d/debian.list:deb http://deb.debian.org/debian buster-backports main contrib non-free
/etc/apt/sources.list.d/debian.list.save:deb http://deb.debian.org/debian buster main contrib non-free
/etc/apt/sources.list.d/debian.list.save:deb http://deb.debian.org/debian-security buster/updates main contrib non-free
/etc/apt/sources.list.d/debian.list.save:deb http://deb.debian.org/debian buster-backports main contrib non-free
/etc/apt/sources.list.d/ggg-marillat.list:deb http://www.deb-multimedia.org buster main non-free
/etc/apt/sources.list.d/ggg-marillat.list.save:deb http://www.deb-multimedia.org buster main non-free
/etc/apt/sources.list.d/mysql.list:deb http://repo.mysql.com/apt/debian/ buster mysql-apt-config
/etc/apt/sources.list.d/mysql.list:deb http://repo.mysql.com/apt/debian/ buster mysql-8.0
/etc/apt/sources.list.d/mysql.list:deb http://repo.mysql.com/apt/debian/ buster mysql-tools
/etc/apt/sources.list.d/mysql.list:deb-src http://repo.mysql.com/apt/debian/ buster mysql-8.0
/etc/apt/sources.list.d/mysql.list.save:deb http://repo.mysql.com/apt/debian/ buster mysql-apt-config
/etc/apt/sources.list.d/mysql.list.save:deb http://repo.mysql.com/apt/debian/ buster mysql-8.0
/etc/apt/sources.list.d/mysql.list.save:deb http://repo.mysql.com/apt/debian/ buster mysql-tools
/etc/apt/sources.list.d/mysql.list.save:deb-src http://repo.mysql.com/apt/debian/ buster mysql-8.0
/etc/apt/sources.list.d/vivaldi.list:deb http://repo.vivaldi.com/stable/deb/ stable main
/etc/apt/sources.list.d/vivaldi.list.save:deb http://repo.vivaldi.com/stable/deb/ stable main
~ ❯❯❯

lmao look what discourse is saying:

Let others join the conversation

This topic is clearly important to you – you've posted more than 34% of the replies here.
It could be even better if you got other people space to share their points of view, too. Can you invite them over?

Yeah, you do have a repo mess there.
OTH running "apug" I'm getting this a lot lately:

dpkg: warning: downgrading enlightenment from 0.24.1+18+gita175903a21-6buster18 to 0.24.1+18+git653a456a02-6buster18
Preparing to unpack .../2-enlightenment_0.24.1+18+git653a456a02-6buster18_amd64.deb ...
update-alternatives: using /usr/bin/starte16 to provide /usr/bin/x-window-manager (x-window-manager) in auto mode
Unpacking enlightenment (0.24.1+18+git653a456a02-6buster18) over (0.24.1+18+gita175903a21-6buster18) ...
dpkg: warning: downgrading enlightenment-data from 0.24.1+18+gita175903a21-6buster18 to 0.24.1+18+git653a456a02-6buster18
Preparing to unpack .../3-enlightenment-data_0.24.1+18+git653a456a02-6buster18_all.deb ...
Unpacking enlightenment-data (0.24.1+18+git653a456a02-6buster18) over (0.24.1+18+gita175903a21-6buster18) ...
dpkg: warning: downgrading terminology-data from 3.8.13+1.7.0+git668c506a1-6buster13 to 3.8.13+1.7.0+git2b5f698c9-6buster13
Preparing to unpack .../4-terminology-data_3.8.13+1.7.0+git2b5f698c9-6buster13_all.deb ...
Unpacking terminology-data (3.8.13+1.7.0+git2b5f698c9-6buster13) over (3.8.13+1.7.0+git668c506a1-6buster13) ...
dpkg: warning: downgrading terminology:amd64 from 3.8.13+1.7.0+git668c506a1-6buster13 to 3.8.13+1.7.0+git2b5f698c9-6buster13
Preparing to unpack .../5-terminology_3.8.13+1.7.0+git2b5f698c9-6buster13_amd64.deb ...

Which, as can clearly be seen is purely git numbering related.

I have no idea what any of this means lmao, but there are a few things (e.g. mysql) that i could gte rid of if i knew how

"sudo add-apt-repository -r mysql.list"

or any other repo name which is obsolete in your opinion....the -r flag is for removal.

Another sure fire way is to do an upgrade with an Elive.iso image....that will purge all 3rd party repositories. :madness:

1 Like

exactly :slight_smile: and he should have received a notification by elive-health telling him :wink: that was the feature I added when i said that "he should have a different problem laying there":

image

you should have seen this message @TheTechRobo, unless your repos are so broken that you dont have an updated elive-health :rofl2:

in short, his issue was serious: the system wanted to install elive-tools from the version of elive 3.0 (which is extremely older! making his entire OS to be pretty messed up, since so many things on elive depend of elive-tools). So Elive can downgrade without issues, but not if the downgrade is to an unexpected version

by other side, I don't see anything wrong on its repositories related to that version of elive-tools (from 3.0 / wheezy), how / why its wanted to downgrade to this version? :thinking:

@TheTechRobo show me the result of this: appo elive-tools

yeah is the only and best way to solve it, to repair the repos and the entire system (packages, states, conf files, etc)

i think elive-health should have an even better / improved way to detect a possibly wrong system :thinking: not sure which other checks can have, but at least this repo check is a good one!

Again:

It isn't downgrading .... dpkg is just calling it that because of the attached git numbering.
Look at the little list I posted above.
I'm surprised you never noticed that. :shocked:

Although I'll give you that it's strange that it wants to downgrade to 3.0.6. OTH @TheTechRobo is a barrel of surprises sometimes. :cheerleader:

1 Like

yeah, thats correct for these packages (and thats why the numbering includes other values previously like the version-tag, datetime-based values was buggy in the past and thats why they are not used (but this issue may have been fixed recently, not tried yet), in fact only a few packages uses datetime based values like the installer: 3.8.13+202006131742+git0285b6e0cf-6buster12

yes i did :slight_smile: and that's why the elive repos are configured to accept downgrades, also, a downgrade is not a wrong thing at all, it just means "different version than the one you have installed", which older or newer, people should always use "what has been uploaded", so in short: it avoids any issues / making everything working by default

by other side, if datetime based values are really fixed and packages uses that now, downgrades will be not needed (but at the same time, no need to remove that option enabled)

anyways, the real problem I was talking about was not about -these- downgrades (which as explained, they are perfectly fine), but about the strange and massive downgrade of elive-tools:

exactly that :slight_smile:

downgrading to 3.0.6 makes no sense, he used the wheezy (elive 3.0 ) repo on his beta version, everything will break up

also, there's no sense to downgrade to 3.0.6 unless he removed the repo of the beta versions (buster), in other words: if there's elive-tools in versions 3.0.6something AND 3.8.13something, it should not want to use the one from 3.0.6*

@TheTechRobo so what shows on you "appo elive-tools" ? :slight_smile:

in fact I think that the only reason why they exist the concept itself is because users (in debian-based systems) were able to play with the repos including everything at their own risk, and so the downgrade concept simply took care to not allow downgrades from a newer verssion of debian (package) to an older one :thinking:

Looking at his repo output it seems that the "vivaldi" repository pulled in Stable.
I hadn't noticed that before. :shocked:

That actually shouldn't be happening or even possible, should it?

well, apug will take too long so i had to do apui elive-* but elive-desktop-wrapper requires e17 but e17 cant be installed so...i have to type every single package manually so apt wont error out...any ideas on how to fix ?

still dont know, i dont have access to the pc rn but ill get you the output asap :slight_smile:

well, apug will take too long so i had to do apui elive-* but elive-desktop-wrapper requires e17 but e17 cant be installed so...i have to type every single package manually so apt wont error out...any ideas on how to fix ?

EDIT— I just saw — when i run apug it says that like fifteen packages would be downgraded...not sure if its my repo mess or what, but i dont like it...
i think that if sw isn't in the repo i'll either download a .deb or compile it myself. :madness: