Am 19.11.18 um 08:19 schrieb YUE Daian:
> Have you tried to run `eix-update`?
For sure. Repeated right now, doesn't change the output of "eix -I"
On 2018-11-19 08:14, "Stefan G. Weichinger" wrote:
> upgrading from sys-apps/systemd-236-r5 to 239-r2
>
> the emerge runs through and warns me that it overwrites files ... so it
> merges only partially ...
>
> after that I see:
>
> # systemctl --version
> systemd 239
>
> (which is OK)
>
>
> # eix
upgrading from sys-apps/systemd-236-r5 to 239-r2
the emerge runs through and warns me that it overwrites files ... so it
merges only partially ...
after that I see:
# systemctl --version
systemd 239
(which is OK)
# eix -I systemd
[U] sys-apps/systemd
Available versions: 239-r2(0/2)
On 11/18/18 12:19 PM, james wrote:
> On 11/17/18 9:59 PM, Grant Edwards wrote:
>> On 2018-11-18, james wrote:
>>> On 11/17/18 6:51 PM, Grant Edwards wrote:
On 2018-11-17, Mick wrote:
> On Saturday, 17 November 2018 23:00:22 GMT Grant Edwards wrote:
>> On 2018-11-17, james wrote:
On 11/18/18 10:19, (Nuno Silva) wrote:
> On 2018-11-18, Daniel Frey wrote:
>
>> On 11/18/18 02:47, Alarig Le Lay wrote:
>>> Hi Daniel,
>>>
>>> Didi you tried to remove the temporary directory (inside /var/tmp) and
>>> re-emerge id again? It looks like an incorrectly decompressed archive.
>>>
>>
On 2018-11-18, Daniel Frey wrote:
> On 11/18/18 02:47, Alarig Le Lay wrote:
>> Hi Daniel,
>>
>> Didi you tried to remove the temporary directory (inside /var/tmp) and
>> re-emerge id again? It looks like an incorrectly decompressed archive.
>>
>
> I just tried this, to no avail.
>
> I'm trying
On 11/18/18 02:47, Alarig Le Lay wrote:
> Hi Daniel,
>
> Didi you tried to remove the temporary directory (inside /var/tmp) and
> re-emerge id again? It looks like an incorrectly decompressed archive.
>
I just tried this, to no avail.
I'm trying to rebuild the installed packages I have under
On 11/17/18 9:59 PM, Grant Edwards wrote:
> On 2018-11-18, james wrote:
>> On 11/17/18 6:51 PM, Grant Edwards wrote:
>>> On 2018-11-17, Mick wrote:
On Saturday, 17 November 2018 23:00:22 GMT Grant Edwards wrote:
> On 2018-11-17, james wrote:
>
>> Actually and AMD Arm (64bit)
On Sunday, 18 November 2018 13:49:12 GMT jdm wrote:
> On Sat, 17 Nov 2018 23:39:42 +
>
> Mick wrote:
> > On Saturday, 17 November 2018 10:55:21 GMT jdm wrote:
> > > Hi,
> > >
> > > I am trying to run virt-manager and or qemu with 3d acceleration
> > > using virtio-gpu options.
> > >
> > >
On Sat, 17 Nov 2018 23:39:42 +
Mick wrote:
> On Saturday, 17 November 2018 10:55:21 GMT jdm wrote:
> > Hi,
> >
> > I am trying to run virt-manager and or qemu with 3d acceleration
> > using virtio-gpu options.
> >
> > When I start the virtual machine in virt-manager all I get is a
> >
* Neil Bothwick:
> That's because ~ doesn't mean unstable, it means testing. Stable in
> this context means less likely to change, not less likely to fall
> over. Plus the differentiation is for the ebuilds, not the software
> itself.
It is also worth mentioning that ebuilds cannot be added to
On Sun, 18 Nov 2018 00:33:41 -0500, Andrew Udvare wrote:
> I switched fully to ACCEPT_KEYWORDS="~amd64" (make.conf) after running
> mixed for a while. These kinds of issues come up too often and I don't
> have a lot of time to solve them, plus for my dev machine I just don't
> notice stable vs
Hi Daniel,
Didi you tried to remove the temporary directory (inside /var/tmp) and
re-emerge id again? It looks like an incorrectly decompressed archive.
--
Alarig
13 matches
Mail list logo
