> Thanks - what's the best way on a *production* server to revert the patch
> and install the better fix?
I don't know if this is the best way, but the most basic way is
probably to grab the updated file from the git web interface:
http://git.koha-community.org/gitweb/
I navigated to the 3.6.4 b
At 02:01 PM 5/22/2012 -0400, Owen Leonard wrote:
[snip]
Judging from the description and the timeline of Koha 3.6.1 I'm
guessing the bug is caused by my first fix for Bug 6291 which was
subsequently reverted in favor of a better fix.
Thanks - what's the best way on a *production* server to reve
On 23 May 2012 09:07, Paul Poulain wrote:
> Hello,
>
> I just pushed a few minuts ago a patch with KOCT on the contrib repository
> (http://git.koha-community.org/gitweb/?p=contrib/global.git;a=summary)
>
Awesome! Thank you
Chris
___
Koha-devel mailing
Hello,
I just pushed a few minuts ago a patch with KOCT on the contrib repository
(http://git.koha-community.org/gitweb/?p=contrib/global.git;a=summary)
--
Paul POULAIN
http://www.biblibre.com
Expert en Logiciels Libres pour l'info-doc
Tel : (33) 4 91 81 35 08
___
> This is probably Koha bug 7199
Probably, in that your description matches exactly the PDF attached to
the bug ;)
However, I can't reproduce the problem in master so this may already
have been fixed. Tested in Firefox 12, Chrome 19, Opera 11, and IE 9
on Windows 7.
Judging from the description
Our cataloguers are having a local problem that I was unaware of. This is
probably Koha bug 7199 which appears to be a tad inactive; I'd be happy to
assist, but have no knowledge whatsoever of how browsers render
CSS|templates for printing.
Trying to "print page" after a staff screen listing s
For my part, I tend to review patches textual to see if they make sense as
a changeset. If I cannot tell from reading what this patch does, I'll
either apply and test, or ask for clarification. Generally, both of those
actions take more effort than reading on Bugzilla, and thus take longer.
I ag
Just a quick response on first glance: The numbers in this discussion are imo
far from accurate. As for me, I mostly QA without signing off, just to spare
time. In most cases I did apply and test (at least some functionality, in other
cases much more). I would not recommend doing QA in Bugzilla
Most academic libraries in the Arabian Gulf region (Saudi, Kuwait, Bahrain,
Qatar, UAE, Oman) always have bilingual catalogers, some do Arabic books
cataloging (Arabs mostly from Saudi and Egypt with near zero English
background) and some do English books cataloging (non-Arabs mostly from
India and
Hello,
I have asked a question about two years ago about when we can have Koha
support of Multi-Lingual SQL files (used for marc21/Auth fields description
in the Staff client) and Multi-Lingual users defined parameters (used for
describing items/ libraries & groups/ locations/ patrons categories/
* Paul Poulain (paul.poul...@biblibre.com) wrote:
> Le 21/05/2012 19:38, Chris Nighswonger a écrit :
> > http://wiki.koha-community.org/wiki/Bug-enhancement-patch_Workflow#Steps
> >
> > 1. I propose that we modify step 5 to read:
> >
> > "The patch is checked and signed-off by the QA team member.
Le 21/05/2012 19:38, Chris Nighswonger a écrit :
> http://wiki.koha-community.org/wiki/Bug-enhancement-patch_Workflow#Steps
>
> 1. I propose that we modify step 5 to read:
>
> "The patch is checked and signed-off by the QA team member. Then the bug
> status is set to Passed QA"
Something I made d
12 matches
Mail list logo
