Erro no empacotamento do svn

Ola!
Eu baixei o svn da versao 1.26 estavel a revision e 3408.
No momento em q vou empacotar o codigo para um pacote .deb
me deparei com o seguinte erro==>

dpkg-buildpackage: source version 1.26_unofficial
Undefined subroutine &Dpkg::Version::_g called at
/usr/share/perl5/Dpkg/Version.pm line 204.

Alguem pode me ajudar a resolver isso?

Grato
Ricardo

Ola!
Eu baixei o svn da versao 1.26 estavel a revision e 3408.
No momento em q vou empacotar o codigo para um pacote .deb
me deparei com o seguinte erro==>

dpkg-buildpackage: source version 1.26_unofficial
Undefined subroutine &Dpkg::Version::_g called at
/usr/share/perl5/Dpkg/Version.pm line 204.

Alguem pode me ajudar a resolver isso?

Grato
Ricardo

mailing lists problems

Hi there,

For some yet unknown reason, the mailing lists were down for at least
the first 20 days of August. Nobody complained privately, so I think
most of you were probably on holidays as well during this time.

All should be back online now.

Sorry for the inconvenience.

Jerome Alet

[ANNOUNCE] Official tarball for PyKota v1.26 + HotFixes

Hi there,

Exactly one year before today, PyKota v1.26 was published.

Today, I've (finally, some would say) put online a tarball containing
v1.26 + all the important fixes that were made during this year.

These fixes were backported from the 1.27 development tree, which
shouldn't be considered useable yet.

You can safely (well, I hope, but please do a backup first) install
this tarball on top of, or instead of, PyKota v1.26. You should not
install it on top of 1.27alpha_something since there are several
changes to the pykota.conf configuration file and to the code.

People with an entry pass can download it from :

  http://www.pykota.com/software/pykota/download/tarballs/pykota-1.26_fixes_official.tar.gz

People without an entry pass can either purchase one, or grab the same
code from the 1.26_fixes branch in subversion.

Hoping today won't be a brown paper bag day...

bye

Jerome Alet

Holidays

Hi there,

I'll be on holidays from tomorrow until sometimes around August 15th.

People who have a support contract can of course still use the
http://otrs.librelogiciel.com/otrs/customer.pl website during this
time period, since this is the only way I can be reached anywhere
anytime, and (usually) almost immediately.

For other people, please don't hesitate to ask questions to the
mailing lists anyway, since there are a lot of people who know
the software enough to be able to help you.

bye

Jerome Alet

Mailing lists follow-up

Hi there,

I've now put a gateway which will cause all messages
sent to these three old mailing lists addresses :

    pykota@...
    pykota-devel@...
    tea4cups@...

to be transparently forwarded to the new mailing lists addresses,
respectively :

    pykota@...
    pykota-devel@...
    tea4cups@...

You are encouraged to exclusively use the new addresses above from
now on, however this gateway will make the transition smoother.

The two other mailing lists won't have such a gateway, because they
are in readonly mode for you anyway.

bye

Jerome Alet

PING

Just to be sure all works fine again, please could someone answer
to this messages to the list ?

Thanks in advance

Jerome Alet

[ANNOUNCE] Mailing lists moved

Hi there,

As announced yesterday, the mailing lists were moved to the new
server and to the pykota.com domain.

The new adresses are :

  pykota@...
  pykota-devel@...
  tea4cups@...
  pykota-support@...
  pykota-techsupport@...

Of these five mailing list, only the three first ones can receive messages
from you. The two other ones are readonly and reserved for announces
to people with respectively an unlimited entry pass or a technical support
contract.

You can change your preferences or unsubscribe from :

  http://lists.pykota.com/mailman/listinfo/pykota
  http://lists.pykota.com/mailman/listinfo/pykota-devel
  http://lists.pykota.com/mailman/listinfo/tea4cups
  http://lists.pykota.com/mailman/listinfo/pykota-support
  http://lists.pykota.com/mailman/listinfo/pykota-techsupport

Feel free to use these lists, it should work.

Please report any problem ASAP.

[ANNOUNCE] Mailing lists maintainance

Hi there,

As previously announced a few weeks ago, all the @librelogiciel.com
printing related mailing lists will be moved to the pykota.com domain.

This move will happen later this evening, with full functionnality 
restored by tomorrow evening, if all goes as expected.

If you actually filter incoming mail, ensure your filter accept
mail coming from pykota.com.

As far as your existing subscriptions are concerned, you've got 
nothing to do because your mailing list accounts will be moved at 
the same time as the mailing list themselves. 

The http links to subcribe or unsubscribe from these lists will also
be moved, and will be inactivated during the move.

Once the move is done, you'll have to send messages to, for example,
pykota@..., instead of, for example, pykota@...
The old list addresses might still work but will be phased out eventually.

I ask you to NOT answer to this message. If you want to answer to it,
do so privately to : alet@...

Please restrain from sending any message to any of these mailing lists
until you receive a notice that you can do it. This in order to not
lose anything important in the archiving process.

Thanks for your comprehension and for being so patient with my slowness.

Re: pykota Digest, Vol 63, Issue 7

If you require a user to authenticate against a directory in order to  
view their print history, then you may be interested in PrintAgent : http://www.lucidsystems.org/printingworks/printagaent

> >
> >  I'm in the process of migrating our windows based printing  
> account system
> > to pykota. On the present system, each user can access his  
> printing reports,
> > and check how his balance was debited for his printings, or how it  
> was
> > increased by his deposits. You can find an example on the image in
> > attachment. Notice that for each printing the resulting balance is  
> shown,
> > which allows the user to easily understand why they deposited 100,  
> and the
> > balance was increased to 95 only.
>
> Actually the "printquota.cgi" CGI script can provide part of these
> informations. If you want more you can either use the dumpykota  
> command
> line tool or the dumpykota.cgi CGI script (this one is currently  
> broken
> in the latest development tree), but of course you won't be able
> to display data which is not already present in the database (see  
> below)
>
> >  Looking at the pykota database, it seems that there is no  
> information on
> > the resulting balance, at the time the job was printed. Is this  

duplex accounting

Hi Jerome,

Another feature that would be nice, would be the possibility of having
different prices for duplex printings. I know that most likely it would
always charge you for an even number of pages, because that's what the
printer actually counts. To go around this, you could compare the software
accounting with the hardware accounting, and charge by the lesser value.
From the logs, you are already doing this comparison:

Beware : computed job size (2) != precomputed job size (1)

I know it remains the fact of detecting that a job is duplex...

Anyway, it's just a suggestion, that I hope you consider introducing in the
next release 

Best regards,
Elio

user reports

Hello,

 I'm in the process of migrating our windows based printing account system
to pykota. On the present system, each user can access his printing reports,
and check how his balance was debited for his printings, or how it was
increased by his deposits. You can find an example on the image in
attachment. Notice that for each printing the resulting balance is shown,
which allows the user to easily understand why they deposited 100, and the
balance was increased to 95 only.

 Looking at the pykota database, it seems that there is no information on
the resulting balance, at the time the job was printed. Is this correct, or
am I missing something?

 I suppose I could do the math and trace back the balance, but I would have
more confidence that no one has fiddled with the database, if the balance
were to be recorded on each transaction.

 Would it be possible to record this information?

Best regards,
Elio Coutinho

Hello,

 I'm in the process of migrating our windows based printing account system
to pykota. On the present system, each user can access his printing reports,
and check how his balance was debited for his printings, or how it was
increased by his deposits. You can find an example on the image in