adopting package as tu

xerxes2 · 2005-07-25 18:35:04

hello guys!
i've just put psyco in community and then tried to adopt the existing package at aur but it doesn't seems to work,

should i adopt the package before i upload to community?
what is the right way to do it?

Dusty · 2005-07-25 19:09:40

I think you'd ask the aur-users list that, eh?

Dusty

phrakture · 2005-07-25 20:03:20

xerxes2 wrote:

hello guys!
i've just put psyco in community and then tried to adopt the existing package at aur but it doesn't seems to work,
should i adopt the package before i upload to community?
what is the right way to do it?

No... here's how it works (most is this is gleened from neotuli):

do your community build, cvs ci PKGBUILD (and other files), cvs commit - then run "communitypkg" from that dir (it's part of aurtools).

communitypkg will upload the pkg file, and tag everything as "CURRENT" - the next time the little AUR cron job comes around (I think it's 10 minutes for the web db and 30 minutes for gensync), it will notice that a package from unsupported is now in community, and it will orphan the package...

so just wait about 10 minutes and it will be orphaned on the front end...

it then takes some time for gensync to catch up, though

xerxes2 · 2005-07-25 22:53:41

that was what i tried phrakture,
here are the steps i take to add a package to community:

1. add the dir:
mkdir <package>
cvs add <package>

2. save the pkgbuild in that dir and run makepkg

3. run 'communitypkg'

these steps worked with ion so i don't think i forget something,
or should there be some cvs commit also?

phrakture · 2005-07-25 22:56:34

hmmm... did you check-in the PKGBUILD as well?

do a "echo $?" after communitypkg, I think it fails silently if anything fails... not sure though...

it could be the cron job on the server that's borked... not sure. I will try and update some things when I get home and see if anything changes.

xerxes2 · 2005-07-25 23:00:24

should i run 'cvs add PKGBUILD' also maybe???

phrakture · 2005-07-25 23:02:28

Yeah, do that... communitypkg only adds the pkg.tar.gz file, the others are up to you

xerxes2 · 2005-07-25 23:04:40

here is the output from communitypkg:

[xerxes2@UFU psyco]€ communitypkg
{'size0': ['0'], 'numpkgs': ['1'], 'name0': ['psyco-1.4-1.pkg.tar.gz']}
{'md5sum0': ['PASS'], 'numpkgs': ['1']}
===> Uploaded psyco-1.4-1.pkg.tar.gz
cvs commit: Examining .
===> Commited with "upgpkg: psyco 1.4-1" message
cvs tag: Tagging .
===> Tagged as CURRENT

it looks ok to me,

xerxes2 · 2005-07-25 23:29:40

it worked now,
maybe it was a server problem before:

Arch Linux

#1 2005-07-25 18:35:04

adopting package as tu

#2 2005-07-25 19:09:40

Re: adopting package as tu

#3 2005-07-25 20:03:20

Re: adopting package as tu

#4 2005-07-25 22:53:41

Re: adopting package as tu

#5 2005-07-25 22:56:34

Re: adopting package as tu

#6 2005-07-25 23:00:24

Re: adopting package as tu

#7 2005-07-25 23:02:28

Re: adopting package as tu

#8 2005-07-25 23:04:40

Re: adopting package as tu

#9 2005-07-25 23:29:40

Re: adopting package as tu

Board footer