1
=== modified file 'lib/lp/soyuz/help/derived-series-syncing.html'
2
--- lib/lp/soyuz/help/derived-series-syncing.html	2010-09-07 07:30:42 +0000
3
+++ lib/lp/soyuz/help/derived-series-syncing.html	2011-05-23 15:59:30 +0000
4
@@ -12,35 +12,76 @@
5
12
    <h1>Syncing software from a parent series</h1>
12
    <h1>Syncing software from a parent series</h1>
6
13
13
7
14
    <p>
14
    <p>
9
15
      A nice introduction text written by the great
15
      Syncing software from a parent series will take the package that's
10
16
      currently published in it, and upload it to the derived series without
11
17
      you having to use command line tools such as <em>dput</em> or 
12
18
      <em>ftp</em>.
13
16
    </p>
19
    </p>
14
17
20
15
18
    <p>
21
    <p>
16
19
      <strong>Important:</strong> Syncing a package from the parent
22
      <strong>Important:</strong> Syncing a package from the parent
18
20
      series will overwrite ....
23
      series will supersede any changes made in the derived version. If there
19
24
      are local changes you don't wish to lose, you will need to manually
20
25
      merge the changes into the upstream package and upload that to the
21
26
      derived series.
22
21
    </p>
27
    </p>
23
22
28
24
23
    <h2>Checking the differences</h2>
29
    <h2>Checking the differences</h2>
25
24
30
26
25
    <p>
31
    <p>
46
26
    Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do
32
    Each row in the table shows a package that has different versions in
47
27
    eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim
33
    the derived series and the parent(s).  Clicking the package name
48
28
    ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut
34
    will expand the row to show more details about the package and allow 
49
29
    aliquip ex ea commodo consequat. Duis aute irure dolor in
35
    you to take some actions:
50
30
    reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla
36
      <ul>
51
31
    pariatur. Excepteur sint occaecat cupidatat non proident, sunt in
37
        <li>Add a comment about this package.</li>
52
32
    culpa qui officia deserunt mollit anim id est laborum.
38
        <li>Request debdiffs</li>
53
33
    </p>
39
        <li>Ignoring this difference, or all differences for this package</li>
54
34
40
      </ul>
55
35
    <p>
41
    </p>
56
36
    <strong>Step 1:</strong>
42
57
37
    Sed ut perspiciatis unde omnis iste natus error sit voluptatem
43
    <h3>Adding comments</h3>
58
38
    accusantium doloremque laudantium, totam rem aperiam, eaque ipsa
44
    <p>
59
39
    quae ab illo inventore veritatis et quasi architecto beatae vitae
45
    Click the green "Add comment" button and enter the comment inline.
60
40
    dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit
46
    All previous comments are shown here also.
61
41
    aspernatur aut odit aut fugit, sed quia consequuntur magni dolores
47
    </p>
62
42
    eos qui ratione voluptatem sequi nesciunt.
48
63
43
    </p>
49
    <h3>Requesting debdiffs</h3>
64
44
50
    <p>
65
51
    Click the "Compute differences from last common version".  A request is
66
52
    sent to the server to initiate the debdiff calculation.  While you wait
67
53
    for the calculation the icon will flash. The page will update
68
54
    automatically when the debdiff becomes available, giving you a link to
69
55
    download the debdiff file.
70
56
    </p>
71
57
72
58
    <h3>Ignoring differences</h3>
73
59
    <p>
74
60
    If you don't care about this package you have the option of setting it to
75
61
    <em>ignored</em>, which means that it will no longer appear in the list.   
76
62
    You can choose to ignore just "These versions", which means if a new 
77
63
    version is uploaded it will re-appear, or "All Versions" which means 
78
64
    you won't see it again unless you search explicitly for ignored 
79
65
    packages in the search criteria at the top of the page.
80
66
    </p>
81
67
82
68
    <h2>Requesting a sync</h2>
83
69
    <p>
84
70
    There are two methods of syncing:
85
71
      <ul>
86
72
        <li><strong>A mass-sync:</strong>  This grabs all packages in all 
87
73
            parents that have a higher version and uploads them to the 
88
74
            derived series by clicking the mass-sync button at the bottom 
89
75
            of the page.  To do this you need to have archive administrator 
90
76
            permissions.</li>
91
77
        <li><strong>A selective sync:</strong>  You can check the box next 
92
78
            to each package and then click the sync button at the bottom of
93
79
            the page. To do this you need to have permissions to upload 
94
80
            each package.</li>
95
81
      </ul>
96
82
    After you request a sync the operation will complete in the background
97
83
    and the package(s) will flow into the distribution just like a normal 
98
84
    upload, including being held in the upload queue as appropriate.
99
85
    </p>
100
45
  </body>
86
  </body>
101
46
</html>
87
</html>
Reviewer	Review Type	Date Requested	Status
Julian Edwards (community)	code		Approve on 2011-05-23
Matthew Revell (community)	text	2011-05-23	Approve on 2011-05-23
Review via email: mp+61960@code.launchpad.net