summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/attachments/20120311/b542d619/attachment-0001.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/attachments/20120311/b542d619/attachment-0001.html')
-rw-r--r--zarb-ml/mageia-dev/attachments/20120311/b542d619/attachment-0001.html17
1 files changed, 17 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/attachments/20120311/b542d619/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20120311/b542d619/attachment-0001.html
new file mode 100644
index 000000000..3b9de4a8c
--- /dev/null
+++ b/zarb-ml/mageia-dev/attachments/20120311/b542d619/attachment-0001.html
@@ -0,0 +1,17 @@
+<p><br>
+On Mar 11, 2012 12:38 PM, &quot;Oliver Burger&quot; &lt;<a href="mailto:oliver.bgr@googlemail.com">oliver.bgr@googlemail.com</a>&gt; wrote:<br>
+&gt;<br>
+&gt; 2012/3/11 Sander Lepik &lt;<a href="mailto:sander.lepik@eesti.ee">sander.lepik@eesti.ee</a>&gt;:<br>
+&gt; &gt; It&#39;s a new package. How much harm can it do? I would understand this<br>
+&gt; &gt; rejection if we would have backports enabled. But we don&#39;t. Some point<br>
+&gt; &gt; release can cause more trouble than this package. This is getting<br>
+&gt; &gt; ridiculous.<br>
+&gt; I have to agree with Sander here. In the meeting someone asked if<br>
+&gt; submitting new packages would still be able and the answer was<br>
+&gt; something like<br>
+&gt; &quot;Yes, but we would prefer you to focus on fixing bugs&quot;.<br>
+&gt; Of course focusing on fixing bugs is a good thing, but we are still<br>
+&gt; almost two months before release and the fact that we don&#39;t have<br>
+&gt; backports (and probably never will :/ ) is a big problem.</p>
+<p>As far as I know only packages with different version are rejected by your I, not new ones.<br>
+</p>