1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA256 |
3 |
|
4 |
On 04/04/2015 01:09 PM, Thomas D. wrote: |
5 |
> Hi, |
6 |
> |
7 |
> some of you maybe know or already have noticed that the |
8 |
> net-firewall/shorewall* ebuilds were re-integrated into a new |
9 |
> all-in-one ebuild for easier maintenance. |
10 |
> |
11 |
> The package is proxy-maintained. |
12 |
> |
13 |
> While preparing the new ebuild I discussed with the proxy-maint |
14 |
> team and shorewall users if we should create a news item for that |
15 |
> change. Most people participating in the discussion thought that |
16 |
> emerge's error message like |
17 |
> |
18 |
>> # emerge -p --update net-firewall/shorewall::gentoo |
19 |
>> |
20 |
>> These are the packages that would be merged, in order: |
21 |
>> |
22 |
>> Calculating dependencies... done! [ebuild U ] |
23 |
>> net-firewall/shorewall-4.6.6.2::gentoo [4.5.21.10-r1::gentoo] |
24 |
>> USE="doc init%* ipv4%* ipv6%* lite4%* -lite6%" 0 KiB [blocks B |
25 |
>> ] net-firewall/shorewall-init ("net-firewall/shorewall-init" is |
26 |
>> blocking net-firewall/shorewall-4.6.6.2) [blocks B ] |
27 |
>> net-firewall/shorewall-core ("net-firewall/shorewall-core" is |
28 |
>> blocking net-firewall/shorewall-4.6.6.2) |
29 |
>> |
30 |
>> Total: 1 package (1 upgrade), Size of downloads: 0 KiB Conflict: |
31 |
>> 2 blocks (2 unsatisfied) |
32 |
>> |
33 |
>> !!! Multiple package instances within a single package slot have |
34 |
>> been pulled !!! into the dependency graph, resulting in a slot |
35 |
>> conflict: |
36 |
>> |
37 |
>> net-firewall/shorewall:0 |
38 |
>> |
39 |
>> (net-firewall/shorewall-4.6.6.2:0/0::gentoo, ebuild scheduled for |
40 |
>> merge) pulled in by net-firewall/shorewall::gentoo (Argument) |
41 |
>> |
42 |
>> (net-firewall/shorewall-4.5.21.10-r1:0/0::gentoo, installed) |
43 |
>> pulled in by =net-firewall/shorewall-4.5.21.10-r1 required by |
44 |
>> (net-firewall/shorewall-init-4.5.21.10-r1:0/0::gentoo, |
45 |
>> installed) ^ ^^^^^^^^^^^^ |
46 |
>> |
47 |
>> |
48 |
>> It may be possible to solve this problem by using package.mask |
49 |
>> to prevent one of those packages from being selected. However, it |
50 |
>> is also possible that conflicting dependencies exist such that |
51 |
>> they are impossible to satisfy simultaneously. If such a |
52 |
>> conflict exists in the dependencies of two different packages, |
53 |
>> then those packages can not be installed simultaneously. You may |
54 |
>> want to try a larger value of the --backtrack option, such as |
55 |
>> --backtrack=30, in order to see if that will solve this conflict |
56 |
>> automatically. |
57 |
>> |
58 |
>> For more information, see MASKED PACKAGES section in the emerge |
59 |
>> man page or refer to the Gentoo Handbook. |
60 |
>> |
61 |
>> |
62 |
>> * Error: The above package list contains packages which cannot |
63 |
>> be * installed at the same time on the same system. |
64 |
>> |
65 |
>> (net-firewall/shorewall-init-4.5.21.10-r1:0/0::gentoo, installed) |
66 |
>> pulled in by net-firewall/shorewall-init required by @selected |
67 |
>> |
68 |
>> (net-firewall/shorewall-core-4.5.21.10-r1:0/0::gentoo, installed) |
69 |
>> pulled in by =net-firewall/shorewall-core-4.5.21.10-r1 required |
70 |
>> by (net-firewall/shorewall-4.5.21.10-r1:0/0::gentoo, installed) |
71 |
>> |
72 |
>> |
73 |
>> For more information about Blocked Packages, please refer to the |
74 |
>> following section of the Gentoo Linux x86 Handbook (architecture |
75 |
>> is irrelevant): |
76 |
>> |
77 |
>> https://wiki.gentoo.org/wiki/Handbook:X86/Working/Portage#Blocked_packages |
78 |
> |
79 |
>> |
80 |
> should be clear enough for everyone. |
81 |
> |
82 |
> |
83 |
> Well, it turns out that not everyone understands the merge conflict |
84 |
> and knows what to do. Multiple users filled bugs and requested a |
85 |
> news item, two recent examples: |
86 |
> |
87 |
> - https://bugs.gentoo.org/show_bug.cgi?id=544216#c2 - |
88 |
> https://bugs.gentoo.org/show_bug.cgi?id=539664#c2 |
89 |
> |
90 |
> |
91 |
> As proxy-maintainer I changed my mind today and created a news |
92 |
> item. Mostly because it doesn't hurt anyone (no negative impact). |
93 |
> It only helps people who don't know what to do... and why shouldn't |
94 |
> we help if we can? |
95 |
> |
96 |
> Please review my proposal below: |
97 |
> |
98 |
> Just a few notes to explain my choice of words: |
99 |
> |
100 |
> 1) The news item will tell the user what has changed and why this |
101 |
> change was made. Interested users can read the bug report for |
102 |
> further information. |
103 |
> |
104 |
> 2) The given emerge command should work on all systems for every |
105 |
> user. No need to check which package in detail they need to |
106 |
> remove. No error messages like "--- Couldn't find |
107 |
> 'net-firewall/shorewall-lite' to unmerge." because they didn't have |
108 |
> shorewall-lite installed. |
109 |
> |
110 |
> 3) The last paragraph should indicate that the new shorewall ebuild |
111 |
> is "stable" and that they don't have to react immediately but |
112 |
> within the next 30-60 days if they don't want to upgrade now. |
113 |
> |
114 |
> |
115 |
> =========================================================================== |
116 |
> |
117 |
> |
118 |
Title: New net-firewall/shorewall all-in-one package |
119 |
> Author: Thomas D. <whissi@××××××.de> Content-Type: text/plain |
120 |
> Posted: 2015-04-<to-be-set> Revision: 1 News-Item-Format: 1.0 |
121 |
> Display-If-Installed: net-firewall/shorewall-core |
122 |
> Display-If-Installed: net-firewall/shorewall6 Display-If-Installed: |
123 |
> net-firewall/shorewall-lite Display-If-Installed: |
124 |
> net-firewall/shorewall6-lite Display-If-Installed: |
125 |
> net-firewall/shorewall-init |
126 |
> |
127 |
> Starting with net-firewall/shorewall-4.6 we have re-integrated |
128 |
> |
129 |
> - net-firewall/shorewall-core - net-firewall/shorewall6 - |
130 |
> net-firewall/shorewall-lite - net-firewall/shorewall6-lite - |
131 |
> net-firewall/shorewall-init |
132 |
> |
133 |
> into a new all-in-one net-firewall/shorewall ebuild (see bug |
134 |
> 522278). |
135 |
> |
136 |
> The new all-in-one ebuild makes maintenance a lot more easier |
137 |
> because the package is proxy-maintained and finding someone who is |
138 |
> willing to help you bumping 6 packages each time you provide an |
139 |
> update was not easy in the past. |
140 |
> |
141 |
> Because net-firewall/shorewall{-core,6,-lite,6-lite,init} is now |
142 |
> integrated in net-firewall/shorewall, we have to hard mask these |
143 |
> old ebuilds in the new monolithic ebuild to prevent file |
144 |
> collisions. |
145 |
> |
146 |
> Due to this block we cannot migrate to the new version without |
147 |
> user interaction. Please remove the previous split ebuilds from |
148 |
> your system if you want to upgrade: |
149 |
> |
150 |
> $ emerge --ask --unmerge 'net-firewall/shorewall-*' \ |
151 |
> 'net-firewall/shorewall6*' |
152 |
> |
153 |
> |
154 |
> Please note: Since the second shorewall-4.6 ebuild is now |
155 |
> stabilized and shorewall-4.5 is not compatible with the perl-5.20 |
156 |
> (see bug 524558) we will start the removal process for |
157 |
> shorewall-4.5 ebuilds within the next 30 days. |
158 |
> =========================================================================== |
159 |
> |
160 |
> |
161 |
> |
162 |
> -Thomas |
163 |
> |
164 |
|
165 |
As someone who runs shorewall on a VPS, the news item would be really |
166 |
helpful when I get around to updating the packages for it so I don't |
167 |
miss the blockage. I'm not a dev (yet) but this seems sane to me. |
168 |
-----BEGIN PGP SIGNATURE----- |
169 |
Version: GnuPG v2 |
170 |
|
171 |
iQEcBAEBCAAGBQJVIGsDAAoJEJUrb08JgYgHAOoH/iOtw2eUqDf4IRn8AhHudWGq |
172 |
tVTwZJX04lfLyo1dXImRMJHG4cmMebSpzKQ0BrxcIrjQHpyUeXqSx6ksfZUmd/C6 |
173 |
sQSvcQyBpNGB37TI80JR2ljF8P7DLtagZKlcqhkvPxehKIm1PbmVavGzbqeJWMs9 |
174 |
9d3bcYFfNGLEroBuiw40d6196IhweqHybVdk9brKnu6npsXnsikuAWE9WIk3t3+S |
175 |
zi2LO4T2wQgUtY3cB6ugq6nWlqQaZLy7KyXNFHqG5mKPU2qDBtMdNKx7Eau7rvKR |
176 |
JgwVkp00/Sha5JhH55mHhmJ7jEULOdS67OjdWSDkDVzuocXmZ5w9hE8xlsUl72s= |
177 |
=+i33 |
178 |
-----END PGP SIGNATURE----- |