On 25 July 2010 18:45, Ionuț Bîru wrote:
> On 07/25/2010 07:37 PM, Guillaume ALAUX wrote:
>
>> On 25 July 2010 18:17, Ionuț Bîru wrote:
>>
>> On 07/25/2010 07:14 PM, Peter Lewis wrote:
>>>
>>> Hi,
On Sunday 25 Jul 2010 at 16:50 Guillaume ALAUX wrote:
I also have some sugge
On 07/25/2010 07:37 PM, Guillaume ALAUX wrote:
On 25 July 2010 18:17, Ionuț Bîru wrote:
On 07/25/2010 07:14 PM, Peter Lewis wrote:
Hi,
On Sunday 25 Jul 2010 at 16:50 Guillaume ALAUX wrote:
I also have some suggestions for these packages:
- rename them from {jre,jdk} to {java6-sun-jre,java
On 25 July 2010 18:17, Ionuț Bîru wrote:
> On 07/25/2010 07:14 PM, Peter Lewis wrote:
>
>> Hi,
>>
>> On Sunday 25 Jul 2010 at 16:50 Guillaume ALAUX wrote:
>>
>>> I also have some suggestions for these packages:
>>> - rename them from {jre,jdk} to {java6-sun-jre,java6-sun-jdk} or so would
>>> enab
On 07/25/2010 07:14 PM, Peter Lewis wrote:
Hi,
On Sunday 25 Jul 2010 at 16:50 Guillaume ALAUX wrote:
I also have some suggestions for these packages:
- rename them from {jre,jdk} to {java6-sun-jre,java6-sun-jdk} or so would
enable us to use different versions of SUN's JVM (Java5, 6 and 7)
Wel
Hi,
On Sunday 25 Jul 2010 at 16:50 Guillaume ALAUX wrote:
> I also have some suggestions for these packages:
> - rename them from {jre,jdk} to {java6-sun-jre,java6-sun-jdk} or so would
> enable us to use different versions of SUN's JVM (Java5, 6 and 7)
Well the open jdk package is called "openjdk
Hi everyone,
"community/jre" and "community/jdk" packages are out of date.
I have merged the two PKGBUILDs in one split PKGBUILD (enclosed to this
email with the srcpkg) and updated the links and md5sums.
It works fine on my i686 Arch. Will test it on x64 tonight when at home.
Would someone wan
On Sun, Jul 25, 2010 at 8:38 PM, Ionuț Bîru wrote:
> On 07/25/2010 01:56 PM, Jordan Windsor wrote:
>>
>> On Sun, Jul 25, 2010 at 8:06 PM, Ionuț Bîru wrote:
>>>
>>> On 07/25/2010 01:13 PM, Jordan Windsor wrote:
On Sun, Jul 25, 2010 at 6:41 PM, Norbert Zeh wrote:
>
> PT M. [201
On 24/07/10 02:55, Dan Vratil wrote:
I tried the latest version of mailman (2.1.13) as you suggested. I used the
PKGBUILD from SVN trunk, but I modified it, so that it does not require
/home/mailman and mailman user and group to exist during build and I modified
the mailman.install file so that u
On 07/25/2010 01:56 PM, Jordan Windsor wrote:
On Sun, Jul 25, 2010 at 8:06 PM, Ionuț Bîru wrote:
On 07/25/2010 01:13 PM, Jordan Windsor wrote:
On Sun, Jul 25, 2010 at 6:41 PM, Norbert Zehwrote:
PT M. [2010.07.25 1606 +0800]:
There's the line "Architecture = auto" in the new pacman.con
On 25/07/10 20:56, Jordan Windsor wrote:
On Sun, Jul 25, 2010 at 8:06 PM, Ionuț Bîru wrote:
On 07/25/2010 01:13 PM, Jordan Windsor wrote:
On Sun, Jul 25, 2010 at 6:41 PM, Norbert Zehwrote:
PT M. [2010.07.25 1606 +0800]:
There's the line "Architecture = auto" in the new pacman.conf, ma
On Sun, Jul 25, 2010 at 8:06 PM, Ionuț Bîru wrote:
> On 07/25/2010 01:13 PM, Jordan Windsor wrote:
>>
>> On Sun, Jul 25, 2010 at 6:41 PM, Norbert Zeh wrote:
>>>
>>> PT M. [2010.07.25 1606 +0800]:
There's the line "Architecture = auto" in the new pacman.conf, maybe you
can
spec
On 07/25/2010 01:13 PM, Jordan Windsor wrote:
On Sun, Jul 25, 2010 at 6:41 PM, Norbert Zeh wrote:
PT M. [2010.07.25 1606 +0800]:
There's the line "Architecture = auto" in the new pacman.conf, maybe you can
specify i686 here.
This is exactly what resolved the problem for me. Found this advic
On Sun, Jul 25, 2010 at 6:41 PM, Norbert Zeh wrote:
> PT M. [2010.07.25 1606 +0800]:
>> There's the line "Architecture = auto" in the new pacman.conf, maybe you can
>> specify i686 here.
>
> This is exactly what resolved the problem for me. Found this advice
> by googling a bit.
>
> - Norbert
>
>
Am 23.07.2010 12:39, schrieb Nathan Wayde:
> On 23/07/10 11:36, Florian Pritz wrote:
>> On 23.07.2010 12:27, Mario Daniel Carugno wrote:
>>> First i present myself. My name is Mario and i was reading this list
>>> for a few weeks.
>>> I'm coming from Debian, [...]
>>
>> Welcome :)
>>
>>> For instan
PT M. [2010.07.25 1606 +0800]:
> There's the line "Architecture = auto" in the new pacman.conf, maybe you can
> specify i686 here.
This is exactly what resolved the problem for me. Found this advice
by googling a bit.
- Norbert
--
() ascii ribbon campaign - against html e-mail
/\ www.asci
On 07/25/2010 10:52 AM, Jordan Windsor wrote:
I'm following the guide available at this URL:
http://wiki.archlinux.org/index.php/Arch64_Install_bundled_32bit_system
Currently I'm stuck on this step:
[r...@archpc ~]# pacman --root /opt/arch32 --cachedir
/opt/arch32/var/cache/pacman/pkg --config /
There's the line "Architecture = auto" in the new pacman.conf, maybe you can
specify i686 here.
On Sun, Jul 25, 2010 at 3:52 PM, Jordan Windsor wrote:
> I'm following the guide available at this URL:
> http://wiki.archlinux.org/index.php/Arch64_Install_bundled_32bit_system
> Currently I'm stuck
On Sun, 25 Jul 2010 17:22:45 +0930
Jordan Windsor wrote:
> I'm following the guide available at this URL:
> http://wiki.archlinux.org/index.php/Arch64_Install_bundled_32bit_system
> Currently I'm stuck on this step:
>
> [r...@archpc ~]# pacman --root /opt/arch32 --cachedir
> /opt/arch32/var/cache
I'm following the guide available at this URL:
http://wiki.archlinux.org/index.php/Arch64_Install_bundled_32bit_system
Currently I'm stuck on this step:
[r...@archpc ~]# pacman --root /opt/arch32 --cachedir
/opt/arch32/var/cache/pacman/pkg --config /opt/arch32/pacman.conf -S
base base-devel
error:
19 matches
Mail list logo
