They are not. Any packages are not supported yet. We are testing support for
any packages in addition to split packages on the main arch server. When
this is complete, I will release new dbscripts
Do I need to replace ('any') with ('i686' 'x86_64') in the PKGBUILD for
inclusion in [community]
2009/7/20 Xyne x...@archlinux.ca:
They are not. Any packages are not supported yet. We are testing support for
any packages in addition to split packages on the main arch server. When
this is complete, I will release new dbscripts
Do I need to replace ('any') with ('i686' 'x86_64') in the
On Mon, Jul 20, 2009 at 10:29 AM, Abhishek Dasguptaabh...@gmail.com wrote:
2009/7/20 Xyne x...@archlinux.ca:
They are not. Any packages are not supported yet. We are testing support for
any packages in addition to split packages on the main arch server. When
this is complete, I will release
On Fri, 17 Jul 2009 16:32:12 -0700
Aaron Griffin aaronmgrif...@gmail.com wrote:
Renaming packages is no longer necessary. In fact, the scripts require the
arch in the package now. You're using the same scripts which run the
official repos, so they should do things correctly.
Note that
They are not. Any packages are not supported yet. We are testing support for
any packages in addition to split packages on the main arch server. When
this is complete, I will release new dbscripts
On Jul 18, 2009 5:43 PM, Xyne x...@archlinux.ca wrote:
On Fri, 17 Jul 2009 16:32:12 -0700
Aaron
In the future, mails like this will be autogenerated and sent to the
arch-commits list.
Do you guys want your own commits list? Do you want this mail sent
elsewhere? Let me know
If something gets bungled, packages still exist in
/srv/package-cleanup for you to pull out if you need it. An admin
Aaron Griffin wrote:
In the future, mails like this will be autogenerated and sent to the
arch-commits list.
Do you guys want your own commits list? Do you want this mail sent
elsewhere? Let me know
If something gets bungled, packages still exist in
/srv/package-cleanup for you to pull out if
Renaming packages is no longer necessary. In fact, the scripts require the
arch in the package now. You're using the same scripts which run the
official repos, so they should do things correctly.
Note that existing packages are fine, but all packages in the future MUST
have the arch in the
On Sat, Jul 18, 2009 at 2:32 AM, Aaron Griffinaaronmgrif...@gmail.com wrote:
Renaming packages is no longer necessary. In fact, the scripts require the
arch in the package now. You're using the same scripts which run the
official repos, so they should do things correctly.
Note that existing
