On 13/09/2018 15:42, KatolaZ wrote:
We don't need a duct-tape fix, rather one
that works for everybody and does not need any manual
intervention. .
I agree with that because that is what really everybody ultimately wants
(IMHO).
We are getting there. Stay tuned.
OK, I will (mumb
Because I don't know how to file a bug-report against the whole
merged/beowulf branch which presently does not allow a straight forward
migration of a DE from ASCII to Beowulf I thought, if I bring up this
subject in this list some of the Developers might have a look at it.
It is not my desire
On 06/01/2017 20:27, Dan Purgert wrote:
Maybe I missed something in the original mail - I read Fred's mail as a
"ha, lookie you RedHat, getting the same 'X is now considered legacy'
statements made about one of your things"...
Spot on, it was a spoof on RedHat. Don't they keep on telling us th
On 06/01/2017 14:59, Anto wrote:
I am not sure why BlankOn Linux is being bought up into this anti
systemd mailing list. They clearly endorse systemd and follow debian,
https://translate.google.co.uk/translate?hl=en&sl=id&u=http://dev.blankonlinux.or.id/ticket/1415.
But hey, this is an open mail
Just for the fun.
Does Gnome3 (aka RH) know that they use a technology which is considered
by some a legacy technology?
Me thinks, that maybe by the time s*d is more than just useable it might
also be considered a legacy init-scheme.
Quoting from the Release Notes of the BlankOn Distro:
BlankO
On 12/09/2016 10:32, Jaromil wrote:
> ...
>
> (the above space is left intentionally blank for conspiracy theorists)
>
> Openrc in Debian coul be labeled as a "self hating package",
> I recommend you compile from source until we provide an openrc
> package.
The same could be said regarding the '
On 02/09/2016 10:04, Attila Soki wrote:
> ...
> Of course a devuan plugin would make all this unnecessary.
> But before i can file a bug, or maybe create a devuan plugin, i must
> know which is the preferred way to identify devuan.
> grepping /etc/issues
> or
> grepping /etc/os-release
> or
> ?
Th
On 12/08/2016 19:47, Steve Litt wrote:
Hi Steve
[big snip]
Thanks for your valued thought but I consider the incident "water under
the bridge". All what I wanted is to warn PID 1 'runit' users that the
upgrading is a botched affair. As I said, I was able to recover the
system but belive me, its no
On 12/08/2016 13:43, Tom H wrote:
>> On 12/08/2016 11:49, Tom H wrote:
>>>
>>> Off-list
>>>
>>> Install
>>> runic-init
>>> in order to restore
>>> /sbin/init
>>> and
>>> /sbin/runit
>>
>> Thanks for the suggestion. Unfortunately 'runic-init' it is not in
>> 'ascii' and googling didn't help neither.
On 13/08/2016 11:52, aitor_czr wrote:
> [Snip}
>
> Yes, we need testers :)
>
> Best,
>
> Aitor.
Oh yes, I will test it once it hits 'ascii' or
perhaps even the 'unstable' branch. Sorry can't
do better bacause I am just a user with a fairly
good head on its shoulder.
Regards
Fred
__
Hi,
My apololgies for sounding a bit emotional about this issue.
If, up to now, you have "runit" running as pid 1 and managed to
maintain the ability to boot from the kernel commandline using
the sysv-init read on.
The latest update to package 'runit' *wipes* out the 2 binaries
/sbin/runit-init
On 26/04/2016 20:15, Julien Pinon wrote:
> Le mardi 26 avril 2016 à 18:00,
> Fred DC écrivait :
>
>> Maybe I do something wrongly, I am not too familiar with gpg.
>>
>> All as root
>> "apt-get update" says: NO_PUBKEY AF49E19219D58C5D
>>
>> s
On 26/04/2016 16:43, Florian Zieboll wrote:
>
> assuming that "$KEY_ID" is the correct Devuan archive signing key, as
> root or sudo'ed:
>
> $ gpg --recv-key $KEY_ID
> $ gpg --export $KEY_ID | apt-key add -
>
> resp. in one go:
>
> $ apt-key adv --keyserver hkp://keys.gnupg.net \
>
By updating devuan ascii I get the following error:
Failed to fetch http://packages.devuan.org/devuan/dists/ascii/InRelease
The following signatures couldn't be verified because the public key is
not available: NO_PUBKEY AF49E19219D58C5D
Any advise?
Fred
___
On 13/04/2016 17:30, Jaromil wrote:
> ...
> So now Franco is fixing this as we speak and you should be able to
> upgrade to 13-04-2016 pretty soon...
>
> ciao
Confirmed, 142 packages to update. The joy of a rolling release ;-).
Thank you and the Team.
Fred
I am not sure if the Devuan-Admin is aware that
packages.devuan.org_merged_dists_ascii has not seen an
update since the 9th of April.
Debian Stretch repos show a date of 13-04-2016
Regards
Fred
___
On 06/04/2016 20:36, Rob wrote:
>
> Debian intend to shut off SHA1 completely on January 1, 2017.
> https://wiki.debian.org/Teams/Apt/Sha1Removal
Ok, I don't need to panic. Thanks Rob.
Fred
___
Dng mailing list
Dng@lists.dyne.org
https://mailingli
Does that mean that one of these days I won't be able to
update ascii?
W: http://packages.devuan.org/merged/dists/ascii/InRelease: Signature by
key 72E3CB773315DFA2E464743D94532124541922FB uses weak digest algorithm
(SHA1)
Regards
Fred
___
Dng mailing
On 23/03/2016 03:32, Hendrik Boom wrote:
> ...
> Assuming pulseaudio was the culprit (which seems likely) it probably
> was *not* installed when I installed alpha 2. It must have been
> entrained with something I installed later, but I can't tell what.
> Aptitude didn't want to delete anything
On 25/02/2016 23:00, Go Linux wrote:
> On Thu, 25 Feb 2016 20:11:56 + (UTC)
>
> Go Linux wrote:
>
> ...
> I once tried lxde and was not impressed. Maybe it's improved since then.
> ...
> golinux
Moved from xfce to icewm + SpaceFM + gmrun + some decent artwork and I
love it. It just works.
On 25/02/2016 15:06, Irrwahn wrote:
> On Thu, 25 Feb 2016 13:34:01 +0100, Richard Lucassen wrote:
>> On Thu, 25 Feb 2016 10:03:41 +0100
>> Irrwahn wrote:
> [...]
>> It simply says "install busybox". Or have I missed a crucial issue
>> somewhere?
>
> Sorry, but apparently you did:
>
> 0. The b
On 25/02/2016 11:03, Irrwahn wrote:
>
> it indeed declares a "Breaks: initscripts
> (< 2.88dsf-59.3~)", which is built from the sysvinit source package.
>
> So, for Devuan testing/ascii we would need an update here, sooner or later.
You spelled it out what I, silly me, omitted. Thank you.
I don't know if this is the right place to report this.
Please accept my apologies.
Upgrading initramfs-tools version 0.120 to 0.123
breaks initscripts <2.88dsf-59.3-1
presently installed is 2.88dsf-59.2+devuan2
Right now I have put the package on hold because if force the
install the kernel gets
On 30/12/2015 17:16, Didier Kryn wrote:
> ...
> It seems, from the dependencies, as being built on top of lxde
> libraries.
May I suggest to visit: lumina-desktop.org
It is much more illuminating as a 1000 words from me.
Regards
Fred
___
Dng maili
On 30/12/2015 14:43, Didier Kryn wrote:
> Le 30/12/2015 00:38, Dragan FOSS a écrit :
>> On 12/30/2015 12:03 AM, Didier Kryn wrote:
>>> Out of the description it seems to come out of a Devuan dream, both for
>>> what it provides and for what it doesn't.
>>
>> You can try, deb packages are there:
>>
On 18/07/2015 10:49, Laurent Bercot wrote:
>
> Believe me, providing sysv-rc compatibility when you're working on
> a supervision suite is no small feat: the paradigm is very different,
>
> . If it was easy, we would have provided compatibility packages
> long ago, and supervision wo
On 04/07/2015 10:26, Martin Steigerwald wrote:
>
> So it seems this is not a *direct* dependency. It may be that some of the
> dependencies depend on libsystemd0.
>
So it is: libprocps4 depends on libsystemd0
Fred
___
Dng mailing list
Dng@lists.dyne.
On 01/07/2015 10:16, KatolaZ wrote:
>
> I am not the best person to answer your questions, but I believe that
> all these problems should be fixed in the beta release, when it's
> ready.
I am just a user but I can report that these issues have been addresses
in Ascii. I use lightdm with consolek
28 matches
Mail list logo
