Re: Log for attempted build of encfs_1.8.1-2 on m68k (dist=unstable)
Eduard Bloch dixit:
>First news regarding encfs: I had a look on it... and couldn't figure
>out what's wrong with autoconf. I might dig further but it's waste of
>time because upstream has already switched to Cmake in his master git
>branch. I tried this quickly and it compiles just fine on m68k.
>Therefore, I would postpone the issue.
OK, sure. Agreed.
>Do you (?) want to be notified (somehow?) when the next upstream
>revision is out there?
Just upload it to unstable, so no.
>Mh, thanks for the explanation. Btw, your patch from the mentioned bug
>report works even for 1.58. I will try to get more feedback on this
>issue, it's hard to believe that nobody is going to solve it.
OK.
>Ok. But it's still weird, looks like no https transport is available on
>m68k?
It should be, but occasionally too slow to be usable.
But apt-transport-https is never installed by default
on Debian, and to install it you need an http mirror…
>> Mh, these are all emulator issues. We generally ssh into the system,
>> it makes for a much, much smoother feeling.
>
>Ok. I wish the README would just say this from the beginning - ssh into
Mh…
>it as soon as possible. And ideally, openssh-server package should be in
>apt cache before (however this means not cleaning apt/dpkg caches before
>you create the FS image, but it's always a tradeoff).
I think you’d want to get the latest ssh. And I’m not preinstalling
it because it needs entropy, which the initial keyboard input from
you provides ;-)
>> Correct. I think the README and/or Wiki page says so, too?
>
>Somewhere down in the task list...
Oh yes, we can all documentate so well ;-)
Have a nice weekend,
//mirabilos, currently at Linuxhotel
--
(gnutls can also be used, but if you are compiling lynx for your own use,
there is no reason to consider using that package)
-- Thomas E. Dickey on the Lynx mailing list, about OpenSSL
Reply to: