On Fri, Apr 28, 2017 at 6:43 PM, Eric Blau wrote:
> On Fri, Apr 28, 2017 at 2:19 PM, Carsten Mattner
> wrote:
>> On Fri, Apr 28, 2017 at 5:11 PM, Eric Blau wrote:
>>> On Fri, Apr 28, 2017 at 12:29 PM, Carsten Mattner via arch-general
>>> wrote:
>>>
>>> There's a fix that's been submitted to the
On Fri, Apr 28, 2017 at 6:34 PM, Eric Blau wrote:
> On Fri, Apr 28, 2017 at 2:20 PM, Carsten Mattner
> wrote:
>> Eric, does it also fail in XFCE or GNOME3? Like I wrote, I've found
>> Plasma's compositor to be buggier.
>
> I use i3 with compton as a compositor. Maybe I would have better luck
> ru
On Fri, Apr 28, 2017 at 2:19 PM, Carsten Mattner
wrote:
> On Fri, Apr 28, 2017 at 5:11 PM, Eric Blau wrote:
>> On Fri, Apr 28, 2017 at 12:29 PM, Carsten Mattner via arch-general
>> wrote:
>>
>> There's a fix that's been submitted to the tip, but no effort has
>> been made to patch the bug in the
On Fri, Apr 28, 2017 at 2:20 PM, Carsten Mattner
wrote:
> Eric, does it also fail in XFCE or GNOME3? Like I wrote, I've found
> Plasma's compositor to be buggier.
I use i3 with compton as a compositor. Maybe I would have better luck
running 4.10.x without compton. I haven't tried that yet.
I rev
Eric, does it also fail in XFCE or GNOME3? Like I wrote, I've found
Plasma's compositor to be buggier.
On Fri, Apr 28, 2017 at 5:11 PM, Eric Blau wrote:
> On Fri, Apr 28, 2017 at 12:29 PM, Carsten Mattner via arch-general
> wrote:
> >
> > The constant churn of refactorings and whatnot makes it impossible
> > for all the hardware that say i915 supports to actually work
> > reliably across kernel re
On Fri, Apr 28, 2017 at 12:29 PM, Carsten Mattner via arch-general
wrote:
>
> The constant churn of refactorings and whatnot makes it impossible for
> all the hardware that say i915 supports to actually work reliably
> across kernel releases. What used to work flawlessly in 4.1 can be
> broken in
On Fri, Apr 28, 2017 at 12:40 PM, fnodeuser wrote:
> Tobias Powalowski,
>
> you continue to place pkgs in the testing repo that do not require
> any further testing.
>
> for what reasons, exactly, do the linux 4.10.13 and hwids 20170328
> pkgs need to be in testing for 4+ days?
>
> also, you did n
Today is the 28th, and the date reported by pacman is the 27th.
Suggestion to OP:
# ntpdate your.favorite.mirror.ntp.org
Because to me it just looks like he might be a few multiples of 86400
seconds off.
On a similar note, I wonder why you didn't complain that the new ELF
binary was apparently b
1) Tobias: Thank you for doing a terrific and diligent job packaging
and testing kernels and, which come into testing in short order.
2) Florian: Thank you for your comments - agree completely.
3) Adding to what Florian said - Testing also allows Arch users to
signoff after performing
On 28.04.2017 14:40, fnodeuser wrote:
> you continue to place pkgs in the testing repo that do not require any
> further testing.
Thank you for showing that you do not understand our repository policy.
All [core] packages go to [testing] first to ensure that we do not
completely break anyone's s
Tobias Powalowski,
you continue to place pkgs in the testing repo that do not require any further
testing.
for what reasons, exactly, do the linux 4.10.13 and hwids 20170328 pkgs need to
be in
testing for 4+ days?
also, you did not replace git:// with git+https:// in the hwids PKGBUILD file.
On 27 April 2017 at 23:16, David Runge wrote:
> Sounds great. Before the beginning of July I don't have much time
> though, as I'm in the same boat you were in (thesis and all that
> madness).
>
> On the plus side: I have been using Arch for about 10 years now and it
> would be nice to get a littl
13 matches
Mail list logo
