On Fri, May 30, 2008 at 11:30 AM, Eric Belanger <belanger@astro.umontreal.ca> wrote:
On Fri, 30 May 2008, Thayer Williams wrote:
On Fri, May 30, 2008 at 10:16 AM, Travis Willard <travis@archlinux.org> wrote:
On Fri, May 30, 2008 at 1:01 PM, Thayer Williams <thayer@archlinux.org> wrote:
I've updated the kde-common package for i686, but I can't build it for x86_64. I guess it's time to start looking for a 3rd computer...
Actually, this is one of those packages that could easily be for the 'any' arch. Basically, since it's all scripts, and all of 'em are just copied into the proper locations, you can cheat - change your arch in makepkg.conf, rebuild the package (generating an x86_64 package, which is identical to the i686 one) and upload it, then change back your makepkg.conf
Since you're not building any code, this'll work fine.
...splitting this thread before its deviates further:
I just attempted to commit an x86_64 package and extrapkg spat out:
scp: staging/extra64/add/kde-common-3.5.9-2-x86_64.pkg.tar.gz: No such file or directory md5sum: staging/extra64/add/kde-common-3.5.9-2-x86_64.pkg.tar.gz: No such file or directory File got corrupted during upload, cancelled.
I had removed the {repo}64 dirs from ~/staging last week after reading somewhere that we didn't need these any longer. However, as soon as I added them again the package committed as expected. Is this is a bug or did I miss something else about the staging dirs?
You still need the {repo}64 staging dir. It's only after the devtools will be updated that these {repo}64 dirs will be no longer needed.
OK gotcha. Someone had updated the DeveloperWiki to reflect this change so I assumed it was in effect.