On 30/01/2017 01:06, Mick wrote:
> On Sunday 29 Jan 2017 22:10:59 Neil Bothwick wrote:
>> On Sun, 29 Jan 2017 19:17:47 +, Mick wrote:
Are you running fstrim once in a while like it's recommended?
Apparently using 'discard' as an option when mounting is no longer
recommended. On m
On Monday 30 Jan 2017 10:02:20 I wrote:
> On Sunday 29 Jan 2017 09:59:53 Daniel Frey wrote:
> > As far as monitoring, some vendors have tools for that I believe. They
> > usually do run SMART.
>
> I've found an off-line testing suite here [1], which I'll have a play
> with.
Oops!
[1] https:/
On Sunday 29 Jan 2017 09:59:53 Daniel Frey wrote:
> As far as monitoring, some vendors have tools for that I believe. They
> usually do run SMART.
I've found an off-line testing suite here [1], which I'll have a play with.
> Are you running fstrim once in a while like it's recommended? Apparentl
On 01/29/2017 03:06 PM, Mick wrote:
> On Sunday 29 Jan 2017 22:10:59 Neil Bothwick wrote:
>> On Sun, 29 Jan 2017 19:17:47 +, Mick wrote:
Are you running fstrim once in a while like it's recommended?
Apparently using 'discard' as an option when mounting is no longer
recommended. O
On Sun, 29 Jan 2017 23:06:23 +, Mick wrote:
> > Running fstrim frequently, or even using mount -o discard, might
> > negatively affect the lifetime of poor-quality SSD devices. For most
> > desktop and server systems a sufficient trimming frequency is once a
> > week. Note that not all device
On Sunday 29 Jan 2017 22:10:59 Neil Bothwick wrote:
> On Sun, 29 Jan 2017 19:17:47 +, Mick wrote:
> > > Are you running fstrim once in a while like it's recommended?
> > > Apparently using 'discard' as an option when mounting is no longer
> > > recommended. On my laptops I use a systemd timer t
On Sun, 29 Jan 2017 19:17:47 +, Mick wrote:
> > Are you running fstrim once in a while like it's recommended?
> > Apparently using 'discard' as an option when mounting is no longer
> > recommended. On my laptops I use a systemd timer to do this. Before
> > that I used anacron (I think it was a
On Sunday 29 Jan 2017 09:59:53 Daniel Frey wrote:
> On 01/29/2017 02:09 AM, Peter Humphrey wrote:
> >> Do you have a SSD? That sounds like symptoms of a failing SSD to me
> >> (it's happened more than once to me :/)
> >
> > Yes, nothing but one 256 GB NVMe drive in this box. Is there something
> >
On 01/29/2017 02:09 AM, Peter Humphrey wrote:
>> Do you have a SSD? That sounds like symptoms of a failing SSD to me
>> (it's happened more than once to me :/)
>
> Yes, nothing but one 256 GB NVMe drive in this box. Is there something like
> hdparm that will keep an eye on it for me?
>
> I hope
On Saturday 28 Jan 2017 08:40:04 Daniel Frey wrote:
> On 01/28/2017 03:16 AM, Peter Humphrey wrote:
> > On Thursday 26 Jan 2017 22:42:06 Alan McKinnon wrote:
> >> Somethng has gone wrong with your installation of portage or your copy
> >> of the tree - that "no ebuilds" message is impossible.
> >
On 01/28/2017 03:16 AM, Peter Humphrey wrote:
> On Thursday 26 Jan 2017 22:42:06 Alan McKinnon wrote:
>
>> Somethng has gone wrong with your installation of portage or your copy
>> of the tree - that "no ebuilds" message is impossible.
>
> Indeed so. So I've now built a fresh system and I'll see
On Thursday 26 Jan 2017 15:08:25 Dale wrote:
> OP. From my emerge --info:
>
> sync-uri: rsync://rsync26.us.gentoo.org/gentoo-portage
>
> That one worked just the other day. You may want to try it. Also,
> emerge-webrsync may be a option after trying another mirror. Also, if
> you change the
On Thursday 26 Jan 2017 22:42:06 Alan McKinnon wrote:
> Somethng has gone wrong with your installation of portage or your copy
> of the tree - that "no ebuilds" message is impossible.
Indeed so. So I've now built a fresh system and I'll see how that goes.
> It will probably be a cruel task to tr
On Thursday 26 January 2017 22:42:06 Alan McKinnon wrote:
> On 26/01/2017 17:35, Peter Humphrey wrote:
> > (Sent via webmail while I continue wrestling with KMail...)
> >
> > Alan McKinnon wrote :
> >> Does explicitly emerging gdbus-codegen-2.50.2 then re-running a world
> >> emerge give a differ
Mick wrote:
> On Thursday 26 Jan 2017 15:08:25 Dale wrote:
>> That's my thinking as well. I recall not long ago that I caught a bad
>> sync.. It was several days later that I was able to get a good one
>> and even then, it required me to switch to another mirror. I think in
>> my case, someone deci
On Thursday 26 Jan 2017 15:08:25 Dale wrote:
> That's my thinking as well. I recall not long ago that I caught a bad
> sync.. It was several days later that I was able to get a good one and
> even then, it required me to switch to another mirror. I think in my
> case, someone decided to shut do
On 01/26/2017 11:15 AM, Peter Humphrey wrote:
> Corbin Bird wrote :
>
>
>> If you would please, run this command and post the output ( a test in
>> other words ).
>>
>>> emerge -pvt dev-util/gdbus-codegen:0
> It wants to downgrade again, with the same output as I posted last time.
>
A package ver
Alan McKinnon wrote:
> On 26/01/2017 17:35, Peter Humphrey wrote:
>> (Sent via webmail while I continue wrestling with KMail...)
>>
>> Alan McKinnon wrote :
>>
>>> Does explicitly emerging gdbus-codegen-2.50.2 then re-running a world
>>> emerge give a different result?
>> peak ~ # emerj -1 =gdbus-
On 26/01/2017 17:35, Peter Humphrey wrote:
> (Sent via webmail while I continue wrestling with KMail...)
>
> Alan McKinnon wrote :
>
>> Does explicitly emerging gdbus-codegen-2.50.2 then re-running a world
>> emerge give a different result?
>
> peak ~ # emerj -1 =gdbus-codegen-2.50.2
> Calculat
On Thu, 26 Jan 2017 17:15:04 +, Peter Humphrey wrote:
> > If you would please, run this command and post the output ( a test in
> > other words ).
> >
> > > emerge -pvt dev-util/gdbus-codegen:0
>
> It wants to downgrade again, with the same output as I posted last time.
The addition of
Corbin Bird wrote :
> If you would please, run this command and post the output ( a test in
> other words ).
>
> > emerge -pvt dev-util/gdbus-codegen:0
It wants to downgrade again, with the same output as I posted last time.
--
Regards,
Peter.
Dale wrote :
> I'd try a fresh sync first. Maybe something went wrong during the last
> one?? Here is some info from mine:
Yes, that was my first thought, but I've sync'd several times in the last 24
hours so that isn't it.
> root@fireball / # equery l -p gobject-introspection
> * Searching
On 01/26/2017 09:35 AM, Peter Humphrey wrote:
> (Sent via webmail while I continue wrestling with KMail...)
>
> Alan McKinnon wrote :
>
>> Does explicitly emerging gdbus-codegen-2.50.2 then re-running a world
>> emerge give a different result?
> peak ~ # emerj -1 =gdbus-codegen-2.50.2
> Calculati
Peter Humphrey wrote:
> (Sent via webmail while I continue wrestling with KMail...)
>
> Alan McKinnon wrote :
>
>> Does explicitly emerging gdbus-codegen-2.50.2 then re-running a world
>> emerge give a different result?
> peak ~ # emerj -1 =gdbus-codegen-2.50.2
> Calculating dependencies ... done
(Sent via webmail while I continue wrestling with KMail...)
Alan McKinnon wrote :
> Does explicitly emerging gdbus-codegen-2.50.2 then re-running a world
> emerge give a different result?
peak ~ # emerj -1 =gdbus-codegen-2.50.2
Calculating dependencies ... done!
emerge: there are no ebuilds t
On 26/01/2017 12:10, Peter Humphrey wrote:
> Hello list,
>
> Today I have a block that I can't see a way out of.
>
> [blocks B ] codegen-2.50.2" is blocking dev-libs/glib-2.50.2)
> [...]
> (dev-util/gdbus-codegen-2.48.2:0/0::gentoo, ebuild scheduled for merge)
> pulled in by
> dev-ut
Hello list,
Today I have a block that I can't see a way out of.
[blocks B ] =dev-util/gdbus-codegen-2.32 required by (sys-fs/
udisks-2.1.8:2/2::gentoo, installed)
>=dev-util/gdbus-codegen-2.48 required by (x11-libs/gtk
+-3.22.5:3/3::gentoo, installed)
dev-util/gdbus-codegen required
27 matches
Mail list logo
