Re: [DNG] Only a few packages now still on hold
On 8/2/21 11:02 AM, Mark Hindley wrote: Hendrik, As suggested by Rod, I also prefer plain apt to aptitude. In general it is a very good package manager and is pretty successful at resolving dependencies and not breaking your system. Or try good old dselect Cheers Mike ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Only a few packages now still on hold
On Mon, Aug 02, 2021 at 10:15:31PM +1000, wirelessduck--- via Dng wrote: > Is seatd likely to get anywhere in the next Debian development cycle after > bullseye/chimaera? Would this allow us to just need only one option for users > to install? It is already packaged in Devuan and is also waiting to enter Debian[1]. I am aware that the wlroots maintainers need/want to to use it in version 0.14 and later. So there is the prospect of some progress. However, currently seatd uses other logind implementations as backends[2] so it is a layer on top of that rather than a replacement at the moment. Mark [1] https://ftp-master.debian.org/new/seatd_0.5.0-2.html [2] https://git.sr.ht/~kennylevinsen/seatd#whats-in-the-box ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Only a few packages now still on hold
On Sun, 1 Aug 2021 21:58:47 -0400, Hendrik wrote in message
<20210802015847.d7gxxdu7ts753...@topoi.pooq.com>:
> On Sun, Aug 01, 2021 at 09:54:33PM -0400, Hendrik Boom wrote:
> > On Sun, Aug 01, 2021 at 01:13:26PM -0400, Hendrik Boom wrote:
> > > On Sun, Aug 01, 2021 at 05:33:23PM +0200, Bernard Rosset via Dng
> > > wrote:
> > > > On 31/07/2021 22:03, Hendrik Boom wrote:
> > > > > I'm practicing upgrades on my spare laptop, getting ready for
> > > > > doing my server upgrade from ascii to beowulf..
> > > > >
> > > > > They are both running ascii.
> > > > >
> > > > > Starting, of course, by making the ascii up to date still as
> > > > > ascii, before I try tye upgrade to beowulf.
> > > > >
> > > > > Having trouble doing even this innocuous act.
> > > > >
> > > > > I tried starting by using interactive aptitude to just update
> > > > > and upgrade.
> > > >
> > > > After changing your sources to point to the new release,
> > >
> > > I have not yet changed my sources. I figured I should make sure
> > > the ascii system is up-to-date as an ascii system before I start
> > > to upgrade to beowulf.
> > >
> > > > have you run
> > > > "apt-get upgrade" or "apt-get dist-upgrade"?
> > > > It looks to me as if you did the former.
> > >
> > > I used the update and upgrade inside the interactive aptitude.
> > >
> > > I guess I have to do dist-upgrade outside the interacctive
> > > aptitude.
> >
> > And today I did aptitude update and aptitude upgrade in the CLI
> > instead of in the interactive apttude. Just about everything just
> > worked, except for 3 packages:
> > elogind
> > libpam-elogind
> > libelogind0
> > They do nog get upgraded.
> >
> > Following this with
> > aptitude dist-upgrade
> > tells me these will be upgraded, but then balks, telling me to
> > remove libpam-elogind
>
> This is what it says:
>
> root@notlookedfor:~# aptitude dist-upgrade
> The following packages will be upgraded:
> elogind libelogind0 libpam-elogind{b}
> 3 packages upgraded, 0 newly installed, 0 to remove and 0 not
> upgraded. Need to get 861 kB of archives. After unpacking 0 B will be
> used. The following packages have unmet dependencies:
> libpam-elogind : Breaks: libpam-ck-connector but 0.4.6-6 is installed
> The following actions will resolve these dependencies:
>
> Remove the following packages:
> 1) libpam-elogind [234.4-1+devuan1.5 (now)]
..this IME often happens when a newer version needs the old version
stopping it's service(s) and a purge before installing and starting
up the new version.
>
>
> Accept this solution? [Y/n/q/?]
..hit [q], then restart aptitude in the interactive mode, mark
libpam-elogind [234.4-1+devuan1.5 (now)] for removal, as it whines
"Error", hit [e] and browse aptitude's suggestions with [,] and [.]
to see if you can agree on any solution, if not, [q] out and find
aptitude's opinion on "Broken packages" with [B].
..my _guess_ is you may be able to find old lib config files
blocking the removal of libpam-ck-connector or some such.
Purge them.
..hitting [e] and then [Enter] on a package, will find possible
version numbers of that package at the bottom, picking another
newer or older version may also solve your conflict.
..as Tito, Mark, Tom, Rod and I advices, apt, apt-get and probably
a few more, solves package conflicts differently from each other
and from aptitude, IME I can often use e.g. apt-get or even dpkg
when aptitude fails me. Options I remember throwing around also
includes --safe-update and --full-update.
> >
> > How safe is this? isn't elogind kind of important?
> >
> > I'm still just upgrading from ascii to ascii. Beowulf is not in my
> > sights yet.
> >
> > -- hendrik
--
..med vennlig hilsen = with Kind Regards from Arnt Karlsen
...with a number of polar bear hunters in his ancestry...
Scenarios always come in sets of three:
best case, worst case, and just in case.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Only a few packages now still on hold
On Mon, 2 Aug 2021 22:15:31 +1000, wirelessduck--- wrote in message <3a609fa9-9cca-42e3-a66f-fd9f66d69...@gmail.com>: > > On 2 Aug 2021, at 19:02, Mark Hindley wrote: > > > > Yes it can be, but no more so than consolekit. There are 2 > > alternatives for managing seats and sessions in Devuan: consolekit > > (actually consolekit2) and elogind. > > > > Consolekit was probably the default in ascii. It is inactive > > upstream, but still works. Elogind is active and well supported > > and is the default since beowulf. However, the codebase derives > > from systemd and therefore some people will prefer not to use it. > > > > So, you need one or other, but not both or a mixture. > > > > aptitude seems to suggest that you already have elogind installed > > and this is an upgrade. You will have to allow apt to remove the > > consolekit related packages (libpam-ck-connector and possibly some > > policykit libraries). Alternatively, stick with consolekit and > > remove all of the elogind related packages. The choice is yours. > > Both will work once you have a clean installation based on a single > > logind alternative. > > > > Mark > > Is seatd likely to get anywhere in the next Debian development cycle > after bullseye/chimaera? ..I guess not, unless Debian dumps systemd: https://git.sr.ht/~kennylevinsen/seatd > Would this allow us to just need only one option for users to install? > ..we should probably do our own packaging of this, and much more, chk output of: how-can-i-help --old |less ..103 packages due to be kicked out now, many of these were left behind by DD leaving since the systemd coup... arnt@d44:~$ how-can-i-help --old |grephttps://tracker.debian.org/pkg/ \ |cut -d" " -f5 |sort |uniq |wc -l 103 ..more details in: apt-cache show $(how-can-i-help --old |grep \ https://tracker.debian.org/pkg/ |cut -d" " -f3 |sort |uniq ) |less ..806 since I began capturing said sad output into my own list. arnt@d44:~$ cat how-can-I-help |grep https://tracker.debian.org/pkg/ \ |cut -d" " -f5 |sort |uniq |wc -l 806 arnt@d44:~$ -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Only a few packages now still on hold
> On 2 Aug 2021, at 19:02, Mark Hindley wrote: > > Yes it can be, but no more so than consolekit. There are 2 alternatives for > managing > seats and sessions in Devuan: consolekit (actually consolekit2) and elogind. > > Consolekit was probably the default in ascii. It is inactive upstream, but > still > works. Elogind is active and well supported and is the default since > beowulf. However, the codebase derives from systemd and therefore some people > will prefer not to use it. > > So, you need one or other, but not both or a mixture. > > aptitude seems to suggest that you already have elogind installed and this is > an > upgrade. You will have to allow apt to remove the consolekit related packages > (libpam-ck-connector and possibly some policykit libraries). Alternatively, > stick with consolekit and remove all of the elogind related packages. The > choice > is yours. Both will work once you have a clean installation based on a single > logind alternative. > > Mark Is seatd likely to get anywhere in the next Debian development cycle after bullseye/chimaera? Would this allow us to just need only one option for users to install? -- Tom ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Only a few packages now still on hold
Hendrik,
As suggested by Rod, I also prefer plain apt to aptitude. In general it is a
very good package manager and is pretty successful at resolving dependencies and
not breaking your system.
On Sun, Aug 01, 2021 at 09:58:47PM -0400, Hendrik Boom wrote:
> > And today I did aptitude update and aptitude upgrade in the CLI instead
> > of in the interactive apttude. Just about everything just worked,
> > except for 3 packages:
> > elogind
> > libpam-elogind
> > libelogind0
> > They do nog get upgraded.
> >
> > Following this with
> > aptitude dist-upgrade
> > tells me these will be upgraded, but then balks, telling me to remove
> > libpam-elogind
>
> This is what it says:
>
> root@notlookedfor:~# aptitude dist-upgrade
> The following packages will be upgraded:
> elogind libelogind0 libpam-elogind{b}
> 3 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> Need to get 861 kB of archives. After unpacking 0 B will be used.
> The following packages have unmet dependencies:
> libpam-elogind : Breaks: libpam-ck-connector but 0.4.6-6 is installed
> The following actions will resolve these dependencies:
>
> Remove the following packages:
> 1) libpam-elogind [234.4-1+devuan1.5 (now)]
>
> Accept this solution? [Y/n/q/?]
>
> >
> > How safe is this? isn't elogind kind of important?
Yes it can be, but no more so than consolekit. There are 2 alternatives for
managing
seats and sessions in Devuan: consolekit (actually consolekit2) and elogind.
Consolekit was probably the default in ascii. It is inactive upstream, but still
works. Elogind is active and well supported and is the default since
beowulf. However, the codebase derives from systemd and therefore some people
will prefer not to use it.
So, you need one or other, but not both or a mixture.
aptitude seems to suggest that you already have elogind installed and this is an
upgrade. You will have to allow apt to remove the consolekit related packages
(libpam-ck-connector and possibly some policykit libraries). Alternatively,
stick with consolekit and remove all of the elogind related packages. The choice
is yours. Both will work once you have a clean installation based on a single
logind alternative.
Mark
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Only a few packages now still on hold
On Sun, 1 Aug 2021 21:58:47 -0400
Hendrik Boom wrote:
> On Sun, Aug 01, 2021 at 09:54:33PM -0400, Hendrik Boom wrote:
> > On Sun, Aug 01, 2021 at 01:13:26PM -0400, Hendrik Boom wrote:
> > > On Sun, Aug 01, 2021 at 05:33:23PM +0200, Bernard Rosset via Dng wrote:
> > > > On 31/07/2021 22:03, Hendrik Boom wrote:
> > > > > I'm practicing upgrades on my spare laptop, getting ready for doing
> > > > > my server
> > > > > upgrade from ascii to beowulf..
> > > > >
> > > > > They are both running ascii.
> > > > >
> > > > > Starting, of course, by making the ascii up to date still as ascii,
> > > > > before I try tye
> > > > > upgrade to beowulf.
> > > > >
> > > > > Having trouble doing even this innocuous act.
> > > > >
> > > > > I tried starting by using interactive aptitude to just update and
> > > > > upgrade.
> > > >
> > > > After changing your sources to point to the new release,
> > >
> > > I have not yet changed my sources. I figured I should make sure the
> > > ascii system is up-to-date as an ascii system before I start to upgrade
> > > to beowulf.
> > >
> > > > have you run
> > > > "apt-get upgrade" or "apt-get dist-upgrade"?
> > > > It looks to me as if you did the former.
> > >
> > > I used the update and upgrade inside the interactive aptitude.
> > >
> > > I guess I have to do dist-upgrade outside the interacctive aptitude.
> >
> > And today I did aptitude update and aptitude upgrade in the CLI instead
> > of in the interactive apttude. Just about everything just worked,
> > except for 3 packages:
> > elogind
> > libpam-elogind
> > libelogind0
> > They do nog get upgraded.
> >
> > Following this with
> > aptitude dist-upgrade
> > tells me these will be upgraded, but then balks, telling me to remove
> > libpam-elogind
>
> This is what it says:
>
> root@notlookedfor:~# aptitude dist-upgrade
> The following packages will be upgraded:
> elogind libelogind0 libpam-elogind{b}
> 3 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> Need to get 861 kB of archives. After unpacking 0 B will be used.
> The following packages have unmet dependencies:
> libpam-elogind : Breaks: libpam-ck-connector but 0.4.6-6 is installed
> The following actions will resolve these dependencies:
>
> Remove the following packages:
> 1) libpam-elogind [234.4-1+devuan1.5 (now)]
>
>
>
> Accept this solution? [Y/n/q/?]
>
> >
> > How safe is this? isn't elogind kind of important?
> >
> > I'm still just upgrading from ascii to ascii. Beowulf is not in my
> > sights yet.
> >
> > -- hendrik
> >
Hi,
Do you have consolekit installed?
if not you can try at your own _risk_
apt-get download libelogind0
apt-get download libpam-elogind
apt-get download elogind
dpkg --purge --force-all libpam-ck-connector
dpkg -i --force-all ./libelogind0*.deb
dpkg -i --force-all ./elogind*.deb
dpkg -i --force-all ./libpam-elogind*.deb
I told you at your own risk.
Ciao,
Tito
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Only a few packages now still on hold
On Sun, Aug 01, 2021 at 09:54:33PM -0400, Hendrik Boom wrote:
> On Sun, Aug 01, 2021 at 01:13:26PM -0400, Hendrik Boom wrote:
> > On Sun, Aug 01, 2021 at 05:33:23PM +0200, Bernard Rosset via Dng wrote:
> > > On 31/07/2021 22:03, Hendrik Boom wrote:
> > > > I'm practicing upgrades on my spare laptop, getting ready for doing my
> > > > server
> > > > upgrade from ascii to beowulf..
> > > >
> > > > They are both running ascii.
> > > >
> > > > Starting, of course, by making the ascii up to date still as ascii,
> > > > before I try tye
> > > > upgrade to beowulf.
> > > >
> > > > Having trouble doing even this innocuous act.
> > > >
> > > > I tried starting by using interactive aptitude to just update and
> > > > upgrade.
> > >
> > > After changing your sources to point to the new release,
> >
> > I have not yet changed my sources. I figured I should make sure the
> > ascii system is up-to-date as an ascii system before I start to upgrade
> > to beowulf.
> >
> > > have you run
> > > "apt-get upgrade" or "apt-get dist-upgrade"?
> > > It looks to me as if you did the former.
> >
> > I used the update and upgrade inside the interactive aptitude.
> >
> > I guess I have to do dist-upgrade outside the interacctive aptitude.
>
> And today I did aptitude update and aptitude upgrade in the CLI instead
> of in the interactive apttude. Just about everything just worked,
> except for 3 packages:
> elogind
> libpam-elogind
> libelogind0
> They do nog get upgraded.
>
> Following this with
> aptitude dist-upgrade
> tells me these will be upgraded, but then balks, telling me to remove
> libpam-elogind
This is what it says:
root@notlookedfor:~# aptitude dist-upgrade
The following packages will be upgraded:
elogind libelogind0 libpam-elogind{b}
3 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 861 kB of archives. After unpacking 0 B will be used.
The following packages have unmet dependencies:
libpam-elogind : Breaks: libpam-ck-connector but 0.4.6-6 is installed
The following actions will resolve these dependencies:
Remove the following packages:
1) libpam-elogind [234.4-1+devuan1.5 (now)]
Accept this solution? [Y/n/q/?]
>
> How safe is this? isn't elogind kind of important?
>
> I'm still just upgrading from ascii to ascii. Beowulf is not in my
> sights yet.
>
> -- hendrik
>
> ___
> Dng mailing list
> Dng@lists.dyne.org
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Only a few packages now still on hold
On Sun, Aug 01, 2021 at 01:13:26PM -0400, Hendrik Boom wrote: > On Sun, Aug 01, 2021 at 05:33:23PM +0200, Bernard Rosset via Dng wrote: > > On 31/07/2021 22:03, Hendrik Boom wrote: > > > I'm practicing upgrades on my spare laptop, getting ready for doing my > > > server > > > upgrade from ascii to beowulf.. > > > > > > They are both running ascii. > > > > > > Starting, of course, by making the ascii up to date still as ascii, > > > before I try tye > > > upgrade to beowulf. > > > > > > Having trouble doing even this innocuous act. > > > > > > I tried starting by using interactive aptitude to just update and upgrade. > > > > After changing your sources to point to the new release, > > I have not yet changed my sources. I figured I should make sure the > ascii system is up-to-date as an ascii system before I start to upgrade > to beowulf. > > > have you run > > "apt-get upgrade" or "apt-get dist-upgrade"? > > It looks to me as if you did the former. > > I used the update and upgrade inside the interactive aptitude. > > I guess I have to do dist-upgrade outside the interacctive aptitude. And today I did aptitude update and aptitude upgrade in the CLI instead of in the interactive apttude. Just about everything just worked, except for 3 packages: elogind libpam-elogind libelogind0 They do nog get upgraded. Following this with aptitude dist-upgrade tells me these will be upgraded, but then balks, telling me to remove libpam-elogind How safe is this? isn't elogind kind of important? I'm still just upgrading from ascii to ascii. beowulf not in my sights yet. -- hendrik ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
