On Tuesday, November 5, 2019 7:05 PM, Mickaël Bucas wrote:
> Hi Caveman
>
> The Portage tree contains a few binary packages prepared by Gentoo
> developers, like Firefox, Rust, LibreOffice...
> "ls -d /usr/portage//-bin" shows about 90 packages prepared in this
> way, some of them because they
A lot of the time, even with SPF, DKIM etc your messages will be marked
as spam if you have a PGP signature, PDF file, or anything else and are
sending from an unusual domain (ie not gmail/microsoft hosted domain).
My messages do it all the time.
Gregory 'Rudi'
Spam filters are pathetic, they rarely catch spam. Mine actually marks my own
post to this list as spam and puts them in the spam folder, along with other
messages sporadically. If you want to stop spam use a "black list" of open
relays, that works. It also helps if you aggressively report
Grant Taylor wrote:
> On 11/1/19 2:00 PM, Dale wrote:
>> I think we came to the conclusion that one person is causing this.
>
> I don't agree with that conclusion.
>
The only message I noticed missing was from one person. Since they are
coming from one person, that is the cause. If the messages
On Tuesday, 5 November 2019 21:44:51 GMT n952162 wrote:
> I then tried to repeat this process, to see if I could get libcap
> installed and so get further with virtualbox, but for some reason, my
> other computer - although it also has virtualbox installed, has
> libcap-2.24*-r2*.ebuild instead of
I then tried to repeat this process, to see if I could get libcap
installed and so get further with virtualbox, but for some reason, my
other computer - although it also has virtualbox installed, has
libcap-2.24*-r2*.ebuild instead of libcap-2.24.ebuild and worse, a
libcap-2.*25*.tar.xz !!!
I moved the virtualbox-6* ebuilds out of that directory and was able to
regenerate the Manifest!
The ebuild file merge worked quite well ... unfortunately, I ended up here:
/usr/lib/gcc/x86_64-pc-linux-gnu/6.4.0/../../../../x86_64-pc-linux-gnu/bin/ld:
cannot find /lib64/libcap.so.2
Apparently
That's odd. I have 6.0.12 installed, so EAPI 7 should not be a
problem. Note EAPI is applied per ebuild, not a system-wide thing.
What version of portage are you using?
On 2019.11.05 16:22, n952162 wrote:
I found the ebuild /file/ manifest command ... but got this:
* Missing digest for
'/usr/portage/app-emulation/virtualbox/virtualbox-5.1.32.ebuild'
On 11/05/19 22:08, n952162 wrote:
I found a copy of the ebuild on a different machine I have - it's a
x86 not an amd64 architect, but maybe it's architecture-agnostic. I
wonder if I copy that to my amd64
I found the ebuild /file/ manifest command ... but got this:
//usr/portage/app-emulation/virtualbox # ebuild
/usr/portage/app-emulation/virtualbox/virtualbox-5.1.32.ebuild manifest //
//!!! getFetchMap(): 'app-emulation/virtualbox-6.0.12' has unsupported
EAPI: '7'//
On 2019.11.05 16:12, n952162 wrote:
I imagine that's a line in the Manifest file?
I think it IS the manifest file.
Any hope of recreating that?
ebuild /path/to/file.ebuild manifest
(digest and manifest are synonyms in that usage)
I found a copy of the ebuild on a different machine I have - it's a x86
not an amd64 architect, but maybe it's architecture-agnostic. I wonder
if I copy that to my amd64 machine (which has the tarball of the
package), will I need anything else?
On 11/05/19 21:44, Alarig Le Lay wrote:
If the
I imagine that's a line in the Manifest file? Any hope of recreating that?
On 11/05/19 22:11, n952162 wrote:
* Missing digest for
'/usr/portage/app-emulation/virtualbox/virtualbox-5.1.32.ebuild'
On 11/05/19 22:08, n952162 wrote:
I found a copy of the ebuild on a different machine I have -
On 2019-11-04 22:46, n952162 wrote:
> Ah, I didn't know that about running fsck multiple times - I remember
> after doing my home directory - the more important one - it did say
> "file system modified". I don't remember if the root fsck said that,
> though. But it looks like I'm going to
Le 05/11/2019 à 21:17, n952162 a écrit :
> fsck effectively discarded many of my virtualbox libraries but I
> still have the ebuild and tarballs and everything. But I don't see
> anything about repair in the emerge manpage.
>
>
emerge -vaA1 virtualbox
--
Alarig
fsck effectively discarded many of my virtualbox libraries but I
still have the ebuild and tarballs and everything. But I don't see
anything about repair in the emerge manpage.
Le mar. 5 nov. 2019 à 01:02, Caveman Al Toraboran
a écrit :
>
>
> DISCLAIMER: I am not claiming that this idea is new. It is probably not new.
> --- Even though some of its details might be new for a Linux
> distribution, it's all based on boring well-established bits of
>
17 matches
Mail list logo
