my understanding , you don't need bump any version , you may just do:
cvs up ; make build
Thank you very much Sérgio. Back at home, tried this and it worked
exactly as expected.
Cordially,
--
NVieville
It happened again this morning with wl-kmod for F-18. This time it was a
mock error.
I have a question. If I submit a new job, I'll probably have to change
the minor release version number to be able to do so. Isn't it annoying
and wouldn't it be more appropriate to just ask plague
Nicolas Viéville nicolas.vievi...@univ-valenciennes.fr a écrit :
According to the situation in this case the only alternative
I have is to submit a new job (that I can re-submit eventually if
needed), but the counter part is to bump the minor release version
number, even if the package was not
Le samedi 26 octobre 2013 à 09:58 +0200, Xavier Bachelot a écrit :
Nicolas Viéville nicolas.vievi...@univ-valenciennes.fr a écrit :
According to the situation in this case the only alternative
I have is to submit a new job (that I can re-submit eventually if
needed), but the counter part is
On Sáb, 2013-10-26 at 09:36 +0200, Nicolas Viéville wrote:
It happened again this morning with wl-kmod for F-18. This time it was a
mock error.
I have a question. If I submit a new job, I'll probably have to change
the minor release version number to be able to do so. Isn't
[...]
Thank you Sérgio for your explanation and the tip with plague.
But in this case, as I'm not the initial submitter of the job, plague
refuse me to do so, that's why I asked a question about bumping the
minor release version number in my previous message (at the beginning of
On Qua, 2013-10-23 at 08:03 +0200, Nicolas Viéville wrote:
Le mardi 22 octobre 2013 à 15:19 +0200, Nicolas Viéville a écrit :
It was just pushed.
As it's the latest, please submit a new job, the root cause of this is
still unknown
It happened again this morning with wl-kmod
Le mardi 22 octobre 2013 à 15:19 +0200, Nicolas Viéville a écrit :
It was just pushed.
As it's the latest, please submit a new job, the root cause of this is
still unknown
It happened again this morning with wl-kmod for F-18. This time it was a
mock error.
I have a question. If I
It was just pushed.
As it's the latest, please submit a new job, the root cause of this is
still unknown
It happened again this morning with wl-kmod for F-18. This time it was a
mock error.
I have a question. If I submit a new job, I'll probably have to change
the minor release version
2013/10/16 Nicolas Viéville nicolas.vievi...@univ-valenciennes.fr
http://buildsys.rpmfusion.org/plague-results/fedora-18-rpmfusion_nonfree/wl-kmod/
The date is directory is after your email , seems soon we get this on
F18 - testings.
Things seem to have been fixed since my first E-mail
Hello,
There seems that last F-18 build for wl-kmod stayed stuck in buildsys
and was not pushed in corresponding testing repository.
As I'm not the original submitter of the build job 18707 on buildsys,
plague refuse me to resubmit this job.
I wonder if it was possible to make something without
On Qua, 2013-10-16 at 09:01 +0200, Nicolas Viéville wrote:
Hello,
There seems that last F-18 build for wl-kmod stayed stuck in buildsys
and was not pushed in corresponding testing repository.
As I'm not the original submitter of the build job 18707 on buildsys,
plague refuse me to resubmit
http://buildsys.rpmfusion.org/plague-results/fedora-18-rpmfusion_nonfree/wl-kmod/
The date is directory is after your email , seems soon we get this on
F18 - testings.
Things seem to have been fixed since my first E-mail today (now job
number 18707 appears in the successful builds page of
13 matches
Mail list logo
