Changes

Jump to navigation Jump to search
262 bytes removed ,  09:06, 4 December 2012
m
Line 222: Line 222:     
If you carefully check the code changes it may be possible to release e-smith-pop3 & e-smith-apache in the example above, but safest not to.
 
If you carefully check the code changes it may be possible to release e-smith-pop3 & e-smith-apache in the example above, but safest not to.
 +
 +
Note: Shad's automated script doesn't do any blocking of packages.  It just tries to sort out where packages should belong based on where things exist when it starts running.
    
{| style="color:red;background-color:#ffffcc;"
 
{| style="color:red;background-color:#ffffcc;"
|To be clarified:
+
|
- If deps are not resolved, will Shad's script block cp for unresolved packages dependencies?
  −
*Answer from Ian: not sure for updates. But normally it is not hard dependencies being an issue.
  −
 
   
Last, we need to explain how dependencies setup between bugs in Bugzilla operate, and how they relates to hard/soft package dependencies if applicable.
 
Last, we need to explain how dependencies setup between bugs in Bugzilla operate, and how they relates to hard/soft package dependencies if applicable.
  −
*Answer from JP Pialasse: as far as I know the script will execute the update without the dependency if they are not resolvable or not, you will have to download yourself and cp in the destination repo to have them if it happens
      
|}
 
|}

Navigation menu