The nice thing is the Devuan devs are already working on removing
mandatory libsystemd0 for stable, and some packages will accept an
installation with apt-get install packagename loginkit if you want to
avoid systemd.
I'll try to write up instructions for sure to include apt-pinning, much
to do first though and it'll be a seperate doc at first though. Much
thanks for the tips though, that's very enlightening as to how to
manage a Sid/Ceres system, for now the docs have changed to mention
that ceres should be used by expert users only and all branches are
mentioned as being supported for upgrading or migrating to as you've
confirmed Ceres.
Only thing left is can you upgrade from oldoldstable, has anyone tried
that?
On Wednesday, November 11, 2015 9:04 AM, Mitt Green
<mitt_gr...@yahoo.com> wrote:
I think:
- Devuan should add libsystemd0 and systemd packages to
devuan-baseconf
to exclude their appearance on one's system;
- Devuan's first focus is stable, thus testing and unstable users
should be able to solve packaging problems, which includes
pinning and even forking packages (which should be followed by
pushing newly forked packages to repository so others won't be
in need to create their own all the time);
- you shouldn't use testing and unstable in production not because
the latest
software is less stable but because updates are too frequent and
unwanted dependencies can be added.
There is not much can break, packages dependent on what you have
pinned,
won't be upgraded. For example, I've pinned libsystemd0 (let's say,
added to "unwanted packages" list), so gvfs won't upgrade. Or
another example, today I updated repos and saw "aha, rpcbind now
needs
libsystemd0, okay, let it be not the latest version". It won't
upgrade.
Of course I have an option to download the source and remove
libsystemd0
dependency, but, as I pointed out, I am not the only who uses
unstable
(I hope) and there should be people who solve such psoftware is less
stable but because updates are too frequent and
unwanted dependencies can be added.
There is not much can break, packages dependent on what you have
pinned,
won't be upgraded. For example, I've pinned libsystemd0 (let's say,
added to "unwanted packages" list), so gvfs won't upgrade. Or
another example, today I updated repos and saw "aha, rpcbind now
needs
libsystemd0, okay, let it be not the latest version". It won't
upgrade.
Of course I have an option to download the source and remove
libsystemd0
dependency, but, as I pointed out, I am not the only who uses
unstable
(I hope) and there should be people who solve such problems. But, as
I said,
the most important is to get stable to work. Stable doesn't have as
frequent
updates as testing and unstable.
I didn't use (and still don't) dist-upgrade.
Also, packages that can't be upgraded are always shown as "kept
back".
And there is a solution to use angband repos (angband.pl)
if you use unstable.
Hope this helps,roblems. But, as I said,
the most important is to get stable to work. Stable doesn't have as
frequent
updates as testing and unstable.
I didn't use (and still don't) dist-upgrade.
Also, packages that can't be upgraded are always shown as "kept
back".
And there is a solution to use angband repos (angband.pl)
if you use unstable.
Hope this helps,
Mitt
------------------------------------------------------------------------------
On Wednesday, November 11, 2015 11:15 AM, Simon Hobson
<li...@thehobsons.co.uk> wrote:
Mitt Green <mitt_gr...@yahoo.com> wrote:
But I also have libsystemd0 file in /etc/apt/preferences.d
containing:
--------------------
Package: libsystemd0
Pin: origin ""
Pin-Priority: -1
--------------------
Does anyone have any tips for getting more meaningful output from apt
when something fails ?
Specifically, not long ago I pinned systemd out like that and tried a
dist-upgrade to Debian Jessie to see what would happen. It took some
time (and trial and error) to figure out which package was blocking
it since apt seems to baulk at something that depends on something
that depends on something else that is blocked - making it hard to
figure out what that something else actually is.
In my case, turned out to be clamd causing the problem.
_______________________________________________
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
--
Take back your privacy. Switch to www.StartMail.com
_______________________________________________
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
