changing:
my_notify = notify_notification_new("New updates for Archlinux available!",output_string,NULL,NULL);
to:
my_notify = notify_notification_new("New updates for Archlinux available!",output_string,NULL);
fixes it.
Mektub
]]>/usr/bin/pacman -Sy > /dev/null
and this is slightly horrifying. Much safer is to use the following:
# Setup
mkdir -p /tmp/localsync
ln -s /var/lib/pacman/local /tmp/localsync &> /dev/null
# Call this regularly
fakeroot pacman -Syy --dbpath /tmp/localsync/ &> /dev/null
pacman -Qqu --dbpath /tmp/localsync/ | wc -l
Does not need root and does not risk serious breakage.
]]>==> Beginne build()...
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for stdbool.h that conforms to C99... yes
checking for _Bool... yes
checking for setuid... yes
checking for library containing notify_init... -lnotify
checking for pacman... ok
checking for gzip... ok
configure: creating ./config.status
config.status: creating Makefile
gcc -march=amdfam10 -O2 -pipe -Wall -DVERSION=\"@VERSION@\" `pkg-config --cflags --libs gtk+-2.0` archup.c -o archup -lnotify
gzip archup.1
archup.c: In Funktion »main«:
archup.c:201:3: Fehler: zu viele Argumente für Funktion »notify_notification_new«
/usr/include/libnotify/notification.h:114:21: Anmerkung: declared here
make: *** [archup-bin] Fehler 1
Breche ab ...
notification.h (v.7.1):
NotifyNotification *notify_notification_new (const char *summary,
const char *body,
const char *icon);
notification.h (v.5.2):
NotifyNotification *notify_notification_new (const char *summary,
const char *body,
const char *icon,
GtkWidget *attach);
In the program archup:
my_notify = notify_notification_new("New updates for Archlinux available!",output_string,NULL,NULL);
After the update to version 1.7.1 libnonify, archup an error archup: error while loading shared libraries: libnotify.so.1: cannot open shared object file: No such file or directory
I have archup scheduled via cron but I'm getting a cron email every time it runs with the following errors:
** (process:320): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion `!DBUS_G_PROXY_DESTROYED (proxy)' failed
** (process:320): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion `!DBUS_G_PROXY_DESTROYED (proxy)' failed
I have same the same thing.
]]>I know I should submit a patch or shut up, but I don't have libnotify to test it, so I hope this kind of feedback is okay:
1) manual option-parsing is nasty. why aren't you using getopt_long?
2)
char *output_string=malloc(23);
sprintf(output_string,"There are updates for:\n");
You allocate 23 bytes but you write 24. I know, 23 is the nicer number, but don't forget about the trailing null byte.
3)
if (got_updates == TRUE)
{
/* some code here */
free(output_string);
}
You allocate memory in any case, therefore you should free it in any case.
regards, rck
]]>You have to test /proc/acpi/battery/*/state
I think it could be great if you implement something like this. An option could be available for people who wants archup on battery.
]]>** (process:320): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion `!DBUS_G_PROXY_DESTROYED (proxy)' failed
** (process:320): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion `!DBUS_G_PROXY_DESTROYED (proxy)' failed
]]>@flamelab
Cool-patience is a virtue...
I will see what tomorrow brings.
have to activate the cron-daemon in rc.conf ;-)
]]>XAUTHORITY=$(/usr/bin/find /var/run/gdm -path "*${arch_user}*/database") DISPLAY=:0.0 /usr/bin/archup --uid $(id -u $arch_user)
Can archup be used with scrotwm?
Thanks.
I use Scrotwm with archup without any problem.
]]>