I played in the cooker/cauldron/unstable for years without knowing how to use the bug report system properly (for kde and the kernel...Mandriva, Mageia, pclinuxos ).

But I used the forums a lot at LQ and the host os forums to feel my way.

it's not broken so no need to fix it

In my case the reason was the included repository

  deb http://packages.devuan.org/devuan/ unstable main    
  

Disabling it solved the problem.

Uncle aluma,

Devuan has always recommended...almost insisted...for users to use actual Devuan release names in their sources list instead of the generic names of stable, testing, and unstable.

However, I was still frisky back then. I've gotten older and cantankerous and just want a stable system now.

Lol, you and me both. Been running Devuan 1 for 6.5 years now, lol.

Not long ago had conversation with a guy in the library who was interested in what distro I was running, told him, and he was like OMG why are you running something that old?

me: Because it works

him: omg but there's new stuff

me: don't care, it's not broken so no need to fix it

him: But things will break

me: it's not broken

him: it will be

me: IT'S NOT ******* BROKEN!

LOL! But in all seriousness, 6 and a half years and all machines are still working fine, that's awesome, one of the reasons I love Devuan, never had an update in those years that broke anything, it all just kept humming right along.

  deb http://packages.devuan.org/devuan/ unstable main    
  

Disabling it solved the problem.
Indeed, the libnm0 version in this repository is newer than the installable version of network-manager.

The answer is: fix it yourself (and/or file a bug report), or wait.

In my humble opinion, this should be promoted as the expected outcome for anyone wishing to venture into the testing/unstable waters.

Example:  A few days ago an update of nfs-common broke my ability to mount nfs shares.  I waited and no fix has showed up, yet, and I can find no bug report that addresses this.  So, I uninstalled and then reinstalled from excalibur repos.  Then I held the package to current level.  I wish I knew enough to file a helpful bug report, so instead, I will continue waiting.  In the meantime, my ceres is now fully functional, again.
If this is not something that excites you, then it would be rough sailing to jump into these waters.

@fsmithred
Need to say.
This happened on an experimental computer.
On the other, where all sorts of extra packets do not fall, everything is fine.

Regards.

Yeah, mixing stable and unstable is a recipe for problems. A better choice is to mix testing and unstable, and in either case, setting unstable to a lower priority would let you be more selective about which packages come from unstable.

fsmithred wrote:

we got to the fifth post and nobody has yet asked why network-manager got removed?

If the first post had been an attempt at a bug report, I'm sure more would have been done to encourage diagnosis and sending of the relevant information to bugs.devuan.org

But since it was essentially just a rant just about dropped balls and low bars, I'd say the responses were just right.

Indeed.
Had the OP phrased the post as a bug report or request for help, help they likely would have received. Whining about how terrible the distro is because  an update on unstable "Removed internet access" gets... Some ROFL at best.

I'll tolerate plenty of complains if a routine update to a stable release causes borkage (particularly if the post includes technical details, as opposed to "$gui_thing got broke because I didn't read apt output"), hell, sometimes I'll even join in...
But unstable and testing are subject to this kind of dependency screwyness at any time, and that's kinda the point of having unstable and testing branches to begin with.

i.e.

This^ The answer is: fix it yourself (and/or file a bug report), or wait.

   root@aa:/# apt policy network-manager network-manager-gnome network-manager-tde
network-manager:
  Installed: 1.44.2-3devuan1
  Candidate: 1.44.2-5devuan1
  Version table:
     1.44.2-5devuan1 500
        500 http://packages.devuan.org/devuan unstable/main amd64 Packages
 *** 1.44.2-3devuan1 100
        100 /var/lib/dpkg/status
     1.42.4-1devuan1 500
        500 http://deb.devuan.org/merged daedalus/main amd64 Packages
network-manager-gnome:
  Installed: (none)
  Candidate: 1.30.0-2
  Version table:
     1.30.0-2 500
        500 http://deb.devuan.org/merged daedalus/main amd64 Packages
network-manager-tde:
  Installed: 4:14.1.1-0debian12.0.0+0
  Candidate: 4:14.1.2~pre3-0debian12.0.0+1
  Version table:
     4:14.1.2~pre3-0debian12.0.0+1 500
        500 http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-sb daedalus/main-r14 amd64 Packages
 *** 4:14.1.1-0debian12.0.0+0 500
        500 http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-r14.1.x daedalus/main amd64 Packages
        100 /var/lib/dpkg/status
root@aa:/#

Need to say.
This happened on an experimental computer.
On the other, where all sorts of extra packets do not fall, everything is fine.

Regards.

Look at the terminal output before agreeing to an upgrade. If it's going to remove something that you consider detrimental to your system, tell it n (no). You can then upgrade the other packages individually that aren't part of the packages that will/would be removed.

Under normal circumstances, it will be fixed within a few days. Other times, it may take a week or two. I remember one time...not that my memory is that good any longer...but I remember one time...I probably went nearly two or three months before the package was fixed and able to be upgraded.

During that time, I upgraded all of the other stuff individually.

However, I was still frisky back then. I've gotten older and cantankerous and just want a stable system now.

What do you get if you run this?

apt policy network-manager network-manager-gnome network-manager-tde

After getting network-manager and libnm0 kept back for days, I got sick of waiting for a fix to come through.  I experimented and got this to work:

sudo apt-get install --reinstall libnm0

This upgraded libnm0, network-manager and removed some other package I did not recognize.

Everything has been fine since then.