Sorry for my late answer, but i could not read it before.
If one does another update (i.e. adds subrel), it should mean that the
fixes/whatever have been done to the cauldron tree first and thus
cauldron has 1.0-2.mga1, while mga1 gets 1.0-1.1.mga1.
That's also my point of view...
Maintainer
'Twas brillig, and Samuel Verschelde at 28/07/11 13:11 did gyre and gimble:
Le jeudi 28 juillet 2011 13:02:26, Colin Guthrie a écrit :
'Twas brillig, and Samuel Verschelde at 28/07/11 09:08 did gyre and gimble:
We have updates blocked by this release 0 issue, so we need a quick
decision. I
Le vendredi 29 juillet 2011 10:25:02, Colin Guthrie a écrit :
'Twas brillig, and Samuel Verschelde at 28/07/11 13:11 did gyre and gimble:
Le jeudi 28 juillet 2011 13:02:26, Colin Guthrie a écrit :
'Twas brillig, and Samuel Verschelde at 28/07/11 09:08 did gyre and
gimble:
We have updates
'Twas brillig, and Samuel Verschelde at 29/07/11 09:32 did gyre and gimble:
Le vendredi 29 juillet 2011 10:25:02, Colin Guthrie a écrit :
'Twas brillig, and Samuel Verschelde at 28/07/11 13:11 did gyre and gimble:
Le jeudi 28 juillet 2011 13:02:26, Colin Guthrie a écrit :
'Twas brillig, and
Le jeudi 28 juillet 2011 10:08:44, Samuel Verschelde a écrit :
Le mercredi 27 juillet 2011 22:52:00, Samuel Verschelde a écrit :
Le mercredi 27 juillet 2011 16:59:37, Samuel Verschelde a écrit :
Ok, there will be no meeting tonight, so let's decide it on the ML. Was
everyone convinced
Le Vendredi 29 Juillet 2011 22:16:26 Samuel Verschelde a écrit :
Le jeudi 28 juillet 2011 10:08:44, Samuel Verschelde a écrit :
Le mercredi 27 juillet 2011 22:52:00, Samuel Verschelde a écrit :
Le mercredi 27 juillet 2011 16:59:37, Samuel Verschelde a écrit :
Ok, there will be no meeting
Le vendredi 29 juillet 2011 22:45:41, Luis Daniel Lucio Quiroz a écrit :
Le Vendredi 29 Juillet 2011 22:16:26 Samuel Verschelde a écrit :
Le jeudi 28 juillet 2011 10:08:44, Samuel Verschelde a écrit :
Le mercredi 27 juillet 2011 22:52:00, Samuel Verschelde a écrit :
Le mercredi 27
Le mercredi 27 juillet 2011 22:52:00, Samuel Verschelde a écrit :
Le mercredi 27 juillet 2011 16:59:37, Samuel Verschelde a écrit :
Le mercredi 27 juillet 2011 12:52:04, Samuel Verschelde a écrit :
Le mardi 26 juillet 2011 19:38:30, Samuel Verschelde a écrit :
Le mardi 26 juillet 2011
'Twas brillig, and Samuel Verschelde at 28/07/11 09:08 did gyre and gimble:
We have updates blocked by this release 0 issue, so we need a quick decision.
I propose that if tomorrow nobody reacted against the proposal, it will be
adopted.
Personally, I would vote to keep it the way it is with
Le jeudi 28 juillet 2011 13:02:26, Colin Guthrie a écrit :
'Twas brillig, and Samuel Verschelde at 28/07/11 09:08 did gyre and gimble:
We have updates blocked by this release 0 issue, so we need a quick
decision. I propose that if tomorrow nobody reacted against the
proposal, it will be
27.07.2011 17:59, Samuel Verschelde kirjutas:
Ok, there will be no meeting tonight, so let's decide it on the ML. Was
everyone convinced by misc's demonstration and do we agree to stop using the 0
release for updates and activate the Youri::Submit::Test::Precedence check on
submit to prevent
Le mercredi 27 juillet 2011 16:59:37, Samuel Verschelde a écrit :
Le mercredi 27 juillet 2011 12:52:04, Samuel Verschelde a écrit :
Le mardi 26 juillet 2011 19:38:30, Samuel Verschelde a écrit :
Le mardi 26 juillet 2011 18:42:05, Michael Scherer a écrit :
[snip]
Yet, the problem
Hi,
while trying to work on the queue of update needing a push, I noticed
that almost all of them use a Release: 0.
Since this has a specific meaning ( ie, used for pre release, or svn
snapshot ), using this for updates is quite confusing, and I do not see
the reason for that.
If the goal is
Le 26/07/2011 12:40, Michael Scherer a écrit :
Hi,
while trying to work on the queue of update needing a push, I noticed
that almost all of them use a Release: 0.
Since this has a specific meaning ( ie, used for pre release, or svn
snapshot ), using this for updates is quite confusing, and I
26.07.2011 13:40, Michael Scherer kirjutas:
Hi,
while trying to work on the queue of update needing a push, I noticed
that almost all of them use a Release: 0.
Since this has a specific meaning ( ie, used for pre release, or svn
snapshot ), using this for updates is quite confusing, and I do
On 26 July 2011 13:22, Luc Menut lme...@free.fr wrote:
Le 26/07/2011 12:40, Michael Scherer a écrit :
Hi,
while trying to work on the queue of update needing a push, I noticed
that almost all of them use a Release: 0.
Since this has a specific meaning ( ie, used for pre release, or svn
Le mardi 26 juillet 2011 12:40:02, Michael Scherer a écrit :
Hi,
while trying to work on the queue of update needing a push, I noticed
that almost all of them use a Release: 0.
Since this has a specific meaning ( ie, used for pre release, or svn
snapshot ), using this for updates is quite
Le mardi 26 juillet 2011 17:48:55, Samuel Verschelde a écrit :
Le mardi 26 juillet 2011 12:40:02, Michael Scherer a écrit :
Hi,
while trying to work on the queue of update needing a push, I noticed
that almost all of them use a Release: 0.
Since this has a specific meaning ( ie,
'Twas brillig, and Michael Scherer at 26/07/11 11:40 did gyre and gimble:
If the goal is to be sure that the software is still upgradable, the
whole %mkrel stuff should take care of that.
No it doesn't. That only works for one release assuming we do not use
subrel with that release. Even with
On 26.07.2011 18:48, Samuel Verschelde wrote:
Le mardi 26 juillet 2011 12:40:02, Michael Scherer a écrit :
Hi,
while trying to work on the queue of update needing a push, I noticed
that almost all of them use a Release: 0.
Since this has a specific meaning ( ie, used for pre release, or svn
On 26.07.2011 19:20, Colin Guthrie wrote:
'Twas brillig, and Michael Scherer at 26/07/11 11:40 did gyre and gimble:
If the goal is to be sure that the software is still upgradable, the
whole %mkrel stuff should take care of that.
No it doesn't. That only works for one release assuming we do
Le mardi 26 juillet 2011 à 15:26 +0300, Ahmad Samir a écrit :
On 26 July 2011 13:22, Luc Menut lme...@free.fr wrote:
Le 26/07/2011 12:40, Michael Scherer a écrit :
Hi,
while trying to work on the queue of update needing a push, I noticed
that almost all of them use a Release: 0.
26.07.2011 19:42, Michael Scherer kirjutas:
Likely because none of them know the specific meaning of using 0.
From where is this specific meaning coming? Where is it documented?
--
Sander
Le mardi 26 juillet 2011 à 17:53 +0200, Samuel Verschelde a écrit :
Le mardi 26 juillet 2011 17:48:55, Samuel Verschelde a écrit :
Le mardi 26 juillet 2011 12:40:02, Michael Scherer a écrit :
Hi,
while trying to work on the queue of update needing a push, I noticed
that almost all
'Twas brillig, and Anssi Hannula at 26/07/11 17:27 did gyre and gimble:
On 26.07.2011 19:20, Colin Guthrie wrote:
'Twas brillig, and Michael Scherer at 26/07/11 11:40 did gyre and gimble:
If the goal is to be sure that the software is still upgradable, the
whole %mkrel stuff should take care
Le mardi 26 juillet 2011 18:26:25, Anssi Hannula a écrit :
On 26.07.2011 18:48, Samuel Verschelde wrote:
Le mardi 26 juillet 2011 12:40:02, Michael Scherer a écrit :
Hi,
while trying to work on the queue of update needing a push, I noticed
that almost all of them use a Release: 0.
Le mardi 26 juillet 2011 18:55:31, Colin Guthrie a écrit :
'Twas brillig, and Anssi Hannula at 26/07/11 17:27 did gyre and gimble:
On 26.07.2011 19:20, Colin Guthrie wrote:
'Twas brillig, and Michael Scherer at 26/07/11 11:40 did gyre and gimble:
If the goal is to be sure that the software
Le mardi 26 juillet 2011 18:42:05, Michael Scherer a écrit :
[snip]
Yet, the problem would also be there for regular non-version upgrade
( ie, if we have foo-2-2.mga2 in cauldron and stable, and that we need
to rebuild on stable and not on cauldron, we face the same problem ), so
using 0 is
Le mardi 26 juillet 2011 à 19:46 +0300, Sander Lepik a écrit :
26.07.2011 19:42, Michael Scherer kirjutas:
Likely because none of them know the specific meaning of using 0.
From where is this specific meaning coming? Where is it documented?
Where does it come, I do not know, likely due to
Le mardi 26 juillet 2011 à 19:21 +0200, Samuel Verschelde a écrit :
Le mardi 26 juillet 2011 18:26:25, Anssi Hannula a écrit :
On 26.07.2011 18:48, Samuel Verschelde wrote:
Le mardi 26 juillet 2011 12:40:02, Michael Scherer a écrit :
Hi,
while trying to work on the queue of update
30 matches
Mail list logo
