Hi David,
> It doesn't matter whether you use the
> latest install set or the one from 3 'releases' back, after the first update,
> you will have the exact same, current Arch Linux we all have. It is the
> smartest
> way to do a Linux distribution -- hands down.
I don't agree with you. For 99 % (
On Wed, Apr 07, 2010 at 07:51:54PM +0200, Pierre Schmitz wrote:
> On Wed, 07 Apr 2010 12:44:22 -0500, "David C. Rankin"
> wrote:
> > ... It doesn't matter whether you use
> > the
> > latest install set or the one from 3 'releases' back, after the first
> > update,
> > you will have the exact same
On Wed, 07 Apr 2010 13:45:41 -0500, "David C. Rankin"
wrote:
> I missed that completely in my train of thought. But without the change
in
> package compression it would still hold true. Prior to the xz
compression
> change, I had had no problems using the 2/09 install media even after
the
>
On 04/07/2010 12:51 PM, Pierre Schmitz wrote:
>
> It's not entirely true. You always should install using the latest iso and
> it is also important to release new isos regularly. Due to our continuous
> updates and changes old isos and especially netinstall are broken. For
> example you cannot run
On 04/07/2010 12:56 PM, Evangelos Foutras wrote:
> Add a ServerFlags section to your xorg.conf and inside that insert:
>
> Option "IgnoreABI" "True"
>
> When a new driver is released that recognizes the new xorg-server
> version, you can remove that.
Thank you Evangelos.
Hopefully DR's issu
>>
>> (p.s. this is 'in addition to' and not 'in lieu of' the current topic)
>>
>
> This is a complete thread hijacking, has nothing to do with the
> current topic, and adds NOTHING to it.
>
> darose updated to the Xserver in EXTRA which is 1.7.5.902-1
>
> nvidia works fine in extra, even in tes
On Wed, 2010-04-07 at 12:44 -0500, David C. Rankin wrote:
>
> ( if the other distros were 1/2 as smart as Arch, they would all be using a
> rolling-release model... )
>
>
Not true. If you want a distro that "just works", you need to really
test a lot before you change a version of the package
On Wed, 2010-04-07 at 20:56 +0300, Evangelos Foutras wrote:
> On Wed, Apr 7, 2010 at 8:35 PM, David C. Rankin
> wrote:
> > On the same note, after the latest Xorg update, X (nVidia card) was failing
> > to
> > start on the same xorg.conf I had used with my arch box since I first
> > installed
>
On Wed, Apr 7, 2010 at 7:35 PM, David C. Rankin
wrote:
> On 04/07/2010 09:55 AM, David Rosenstrauch wrote:
>> On 04/07/2010 10:46 AM, Xavier Chantry wrote:
>>> Can you attach full Xorg log and config ?
>>
>> I'm not using any xorg config. Log is at:
>>
>> http://www.darose.net/Xorg.0.log
>>
>>> A
On Wed, Apr 7, 2010 at 7:59 PM, David Rosenstrauch wrote:
>
> Anybody have any ideas on this? GUI is completely unusable on the server
> until I solve this! :-(
>
> I really have zero idea what's going on. And it's a difficult thing to find
> good specific search terms for, as there's been nume
On 04/07/2010 10:55 AM, David Rosenstrauch wrote:
On 04/07/2010 10:46 AM, Xavier Chantry wrote:
Can you attach full Xorg log and config ?
I'm not using any xorg config. Log is at:
http://www.darose.net/Xorg.0.log
And does it work with xf86-input-keyboard driver ?
I have xf86-input-keyboar
On Wed, Apr 7, 2010 at 8:35 PM, David C. Rankin
wrote:
> On the same note, after the latest Xorg update, X (nVidia card) was failing to
> start on the same xorg.conf I had used with my arch box since I first
> installed
> arch.
Add a ServerFlags section to your xorg.conf and inside that insert:
On Wed, 07 Apr 2010 12:44:22 -0500, "David C. Rankin"
wrote:
> ... It doesn't matter whether you use
> the
> latest install set or the one from 3 'releases' back, after the first
> update,
> you will have the exact same, current Arch Linux we all have.
It's not entirely true. You always should i
On 04/03/2010 04:59 PM, Keith Hinton wrote:
> Hi,
> First of all, if anyone is curious as to why I have posted to the
> Arch-General mailing list, I'm mainly doing this, in case any of the
> Arch Release team is actually hanging out on this list.
> I was curious, seeing as the last Arch Linux relea
On 04/07/2010 09:55 AM, David Rosenstrauch wrote:
> On 04/07/2010 10:46 AM, Xavier Chantry wrote:
>> Can you attach full Xorg log and config ?
>
> I'm not using any xorg config. Log is at:
>
> http://www.darose.net/Xorg.0.log
>
>> And does it work with xf86-input-keyboard driver ?
>
> I have x
On Wed, Apr 7, 2010 at 10:16 AM, Allan McRae wrote:
> On 08/04/10 00:54, Florian Pritz wrote:
>>
>> On 07.04.2010 16:10, Allan McRae wrote:
>>>
>>> This would really not help here. Pacman does not directly link openssl,
>>> but does through libarchive and libfetch. Adding versioned libarchive
>>
On 08/04/10 00:54, Florian Pritz wrote:
On 07.04.2010 16:10, Allan McRae wrote:
This would really not help here. Pacman does not directly link openssl,
but does through libarchive and libfetch. Adding versioned libarchive
and libfetch to pacman's deps and using sodeps on openssl in those
packa
On 04/07/2010 10:46 AM, Xavier Chantry wrote:
Can you attach full Xorg log and config ?
I'm not using any xorg config. Log is at:
http://www.darose.net/Xorg.0.log
And does it work with xf86-input-keyboard driver ?
I have xf86-input-keyboard installed. I assumed X was just
automatically
On 07.04.2010 16:10, Allan McRae wrote:
> This would really not help here. Pacman does not directly link openssl,
> but does through libarchive and libfetch. Adding versioned libarchive
> and libfetch to pacman's deps and using sodeps on openssl in those
> packages would prevent pacman's SyncF
On Wed, Apr 7, 2010 at 4:32 PM, David Rosenstrauch wrote:
> I upgraded my extremely not-up-to-date server last night (523 packages
> upgraded). The upgrade generally went well, except for one significant
> issue: the keyboard is no longer working under Xorg. It works fine in a
> command line tt
I upgraded my extremely not-up-to-date server last night (523 packages
upgraded). The upgrade generally went well, except for one significant
issue: the keyboard is no longer working under Xorg. It works fine in
a command line tty though (i.e., ctrl-alt-F1).
Not sure what the problem is, as
On 07/04/10 23:47, Florian Pritz wrote:
On 07.04.2010 06:42, Pierre Schmitz wrote:
I just tested what happens if I change pacman depends to
"'libarchive>=2.8.3-3' 'libfetch>=2.30-3'".
Maybe start using sodeps to generate those dependencies? libfetch
(doesn't have a soname with version btw) wou
On 07.04.2010 06:42, Pierre Schmitz wrote:
> I just tested what happens if I change pacman depends to
> "'libarchive>=2.8.3-3' 'libfetch>=2.30-3'".
Maybe start using sodeps to generate those dependencies? libfetch
(doesn't have a soname with version btw) would depend on the new openssl
libs and p
On Wed, Apr 07, 2010 at 11:49:10AM +0200, Thomas Bächler wrote:
> Am 30.03.2010 03:36, schrieb Pierre Schmitz:
> > I created a rebuld list for the just released openssl 1.0.0 (Thanks Dan
> > for fixing the todo list that fast!). These are 236 packages for each
> > architecture; so this will need so
On 7 April 2010 17:24, wrote:
> On Wed, Apr 07, 2010 at 02:21:20AM +0200, Philipp wrote:
>
>> Excerpts from fons's message of 2010-04-07 00:46:09 +0200:
>> > It seems like Arch is currently offering Jack and qjackctl
>> > packages that are not compatible.
>> >
>> > The Jack authors changed one so
On Wed, Apr 07, 2010 at 02:21:20AM +0200, Philipp wrote:
> Excerpts from fons's message of 2010-04-07 00:46:09 +0200:
> > It seems like Arch is currently offering Jack and qjackctl
> > packages that are not compatible.
> >
> > The Jack authors changed one some command line options
> > in 0.118. '
Excerpts from Allan McRae's message of 2010-04-07 03:06:50 +0200:
> On 07/04/10 10:21, Philipp wrote:
> > Excerpts from fons's message of 2010-04-07 00:46:09 +0200:
> >> It seems like Arch is currently offering Jack and qjackctl
> >> packages that are not compatible.
> >>
> >> The Jack authors chan
27 matches
Mail list logo
