This fix is very important for Landscape. Landscape _will_not_work_
without it.
** Summary changed:
- landscape-client should have a cron job for updating smart package data
+ landscape-client must have a cron job for updating smart package data
--
landscape-client must have a cron job for upda
** Changed in: landscape-client (Ubuntu)
Status: New => In Progress
--
landscape-client must have a cron job for updating smart package data
https://bugs.launchpad.net/bugs/268765
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: landscape-client (Ubuntu)
Importance: Undecided => Critical
** Changed in: landscape-client (Ubuntu)
Target: None => ubuntu-8.10-beta
--
landscape-client must have a cron job for updating smart package data
https://bugs.launchpad.net/bugs/268765
You received this bug not
Hi Chris,
Given that landscape-client starts a daemon if enabled (/usr/bin
/landscape-client, launched from /etc/init.d/landscape-client), wouldn't
it be preferable to have landscape-client itself run this update
periodically, rather than having cron run it?
Alternatively, could you adjust this c
Would a daily cron job be possible ?
An hourly cron job would put unnecessary strain on the archive. Update-
notifier and the apt update cron job are run on daily basis.
--
landscape-client must have a cron job for updating smart package data
https://bugs.launchpad.net/bugs/268765
You received t
What about this for the cron job? It only runs if landscape-client is
enabled.
#!/bin/sh
[ -f "/etc/default/landscape-client" ] || exit 0
source /etc/default/landscape-client
[ "$RUN" -eq "1" ] && /usr/share/smart/smart update > /dev/null 2>&1
exit 0
--
landscape-client must have a cron job
This bug was fixed in the package landscape-client - 1.0.21-0ubuntu2
---
landscape-client (1.0.21-0ubuntu2) intrepid; urgency=low
* debian/rules: Install an hourly cron job to update smart package data.
Thanks to Christopher Armstrong (LP: #268765).
* debian/control:
- Mov
Erm, isn't a hourly cronjob a bit exaggerated? Mirrors only update
daily, and the already existing cronjob for apt runs once a day.
Also, why can't smart use the already existing downloaded apt cache?
Eventually it just gets the Packages.gz files, we don't provide any
other index. Why does it need
This hourly cronjob was debated yesterday on #ubuntu-devel. For now, we
are keeping it, specially because we changed it so it only runs when
landscape-client itself is running:
niemeyer: the concern is to put too much load on the servers and
mirrors
mathiaz: I agree that if you're managing a bu
This only required packaging change, not upstream change, so marking
Invalid for landscape-client upstream
** Changed in: landscape-client
Status: In Progress => Invalid
--
landscape-client must have a cron job for updating smart package data
https://bugs.launchpad.net/bugs/268765
You rec
This fix is very important for Landscape. Landscape _will_not_work_
without it.
** Summary changed:
- landscape-client should have a cron job for updating smart package data
+ landscape-client must have a cron job for updating smart package data
--
landscape-client must have a cron job for upda
** Changed in: landscape-client (Ubuntu)
Status: New => In Progress
--
landscape-client must have a cron job for updating smart package data
https://bugs.launchpad.net/bugs/268765
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: landscape-client (Ubuntu)
Importance: Undecided => Critical
** Changed in: landscape-client (Ubuntu)
Target: None => ubuntu-8.10-beta
--
landscape-client must have a cron job for updating smart package data
https://bugs.launchpad.net/bugs/268765
You received this bug not
Hi Chris,
Given that landscape-client starts a daemon if enabled (/usr/bin
/landscape-client, launched from /etc/init.d/landscape-client), wouldn't
it be preferable to have landscape-client itself run this update
periodically, rather than having cron run it?
Alternatively, could you adjust this c
Would a daily cron job be possible ?
An hourly cron job would put unnecessary strain on the archive. Update-
notifier and the apt update cron job are run on daily basis.
--
landscape-client must have a cron job for updating smart package data
https://bugs.launchpad.net/bugs/268765
You received t
What about this for the cron job? It only runs if landscape-client is
enabled.
#!/bin/sh
[ -f "/etc/default/landscape-client" ] || exit 0
source /etc/default/landscape-client
[ "$RUN" -eq "1" ] && /usr/share/smart/smart update > /dev/null 2>&1
exit 0
--
landscape-client must have a cron job
This bug was fixed in the package landscape-client - 1.0.21-0ubuntu2
---
landscape-client (1.0.21-0ubuntu2) intrepid; urgency=low
* debian/rules: Install an hourly cron job to update smart package data.
Thanks to Christopher Armstrong (LP: #268765).
* debian/control:
- Mov
Erm, isn't a hourly cronjob a bit exaggerated? Mirrors only update
daily, and the already existing cronjob for apt runs once a day.
Also, why can't smart use the already existing downloaded apt cache?
Eventually it just gets the Packages.gz files, we don't provide any
other index. Why does it need
This hourly cronjob was debated yesterday on #ubuntu-devel. For now, we
are keeping it, specially because we changed it so it only runs when
landscape-client itself is running:
niemeyer: the concern is to put too much load on the servers and
mirrors
mathiaz: I agree that if you're managing a bu
This only required packaging change, not upstream change, so marking
Invalid for landscape-client upstream
** Changed in: landscape-client
Status: In Progress => Invalid
--
landscape-client must have a cron job for updating smart package data
https://bugs.launchpad.net/bugs/268765
You rec
This fix is very important for Landscape. Landscape _will_not_work_
without it.
** Summary changed:
- landscape-client should have a cron job for updating smart package data
+ landscape-client must have a cron job for updating smart package data
--
landscape-client must have a cron job for upda
** Changed in: landscape-client (Ubuntu)
Status: New => In Progress
--
landscape-client must have a cron job for updating smart package data
https://bugs.launchpad.net/bugs/268765
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: landscape-client (Ubuntu)
Importance: Undecided => Critical
** Changed in: landscape-client (Ubuntu)
Target: None => ubuntu-8.10-beta
--
landscape-client must have a cron job for updating smart package data
https://bugs.launchpad.net/bugs/268765
You received this bug not
Hi Chris,
Given that landscape-client starts a daemon if enabled (/usr/bin
/landscape-client, launched from /etc/init.d/landscape-client), wouldn't
it be preferable to have landscape-client itself run this update
periodically, rather than having cron run it?
Alternatively, could you adjust this c
Would a daily cron job be possible ?
An hourly cron job would put unnecessary strain on the archive. Update-
notifier and the apt update cron job are run on daily basis.
--
landscape-client must have a cron job for updating smart package data
https://bugs.launchpad.net/bugs/268765
You received t
What about this for the cron job? It only runs if landscape-client is
enabled.
#!/bin/sh
[ -f "/etc/default/landscape-client" ] || exit 0
source /etc/default/landscape-client
[ "$RUN" -eq "1" ] && /usr/share/smart/smart update > /dev/null 2>&1
exit 0
--
landscape-client must have a cron job
This bug was fixed in the package landscape-client - 1.0.21-0ubuntu2
---
landscape-client (1.0.21-0ubuntu2) intrepid; urgency=low
* debian/rules: Install an hourly cron job to update smart package data.
Thanks to Christopher Armstrong (LP: #268765).
* debian/control:
- Mov
Erm, isn't a hourly cronjob a bit exaggerated? Mirrors only update
daily, and the already existing cronjob for apt runs once a day.
Also, why can't smart use the already existing downloaded apt cache?
Eventually it just gets the Packages.gz files, we don't provide any
other index. Why does it need
This hourly cronjob was debated yesterday on #ubuntu-devel. For now, we
are keeping it, specially because we changed it so it only runs when
landscape-client itself is running:
niemeyer: the concern is to put too much load on the servers and
mirrors
mathiaz: I agree that if you're managing a bu
This only required packaging change, not upstream change, so marking
Invalid for landscape-client upstream
** Changed in: landscape-client
Status: In Progress => Invalid
--
landscape-client must have a cron job for updating smart package data
https://bugs.launchpad.net/bugs/268765
You rec
This fix is very important for Landscape. Landscape _will_not_work_
without it.
** Summary changed:
- landscape-client should have a cron job for updating smart package data
+ landscape-client must have a cron job for updating smart package data
--
landscape-client must have a cron job for upda
** Changed in: landscape-client (Ubuntu)
Status: New => In Progress
--
landscape-client must have a cron job for updating smart package data
https://bugs.launchpad.net/bugs/268765
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: landscape-client (Ubuntu)
Importance: Undecided => Critical
** Changed in: landscape-client (Ubuntu)
Target: None => ubuntu-8.10-beta
--
landscape-client must have a cron job for updating smart package data
https://bugs.launchpad.net/bugs/268765
You received this bug not
Hi Chris,
Given that landscape-client starts a daemon if enabled (/usr/bin
/landscape-client, launched from /etc/init.d/landscape-client), wouldn't
it be preferable to have landscape-client itself run this update
periodically, rather than having cron run it?
Alternatively, could you adjust this c
Would a daily cron job be possible ?
An hourly cron job would put unnecessary strain on the archive. Update-
notifier and the apt update cron job are run on daily basis.
--
landscape-client must have a cron job for updating smart package data
https://bugs.launchpad.net/bugs/268765
You received t
This fix is very important for Landscape. Landscape _will_not_work_
without it.
** Summary changed:
- landscape-client should have a cron job for updating smart package data
+ landscape-client must have a cron job for updating smart package data
--
landscape-client must have a cron job for upda
** Changed in: landscape-client (Ubuntu)
Status: New => In Progress
--
landscape-client must have a cron job for updating smart package data
https://bugs.launchpad.net/bugs/268765
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: landscape-client (Ubuntu)
Importance: Undecided => Critical
** Changed in: landscape-client (Ubuntu)
Target: None => ubuntu-8.10-beta
--
landscape-client must have a cron job for updating smart package data
https://bugs.launchpad.net/bugs/268765
You received this bug not
Hi Chris,
Given that landscape-client starts a daemon if enabled (/usr/bin
/landscape-client, launched from /etc/init.d/landscape-client), wouldn't
it be preferable to have landscape-client itself run this update
periodically, rather than having cron run it?
Alternatively, could you adjust this c
Would a daily cron job be possible ?
An hourly cron job would put unnecessary strain on the archive. Update-
notifier and the apt update cron job are run on daily basis.
--
landscape-client must have a cron job for updating smart package data
https://bugs.launchpad.net/bugs/268765
You received t
What about this for the cron job? It only runs if landscape-client is
enabled.
#!/bin/sh
[ -f "/etc/default/landscape-client" ] || exit 0
source /etc/default/landscape-client
[ "$RUN" -eq "1" ] && /usr/share/smart/smart update > /dev/null 2>&1
exit 0
--
landscape-client must have a cron job
This bug was fixed in the package landscape-client - 1.0.21-0ubuntu2
---
landscape-client (1.0.21-0ubuntu2) intrepid; urgency=low
* debian/rules: Install an hourly cron job to update smart package data.
Thanks to Christopher Armstrong (LP: #268765).
* debian/control:
- Mov
Erm, isn't a hourly cronjob a bit exaggerated? Mirrors only update
daily, and the already existing cronjob for apt runs once a day.
Also, why can't smart use the already existing downloaded apt cache?
Eventually it just gets the Packages.gz files, we don't provide any
other index. Why does it need
This hourly cronjob was debated yesterday on #ubuntu-devel. For now, we
are keeping it, specially because we changed it so it only runs when
landscape-client itself is running:
niemeyer: the concern is to put too much load on the servers and
mirrors
mathiaz: I agree that if you're managing a bu
This only required packaging change, not upstream change, so marking
Invalid for landscape-client upstream
** Changed in: landscape-client
Status: In Progress => Invalid
--
landscape-client must have a cron job for updating smart package data
https://bugs.launchpad.net/bugs/268765
You rec
What about this for the cron job? It only runs if landscape-client is
enabled.
#!/bin/sh
[ -f "/etc/default/landscape-client" ] || exit 0
source /etc/default/landscape-client
[ "$RUN" -eq "1" ] && /usr/share/smart/smart update > /dev/null 2>&1
exit 0
--
landscape-client must have a cron job
This bug was fixed in the package landscape-client - 1.0.21-0ubuntu2
---
landscape-client (1.0.21-0ubuntu2) intrepid; urgency=low
* debian/rules: Install an hourly cron job to update smart package data.
Thanks to Christopher Armstrong (LP: #268765).
* debian/control:
- Mov
Erm, isn't a hourly cronjob a bit exaggerated? Mirrors only update
daily, and the already existing cronjob for apt runs once a day.
Also, why can't smart use the already existing downloaded apt cache?
Eventually it just gets the Packages.gz files, we don't provide any
other index. Why does it need
This hourly cronjob was debated yesterday on #ubuntu-devel. For now, we
are keeping it, specially because we changed it so it only runs when
landscape-client itself is running:
niemeyer: the concern is to put too much load on the servers and
mirrors
mathiaz: I agree that if you're managing a bu
This only required packaging change, not upstream change, so marking
Invalid for landscape-client upstream
** Changed in: landscape-client
Status: In Progress => Invalid
--
landscape-client must have a cron job for updating smart package data
https://bugs.launchpad.net/bugs/268765
You rec
This fix is very important for Landscape. Landscape _will_not_work_
without it.
** Summary changed:
- landscape-client should have a cron job for updating smart package data
+ landscape-client must have a cron job for updating smart package data
--
landscape-client must have a cron job for upda
** Changed in: landscape-client (Ubuntu)
Status: New => In Progress
--
landscape-client must have a cron job for updating smart package data
https://bugs.launchpad.net/bugs/268765
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: landscape-client (Ubuntu)
Importance: Undecided => Critical
** Changed in: landscape-client (Ubuntu)
Target: None => ubuntu-8.10-beta
--
landscape-client must have a cron job for updating smart package data
https://bugs.launchpad.net/bugs/268765
You received this bug not
Hi Chris,
Given that landscape-client starts a daemon if enabled (/usr/bin
/landscape-client, launched from /etc/init.d/landscape-client), wouldn't
it be preferable to have landscape-client itself run this update
periodically, rather than having cron run it?
Alternatively, could you adjust this c
Would a daily cron job be possible ?
An hourly cron job would put unnecessary strain on the archive. Update-
notifier and the apt update cron job are run on daily basis.
--
landscape-client must have a cron job for updating smart package data
https://bugs.launchpad.net/bugs/268765
You received t
What about this for the cron job? It only runs if landscape-client is
enabled.
#!/bin/sh
[ -f "/etc/default/landscape-client" ] || exit 0
source /etc/default/landscape-client
[ "$RUN" -eq "1" ] && /usr/share/smart/smart update > /dev/null 2>&1
exit 0
--
landscape-client must have a cron job
This bug was fixed in the package landscape-client - 1.0.21-0ubuntu2
---
landscape-client (1.0.21-0ubuntu2) intrepid; urgency=low
* debian/rules: Install an hourly cron job to update smart package data.
Thanks to Christopher Armstrong (LP: #268765).
* debian/control:
- Mov
Erm, isn't a hourly cronjob a bit exaggerated? Mirrors only update
daily, and the already existing cronjob for apt runs once a day.
Also, why can't smart use the already existing downloaded apt cache?
Eventually it just gets the Packages.gz files, we don't provide any
other index. Why does it need
This hourly cronjob was debated yesterday on #ubuntu-devel. For now, we
are keeping it, specially because we changed it so it only runs when
landscape-client itself is running:
niemeyer: the concern is to put too much load on the servers and
mirrors
mathiaz: I agree that if you're managing a bu
This only required packaging change, not upstream change, so marking
Invalid for landscape-client upstream
** Changed in: landscape-client
Status: In Progress => Invalid
--
landscape-client must have a cron job for updating smart package data
https://bugs.launchpad.net/bugs/268765
You rec
60 matches
Mail list logo
