Custom Query (22 matches)

As we add more features to Gutenbach, there are many things that need to be able to access the queue data -- client scripts, the gutenbach-queue package, and the web interface. It is better if this information is stored in a database somewhere, and is updated periodically, instead of polling CUPS every single time.

You can currently only cancel a single job at a time, or /all/ jobs, which is not always very desirable. If you try to use regexes it errors out:

jhamrick@blueberry-meringue:~/media/music/Sublime/40 oz. to Freedom$ gbrm sipbmp3 576[5-9] Argument "576[5-9]" isn't numeric in subroutine entry at /mit/gutenbach/arch/i386_deb50/perl/lib/perl5/Net/CUPS/Destination.pm line 1082. Argument "576[5-9]" isn't numeric in subroutine entry at /mit/gutenbach/arch/i386_deb50/perl/lib/perl5/Net/CUPS/Destination.pm line 1047. Use of uninitialized value $title in concatenation (.) or string at /mit/gutenbach/arch/i386_deb50/bin/gbrm.real line 68. Canceled job (id 576[5-9])

If you try multiple jobs, it only cancels the first one:

jhamrick@blueberry-meringue:~/media/music/Sublime/40 oz. to Freedom$ gbrm sipbmp3 5765 5766 Canceled job '40oz. To Freedom - Sublime - 40 oz. to Freedom' (id 5765)

There should be a default gutenbach queue for the clients, e.g.:

gbr *.mp3

Should print to whatever the default queue is (say, sipbmp3). If someone wants to use a different queue, they can specify it:

gbr -Ppikamp3 *.mp3

There should be a utility in gutenbach-client-config to specify what the default printer is, e.g.:

gutenbach-client-config -D sipbmp3