Hello
> > If you are worried that somebody who has
> > compromised your OS remotely will hack your bootloader, then
> > reconsider their motives: They are already on a running host OS
> > as root and can look inside your encrypted disk volumes too -
> > you have lost already.
>
> Secureboot is t
Hi all,
meanwhile I upgraded the next server from debian wheezy to devuan jessie.
With the same result on upgrading packages, like today:
Trigger für libc-bin (2.19-18+deb8u10) werden verarbeitet ...
syntax error at (eval 6) line 91, near ") {"
Can't use global $/ in "my" at (eval 6) line 94, ne
Thomas,
First, it seems that you're actually trying to install different revisions
of the same package. You had libc-bin (2.19-18+deb8u9) in your first email,
and libc-bin (2.19-18+deb8u10) in your second. While this is a minor
difference, I've seen it cause issues. I spun a test Debian Wheezy sy
On 10/23/2017 09:19 AM, John Hughes wrote:
On 23/10/17 15:59, Patrick Meade wrote:
As John Hughes said, this isn't quite as bad as we originally thought.
We can still run redis-server with the Debian provided sysvinit
script, and Debian isn't throwing away upstream files for no reason.
Also n
On Mon, 23 Oct 2017 13:45:48 -0500, lpb+dev...@kandl.houston.tx.us
wrote in message
<3b6863f4-a35a-8b41-b09a-333778dab...@kandl.houston.tx.us>:
> I'm having trouble doing an "apt-get upgrade" over tor+http. The
> update works fine; my guess is the manifests have bad information.
> Here's what a se
On 24/10/17 14:44, Patrick Meade wrote:
Only the first option is acceptable to me, so what needs to be done is
also clear to me. I'm hoping that the Debian maintainer will be
willing to revert this change, as that would be the easiest way for
everybody to win. If not, well... there is some wo
This is what the debian maintainer wrote to me about redis.
(i ask if i miss understood the patch loq )
> Maybe i miss understood the message ?
You did. As the changelog entry mentions, it's only the Debian-
specific (eg.) /etc/redis/redis-server.pre-up.d support that have
been removed... and th
> From: a...@iaksess.no
> To: dng@lists.dyne.org
>
> On Mon, 23 Oct 2017 13:45:48 -0500, lpb+dev...@kandl.houston.tx.us
> wrote in message
> 3b6863f4-a35a-8b41-b09a-333778dab...@kandl.houston.tx.us:
>
>> I'm having trouble doing an "apt-get upgrade" over tor+http. The
>> update works fine; my guess
On Tue, Oct 24, 2017 at 10:26:01AM -0400, Fungal-net wrote:
[cut]
>
> I reported the same in the forum and although I did not get an answer yet
> when earlier today I was trying to figure it out I changed all rep's /merged/
> to
> /devuan/ and I got working releases. The /merged/ directories
> From: kato...@freaknet.org
> To: dng@lists.dyne.org
>
> On Tue, Oct 24, 2017 at 10:26:01AM -0400, Fungal-net wrote:
>
> [cut]
>
>>
>> I reported the same in the forum and although I did not get an answer yet
>> when earlier today I was trying to figure it out I changed all rep"s
>> /merged/ to
>
> From: kato...@freaknet.org
>
>> To: dng@lists.dyne.org
>>
>> On Tue, Oct 24, 2017 at 10:26:01AM -0400, Fungal-net wrote:
>>
>> [cut]
>>
>>>
>>> I reported the same in the forum and although I did not get an answer yet
>>> when earlier today I was trying to figure it out I changed all rep"s
>>> /
On Tue, Oct 24, 2017 at 11:45:57AM -0400, Fungal-net wrote:
[cut]
> > The repository is not updated and the previous index files will be used.
> > GPG error: tor://devuanfwojg73k6r.onion/merged ascii InRelease: The
> > following signatures couldn't be verified because the public key is not
> >
On Tue, 24 Oct 2017 18:26:45 +0100, KatolaZ wrote in message
<20171024172645.gy4...@katolaz.homeunix.net>:
>
> jessie-proposed is under /devuan
> jessie-proposed-updates is under /devuan
> experimentalis under /devuan
..are you now saying these 3 should be /devuan and NO
I didn't change anything on my side, and now it seems to be working.
On 10/24/2017 02:18 PM, Arnt Karlsen wrote:
> On Tue, 24 Oct 2017 18:26:45 +0100, KatolaZ wrote in message
> <20171024172645.gy4...@katolaz.homeunix.net>:
>
>>
>> jessie-proposed is under /devuan
>> jessie-proposed-u
On Tuesday 24 October 2017 at 21:37:38, lpb+dev...@kandl.houston.tx.us wrote:
> I didn't change anything on my side, and now it seems to be working.
Please could you clarify what configuration you are using now, so we can know
what you haven't changed and is working :)
I for one would be intere
On 10/20/2017 11:47 PM, goli...@dyne.org wrote:
If you want to help testing the new amprolla3, you just need to:
- replace "auto.mirror.devuan.org" with "pkgmaster.devuan.org" in
your /etc/apt/sources.list
- # apt-get update
- # apt-get install devuan-keyring
I'm on ASCII, just made the sw
This is my sources.list:
deb tor+http://devuanfwojg73k6r.onion/merged jessie main contrib
deb tor+http://devuanfwojg73k6r.onion/merged jessie-updates main contrib
deb tor+http://devuanfwojg73k6r.onion/merged jessie-security main contrib
That's it, no changes from that.
On 10/24/2017 02
>>> On Tue, 24 Oct 2017 18:26:45 +0100, KatolaZ wrote in message
> jessie-proposed is under /devuan
> jessie-proposed-updates is under /devuan
> experimental is under /devuan
> The rest is under /merges, if I have not missed something.
I did not ask because I wanted to b
Am 24.10.2017 um 10:45 schrieb Linux O'Beardly:
> First, it seems that you're actually trying to install different
> revisions of the same package. You had libc-bin (2.19-18+deb8u9) in your
> first email, and libc-bin (2.19-18+deb8u10) in your second. While this
> is a minor difference, I've seen
19 matches
Mail list logo
