Bernhard R. Link wrote: > When is "all operations on a dist are completed"? > Before the Release file is generated, so it can add files to it? > After the Release file is generated, so it can look at this? > After the release file is generated, and more importantly, after all the .new files have been moved/renamed. > Some words on what you want to actually do would also help me to design > this more realistically. > > Hochachtungsvoll, > Bernhard R. Link >
My initial goal is to push updated dists via rsync to a server which resides outside the network DMZ. For example: Suite: dev Codename: dev Architectures: i386 source Components: main non-free extra DebIndices: Packages Release . .gz tiffany.py rsync2external.sh For the dist "dev" we have three components, "main," "non-free," and "extra." Using the "DebIndices" export hooks, the script "rsync2external.sh" is called three separate times. Additionally, the Release and Packages files are still in the temp filename format, with the .new suffix appended and the old files still in place. Ideally, the new post-processing hooks would be called only when all the changed components have successfully been processed, the .new files have been moved/renamed, and the dist is fully created. If this helps any, a use case to see what I am referring to when I say "the Release and Packages files are still in the temp filename format" is to create a "DebIndicies" export hook which just executes 'ls -laR $1'. This should return something similar to the following for each component: repo/dists/dev/main/binary-i386: total 733 drwxr-xr-x 2 ryan ryan 112 2008-08-18 15:40 . drwxr-xr-x 3 ryan ryan 80 2008-08-18 15:40 .. -rw-r--r-- 1 ryan ryan 157744 2008-08-18 15:40 Packages.gz.new -rw-r--r-- 1 ryan ryan 586811 2008-08-18 15:40 Packages.new Please note, the previous example was tested using v3.6.2 from cvs. Thanks again! -Ryan H. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
