* Bad instructions on linuxwireless.org?
@ 2011-06-14 19:07 Thomas Novin
2011-06-14 19:11 ` Luis R. Rodriguez
0 siblings, 1 reply; 4+ messages in thread
From: Thomas Novin @ 2011-06-14 19:07 UTC (permalink / raw)
To: linux-wireless
Hi all
Just updated to a newer compat-wireless on my Ubuntu 11.04 system using
instructions on
http://linuxwireless.org/en/users/Download#Requirements_for_bleeding_edge.
It is often referred to that you should use 'date -I' to get the correct
directory. This expands to todays date in format of YYYY-MM-DD or
2011-06-14 for today.
However, extracting
http://wireless.kernel.org/download/compat-wireless-2.6/compat-wireless-2.6.tar.bz2 gives you a compat-wireless-2011-06-01 directory, not 2011-06-14.
I noticed in the archive that it is indeed from today with files dated
at least from yesterday.
Rgds//T
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Bad instructions on linuxwireless.org?
2011-06-14 19:07 Bad instructions on linuxwireless.org? Thomas Novin
@ 2011-06-14 19:11 ` Luis R. Rodriguez
2011-06-14 20:11 ` Thomas Novin
0 siblings, 1 reply; 4+ messages in thread
From: Luis R. Rodriguez @ 2011-06-14 19:11 UTC (permalink / raw)
To: Thomas Novin; +Cc: linux-wireless
On Tue, Jun 14, 2011 at 12:07 PM, Thomas Novin <thomas@xyz.pp.se> wrote:
> Hi all
>
> Just updated to a newer compat-wireless on my Ubuntu 11.04 system using
> instructions on
> http://linuxwireless.org/en/users/Download#Requirements_for_bleeding_edge.
>
> It is often referred to that you should use 'date -I' to get the correct
> directory. This expands to todays date in format of YYYY-MM-DD or
> 2011-06-14 for today.
>
> However, extracting
> http://wireless.kernel.org/download/compat-wireless-2.6/compat-wireless-2.6.tar.bz2 gives you a compat-wireless-2011-06-01 directory, not 2011-06-14.
>
> I noticed in the archive that it is indeed from today with files dated
> at least from yesterday.
Try again, a new tarball just baked.
Luis
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Bad instructions on linuxwireless.org?
2011-06-14 19:11 ` Luis R. Rodriguez
@ 2011-06-14 20:11 ` Thomas Novin
2011-06-14 21:21 ` Luis R. Rodriguez
0 siblings, 1 reply; 4+ messages in thread
From: Thomas Novin @ 2011-06-14 20:11 UTC (permalink / raw)
To: Luis R. Rodriguez; +Cc: linux-wireless
On Tue, Jun 14, 2011 at 9:11 PM, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
>
> Try again, a new tarball just baked.
>
That worked, the previous one was baked 2011-06-13 so why was my
directory named 2011-06-01 instead of that? I downloaded it just 15
minutes before sending that first email.
But OK, maybe a temporary problem.
Thanks//T
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Bad instructions on linuxwireless.org?
2011-06-14 20:11 ` Thomas Novin
@ 2011-06-14 21:21 ` Luis R. Rodriguez
0 siblings, 0 replies; 4+ messages in thread
From: Luis R. Rodriguez @ 2011-06-14 21:21 UTC (permalink / raw)
To: Thomas Novin; +Cc: linux-wireless
On Tue, Jun 14, 2011 at 1:11 PM, Thomas Novin <thomas@xyz.pp.se> wrote:
> On Tue, Jun 14, 2011 at 9:11 PM, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
>>
>> Try again, a new tarball just baked.
>>
>
> That worked, the previous one was baked 2011-06-13 so why was my
> directory named 2011-06-01 instead of that? I downloaded it just 15
> minutes before sending that first email.
>
> But OK, maybe a temporary problem.
When compat-wireless cannot run ./scripts/admin-update.sh it barfs and
does not make a tarball. After I applied Hauke's new patches it was
able to run that fine and we get a tarball out.
Luis
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2011-06-14 21:21 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-06-14 19:07 Bad instructions on linuxwireless.org? Thomas Novin
2011-06-14 19:11 ` Luis R. Rodriguez
2011-06-14 20:11 ` Thomas Novin
2011-06-14 21:21 ` Luis R. Rodriguez
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox