1
|
Date: Mon, 19 Jan 2015 19:28:18 +0100
|
2
|
From: rbarlow@redhat.com
|
3
|
To: dropbox+pulp+c71e@plan.io
|
4
|
Message-ID: <54bd4cc2614e5_72783fa5ad73deac555a@apollo.mail>
|
5
|
in-reply-to: redmine.issue-112.20150119162039@plan.io
|
6
|
Subject: Re: [Pulp - Task #112] (NEW) Add a test to ensure pulp's setup.py
|
7
|
versions are the same as the RPM versions
|
8
|
Mime-Version: 1.0
|
9
|
Content-Type: multipart/mixed;
|
10
|
boundary=DqTQSWpbg52wGwmS56OuGElxKiDtdInxH;
|
11
|
charset=UTF-8
|
12
|
Content-Transfer-Encoding: 7bit
|
13
|
X-Scanned-By: MIMEDefang 2.68 on 10.5.11.23
|
14
|
X-HE-Spam-Level: -----
|
15
|
X-HE-Spam-Score: -5.0
|
16
|
X-HE-Spam-Report: Content analysis details: (-5.0 points) pts rule name
|
17
|
description ---- ----------------------
|
18
|
-------------------------------------------------- -5.0 RCVD_IN_DNSWL_HI RBL:
|
19
|
Sender listed at http://www.dnswl.org/, high trust [209.132.183.28 listed in
|
20
|
list.dnswl.org]
|
21
|
X-HE-SPF: PASSED
|
22
|
|
23
|
|
24
|
--DqTQSWpbg52wGwmS56OuGElxKiDtdInxH
|
25
|
Content-Type: text/plain;
|
26
|
charset=utf-8
|
27
|
Content-Transfer-Encoding: quoted-printable
|
28
|
|
29
|
We don't necessarily have to make this a unit test. It could just be
|
30
|
another thing that run-tests.py does. We may be able to make the
|
31
|
pulp.devel package have to code to perform this test and have each
|
32
|
run-tests.py use it.
|
33
|
|
34
|
> --- Please write your response above this line ---
|
35
|
> =
|
36
|
|
37
|
> Issue #112 has been reported by Chris Duryee.
|
38
|
> -----------------------------------------------------------------------=
|
39
|
-
|
40
|
> =
|
41
|
|
42
|
> =
|
43
|
|
44
|
> Task #112: Add a test to ensure pulp's setup.py versions are the same=
|
45
|
|
46
|
> as the RPM versions <https://pulp.plan.io/issues/112>
|
47
|
> =
|
48
|
|
49
|
> * Author: Chris Duryee
|
50
|
> * Status: NEW
|
51
|
> * Priority: Normal
|
52
|
> * Assignee:
|
53
|
> * Category:
|
54
|
> * Sprint/Milestone: =
|
55
|
|
56
|
> =
|
57
|
|
58
|
> Pulp is versioned in two places: the spec file, and in various setup.py=
|
59
|
|
60
|
> files. These can get out of sync since tag.sh will not update all of th=
|
61
|
e
|
62
|
> setup.py files.
|
63
|
> =
|
64
|
|
65
|
> We should have an automated test to ensure the versions specificied in
|
66
|
> the setup.py files match what's in the spec file.
|
67
|
> =
|
68
|
|
69
|
> This will be needed for plugins as well as for platform.
|
70
|
> =
|
71
|
|
72
|
> -----------------------------------------------------------------------=
|
73
|
-
|
74
|
> =
|
75
|
|
76
|
> You have received this notification because you have either subscribed
|
77
|
> to or are involved in a project on pulp Planio.
|
78
|
> To change your notification preferences, please click here:
|
79
|
> https://pulp.plan.io/my/account
|
80
|
> =
|
81
|
|
82
|
> =
|
83
|
|
84
|
> =
|
85
|
|
86
|
> This notification was cheerfully delivered by <https://plan.io/>
|
87
|
> =
|
88
|
|
89
|
> Planio <https://plan.io/>
|
90
|
> =
|
91
|
|
92
|
|
93
|
|
94
|
--DqTQSWpbg52wGwmS56OuGElxKiDtdInxH--
|