I made a new set of ISOs for the Arch64 port. I used tpowa's
mkbootcd/archboot - these're great tools. CDs were made with all current
packages up to date until yesterday.
This time we have a full current cd(still uploading), a base cd and a
ftp-only cd. So please test them and report bugs you will surely find.
Network detection worked for me, trying a ftp install worked also well
using ftp.archlinux.org.
We use the same installer as arch32. So look for bugs in the installer
and in our current packages as well.
The CDs include the new glibc, openssl, db and gnutils updates. So it's
not recommended to use the arch64.org repos anymore when you use the
new cds. I'll try to fix and update all extra packages as soon as
possible to get missing dependencies resolved. Until that you may
decide to wait or try old arch64.org extra repo for missing packages.
Good luck and praying for no showstopper bugs!
And here they are: http://www.archlinux.org/~andyrtr/
AndyRTR
I finished bringing all packages from arch64.org into the new extra repo
db on archlinux.org. If you still find a package laying on the ftp and
it's not in the repo db let me know.
Now I'm going to keep the repos up to date and fix bugs you report. A
new ISO is in work.
Community repo and AUR are up to you all out there.
From now on forget Arch64.org - it may rest in peace.
AndyRTR
Now that the x86_64 port is official we want to make it as good as
ArchLinux (i686). You may have noticed that I'm doing most time a
one-man-job. And that's now too much work for one person to keep all
packages up to date in an acceptable time.
Great news: i686 devs and also TUs want to help us. They offer their
time to build the packages they maintain for a second time.
What we need: a build farm running several machines Arch64.
We will use pacbuild. The great distributed package building tool from
Xentac. Read here more about it:
http://wiki.archlinux.org/index.php/Pacbuild and
http://xentac.net/~jchu/blog/static/pacbuild
i686 package maintainers and TrustedUsers will get accounts to sent
pkgbuilds to the farm. The main server will send it further to a pc
running the local build daemon. The more pcs we have running Arch64 with
pacbuild daemon the lower the load will be.
Who can offer his pc for running the pacbuild daemon? What you need:
just a clean(!) Arch64 installation for correct linking. So there should
be only official packages from current/extra and later community on it.
A separate system would be nice but is not a must.
Don't be afraid. There's no need to have a ssh deamon running. The
system should be online most time. 24/7 up would be great.
I will also offer one or two systems. We will test the
configuration.
It would be great to have more systems later running the build daemon so
the nice load would get much lower.
So who will join the packaging party?
AndyRTR
Hi everyone,
Does amarok-1.4.1 with the xine engine work ok for you in Arch64? I'm
getting "xine-engine claims it cannot play MP3's". Please let me know so
I can figure out if its a package problem or whether my installation is
corrupt.
ganja_guru
On Wednesday 12 July 2006 20:10, slubman wrote:
> > Now that the x86_64 port is official we want to make it as good as
> > ArchLinux (i686). You may have noticed that I'm doing most time a
> > one-man-job. And that's now too much work for one person to keep all
> > packages up to date in an acceptable time.
> >
> > Great news: i686 devs and also TUs want to help us. They offer their
> > time to build the packages they maintain for a second time.
> >
> > What we need: a build farm running several machines Arch64.
> >
> > We will use pacbuild. The great distributed package building tool from
> > Xentac. Read here more about it:
> >
> > http://wiki.archlinux.org/index.php/Pacbuild and
> > http://xentac.net/~jchu/blog/static/pacbuild
> >
> > i686 package maintainers and TrustedUsers will get accounts to sent
> > pkgbuilds to the farm. The main server will send it further to a pc
> > running the local build daemon. The more pcs we have running Arch64 with
> > pacbuild daemon the lower the load will be.
> >
> > Who can offer his pc for running the pacbuild daemon? What you need:
> > just a clean(!) Arch64 installation for correct linking. So there should
> > be only official packages from current/extra and later community on it.
> > A separate system would be nice but is not a must.
> >
> > Don't be afraid. There's no need to have a ssh deamon running. The
> > system should be online most time. 24/7 up would be great.
> >
> > I will also offer one or two systems. We will test the
> > configuration.
> >
> > It would be great to have more systems later running the build daemon so
> > the nice load would get much lower.
> >
> > So who will join the packaging party?
> >
> > AndyRTR
>
> Hello
>
> I wan't to add my arch64 to the "farm". Do i have to send the mail to the
> guy in the wiki, or is someone else responsible for the arch64 port ?
I cant't find an answer of this question too... I asked Jason for username and
password for the x86_64 farm but no answer yet.
> Now that the x86_64 port is official we want to make it as good as
> ArchLinux (i686). You may have noticed that I'm doing most time a
> one-man-job. And that's now too much work for one person to keep all
> packages up to date in an acceptable time.
>
> Great news: i686 devs and also TUs want to help us. They offer their
> time to build the packages they maintain for a second time.
>
> What we need: a build farm running several machines Arch64.
>
> We will use pacbuild. The great distributed package building tool from
> Xentac. Read here more about it:
>
> http://wiki.archlinux.org/index.php/Pacbuild and
> http://xentac.net/~jchu/blog/static/pacbuild
>
> i686 package maintainers and TrustedUsers will get accounts to sent
> pkgbuilds to the farm. The main server will send it further to a pc
> running the local build daemon. The more pcs we have running Arch64 with
> pacbuild daemon the lower the load will be.
>
> Who can offer his pc for running the pacbuild daemon? What you need:
> just a clean(!) Arch64 installation for correct linking. So there should
> be only official packages from current/extra and later community on it.
> A separate system would be nice but is not a must.
>
> Don't be afraid. There's no need to have a ssh deamon running. The
> system should be online most time. 24/7 up would be great.
>
> I will also offer one or two systems. We will test the
> configuration.
>
> It would be great to have more systems later running the build daemon so
> the nice load would get much lower.
>
> So who will join the packaging party?
>
> AndyRTR
Hello
I wan't to add my arch64 to the "farm". Do i have to send the mail to the guy
in the wiki, or is someone else responsible for the arch64 port ?
--
slubman (aka Nicolas DOUALOT)
mail: slubman(a)slubman.net
jabber ID: slubman(a)kdetalk.net
site: http://www.slubman.net
FTP install is now possible from all mirrors again and should be the
prefered way to install a fresh Arch64 from now on to not go in trouble
with the glibc update.
Also our current repo is fresh as the 32bit one again :)
http://home.arcor.de/a.radke/arch64/list/pkg_diff.html
Updating extra packages and a new ISO will be the next steps.
AndyRTR