[arch-dev-public] testing ->core/extra movement instructions? - Arch-dev-public - lists.archlinux.org

newer
[arch-dev-public] neon 0.28.2 to...

[arch-dev-public] testing ->core/extra movement instructions?

older
[arch-dev-public] inkscape...

Jan de Groot

15 Apr 2008 15 Apr '08

5:10 p.m.

Can someone give clear instructions on how to move things from testing to core and/or extra? I've done some packages a while ago, which were graphviz and glib2. Looking again, I see glib2 isn't moved at all and graphviz has been fixed up by some other dev last week. What's going on here?

Show replies by date

Aaron Griffin

15 Apr 15 Apr

5:42 p.m.

On Tue, Apr 15, 2008 at 12:10 PM, Jan de Groot wrote:

Can someone give clear instructions on how to move things from testing to core and/or extra? I've done some packages a while ago, which were graphviz and glib2. Looking again, I see glib2 isn't moved at all and graphviz has been fixed up by some other dev last week. What's going on here?

It should be exactly the same as it always ways, except instead of CVS tags, we're using "archrelease" and "svn rm" (or archrm, which does very little) In essence: cd graphviz/trunk archrelease extra-i686 (or run extrapkg to do this and the scp upload) cd ../repos/ svn rm testing-i686 Then you need to do the db-script side exactly as we always have done it: both db-testing and db-extra need to be run, with a package in $STAGING/add and one in $STAGING/del Pierre's testing2extra script should do all this - but I have not used it myself. Jan, did you attempt to do it manually, or use the script?

Eric Belanger

21 Apr 21 Apr

2:39 a.m.

On Tue, 15 Apr 2008, Aaron Griffin wrote:

On Tue, Apr 15, 2008 at 12:10 PM, Jan de Groot wrote:

...
Can someone give clear instructions on how to move things from testing to core and/or extra? I've done some packages a while ago, which were graphviz and glib2. Looking again, I see glib2 isn't moved at all and graphviz has been fixed up by some other dev last week. What's going on here?

It should be exactly the same as it always ways, except instead of CVS tags, we're using "archrelease" and "svn rm" (or archrm, which does very little)

In essence: cd graphviz/trunk archrelease extra-i686 (or run extrapkg to do this and the scp upload) cd ../repos/ svn rm testing-i686

Then you need to do the db-script side exactly as we always have done it: both db-testing and db-extra need to be run, with a package in $STAGING/add and one in $STAGING/del

Pierre's testing2extra script should do all this - but I have not used it myself.

Jan, did you attempt to do it manually, or use the script?

It doesn't seem to work: PWD: ~/svnroot/bmpx/trunk 48 eric@Erix $ archrelease extra-i686 UG ../repos/extra-i686/PKGBUILD property 'svnmerge-integrated' set on '../repos/extra-i686' ~/svnroot/bmpx ~/svnroot/bmpx/trunk Sending repos/extra-i686 Committed revision 547. ~/svnroot/bmpx/trunk -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

Aaron Griffin

4:25 p.m.

On Sun, Apr 20, 2008 at 9:39 PM, Eric Belanger wrote:

On Tue, 15 Apr 2008, Aaron Griffin wrote:

...
On Tue, Apr 15, 2008 at 12:10 PM, Jan de Groot wrote:

...
Can someone give clear instructions on how to move things from testing to core and/or extra? I've done some packages a while ago, which were graphviz and glib2. Looking again, I see glib2 isn't moved at all and graphviz has been fixed up by some other dev last week. What's going on here?

It should be exactly the same as it always ways, except instead of CVS tags, we're using "archrelease" and "svn rm" (or archrm, which does very little)

In essence: cd graphviz/trunk archrelease extra-i686 (or run extrapkg to do this and the scp upload) cd ../repos/ svn rm testing-i686

Then you need to do the db-script side exactly as we always have done it: both db-testing and db-extra need to be run, with a package in $STAGING/add and one in $STAGING/del

Pierre's testing2extra script should do all this - but I have not used it myself.

Jan, did you attempt to do it manually, or use the script?

It doesn't seem to work:

PWD: ~/svnroot/bmpx/trunk 48 eric@Erix $ archrelease extra-i686 UG ../repos/extra-i686/PKGBUILD

property 'svnmerge-integrated' set on '../repos/extra-i686'

~/svnroot/bmpx ~/svnroot/bmpx/trunk Sending repos/extra-i686

Committed revision 547. ~/svnroot/bmpx/trunk

I'm unclear on what you mean. Which part doesn't work? It appears to have released for extra-i686 just fine: http://dev.archlinux.org/~aaron/svn/viewvc/bin/cgi/viewvc.cgi/bmpx/repos/ Which part of this is failing?

Eric Belanger

4:35 p.m.

On Mon, 21 Apr 2008, Aaron Griffin wrote:

On Sun, Apr 20, 2008 at 9:39 PM, Eric Belanger wrote:

...
On Tue, 15 Apr 2008, Aaron Griffin wrote:

...
On Tue, Apr 15, 2008 at 12:10 PM, Jan de Groot wrote:

...
Can someone give clear instructions on how to move things from testing to core and/or extra? I've done some packages a while ago, which were graphviz and glib2. Looking again, I see glib2 isn't moved at all and graphviz has been fixed up by some other dev last week. What's going on here?

It should be exactly the same as it always ways, except instead of CVS tags, we're using "archrelease" and "svn rm" (or archrm, which does very little)

In essence: cd graphviz/trunk archrelease extra-i686 (or run extrapkg to do this and the scp upload) cd ../repos/ svn rm testing-i686

Then you need to do the db-script side exactly as we always have done it: both db-testing and db-extra need to be run, with a package in $STAGING/add and one in $STAGING/del

Pierre's testing2extra script should do all this - but I have not used it myself.

Jan, did you attempt to do it manually, or use the script?

It doesn't seem to work:

PWD: ~/svnroot/bmpx/trunk 48 eric@Erix $ archrelease extra-i686 UG ../repos/extra-i686/PKGBUILD

property 'svnmerge-integrated' set on '../repos/extra-i686'

~/svnroot/bmpx ~/svnroot/bmpx/trunk Sending repos/extra-i686

Committed revision 547. ~/svnroot/bmpx/trunk

I'm unclear on what you mean. Which part doesn't work? It appears to have released for extra-i686 just fine: http://dev.archlinux.org/~aaron/svn/viewvc/bin/cgi/viewvc.cgi/bmpx/repos/

Which part of this is failing?

The PKGBUILD in bmpx/repos/extra-i686 is still the old one with pkgrel=1 instead of being replaced by the one in the trunk at pkgrel=2 (which was previously in testing). Plus the gcc and libsoup patches that are applied to pkgrel=2 in the trunk were not copied to extra-i686. It's like if running 'archrelease extra-i686' didn't updated the files in extra-i686 at all. That's probably the reason why running the db script on gerolde doesn't update the db properly. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

Eric Belanger

23 Apr 23 Apr

4:57 a.m.

On Mon, 21 Apr 2008, Eric Belanger wrote:

On Mon, 21 Apr 2008, Aaron Griffin wrote:

...
On Sun, Apr 20, 2008 at 9:39 PM, Eric Belanger wrote:

...
On Tue, 15 Apr 2008, Aaron Griffin wrote:

...
On Tue, Apr 15, 2008 at 12:10 PM, Jan de Groot wrote:

...
Can someone give clear instructions on how to move things from testing to core and/or extra? I've done some packages a while ago, which were graphviz and glib2. Looking again, I see glib2 isn't moved at all and graphviz has been fixed up by some other dev last week. What's going on here?

It should be exactly the same as it always ways, except instead of CVS tags, we're using "archrelease" and "svn rm" (or archrm, which does very little)

In essence: cd graphviz/trunk archrelease extra-i686 (or run extrapkg to do this and the scp upload) cd ../repos/ svn rm testing-i686

Then you need to do the db-script side exactly as we always have done it: both db-testing and db-extra need to be run, with a package in $STAGING/add and one in $STAGING/del

Pierre's testing2extra script should do all this - but I have not used it myself.

Jan, did you attempt to do it manually, or use the script?

It doesn't seem to work:

PWD: ~/svnroot/bmpx/trunk 48 eric@Erix $ archrelease extra-i686 UG ../repos/extra-i686/PKGBUILD

property 'svnmerge-integrated' set on '../repos/extra-i686'

~/svnroot/bmpx ~/svnroot/bmpx/trunk Sending repos/extra-i686

Committed revision 547. ~/svnroot/bmpx/trunk

I'm unclear on what you mean. Which part doesn't work? It appears to have released for extra-i686 just fine: http://dev.archlinux.org/~aaron/svn/viewvc/bin/cgi/viewvc.cgi/bmpx/repos/

Which part of this is failing?

The PKGBUILD in bmpx/repos/extra-i686 is still the old one with pkgrel=1 instead of being replaced by the one in the trunk at pkgrel=2 (which was previously in testing). Plus the gcc and libsoup patches that are applied to pkgrel=2 in the trunk were not copied to extra-i686. It's like if running 'archrelease extra-i686' didn't updated the files in extra-i686 at all. That's probably the reason why running the db script on gerolde doesn't update the db properly.

I just moved the imagemagick rebuilds from testing to extra. Except for 2 packages, the steps you posted above works. BTW, 'svn commit' must be run after removing the 'svn rm testing-i686'. My guess is that the failures are due to the properties that were set when moving the repos to svn (details in Jason's explanation in the 'Database breakage thread').. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

5855

Age (days ago)

5863

Last active (days ago)

Download

5 comments

3 participants

tags

participants (3)

Aaron Griffin
Eric Belanger
Jan de Groot