MX Linux Forum

My points about the conflicting packages still stand.

This sort of thing really needs to be with the apt-notifier package itself. Reduces the possibility of conflicts later. But also affects all installations.

dolphin_oracle wrote: Tue Dec 26, 2023 5:26 pm My points about the conflicting packages still stand.

This sort of thing really needs to be with the apt-notifier package itself. Reduces the possibility of conflicts later. But also affects all installations.

That's the point, if that's only for rpi, don't think to put this into apt-notifier package only for rpi.

Maybe you mean to create an extra package e.g like apt-notifier-defaults-rpi with only just one rpi conf file holding enabled nala option out of apt-notifier sources?

fehlix wrote: Tue Dec 26, 2023 6:42 pm Maybe you mean to create an extra package e.g like apt-notifier-defaults-rpi with only just one rpi conf file holding enabled nala option out of apt-notifier sources?

Not really no.

My only thought is that if I put such a configuration in one of the pi packages and then later we decide to use such a config blanket across all releases then the potential for a package conflict exists.

This would be mitigated by updating the packages at the same time, to remove the conflict from the pi specific package. This requires remembering to do that.


Right now I don’t think there are such conflicts.

dolphin_oracle wrote: Tue Dec 26, 2023 7:48 pm

fehlix wrote: Tue Dec 26, 2023 6:42 pm Maybe you mean to create an extra package e.g like apt-notifier-defaults-rpi with only just one rpi conf file holding enabled nala option out of apt-notifier sources?

Not really no.

My only thought is that if I put such a configuration in one of the pi packages and then later we decide to use such a config blanket across all releases then the potential for a package conflict exists.

This would be mitigated by updating the packages at the same time, to remove the conflict from the pi specific package. This requires remembering to do that.


Right now I don’t think there are such conflicts.

We could have nala enabled within a package for RPi only
e.g. like
apt-notifier-defaults-rpi_23.12.01_arm64.deb
with a config item:
/etc/apt-notifier/apt-notifier.conf.d/apt-notifier-rpi.conf

In case we want enable nala for other architectures
we can just enable the default within leading package apt-notifier

In case we want to revoke the default,
we could just have apt-notifier-defaults-rpi removed with
a control directive in apt-notifier (may be "Conflicts:")
or update with nala=false.

So yes I see the concerns, but not really seeing conflicts.
that's just an update of one or both packages, to get the defaults adjusted,
in case we want to.
+++EDIT+++
To get out of the /etc/conf directrory in order to not have it as a conffile,
we could have the rpi spcific file within one of other directories
e.g like this:
/usr/share/apt-notifier/conf/apt-notifier.conf.d/05_apt-notifier-rpi.conf
which would make a normal auto-removal also clean the file,
instead of only purge.

There is a rc2.1 img up now with all changes suggested to date.

No ellipses

Nala for updater

Downloaded, installed and booted up to desktop with no problem. Will take a careful look around this morning.

Only thing I noticed in a 2-minute drill was a bunch of items for complete removal sitting in synaptic.

Ok cleaned those up.

Spent a couple of hours, found nothing else to complain about.

There was a question on the RPi Forum this morning about blockage of torrents, but I see we are not installing a firewall by default--good. I installed qbitorrent which has a fancy new look: are we thinking of doing torrents?

So good to go from my perspective--thanks again for your hard work.

Spent a couple of hours with RC2.1 today, doing random things, with no issues.

Chris