gnome-schedule-users Mailing List for gnome-schedule

Trying to install this on a raspberry Pi can some one help?

Mike Hebert

Can someone give me a proper walk through for installing this on a raspberry pi please 

That is crontab trying to send up an email with the output from the job 
(MTA means mail transfer agent). It is probably being run, but fails for 
some reason. I don't see any '*******'  in the screenshot -- did you 
press advanced view and see the actual crontab time format.. ?

Anyway, try an easier command first and see if it works. E.g. 

  echo test > ~/mytestoutput

It could be that your command relies on the window manager, in which 
case it might not work. You can try to check the option for graphical 
application when editing / creating the task. Maybe there are some 
permission errors.

- gaute

Jack Lobingier writes on June 29, 2018 19:52:
> Thank you for your help.  Here is a screen shot of the error.  Not sure
> what 'No MTA installed' is.
> 
> On Fri, Jun 29, 2018 at 12:19 PM, Gaute Hope <eg...@ga...> wrote:
> 
>> Jack Lobingier writes on June 29, 2018 19:00:
>>
>>> I just installed gnome-schedule and all appears to go well, as I can
>>> create
>>> a repetitive task, and I can run it manually.  However, it does not run on
>>> schedule, and the time column has ******** in it.  Maybe this has come up
>>> before, but as I am new to the list it's all new to me.  Please help.
>>>
>>
>> Do you have the cron daemon running on your system? This depends on which
>> distribution you have, so check its docs. If this does not work, can you
>> send a screenshot of the main window?
>> Regards, Gaute
>>
>>
> 

Jack Lobingier writes on June 29, 2018 19:00:
> I just installed gnome-schedule and all appears to go well, as I can create
> a repetitive task, and I can run it manually.  However, it does not run on
> schedule, and the time column has ******** in it.  Maybe this has come up
> before, but as I am new to the list it's all new to me.  Please help.

Do you have the cron daemon running on your system? This depends on 
which distribution you have, so check its docs. If this does not work, 
can you send a screenshot of the main window? 

Regards, Gaute

On Fri, 29 Jun 2018 12:00:47 -0500
Jack Lobingier wrote:

> I just installed gnome-schedule and all appears to go well, as I can create
> a repetitive task, and I can run it manually.  However, it does not run on
> schedule, and the time column has ******** in it.  Maybe this has come up
> before, but as I am new to the list it's all new to me.  Please help.

Post the relevant line from:

crontab -l


-- 
MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com

I just installed gnome-schedule and all appears to go well, as I can create
a repetitive task, and I can run it manually.  However, it does not run on
schedule, and the time column has ******** in it.  Maybe this has come up
before, but as I am new to the list it's all new to me.  Please help.

Jack

Hi Randy,

I only have a short answer at this time:

I assume you already know about the 'advanced' mode, and it probably 
fits your description of more or less the same as crontab. But you do 
get a humanly readable interpretation of the time spec. Does that help?

For the other suggestions; I think there are bugzilla issues (gnome 
tracker) for several of them, which would be really nice to see 
implemented (e.g. toggling tasks on/off).

Did you install gnome-terminal on the host machine?

If you do write the `is_it` script to extend the current crontab 
capabilities this might be something that could be included with 
gnome-schedule.

Best, Gaute

Rue, Randy writes on mars 14, 2018 18:08:
> Hi All,
> 
> I'm trying to find a friendlier way for our users to schedule tasks on a 
> shared server they shell into. They're currently all running crontab 
> from the CLI, but we get regular requests for something with less of a 
> learning curve and with scheduling options more like what they're used 
> to in other apps, e.g. ways to schedule a task to run the "first 
> Monday," "last Friday," etc.
> 
> I've spent some time fooling around with other apps but so far nothing 
> is any less complicated for them to learn, and nothing is significantly 
> more flexible in scheduling recurrence. For example, there's a popular 
> job scheduler that's open source, but seems to be aimed more at large, 
> centrally managed CI/CD workflows, seems to be deliberately thinly 
> documented for the free version, and scheduling the launch itself is no 
> better than crontab (in fact, if you choose their advanced option, you 
> switch to using crontab syntax).
> 
> While our server doesn't run a GUI, we do run other apps on it that run 
> X, and users are used to SSH'ing for GUI apps. So gnome-schedule would 
> run for them, and it's a good fit in that:
> 
> * The users that prefer crontab could use it or not, as they wish, or 
> switch between them without trouble.
> 
> * User profiles, SSH keys, directory mounts, access to their code and 
> data, are all already set up.
> 
> There are a few things missing, however:
> 
> * "First Monday," "last Friday" scheduling
> 
> * Is there a way to disable/enable a task in the GUI? Seems like this 
> would be reasonably simple to add, simply commenting the crontab line. 
> The trick would be the GUI app somehow knowing not to try parsing other 
> comment lines if they're there.
> 
> * I tried the "run task" button and it wants to launch gnome-terminal. I 
> installed gnome-terminal on my test server but the task that runs from 
> cron still doesn't succeed in Terminal. Is there a way to use the shell )
> directly without needing to invoke another GUI app?
> 
> * Some option for output, either logs or emails, and notifications of 
> successes/failures. Admittedly, cron already does some of this, and the 
> users could also add it to whatever code they're calling, but a simple 
> option to easily click a box would free them of the need to recreate it 
> for every task.
> 
> I'm clear that adding recurrence options like "first Monday" is 
> non-trivial. Even the interface changes are the kind of thing that 
> Microsoft pays huge teams of "UX Architects" to hammer out. And 
> implementing it under the hood gets weirder, presumably by adding nested 
> tests for the day and date to the call itself akin to what's explained 
> at 
> https://superuser.com/questions/428807/run-a-cron-job-on-the-first-monday-of-every-month.
> 
> It might make sense to provide templates for first Monday, last Friday, 
> etc, but I'm hoping to provide more than a few basic options without 
> needing to maintain a long list of templates.
> 
> As a starting point I'm instead considering writing a short wrapper 
> named something like "is_it," that would take arguments for days, weeks, 
> etc, and return an exit state for whether or not it's the first Monday, 
> second or fourth Thursday, etc. If I get that into a usable shape I'll 
> reply here with a link to my github.
> 
> 
> Thanks if you've plowed through this. Hope to hear from you,
> 
> Randy in Seattle
> 
> 
> 
> 
> 
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> gnome-schedule-users mailing list
> gno...@li...
> https://lists.sourceforge.net/lists/listinfo/gnome-schedule-users
> 

Hi All,

I'm trying to find a friendlier way for our users to schedule tasks on a 
shared server they shell into. They're currently all running crontab 
from the CLI, but we get regular requests for something with less of a 
learning curve and with scheduling options more like what they're used 
to in other apps, e.g. ways to schedule a task to run the "first 
Monday," "last Friday," etc.

I've spent some time fooling around with other apps but so far nothing 
is any less complicated for them to learn, and nothing is significantly 
more flexible in scheduling recurrence. For example, there's a popular 
job scheduler that's open source, but seems to be aimed more at large, 
centrally managed CI/CD workflows, seems to be deliberately thinly 
documented for the free version, and scheduling the launch itself is no 
better than crontab (in fact, if you choose their advanced option, you 
switch to using crontab syntax).

While our server doesn't run a GUI, we do run other apps on it that run 
X, and users are used to SSH'ing for GUI apps. So gnome-schedule would 
run for them, and it's a good fit in that:

* The users that prefer crontab could use it or not, as they wish, or 
switch between them without trouble.

* User profiles, SSH keys, directory mounts, access to their code and 
data, are all already set up.

There are a few things missing, however:

* "First Monday," "last Friday" scheduling

* Is there a way to disable/enable a task in the GUI? Seems like this 
would be reasonably simple to add, simply commenting the crontab line. 
The trick would be the GUI app somehow knowing not to try parsing other 
comment lines if they're there.

* I tried the "run task" button and it wants to launch gnome-terminal. I 
installed gnome-terminal on my test server but the task that runs from 
cron still doesn't succeed in Terminal. Is there a way to use the shell 
directly without needing to invoke another GUI app?

* Some option for output, either logs or emails, and notifications of 
successes/failures. Admittedly, cron already does some of this, and the 
users could also add it to whatever code they're calling, but a simple 
option to easily click a box would free them of the need to recreate it 
for every task.

I'm clear that adding recurrence options like "first Monday" is 
non-trivial. Even the interface changes are the kind of thing that 
Microsoft pays huge teams of "UX Architects" to hammer out. And 
implementing it under the hood gets weirder, presumably by adding nested 
tests for the day and date to the call itself akin to what's explained 
at 
https://superuser.com/questions/428807/run-a-cron-job-on-the-first-monday-of-every-month.

It might make sense to provide templates for first Monday, last Friday, 
etc, but I'm hoping to provide more than a few basic options without 
needing to maintain a long list of templates.

As a starting point I'm instead considering writing a short wrapper 
named something like "is_it," that would take arguments for days, weeks, 
etc, and return an exit state for whether or not it's the first Monday, 
second or fourth Thursday, etc. If I get that into a usable shape I'll 
reply here with a link to my github.


Thanks if you've plowed through this. Hope to hear from you,

Randy in Seattle

That did the trick! Thanks!

Tom Henderson

On 11/06/2017 05:29 PM, Gaute Hope wrote:
> Tom Henderson writes on november 6, 2017 22:57:
>> I know this is going to be something silly that I'm missing. The 
>> following bash script:
>>
>>> #!/bin/bash
>>>
>>> quote=`wget -q -O - http://www.google.com/finance?q=T | grep ref_ -m 
>>> 1 | sed 's|<[^>]*>||g'`
>>>
>>> echo "AT&T Stock price is $quote"
>>
>> Works fine from the command line, but when I run it in 
>> gnome-schedule, it blows up.
>>
>> Command line
>>
>>> tom@tom-desktop:~$ echo $(/home/tom/scripts/stockquote)
>>> AT&T Stock price is 32.86
>> Output when I run with gnome-schedule:
>>
>>> grep: -m: No such file or directory
>>> grep: 1: No such file or directory
>>> AT&T Stock price is
>>> Press ENTER to continue and close this window.
>> What obvious error am I making?
>
> Hi Tom,
>
> I tried to run your script; except without wrapping it in echo $(..). 
> And it worked in both command-line and as a task in gnome-schedule. 
> Perhaps you have POSIXLY_CORRECT or something set that causes grep to 
> be very strict.. does it work better if you move the '-m 1' flag to 
> before the pattern?
>
> - Gaute
>
>

Tom Henderson writes on november 6, 2017 22:57:
> I know this is going to be something silly that I'm missing. The 
> following bash script:
> 
>> #!/bin/bash
>>
>> quote=`wget -q -O - http://www.google.com/finance?q=T | grep ref_ -m 1 
>> | sed 's|<[^>]*>||g'`
>>
>> echo "AT&T Stock price is $quote"
> 
> Works fine from the command line, but when I run it in gnome-schedule, 
> it blows up.
> 
> Command line
> 
>> tom@tom-desktop:~$ echo $(/home/tom/scripts/stockquote)
>> AT&T Stock price is 32.86
> Output when I run with gnome-schedule:
> 
>> grep: -m: No such file or directory
>> grep: 1: No such file or directory
>> AT&T Stock price is
>> Press ENTER to continue and close this window.
> What obvious error am I making?

Hi Tom,

I tried to run your script; except without wrapping it in echo $(..). 
And it worked in both command-line and as a task in gnome-schedule. 
Perhaps you have POSIXLY_CORRECT or something set that causes grep to be 
very strict.. does it work better if you move the '-m 1' flag to before 
the pattern?

- Gaute

I know this is going to be something silly that I'm missing. The 
following bash script:

> #!/bin/bash
>
> quote=`wget -q -O - http://www.google.com/finance?q=T | grep ref_ -m 1 
> | sed 's|<[^>]*>||g'`
>
> echo "AT&T Stock price is $quote"

Works fine from the command line, but when I run it in gnome-schedule, 
it blows up.

Command line

> tom@tom-desktop:~$ echo $(/home/tom/scripts/stockquote)
> AT&T Stock price is 32.86
Output when I run with gnome-schedule:

> grep: -m: No such file or directory
> grep: 1: No such file or directory
> AT&T Stock price is
> Press ENTER to continue and close this window.
What obvious error am I making?

-- 
Tom Henderson

Hi Larry,

Thanks for the interest.

There has been some discussion on the ubuntu and deb packages here:

https://bugs.launchpad.net/ubuntu/+source/gnome-schedule/+bug/1576060

I think someone packed and supplied a new version there.

Hope that helps, Gaute

fre. 24. feb. 2017 kl. 22.03 skrev Larry Bryan <la...@w8...>:

> I have version 2.1.1 and it appears there is a newer version. How do I
> update the current version?
>
> Larry​
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> gnome-schedule-users mailing list
> gno...@li...
> https://lists.sourceforge.net/lists/listinfo/gnome-schedule-users
>

I have version 2.1.1 and it appears there is a newer version. How do I
update the current version?

Larry​

Hi,

Gnome Schedule version 2.3.2 has just been released with updated
translations, bugfixes, and some dropped depencencies:

    http://sourceforge.net/projects/gnome-schedule/


Regards, Gaute

See http://ubuntuforums.org/showthread.php?t=1432802Je la 16/10/2015 21:05,

Gaute Hope skribis :
> Hi,
>
> Does it work to run it manually?
>
> Regards, Gaute
>
> Den fredag 16. oktober 2015 skrev Kevin Dudley <kk...@ou... 
> <mailto:kk...@ou...>> følgende:
>
>     Hi, I am a relative novice on Linux based systems so would
>     appreciate some help.
>
>     I am trying to create a scheduled task on LXLE (Ubuntu 14.04 base)
>     to sync my Google drive using grive.
>
>     I found the following on
>     http://http://onetransistor.blogspot.co.uk/2014/09/regular-backups-using-grive-on-ubuntu.html
>     */grive --path /home/<username>/Documents /*and have created the
>     task (replacing my username and the target folder) - however
>     nothing happens.
>
>     I have tried executing with a Terminal session open just to see if
>     anything appeared but to no avail - I know the scheduler is
>     working OK as I use it for scheduled backups to a 2nd hard drive
>     and external USB drive (using Lucky Backup which uses rsync) and
>     they work fine.
>
>     One thought I had (and I know it's not good practice, but it's set
>     up now) is that the target folder has a space in its name (Google
>     Drive) so the command is
>     /grive --path /home/kevin/Google Drive./
>     /
>     /
>     When I execute grive in Terminal it needs to run from the local
>     directory  - achieved by /cd/ /Google\ Drive/ so I tried that in
>     the scheduled task (inserting the backslash) but still no joy.
>
>     When I execute the task manually I get the message _"Note about
>     working directory of executed tasks: _Recurrent tasks will be run
>     from the home directory, one-time tasks from the directory where
>     GNOME schedule was run from at the time of task creation (normally
>     the home directory)._"_ But I'm not sure what effect this has, the
>     same message comes up on the Lucky Backup tasks and are OK.
>
>
>     Any assistance would be welcome.
>
>     Thanks,
>
>     Kevin
>
>
>
> ------------------------------------------------------------------------------ 
>
>
>
> _______________________________________________ gnome-schedule-users 
> mailing list gno...@li... 
> https://lists.sourceforge.net/lists/listinfo/gnome-schedule-users

Hi,

Does it work to run it manually?

Regards, Gaute

Den fredag 16. oktober 2015 skrev Kevin Dudley <kk...@ou...> følgende:

> Hi, I am a relative novice on Linux based systems so would appreciate some
> help.
>
> I am trying to create a scheduled task on LXLE (Ubuntu 14.04 base) to sync
> my Google drive using grive.
>
> I found the following on
> http://http://onetransistor.blogspot.co.uk/2014/09/regular-backups-using-grive-on-ubuntu.html
>   *grive --path /home/<username>/Documents *and have created the task
> (replacing my username and the target folder) - however nothing happens.
>
> I have tried executing with a Terminal session open just to see if
> anything appeared but to no avail - I know the scheduler is working OK as I
> use it for scheduled backups to a 2nd hard drive and external USB drive
> (using Lucky Backup which uses rsync) and they work fine.
>
> One thought I had (and I know it's not good practice, but it's set up now)
> is that the target folder has a space in its name (Google Drive) so the
> command is
> *grive --path /home/kevin/Google Drive.*
>
> When I execute grive in Terminal it needs to run from the local directory
>  - achieved by *cd* *Google\ Drive* so I tried that in the scheduled task
> (inserting the backslash) but still no joy.
>
> When I execute the task manually I get the message *"Note about working
> directory of executed tasks:  *Recurrent tasks will be run from the home
> directory, one-time tasks from the directory where GNOME schedule was run
> from at the time of task creation (normally the home directory).*"* But
> I'm not sure what effect this has, the same message comes up on the Lucky
> Backup tasks and are OK.
>
>
> Any assistance would be welcome.
>
> Thanks,
>
> Kevin
>

Hi, I am a relative novice on Linux based systems so would appreciate some help.
I am trying to create a scheduled task on LXLE (Ubuntu 14.04 base) to sync my Google drive using grive.
I found the following on http://http://onetransistor.blogspot.co.uk/2014/09/regular-backups-using-grive-on-ubuntu.html  grive --path /home/<username>/Documents and have created the task (replacing my username and the target folder) - however nothing happens.
I have tried executing with a Terminal session open just to see if anything appeared but to no avail - I know the scheduler is working OK as I use it for scheduled backups to a 2nd hard drive and external USB drive (using Lucky Backup which uses rsync) and they work fine.
One thought I had (and I know it's not good practice, but it's set up now) is that the target folder has a space in its name (Google Drive) so the command isgrive --path /home/kevin/Google Drive.
When I execute grive in Terminal it needs to run from the local directory  - achieved by cd Google\ Drive so I tried that in the scheduled task (inserting the backslash) but still no joy.
When I execute the task manually I get the message "Note about working directory of executed tasks:  Recurrent tasks will be run from the home directory, one-time tasks from the directory where GNOME schedule was run from at the time of task creation (normally the home directory)." But I'm not sure what effect this has, the same message comes up on the Lucky Backup tasks and are OK.

Any assistance would be welcome.
Thanks,
Kevin 		 	   		  

Excerpts from Frank Cox's message of 2014-03-05 21:58:11 +0100: > On Wed, 05 Mar 2014 07:53:47 +0100
> Gaute Hope wrote:
> 
> > Excerpts from Tom Henderson's message of 2014-03-05 01:10:13 +0100:
> > > For now, I accomplish the same thing by converting the scheduled task to 
> > > a comment (add '#') to the front of the command. Not as graceful, but it 
> > > works.
> > 
> > You could do the same for an at script by putting 'exit' at the top.
> 
> I'm missing the point of temporarily disabling an at job.  By definition, an at job is one-shot.  So the way to disable an at job would be to delete it.
> 
> Cronjobs, of course, are a different kettle of fish.
> 

Yes.. You are right, but could be an scheduled task that is put on hold
in case untill the user really decides if it should be scheduled or not.

- gaute

On Wed, 05 Mar 2014 07:53:47 +0100
Gaute Hope wrote:

> Excerpts from Tom Henderson's message of 2014-03-05 01:10:13 +0100:
> > For now, I accomplish the same thing by converting the scheduled task to 
> > a comment (add '#') to the front of the command. Not as graceful, but it 
> > works.
> 
> You could do the same for an at script by putting 'exit' at the top.

I'm missing the point of temporarily disabling an at job.  By definition, an at job is one-shot.  So the way to disable an at job would be to delete it.

Cronjobs, of course, are a different kettle of fish.

-- 
MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com

Excerpts from Tom Henderson's message of 2014-03-05 01:10:13 +0100:
> For now, I accomplish the same thing by converting the scheduled task to 
> a comment (add '#') to the front of the command. Not as graceful, but it 
> works.

You could do the same for an at script by putting 'exit' at the top.

- gaute

For now, I accomplish the same thing by converting the scheduled task to 
a comment (add '#') to the front of the command. Not as graceful, but it 
works.

On 03/04/2014 11:48 AM, Gaute Hope wrote:
> Excerpts from Frank Cox's message of 2014-03-04 18:05:51 +0100:
>> On Tue, 04 Mar 2014 08:34:28 +0100 Gaute Hope wrote:
>>
>>> Ok! I've pushed the change to git: bf76fd9, and it will be included
>>> in the next release.
>> Great, thanks!
>>
>> Here is an enhancement suggestion for sometime in the future:
>>
>> Would it be possible to add a "temporarily disable" option to the
>> menu?  You can comment out a line in the crontab file and disable a
>> job that way.  Perhaps with a note added to it that says "disabled" or
>> something so as not to confuse it with a real remark that someone
>> added to the crontab.  So a disabled job would look something like
>> this:
>>
>> # 0 04 1-7 * 3 mail -s "Subject" frankcox@localhost >/dev/null 2>&1 #
>> JOB_ID_8_DISABLED
>>
>> To re-enable it you would remove the # at the beginning of the line
>> and the _DISABLED at the end of the line.
>>
>> Cron would ignore it, and you could show a _DISABLED line in the
>> pending task window in a lighter colour, with the option on the menu
>> to re-enable it.
>>
> Hi Frank,
>
> Yeah, it would be a great feature, there is actually a (long-standing)
> feature request for it already:
>
> https://bugzilla.gnome.org/show_bug.cgi?id=571987
>
> But I don't have time to implement it myself. Would be happy to accept
> patches for it though!
>
> Cheers, Gaute
>
>
>
> ------------------------------------------------------------------------------
> Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
> With Perforce, you get hassle-free workflows. Merge that actually works.
> Faster operations. Version large binaries.  Built-in WAN optimization and the
> freedom to use Git, Perforce or both. Make the move to Perforce.
> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
>
>
> _______________________________________________
> gnome-schedule-users mailing list
> gno...@li...
> https://lists.sourceforge.net/lists/listinfo/gnome-schedule-users

Excerpts from Frank Cox's message of 2014-03-04 18:05:51 +0100:
> On Tue, 04 Mar 2014 08:34:28 +0100 Gaute Hope wrote:
>
> > Ok! I've pushed the change to git: bf76fd9, and it will be included
> > in the next release.
>
> Great, thanks!
>
> Here is an enhancement suggestion for sometime in the future:
>
> Would it be possible to add a "temporarily disable" option to the
> menu?  You can comment out a line in the crontab file and disable a
> job that way.  Perhaps with a note added to it that says "disabled" or
> something so as not to confuse it with a real remark that someone
> added to the crontab.  So a disabled job would look something like
> this:
>
> # 0 04 1-7 * 3 mail -s "Subject" frankcox@localhost >/dev/null 2>&1 #
> JOB_ID_8_DISABLED
>
> To re-enable it you would remove the # at the beginning of the line
> and the _DISABLED at the end of the line.
>
> Cron would ignore it, and you could show a _DISABLED line in the
> pending task window in a lighter colour, with the option on the menu
> to re-enable it.
>

Hi Frank,

Yeah, it would be a great feature, there is actually a (long-standing)
feature request for it already:

https://bugzilla.gnome.org/show_bug.cgi?id=571987

But I don't have time to implement it myself. Would be happy to accept
patches for it though!

Cheers, Gaute

On Tue, 04 Mar 2014 08:34:28 +0100
Gaute Hope wrote:

> Ok! I've pushed the change to git: bf76fd9, and it will be included in
> the next release.

Great, thanks!

Here is an enhancement suggestion for sometime in the future:

Would it be possible to add a "temporarily disable" option to the menu?  You can comment out a line in the crontab file and disable a job that way.  Perhaps with a note added to it that says "disabled" or something so as not to confuse it with a real remark that someone added to the crontab.  So a disabled job would look something like this:

# 0 04 1-7 * 3 mail -s "Subject" frankcox@localhost >/dev/null 2>&1 # JOB_ID_8_DISABLED

To re-enable it you would remove the # at the beginning of the line and the _DISABLED at the end of the line.

Cron would ignore it, and you could show a _DISABLED line in the pending task window in a lighter colour, with the option on the menu to re-enable it.

-- 
MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com

Excerpts from Frank Cox's message of 2014-03-04 08:20:51 +0100:
> On Tue, 04 Mar 2014 07:57:12 +0100 Gaute Hope wrote:
>
> > I don't think this is related to g-s, you could try turning off the
> > debug stuff:
> >
> > http://www.redhat.com/archives/rpm-list/2004-June/msg00007.html
> >
> > or check if any variables (e.g. BuildRoot) are missing:
> >
> > http://stackoverflow.com/questions/1879734/rpm-build-error
>
> I built gnome-schedule from the srpm the other day as I described
> earlier, and it worked fine.
>
> I just now tried rebuilding it again and it fails in exactly the same
> way.  Which is interesting since it did work fine a few days ago and
> nothing has changed that I'm aware of.
>
> At any rate, adding the %define debug_package %{nil} line to the spec
> file solved the problem and the rpm built fine.
>
> I installed it and the problem is now solved.  at commands show up
> just as expected.  So your changes are indeed the fix.
>

Ok! I've pushed the change to git: bf76fd9, and it will be included in
the next release.

Cheers, Gaute

On Tue, 04 Mar 2014 07:57:12 +0100
Gaute Hope wrote:

> I don't think this is related to g-s, you could try turning off the
> debug stuff:
> 
> http://www.redhat.com/archives/rpm-list/2004-June/msg00007.html
> 
> or check if any variables (e.g. BuildRoot) are missing:
> 
> http://stackoverflow.com/questions/1879734/rpm-build-error

I built gnome-schedule from the srpm the other day as I described earlier, and it worked fine.

I just now tried rebuilding it again and it fails in exactly the same way.  Which is interesting since it did work fine a few days ago and nothing has changed that I'm aware of.

At any rate, adding the %define debug_package %{nil} line to the spec file solved the problem and the rpm built fine.

I installed it and the problem is now solved.  at commands show up just as expected.  So your changes are indeed the fix.



-- 
MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com