Re: [arch-dev-public] Time to go forward with arch=any?
Aaron Griffin a écrit :
Applying these now. I don't like the removal of the quotes in the first part of the simple-syntactic patch - if WORKDIR ever contains a space, due to some change of how it's created, this will blow up... due to that I reverted those parts of the changes, I'd rather be safe if the only cost is some quote characters :)
That's fine.
/arch-new has been updated
Thanks! Just tried them with another texlive pkg, and I get this: [francois@gerolde ~]$ /arch-new/db-update testing ==> Processing 1 new/updated arch-independent packages for 'testing'... Checked out revision 46883. Validating package arch (any) texlive-latex3 Checking SVN for texlive-latex3 Updating DB for testing-i686 ==> Copying DB file from 'testing'... ==> Processing 1 new/updated packages for repository 'testing'... Checked out revision 46883. Copying new files to '/srv/ftp/testing/os/any/' and symlinking Updating DB for testing-x86_64 ==> Copying DB file from 'testing'... ==> Processing 1 new/updated packages for repository 'testing'... Checked out revision 46883. Copying new files to '/srv/ftp/testing/os/any/' and symlinking error: repo lock doesn't exist... something went terribly wrong! However things appear to have worked: [francois@gerolde ~]$ ls -l /srv/ftp/testing/os/*/texlive* -rw-r--r-- 1 francois ftp-extra 59983 2009-07-20 13:15 /srv/ftp/testing/os/any/texlive-latex3-2009.14222-1-any.pkg.tar.gz -rw-r--r-- 1 francois ftp-extra 386464 2009-07-20 06:00 /srv/ftp/testing/os/any/texlive-science-2009.13945-1-any.pkg.tar.gz lrwxrwxrwx 1 francois ftp-extra 67 2009-07-20 13:15 /srv/ftp/testing/os/i686/texlive-latex3-2009.14222-1-any.pkg.tar.gz -> /srv/ftp/testing/os/any//texlive-latex3-2009.14222-1-any.pkg.tar.gz lrwxrwxrwx 1 francois ftp-extra 67 2009-07-20 13:15 /srv/ftp/testing/os/x86_64/texlive-latex3-2009.14222-1-any.pkg.tar.gz -> /srv/ftp/testing/os/any//texlive-latex3-2009.14222-1-any.pkg.tar.gz But the symlinks for texlive-science have disappeared! For sure they were there for both arches earlier today (I had made the one for x86_64 by hand, coz db-update had failed). I thus assume that those two symlinks were removed by some running cronjob. Idea? Both packages are still present in the db, however: [francois@gerolde ~]$ tar tf /srv/ftp/testing/os/i686/testing.db.tar.gz | grep texlive texlive-latex3-2009.14222-1/ texlive-latex3-2009.14222-1/depends texlive-latex3-2009.14222-1/desc texlive-science-2009.13945-1/ texlive-science-2009.13945-1/depends texlive-science-2009.13945-1/desc [francois@gerolde ~]$ tar tf /srv/ftp/testing/os/x86_64/testing.db.tar.gz | grep texlive texlive-latex3-2009.14222-1/ texlive-latex3-2009.14222-1/depends texlive-latex3-2009.14222-1/desc texlive-science-2009.13945-1/ texlive-science-2009.13945-1/depends texlive-science-2009.13945-1/desc So, something fishy is going on with the symlinks and the repo_unlock for x86_64... I have to leave now. But I might have a closer look later tonight. Cheers F
[quoting myself]
But the symlinks for texlive-science have disappeared!
Update: I have just readded both by hand. Let's see if they disappear again!
On Mon, Jul 20, 2009 at 12:27 PM, Firmicus<Firmicus@gmx.net> wrote:
Aaron Griffin a écrit :
Applying these now. I don't like the removal of the quotes in the first part of the simple-syntactic patch - if WORKDIR ever contains a space, due to some change of how it's created, this will blow up... due to that I reverted those parts of the changes, I'd rather be safe if the only cost is some quote characters :)
That's fine.
/arch-new has been updated
Thanks!
Just tried them with another texlive pkg, and I get this:
[francois@gerolde ~]$ /arch-new/db-update testing ==> Processing 1 new/updated arch-independent packages for 'testing'... Checked out revision 46883. Validating package arch (any) texlive-latex3 Checking SVN for texlive-latex3 Updating DB for testing-i686 ==> Copying DB file from 'testing'... ==> Processing 1 new/updated packages for repository 'testing'... Checked out revision 46883. Copying new files to '/srv/ftp/testing/os/any/' and symlinking Updating DB for testing-x86_64 ==> Copying DB file from 'testing'... ==> Processing 1 new/updated packages for repository 'testing'... Checked out revision 46883. Copying new files to '/srv/ftp/testing/os/any/' and symlinking error: repo lock doesn't exist... something went terribly wrong!
However things appear to have worked:
[francois@gerolde ~]$ ls -l /srv/ftp/testing/os/*/texlive* -rw-r--r-- 1 francois ftp-extra 59983 2009-07-20 13:15 /srv/ftp/testing/os/any/texlive-latex3-2009.14222-1-any.pkg.tar.gz -rw-r--r-- 1 francois ftp-extra 386464 2009-07-20 06:00 /srv/ftp/testing/os/any/texlive-science-2009.13945-1-any.pkg.tar.gz lrwxrwxrwx 1 francois ftp-extra 67 2009-07-20 13:15 /srv/ftp/testing/os/i686/texlive-latex3-2009.14222-1-any.pkg.tar.gz -> /srv/ftp/testing/os/any//texlive-latex3-2009.14222-1-any.pkg.tar.gz lrwxrwxrwx 1 francois ftp-extra 67 2009-07-20 13:15 /srv/ftp/testing/os/x86_64/texlive-latex3-2009.14222-1-any.pkg.tar.gz -> /srv/ftp/testing/os/any//texlive-latex3-2009.14222-1-any.pkg.tar.gz
But the symlinks for texlive-science have disappeared! For sure they were there for both arches earlier today (I had made the one for x86_64 by hand, coz db-update had failed). I thus assume that those two symlinks were removed by some running cronjob. Idea?
Both packages are still present in the db, however:
[francois@gerolde ~]$ tar tf /srv/ftp/testing/os/i686/testing.db.tar.gz | grep texlive texlive-latex3-2009.14222-1/ texlive-latex3-2009.14222-1/depends texlive-latex3-2009.14222-1/desc texlive-science-2009.13945-1/ texlive-science-2009.13945-1/depends texlive-science-2009.13945-1/desc
[francois@gerolde ~]$ tar tf /srv/ftp/testing/os/x86_64/testing.db.tar.gz | grep texlive texlive-latex3-2009.14222-1/ texlive-latex3-2009.14222-1/depends texlive-latex3-2009.14222-1/desc texlive-science-2009.13945-1/ texlive-science-2009.13945-1/depends texlive-science-2009.13945-1/desc
So, something fishy is going on with the symlinks and the repo_unlock for x86_64...
I have to leave now. But I might have a closer look later tonight.
From the cleanup email sent to arch-commits:
Scan complete for testing (i686) at /srv/ftp/testing/os/i686/ The following files are in the repo but not the db They will be moved to /srv/package-cleanup ... texlive-science-2009.13945-1-any.pkg.tar.gz .... Interesting... not sure how that could happen...
Aaron Griffin schrieb:
Scan complete for testing (i686) at /srv/ftp/testing/os/i686/ The following files are in the repo but not the db They will be moved to /srv/package-cleanup ... texlive-science-2009.13945-1-any.pkg.tar.gz ....
Interesting... not sure how that could happen...
The cleanup script is kinda dumb, it assumes $arch in {i686, x86_64}. At least it did when I wrote the original.
On Mon, Jul 20, 2009 at 3:10 PM, Thomas Bächler<thomas@archlinux.org> wrote:
Aaron Griffin schrieb:
Scan complete for testing (i686) at /srv/ftp/testing/os/i686/ The following files are in the repo but not the db They will be moved to /srv/package-cleanup ... texlive-science-2009.13945-1-any.pkg.tar.gz ....
Interesting... not sure how that could happen...
The cleanup script is kinda dumb, it assumes $arch in {i686, x86_64}. At least it did when I wrote the original.
I made some small corrections... Francois, could you do the following: * re-add the symlinks * run /arch-new/misc-scripts/ftpdir-cleanup testing i686 /srv/package-cleanup I'm not entirely sure if this fixes it, and don't have a lot of time to test... The issue is probably that the ftpdir-cleanup script that's running isn't the new one with 'any' support :S
Aaron Griffin a écrit :
On Mon, Jul 20, 2009 at 3:10 PM, Thomas Bächler<thomas@archlinux.org> wrote:
Aaron Griffin schrieb:
Scan complete for testing (i686) at /srv/ftp/testing/os/i686/ The following files are in the repo but not the db They will be moved to /srv/package-cleanup ... texlive-science-2009.13945-1-any.pkg.tar.gz ....
Interesting... not sure how that could happen...
The cleanup script is kinda dumb, it assumes $arch in {i686, x86_64}. At least it did when I wrote the original.
I made some small corrections... Francois, could you do the following:
* re-add the symlinks * run /arch-new/misc-scripts/ftpdir-cleanup testing i686 /srv/package-cleanup
I'm not entirely sure if this fixes it, and don't have a lot of time to test... The issue is probably that the ftpdir-cleanup script that's running isn't the new one with 'any' support :S
Yeah, this is it. The new ftpdir-cleanup script should be ok, at least from what I can read... I don't have time now, but tomorrow morning I shall be able to the tests. Good night, F
On Mon, Jul 20, 2009 at 4:28 PM, Firmicus<Firmicus@gmx.net> wrote:
Aaron Griffin a écrit :
On Mon, Jul 20, 2009 at 3:10 PM, Thomas Bächler<thomas@archlinux.org> wrote:
Aaron Griffin schrieb:
Scan complete for testing (i686) at /srv/ftp/testing/os/i686/ The following files are in the repo but not the db They will be moved to /srv/package-cleanup ... texlive-science-2009.13945-1-any.pkg.tar.gz ....
Interesting... not sure how that could happen...
The cleanup script is kinda dumb, it assumes $arch in {i686, x86_64}. At least it did when I wrote the original.
I made some small corrections... Francois, could you do the following:
* re-add the symlinks * run /arch-new/misc-scripts/ftpdir-cleanup testing i686 /srv/package-cleanup
I'm not entirely sure if this fixes it, and don't have a lot of time to test... The issue is probably that the ftpdir-cleanup script that's running isn't the new one with 'any' support :S
Yeah, this is it. The new ftpdir-cleanup script should be ok, at least from what I can read... I don't have time now, but tomorrow morning I shall be able to the tests.
Holy crap, don't run the new script - it's bad news. It moved all core-i686 packages to package-cleanup (I moved them back)... :S
Holy crap, don't run the new script - it's bad news. It moved all core-i686 packages to package-cleanup (I moved them back)...
:S
Were you joking? If you ran e.g. $ /arch-new/misc-scripts/ftpdir-cleanup testing i686 /srv/package-cleanup how could it have affected the core pkgs???
Firmicus schrieb:
Yeah, this is it. The new ftpdir-cleanup script should be ok, at least from what I can read... I don't have time now, but tomorrow morning I shall be able to the tests.
Good night, F
All should be working now, Aaron fixed it. We now have 3 -any packages sitting in the repository, yay!
On Mon, Jul 20, 2009 at 4:25 PM, Thomas Bächler<thomas@archlinux.org> wrote:
Firmicus schrieb:
Yeah, this is it. The new ftpdir-cleanup script should be ok, at least from what I can read... I don't have time now, but tomorrow morning I shall be able to the tests.
Good night, F
All should be working now, Aaron fixed it. We now have 3 -any packages sitting in the repository, yay!
And the cron job will delete the symlinks when it runs :S Can you give a once-over on the /arch-new cron job? If that is all good, I can point cron to that one until we move this
Aaron Griffin schrieb:
All should be working now, Aaron fixed it. We now have 3 -any packages sitting in the repository, yay!
And the cron job will delete the symlinks when it runs :S
Yes, they're gone. Is the arch-new cronjob safe to use now?
Aaron Griffin a écrit :
On Mon, Jul 20, 2009 at 4:25 PM, Thomas Bächler<thomas@archlinux.org> wrote:
Firmicus schrieb:
Yeah, this is it. The new ftpdir-cleanup script should be ok, at least from what I can read... I don't have time now, but tomorrow morning I shall be able to the tests.
Good night, F
All should be working now, Aaron fixed it. We now have 3 -any packages sitting in the repository, yay!
And the cron job will delete the symlinks when it runs :S
Can you give a once-over on the /arch-new cron job? If that is all good, I can point cron to that one until we move this
Wait ... there are still a few things to improve in ftpdir-cleanup. For instance if one of the out-of-date packages in $DELETEFILES is a symlink to an "any" file, that symlink will be removed, but not the original file. Also, I would prefer to have that script take care of all arches at once, like the new db-update script does. That's the easiest way to handle the above situation: if an "any" package is outdated for both arches, then remove both symlinks AND the actual file. But if it is only outdated for one arch, then remove that symlink but keep the original file. I have rewritten the ftp-cleanup script this morning. I'm going to revise it now and should submit my patches very soon. F
Wait ... there are still a few things to improve in ftpdir-cleanup.
For instance if one of the out-of-date packages in $DELETEFILES is a symlink to an "any" file, that symlink will be removed, but not the original file.
Also, I would prefer to have that script take care of all arches at once, like the new db-update script does. That's the easiest way to handle the above situation: if an "any" package is outdated for both arches, then remove both symlinks AND the actual file. But if it is only outdated for one arch, then remove that symlink but keep the original file.
I have rewritten the ftp-cleanup script this morning. I'm going to revise it now and should submit my patches very soon.
Here they are. Looks like it is a lot of changes, but as I noted in the commit message, it really amounts to reshuffling the code in order to have a for loop for each ARCH, followed by a scan of the "any" directory. Hope you like it ;) F
On Tue, Jul 21, 2009 at 02:25, Thomas Bächler<thomas@archlinux.org> wrote:
Firmicus schrieb:
Yeah, this is it. The new ftpdir-cleanup script should be ok, at least from what I can read... I don't have time now, but tomorrow morning I shall be able to the tests.
Good night, F
All should be working now, Aaron fixed it. We now have 3 -any packages sitting in the repository, yay!
I'm on my work at the moment, so cannot check this: http://bugs.archlinux.org/task/15617 Can anyone confirm this? Or is this mirror issue? -- Roman Kyrylych (Роман Кирилич)
On Tue, Jul 21, 2009 at 13:00, Roman Kyrylych<roman.kyrylych@gmail.com> wrote:
On Tue, Jul 21, 2009 at 02:25, Thomas Bächler<thomas@archlinux.org> wrote:
Firmicus schrieb:
Yeah, this is it. The new ftpdir-cleanup script should be ok, at least from what I can read... I don't have time now, but tomorrow morning I shall be able to the tests.
Good night, F
All should be working now, Aaron fixed it. We now have 3 -any packages sitting in the repository, yay!
I'm on my work at the moment, so cannot check this: http://bugs.archlinux.org/task/15617 Can anyone confirm this? Or is this mirror issue?
Also, take a look at http://www.archlinux.org/packages/testing/any/mkinitcpio/ Our web scripts need to be updated to be able to find dependencies for -any packages. -- Roman Kyrylych (Роман Кирилич)
participants (4)
-
Aaron Griffin
-
Firmicus
-
Roman Kyrylych
-
Thomas Bächler