Problem still exists in Ubuntu 14.04 LTS.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bacula in Ubuntu.
https://bugs.launchpad.net/bugs/1004494
Title:
Job not run message after any attempt to run a job using bconsole
To manage
Oleg, you are right, the localized answer works.
In german, the appropriate answer is ja.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bacula in Ubuntu.
https://bugs.launchpad.net/bugs/1004494
Title:
Job not run message after any
looks like the bug is caused by incomplete translation
i have Ubuntu 12.04 with russian localization
if i enter yes i got the same Job not run message
but if i answer in russian (да) it works fine
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
[Expired for bacula (Ubuntu) because there has been no activity for 60
days.]
** Changed in: bacula (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bacula in Ubuntu.
** Changed in: bacula (Ubuntu)
Status: Expired = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bacula in Ubuntu.
https://bugs.launchpad.net/bugs/1004494
Title:
Job not run message after any attempt to run a job
this bug is still here in Ubuntu 12.04, the described workaround is
functioning
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bacula in Ubuntu.
https://bugs.launchpad.net/bugs/1004494
Title:
Job not run message after any attempt
[Expired for bacula (Ubuntu) because there has been no activity for 60
days.]
** Changed in: bacula (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bacula in Ubuntu.
Exactly. This is a usable though not very easy workaround because you
need to modify every parameter in command line.
This is the decision from the Bacula bug tracker administrator:
It looks like your system or Bacula build is broken. Who build the
binaries?
By the way, I am building and
Thanks for submitting this bug. (Note I can't look at the
bugs.bacula.org without signing up for an account.)
To be clear, you are saying that
run job=jobname yes
succeeds, and is a usable workaround?
** Changed in: bacula (Ubuntu)
Importance: Undecided = Medium
** Changed in: bacula