[arch-dev-public] Moving DB scripts live - Arch-dev-public - lists.archlinux.org

newer
[arch-dev-public] Backpacking this...

[arch-dev-public] Moving DB scripts live

older
[arch-dev-public] permission to...

Aaron Griffin

30 Jul 2009 30 Jul '09

4:45 p.m.

So, we have "any" support and split package support sitting in the DB scripts in /arch-new I'd like to move this live soon. What do you all think? Can you test normal packaging with these to confirm there's no major regressions?

Show replies by date

Allan McRae

30 Jul 30 Jul

5:04 p.m.

Aaron Griffin wrote:

So, we have "any" support and split package support sitting in the DB scripts in /arch-new

I'd like to move this live soon. What do you all think? Can you test normal packaging with these to confirm there's no major regressions?

I just used these to upload abs to [testing] then move it to [extra] and everything went fine. One think that may be an issue, /arch-new/db-testing uploaded both i686 and x86_64 (which I guess is needed to handle the "any" arch), but /arch-new/testing2x had to be ran for i686 and x86_64. Does that handle "any" packages? It is 3am here so I have not checked myself... Allan

Aaron Griffin

5:16 p.m.

On Thu, Jul 30, 2009 at 12:04 PM, Allan McRae wrote:

Aaron Griffin wrote:

...
So, we have "any" support and split package support sitting in the DB scripts in /arch-new

I'd like to move this live soon. What do you all think? Can you test normal packaging with these to confirm there's no major regressions?

I just used these to upload abs to [testing] then move it to [extra] and everything went fine. One think that may be an issue, /arch-new/db-testing uploaded both i686 and x86_64 (which I guess is needed to handle the "any" arch), but /arch-new/testing2x had to be ran for i686 and x86_64. Does that handle "any" packages? It is 3am here so I have not checked myself...

Was just talking to Thomas about this - I don't think testing2x was changed to work this way. And yes, for the record, now all architectures are processed at once. No need to run two different script for different arches.

Eric Bélanger

3 Aug 3 Aug

11:03 p.m.

On Thu, Jul 30, 2009 at 1:16 PM, Aaron Griffin wrote:

On Thu, Jul 30, 2009 at 12:04 PM, Allan McRae wrote:

...
Aaron Griffin wrote:

...
So, we have "any" support and split package support sitting in the DB scripts in /arch-new

I'd like to move this live soon. What do you all think? Can you test normal packaging with these to confirm there's no major regressions?

I just used these to upload abs to [testing] then move it to [extra] and everything went fine. One think that may be an issue, /arch-new/db-testing uploaded both i686 and x86_64 (which I guess is needed to handle the "any" arch), but /arch-new/testing2x had to be ran for i686 and x86_64. Does that handle "any" packages? It is 3am here so I have not checked myself...

Was just talking to Thomas about this - I don't think testing2x was changed to work this way.

I guess that it's not fixed yet. There seem to be 'any' support in db-move however. Is that completed? Can I use it to move an 'any' package from testing to extra?

Aaron Griffin

11:05 p.m.

On Mon, Aug 3, 2009 at 6:03 PM, Eric Bélanger wrote:

On Thu, Jul 30, 2009 at 1:16 PM, Aaron Griffin wrote:

...
On Thu, Jul 30, 2009 at 12:04 PM, Allan McRae wrote:

...
Aaron Griffin wrote:

...
So, we have "any" support and split package support sitting in the DB scripts in /arch-new

I'd like to move this live soon. What do you all think? Can you test normal packaging with these to confirm there's no major regressions?

I just used these to upload abs to [testing] then move it to [extra] and everything went fine. One think that may be an issue, /arch-new/db-testing uploaded both i686 and x86_64 (which I guess is needed to handle the "any" arch), but /arch-new/testing2x had to be ran for i686 and x86_64. Does that handle "any" packages? It is 3am here so I have not checked myself...

Was just talking to Thomas about this - I don't think testing2x was changed to work this way.

I guess that it's not fixed yet. There seem to be 'any' support in db-move however. Is that completed? Can I use it to move an 'any' package from testing to extra?

Yep, it should work fine.

Eric Bélanger

11:38 p.m.

On Mon, Aug 3, 2009 at 7:05 PM, Aaron Griffin wrote:

On Mon, Aug 3, 2009 at 6:03 PM, Eric Bélanger wrote:

...
On Thu, Jul 30, 2009 at 1:16 PM, Aaron Griffin wrote:

...
On Thu, Jul 30, 2009 at 12:04 PM, Allan McRae wrote:

...
Aaron Griffin wrote:

...
So, we have "any" support and split package support sitting in the DB scripts in /arch-new

I'd like to move this live soon. What do you all think? Can you test normal packaging with these to confirm there's no major regressions?

I just used these to upload abs to [testing] then move it to [extra] and everything went fine. One think that may be an issue, /arch-new/db-testing uploaded both i686 and x86_64 (which I guess is needed to handle the "any" arch), but /arch-new/testing2x had to be ran for i686 and x86_64. Does that handle "any" packages? It is 3am here so I have not checked myself...

Was just talking to Thomas about this - I don't think testing2x was changed to work this way.

I guess that it's not fixed yet. There seem to be 'any' support in db-move however. Is that completed? Can I use it to move an 'any' package from testing to extra?

Yep, it should work fine.

It seem to have worked fine. BTW, why don't we create testing2coreany and testing2extraany scripts? It would be be more convenient than using db-move directely. Probably we would want to combine all these scripts into a single one that would take care of all arches. Maybe this would work (untested): ================ #!/bin/bash if [ $# -le 0 ]; then echo "usage: $(basename 0) <packagename> [<packagename> [ Moving package '$pkg'" $(dirname $0)/db-move "$pkg" "testing" "core" "i686" $(dirname $0)/db-move "$pkg" "testing" "core" "x86_64" $(dirname $0)/db-move "$pkg" "testing" "core" "any" done ==================== And similar for testing2extra.

Aaron Griffin

4 Aug 4 Aug

2:30 a.m.

On Mon, Aug 3, 2009 at 4:38 PM, Eric Bélanger wrote:

On Mon, Aug 3, 2009 at 7:05 PM, Aaron Griffin wrote:

...
On Mon, Aug 3, 2009 at 6:03 PM, Eric Bélanger wrote:

...
On Thu, Jul 30, 2009 at 1:16 PM, Aaron Griffin wrote:

...
On Thu, Jul 30, 2009 at 12:04 PM, Allan McRae wrote:

...
Aaron Griffin wrote:

...
So, we have "any" support and split package support sitting in the DB scripts in /arch-new

I'd like to move this live soon. What do you all think? Can you test normal packaging with these to confirm there's no major regressions?

I just used these to upload abs to [testing] then move it to [extra] and everything went fine. One think that may be an issue, /arch-new/db-testing uploaded both i686 and x86_64 (which I guess is needed to handle the "any" arch), but /arch-new/testing2x had to be ran for i686 and x86_64. Does that handle "any" packages? It is 3am here so I have not checked myself...

Was just talking to Thomas about this - I don't think testing2x was changed to work this way.

I guess that it's not fixed yet. There seem to be 'any' support in db-move however. Is that completed? Can I use it to move an 'any' package from testing to extra?

Yep, it should work fine.

It seem to have worked fine. BTW, why don't we create testing2coreany and testing2extraany scripts? It would be be more convenient than using db-move directely.

Probably we would want to combine all these scripts into a single one that would take care of all arches. Maybe this would work (untested):

================ #!/bin/bash

if [ $# -le 0 ]; then echo "usage: $(basename 0) <packagename> [<packagename> [
for pkg in $@; do echo "==> Moving package '$pkg'" $(dirname $0)/db-move "$pkg" "testing" "core" "i686" $(dirname $0)/db-move "$pkg" "testing" "core" "x86_64" $(dirname $0)/db-move "$pkg" "testing" "core" "any" done ====================

And similar for testing2extra.

I'll look into it if no one else wants to - if you want, you may be able to make a dummy repo in there (thought the dir will require an admin) to play with so you can test this on gerolde. If not, you can always check out via git and change svn locations and whatnot

Eric Bélanger

4 Sep 4 Sep

12:37 a.m.

On Mon, Aug 3, 2009 at 10:30 PM, Aaron Griffin wrote:

On Mon, Aug 3, 2009 at 4:38 PM, Eric Bélanger wrote:

...
On Mon, Aug 3, 2009 at 7:05 PM, Aaron Griffin wrote:

...
On Mon, Aug 3, 2009 at 6:03 PM, Eric Bélanger wrote:

...
On Thu, Jul 30, 2009 at 1:16 PM, Aaron Griffin wrote:

...
On Thu, Jul 30, 2009 at 12:04 PM, Allan McRae wrote:

...
Aaron Griffin wrote: > > So, we have "any" support and split package support sitting in the DB > scripts in /arch-new > > I'd like to move this live soon. What do you all think? Can you test > normal packaging with these to confirm there's no major regressions? >

I just used these to upload abs to [testing] then move it to [extra] and everything went fine. One think that may be an issue, /arch-new/db-testing uploaded both i686 and x86_64 (which I guess is needed to handle the "any" arch), but /arch-new/testing2x had to be ran for i686 and x86_64. Does that handle "any" packages? It is 3am here so I have not checked myself...

Was just talking to Thomas about this - I don't think testing2x was changed to work this way.

I guess that it's not fixed yet. There seem to be 'any' support in db-move however. Is that completed? Can I use it to move an 'any' package from testing to extra?

Yep, it should work fine.

It seem to have worked fine. BTW, why don't we create testing2coreany and testing2extraany scripts? It would be be more convenient than using db-move directely.

Probably we would want to combine all these scripts into a single one that would take care of all arches. Maybe this would work (untested):

================ #!/bin/bash

if [ $# -le 0 ]; then echo "usage: $(basename 0) <packagename> [<packagename> [
for pkg in $@; do echo "==> Moving package '$pkg'" $(dirname $0)/db-move "$pkg" "testing" "core" "i686" $(dirname $0)/db-move "$pkg" "testing" "core" "x86_64" $(dirname $0)/db-move "$pkg" "testing" "core" "any" done ====================

And similar for testing2extra.

I'll look into it if no one else wants to - if you want, you may be able to make a dummy repo in there (thought the dir will require an admin) to play with so you can test this on gerolde. If not, you can always check out via git and change svn locations and whatnot

I haven't had time to look into this further. Anyone is free to look into it. I'm just bumping the thread so we don't forget it for the next dbscript release.

Thomas Bächler

7:27 a.m.

Eric Bélanger schrieb:

...
Yep, it should work fine.

It seem to have worked fine. BTW, why don't we create testing2coreany and testing2extraany scripts? It would be be more convenient than using db-move directely.

Hm, why not simply with testing2x? If the package is not in core/extra yet, using db-move for the first time should be fine. After that, you can use testing2x and it will detemine the target repository automatically. It should probably get a --i686-only and --x86_64-only switch, although I don't know who would use it.

Eric Bélanger

8:10 a.m.

On Fri, Sep 4, 2009 at 3:27 AM, Thomas Bächler wrote:

Eric Bélanger schrieb:

...
...
Yep, it should work fine.

It seem to have worked fine. BTW, why don't we create testing2coreany and testing2extraany scripts? It would be be more convenient than using db-move directely.

Hm, why not simply with testing2x? If the package is not in core/extra yet, using db-move for the first time should be fine. After that, you can use testing2x and it will detemine the target repository automatically.

It should probably get a --i686-only and --x86_64-only switch, although I don't know who would use it.

testing2x will not work. you need to explicitely tell db-move that it's an any arch package, e.g: /arch/db-move festival-rablpc16k testing extra any testing2x only runs: $(dirname $0)/db-move "${pkg}" "testing" "${repo}" "${_arch}" where _arch is either i686 or x86_64. Until any support is add to it, testing2x will fail.

Thomas Bächler

8:24 a.m.

Eric Bélanger schrieb:

testing2x will not work. you need to explicitely tell db-move that it's an any arch package, e.g:

/arch/db-move festival-rablpc16k testing extra any

testing2x only runs: $(dirname $0)/db-move "${pkg}" "testing" "${repo}" "${_arch}"

where _arch is either i686 or x86_64. Until any support is add to it, testing2x will fail.

testing2x checks out repos/ anyway to determine whether to move to core or extra. It'd be easy to also check whether testing-any exists or testing-{i686,x86_64} exist. It would only fail if this was ambiguous, which would be an error in the db layout anyway.

Eric Bélanger

8:22 a.m.

On Fri, Sep 4, 2009 at 3:27 AM, Thomas Bächler wrote:

Eric Bélanger schrieb: It should probably get a --i686-only and --x86_64-only switch, although I don't know who would use it.

There's already a switch feature. For i686, use testing2x. For x86_64, use testing2x64. Adding any arch support would be easy at first look. We just need to create a testing2xany symlink and add/change a few lines in testing2x. I don't know if it would be better or worse than what I suggested.

Pierre Schmitz

30 Jul 30 Jul

5:31 p.m.

Am Donnerstag 30 Juli 2009 18:45:12 schrieb Aaron Griffin:

So, we have "any" support and split package support sitting in the DB scripts in /arch-new

I'd like to move this live soon. What do you all think? Can you test normal packaging with these to confirm there's no major regressions?

I have tested it with several split, any and normal packages for both arches. -- Pierre Schmitz, http://users.archlinux.de/~pierre

5341

Age (days ago)

5377

Last active (days ago)

Download

12 comments

5 participants

tags

participants (5)

Aaron Griffin
Allan McRae
Eric Bélanger
Pierre Schmitz
Thomas Bächler