Re: [OPEN-ILS-GENERAL] [OPEN-ILS-DEV] Evergreen Test Writing Day

[liam . whalen]

Because I scheduled the current Test Writing Day to take place on the  
same day as the Monthly Maintenance, I will postpone test writing day  
until next week.


Here is a Doodle poll to help choose the new date:

http://doodle.com/poll/6mbgkn22d29y25r3

I will add this new date to the Evergreen community calendar by the  
end of Friday this week.


Liam

Quoting Jason Stephenson :


Quoting Kathy Lussier :

Jason, do you think there will be much of a conflict with release  
day if we hold off on merging any of the tests until after  
tomorrow? The patches from the August test writing day weren't  
merged until last week, and, I don't see why it would be a problem  
waiting a few days to merge this batch.


For monthly releases, I doubt that it would be a huge deal. I don't
think the tests would normally get back ported to the release branches.

I just recall that 2.9.0 release day was a bit of a pain because people
kept pushing documentation commits after I had already started working
on the release.

I still think it would be a good idea to have test writing day or any
other day involving code or documentation to fall on days other than
release days.

It is tough enough to get releases together without the added
distractions.

(Particularly difficult for me since our release schedule seems to
fall on the day after my consortium's Executive and/or Membership
meetings, so I have a day full of meeting the day before the release.)

Cheers,
Jason
--
Jason Stephenson
Assistant Director for Technology Services
Merrimack Valley Library Consortium
4 High ST, Suite 175
North Andover, MA 01845
Phone: 978-557-5891
Email: jstephen...@mvlc.org

Re: [OPEN-ILS-GENERAL] [OPEN-ILS-DEV] Evergreen Test Writing Day

[liam . whalen]

I do not have a page on the Wiki yet describing test writing day.  I  
wrote a quick explanation during the first one.  I will summarize it  
on the Wiki.  Basically, we have a few pieces of code with the tag  
test-writing-day-# on it.  People assign themselves one of those bugs  
(or choose something they want to write a test for), and write a test  
case for it using PgTap or Perl depending on the code in question.


Liam

Quoting Jim Taylor :

Is there a link to a document somewhere that explains "Test Writing  
Day"?   What is the purpose, what happens, how does one get  
involved, etc.?   I assume the name is somewhat self-explanatory but  
the extended discussion here makes me think my first guess was  
wrong.  I browsed the top level of the web site but didn't see  
anything.


Thanks.

Jim

-Original Message-
From: Open-ils-general  
[mailto:open-ils-general-boun...@list.georgialibraries.org] On  
Behalf Of Kathy Lussier

Sent: Tuesday, November 17, 2015 11:47 AM
To: Evergreen Development Discussion List;  
open-ils-general@list.georgialibraries.org

Subject: Re: [OPEN-ILS-GENERAL] [OPEN-ILS-DEV] Evergreen Test Writing Day

Hi all,

Just to add some clarification on the dates, test-writing day is  
scheduled for today, November 17 and the point release is scheduled  
for tomorrow, November 18.


I clarified the dates in IRC earlier when I realized there was  
confusion on the dates, but I neglected to send a follow-up email to  
the lists.


Liam, I don't know how you want to proceed on re-scheduling or not,  
but I think it's fine to continue today.


Kathy

On 11/17/2015 12:30 PM, liam.wha...@bc.libraries.coop wrote:

Because I scheduled the current Test Writing Day to take place on the
same day as the Monthly Maintenance, I will postpone test writing day
until next week.

Here is a Doodle poll to help choose the new date:

http://doodle.com/poll/6mbgkn22d29y25r3

I will add this new date to the Evergreen community calendar by the
end of Friday this week.

Liam

Quoting Jason Stephenson :


Quoting Kathy Lussier :


Jason, do you think there will be much of a conflict with release
day if we hold off on merging any of the tests until after tomorrow?
The patches from the August test writing day weren't merged until
last week, and, I don't see why it would be a problem waiting a few
days to merge this batch.


For monthly releases, I doubt that it would be a huge deal. I don't
think the tests would normally get back ported to the release branches.

I just recall that 2.9.0 release day was a bit of a pain because
people kept pushing documentation commits after I had already started
working on the release.

I still think it would be a good idea to have test writing day or any
other day involving code or documentation to fall on days other than
release days.

It is tough enough to get releases together without the added
distractions.

(Particularly difficult for me since our release schedule seems to
fall on the day after my consortium's Executive and/or Membership
meetings, so I have a day full of meeting the day before the
release.)

Cheers,
Jason
--
Jason Stephenson
Assistant Director for Technology Services Merrimack Valley Library
Consortium
4 High ST, Suite 175
North Andover, MA 01845
Phone: 978-557-5891
Email: jstephen...@mvlc.org






--
Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128
kluss...@masslnc.org
Twitter: http://www.twitter.com/kmlussier

Re: [OPEN-ILS-GENERAL] [OPEN-ILS-DEV] Evergreen Test Writing Day

[liam . whalen]

Here is quick blurb on the Wiki with a couple of links for more  
reading if you are interested.


http://wiki.evergreen-ils.org/doku.php?id=dev:test_writing_day

Liam

uoting Jim Taylor :

Is there a link to a document somewhere that explains "Test Writing  
Day"?   What is the purpose, what happens, how does one get  
involved, etc.?   I assume the name is somewhat self-explanatory but  
the extended discussion here makes me think my first guess was  
wrong.  I browsed the top level of the web site but didn't see  
anything.


Thanks.

Jim

-Original Message-
From: Open-ils-general  
[mailto:open-ils-general-boun...@list.georgialibraries.org] On  
Behalf Of Kathy Lussier

Sent: Tuesday, November 17, 2015 11:47 AM
To: Evergreen Development Discussion List;  
open-ils-general@list.georgialibraries.org

Subject: Re: [OPEN-ILS-GENERAL] [OPEN-ILS-DEV] Evergreen Test Writing Day

Hi all,

Just to add some clarification on the dates, test-writing day is  
scheduled for today, November 17 and the point release is scheduled  
for tomorrow, November 18.


I clarified the dates in IRC earlier when I realized there was  
confusion on the dates, but I neglected to send a follow-up email to  
the lists.


Liam, I don't know how you want to proceed on re-scheduling or not,  
but I think it's fine to continue today.


Kathy

On 11/17/2015 12:30 PM, liam.wha...@bc.libraries.coop wrote:

Because I scheduled the current Test Writing Day to take place on the
same day as the Monthly Maintenance, I will postpone test writing day
until next week.

Here is a Doodle poll to help choose the new date:

http://doodle.com/poll/6mbgkn22d29y25r3

I will add this new date to the Evergreen community calendar by the
end of Friday this week.

Liam

Quoting Jason Stephenson :


Quoting Kathy Lussier :


Jason, do you think there will be much of a conflict with release
day if we hold off on merging any of the tests until after tomorrow?
The patches from the August test writing day weren't merged until
last week, and, I don't see why it would be a problem waiting a few
days to merge this batch.


For monthly releases, I doubt that it would be a huge deal. I don't
think the tests would normally get back ported to the release branches.

I just recall that 2.9.0 release day was a bit of a pain because
people kept pushing documentation commits after I had already started
working on the release.

I still think it would be a good idea to have test writing day or any
other day involving code or documentation to fall on days other than
release days.

It is tough enough to get releases together without the added
distractions.

(Particularly difficult for me since our release schedule seems to
fall on the day after my consortium's Executive and/or Membership
meetings, so I have a day full of meeting the day before the
release.)

Cheers,
Jason
--
Jason Stephenson
Assistant Director for Technology Services Merrimack Valley Library
Consortium
4 High ST, Suite 175
North Andover, MA 01845
Phone: 978-557-5891
Email: jstephen...@mvlc.org






--
Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128
kluss...@masslnc.org
Twitter: http://www.twitter.com/kmlussier

[OPEN-ILS-GENERAL] Evergreen Test Writing Day

[liam . whalen]

Tomorrow is the second evergreen test writing day. It begins at 1:00  
pm EST and goes to 3:00 pm EST (10:00 am PST - 12:00 pm PST).


I have removed the test-writing-day-0 tag from LP bugs. When those  
bugs had no fixes committed for them, I added test-writing-day-1 to  
the bug.  So, search for test-writing-day-1 on launchpad and assign  
yourself to a test writing bug or two.  See you online tomorrow!


Liam

[OPEN-ILS-GENERAL] Evergreen Test Writing Day 2

[liam . whalen]

I am scheduling the next Evergreen Test Writing Day for Friday,  
November 20th from 1:00 PM to 3:00 PM EST, 10:00 PM to 12:00 PM PST.


I will create some launchpad tickets for tests to write.  There are  
some remaining from the previous Test Writing Day, so I will add to  
those.  Feel free to add your own.  Please tag items for this event  
with the test-writing-day-1 tag. Alternatively, there is a tag  
needstest that exists.  Feel free to use that, and I will add the  
test-writing-day-1 tag to it before the 20th.


Liam

[OPEN-ILS-GENERAL] Test Writing Day Moved

[liam . whalen]

As I sent the email scheduling the test writing day, I had another  
participant in the poll.  The day that now works for all poll  
participants is Tuesday, November 17th from 1:00 PM to 3:00 PM EST  
(10:00 AM to 12:00 PM PST).  So, I am moving test writing day to the  
17th.


Liam

[OPEN-ILS-GENERAL] Evergreen Test Writing Day

[Liam Whalen]

I am planning to facilitate a test writing day in August.  If you are 
interested in writing tests for Evergreen code, please fill out the following 
poll.

http://doodle.com/npuignp2499uthf7 http://doodle.com/npuignp2499uthf7

I would like to focus on PgTap tests to start.

Liam Whalen
BC Libraries Cooperative - Sitka
Systems Specialist
855-383-5761 x1022
liam.wha...@bc.libraries.coop

Re: [OPEN-ILS-GENERAL] presentations

[Liam Whalen]

Metadata and Maps

http://git.sitka.bclibraries.ca/gitweb/?p=sitka/opendata-eg2015.git;a=summary 
http://git.sitka.bclibraries.ca/gitweb/?p=sitka/opendata-eg2015.git;a=summary

Liam Whalen
BC Libraries Cooperative - Sitka
Systems Specialist
855-383-5761 x1022
liam.wha...@bc.libraries.coop

 On May 15, 2015, at 4:23 PM, Rogan Hamby rogan.ha...@yclibrary.net wrote:
 
 In the interest of sharing presentations (that weren't done before the 
 conference):
 
 http://www.slideshare.net/roganhamby/welcome-to-the-community 
 http://www.slideshare.net/roganhamby/welcome-to-the-community
 
 and
 
 http://www.slideshare.net/roganhamby/adding-data-sources-to-the-reporter 
 http://www.slideshare.net/roganhamby/adding-data-sources-to-the-reporter
 
 There were quite a few from other folks that I wasn't able to attend so I 
 hope everyone sends out their presentations!
 
 -- 
 
 Rogan Hamby, MLS, CCNP, MIA
 Managers Headquarters Library and Reference Services, 
 York County Library System
 
 “You can never get a cup of tea large enough or a book long enough to suit 
 me.” 
 ― C.S. Lewis http://www.goodreads.com/author/show/1069006.C_S_Lewis

Re: [OPEN-ILS-GENERAL] srfsh% login USER PASSWORD wont authenticate

[Liam Whalen]

Hi Howard,

Try restarting everything.  Shutdown EG and OpenSRF, stop apache, then look for 
processes that are lying around.

ps aux | grep opensrf

Kill anything that is OpenSRF related.

Then restart OpenSRF/EG and finally restart apache.

Let me know if you get any errors.

Liam

 On Mar 6, 2015, at 6:17 PM, Howard Canning hcann...@bluehills.org wrote:
 
 Not having luck with installing Evergreen ILS. Attempted at least 5 long 
 comprehensive times with ubuntu 14.04 and 12.04.
 With Ubuntu 12.04 just now
 cp Open-ILS/examples/apache/eg.conf   /etc/apache2/sites-available/
 cp Open-ILS/examples/apache/eg_vhost.conf /etc/apache2/
 cp Open-ILS/examples/apache/eg_startup/etc/apache2/
 
 actually had in appended to the ends in their directories...so:
 cp Open-ILS/examples/apache/eg.conf.in http://conf.in/   
 /etc/apache2/sites-available/
 cp Open-ILS/examples/apache/eg_vhost.conf.in http://conf.in/ /etc/apache2/
 cp Open-ILS/examples/apache/eg_startup.in http://eg_startup.in/
 /etc/apache2/
 
 and errors like:
 
 ossible unintended interpolation of @sysconfdir in string at 
 Open-ILS/src/support-scripts/eg_db_config line 329.
 Possible unintended interpolation of @sysconfdir in string at 
 Open-ILS/src/support-scripts/eg_db_config line 329.
 Global symbol @sysconfdir requires explicit package name at 
 Open-ILS/src/support-scripts/eg_db_config line 329.
 Global symbol @sysconfdir requires explicit package name at 
 Open-ILS/src/support-scripts/eg_db_config line 329.
 Execution of Open-ILS/src/support-scripts/eg_db_config aborted due to 
 compilation errors.
 
 
 
 Is there a version of OpenSRF, Evergreen, Ubuntu and client that install 
 cleanly with a tutorial to go with.
 I just keep getting errors thrown despite being methodical. Apache restart 
 issues, services not running like  open-ils.auth, apparent data corruption
 My luck is out. Would love to see this working.
 
 Thanks
 
 
 On Fri, Mar 6, 2015 at 6:55 PM, Howard Canning hcann...@bluehills.org 
 mailto:hcann...@bluehills.org wrote:
 Thanks Jason. You were right. Now how do I get it running? :)
 
 opensrf@li904-206:~$ osrf_control --localhost --diagnostic
 * open-ils.acq [22293] uptime=03:34   cputime=00:00:00
 #drones=1
 * open-ils.actor   [22341] uptime=03:33   cputime=00:00:00
 #drones=1
 * open-ils.authis not running
 * open-ils.auth_proxy  [22349] uptime=03:33   cputime=00:00:00
 #drones=1
 * open-ils.booking [22301] uptime=03:33   cputime=00:00:00
 #drones=1
 * open-ils.cat http://open-ils.cat/ [22309] uptime=03:34   
 cputime=00:00:00#drones=1
 * open-ils.circ[22333] uptime=03:34   cputime=00:00:00
 #drones=1
 * open-ils.collections [22381] uptime=03:32   cputime=00:00:00
 #drones=1
 * open-ils.cstore  is not running
 * open-ils.fielder [22421] uptime=03:30   cputime=00:00:00
 #drones=5
 * open-ils.justintime  [22373] uptime=03:33   cputime=00:00:00
 #drones=1
 * open-ils.pcrud   is not running
 * open-ils.penalty [22365] uptime=03:33   cputime=00:00:00
 #drones=1
 * open-ils.permacrud   [22397] uptime=03:32   cputime=00:00:00
 #drones=5
 * open-ils.reporter[22389] uptime=03:32   cputime=00:00:00
 #drones=1
 * open-ils.reporter-store  is not running
 * open-ils.search  [22325] uptime=03:34   cputime=00:00:00
 #drones=1
 * open-ils.serial  [22437] uptime=03:29   cputime=00:00:00
 #drones=5
 *   ERR open-ils.storage Has PID file entry [22357], which matches no 
 running open-ils.storage processes
 * open-ils.supercat[22317] uptime=03:34   cputime=00:00:00
 #drones=1
 * open-ils.trigger [22405] uptime=03:31   cputime=00:00:00
 #drones=1
 * open-ils.url_verify  [22413] uptime=03:32   cputime=00:00:00
 #drones=1
 * open-ils.vandelay[22429] uptime=03:31   cputime=00:00:00
 #drones=1
 * opensrf.dbmath   [1242] uptime=01:20:13cputime=00:00:00
 #drones=5
 * opensrf.math [1222] uptime=01:20:14cputime=00:00:00
 #drones=5
 * opensrf.persist  [1195] uptime=01:20:14cputime=00:00:00
 #drones=5
 *   ERR opensrf.persist [1195] NOT configured for this host.
 * opensrf.settings [1187] uptime=01:20:14cputime=00:00:00
 #drones=5
 * opensrf.validator[1206] uptime=01:20:14cputime=00:00:00
 #drones=5
 *   ERR opensrf.validator [1206] NOT configured for this host.
 * router   [1179] uptime=01:20:16cputime=00:00:00
 * router   [1180] uptime=01:20:16cputime=00:00:00
 
 
 On Fri, Mar 6, 2015 at 2:04 PM, Jason Stephenson jstephen...@mvlc.org 
 mailto:jstephen...@mvlc.org wrote:
 Run osrf_control --localhost --diagnostic that will tell you what services 
 are running.
 
 Chances are, 

Re: [OPEN-ILS-GENERAL] Bug Squashing Day

[liam . whalen]

I am going to participate.

Liam

Quoting Kathy Lussier kluss...@masslnc.org:


Hi all,

Ack!

I closed the Doodle poll last month and set this Monday, March 2 as  
the date for our next Bug Squashing Day.  However, it looks like I  
failed to communicate the date with the rest of the community beyond  
adding it to the community calendar.


I would still like to see if we can get a group together to work on  
bugs on March 2. Does that day still work for everyone who responded  
to the poll?


Thanks and apologies for the oversight! I'm blaming it on the snow.

Kathy



On 01/21/2015 02:44 PM, Kathy Lussier wrote:
My apologies. The link for the Bug Squashing scheduling poll should  
be http://doodle.com/umc27afh7akqczft.


That's what I get for working on two Doodle polls at the same time.

Kathy

On 01/21/2015 02:35 PM, Kathy Lussier wrote:

Hi all,

I'm sending out a reminder to let us know what your availability  
is to participate in our next community Bug Squashing Day.  
http://doodle.com/xwu55tseci3mf34e


I'll be closing the Doodle poll at the end of the day tomorrow.

Kathy
On 01/16/2015 11:56 AM, Kathy Lussier wrote:

Hi all,

It's hard to believe, but it's already time to schedule another  
Bug Squashing Day. We're scheduling the next Bug Squashing Day to  
fall after the 2.8 beta release, but before the RC1 release. The  
closer we can schedule it to the beta release, the better.


Please let us know when you're available!
http://doodle.com/umc27afh7akqczft

Kathy







--
Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128
kluss...@masslnc.org
Twitter: http://www.twitter.com/kmlussier

Re: [OPEN-ILS-GENERAL] Web Client (Sprint 1) demo server

[Liam Whalen]

Hi Grace and Bill,

Thank you for hosting the demo server.  I had a chance to take a look at it 
tonight, and it looks very good.  Thank you Bill for your hard work.

I have found a few issues which I detail below.

When I was testing, I noticed that the results from a patron search or a record 
bucket can sometimes result in a blank table with enough rows for relevant 
entries but no data in those rows.

I was able to reproduce this, but only in Firefox on OSX and Ubuntu 12.04.  I 
could never reproduce this in Chrome.

Firefox was up to date on both machines.  I tried to duplicate this on Firefox 
on a Windows VM, but I was unable to login.  I include the Windows' Firefox 
error at the end of this email.

I was able to reliably reproduce the empty table errors in Firefox on both OS X 
and Ubuntu 12.04.

To get this problem to appear follow these steps.

Log in to the web based staff client.

Search for a patron using the  term ‘test’.

Click on the number beside the first result, which should be circadmin.

Click on each tab, in left to right order, of the Patron interface.  On the 
last tab ‘Other’, choose ‘Group Member Details’.

Next, click on Cataloging - Record Buckets.

Click the Bucket button and choose ESI Bucket.

Click Cataloging - Search the Catalog.

Search for ‘music’

Click the ‘Trunk Music’ result.

From here click the browser’s back button until you get to the splash page.  
Then click the forward button until you get to the end of history.

Keep repeating this back and forth through the history until you notice the 
results for the ESI Bucket no longer populating.

On the next time you return to the start of the history, go forward to the 
patron search and search for ‘test’.  If the results populate keep moving back 
and forth.  Eventually, searching for test will no longer retrieve results.  At 
this point if you click  Seach - Search for Patrons, then the Patron Search 
will no longer populate results.  This usually occurred for me during my 3rd or 
4th time through the browser’s history.

This seems like a contrived example, but I did not run into the problem the 
first time by following these steps.  It happened in the course of using the 
system.  I tested for a while before I could find a way to reliably reproduce 
it.

Even though this process seems contrived, it is possible that libraries would 
trigger whatever is going on here in the course of a day using a circ desk 
computer.

Also, if I close my Firefox browser while logged in, the next time I open the 
browser and return to the base URL for the staff client, the Angular app is 
still in the logged in state.

On a different note, our Sitka sysadmin has a request for the browser base 
staff client to help for testing invalid or non-functioning logins.  Can the 
workstation ID be passed to the login code via an URL variable along with the 
username and password?  This would allow us to identify specific machines in 
logs when libraries are having trouble logging in.

I am getting the following error when I try to login via Firefox on the Windows 
VM:

webby.evergreencatalog.com:7682 uses an invalid security certificate.

The certificate is not trusted because no issuer chain was provided.

(Error code: sec_error_unknown_issuer)

Firefox can't establish a connection to the server at 
wss://webby.evergreencatalog.com:7682/osrf-websocket-translator. 
evergreen-staff-client.0.0.1.min.js:9
Error: WebSocket Error [object Event] : undefined 
evergreen-staff-client.0.0.1.min.js:9
closing websocket evergreen-staff-client.0.0.1.min.js:9
Synchronous XMLHttpRequest on the main thread is deprecated because of its 
detrimental effects to the end user's experience. For more help 
http://xhr.spec.whatwg.org/ exceptionDialog.js:136
www.evergreencatalog.com:443 uses an invalid security certificate.

The certificate is only valid for the following names:
  *.esilibrary.com, esilibrary.com  

(Error code: ssl_error_bad_cert_domain)

Attempted to connect to a site with a bad certificate in the add exception 
dialog. This results in a (mostly harmless) exception being thrown. Logged for 
information purposes only: [Exception... Failure  nsresult: 0x80004005 
(NS_ERROR_FAILURE)  location: JS frame :: 
chrome://pippki/content/exceptionDialog.js :: checkCert :: line 138  data: no] 
exceptionDialog.js:146
webby.evergreencatalog.com:443 uses an invalid security certificate.

The certificate is not trusted because no issuer chain was provided.

(Error code: sec_error_unknown_issuer)

Attempted to connect to a site with a bad certificate in the add exception 
dialog. This results in a (mostly harmless) exception being thrown. Logged for 
information purposes only: [Exception... Failure  nsresult: 0x80004005 
(NS_ERROR_FAILURE)  location: JS frame :: 
chrome://pippki/content/exceptionDialog.js :: checkCert :: line 138  data: no]

I can login via Google Chrome on the Windows VM, so it is probably not related 
to the VM.

Liam Whalen
BC Libraries

Re: [OPEN-ILS-GENERAL] Sharing tips, scripts, etc., from Interest Groups

[Liam Whalen]

Here is a quick run through on how to look at circs with due dates in the 
future:

http://www.portents.ca/eg_reports/now_query.html

I mentioned in the Reports Interest Group meeting that a report could use 
PostgreSQL's 'interval' operator, 
http://www.postgresql.org/docs/9.1/static/functions-datetime.html, but I have 
not been able to make that work tonight.

Liam

On Mar 24, 2014, at 2:23 PM, Elizabeth Thomsen e...@noblenet.org wrote:

 If you attended one of the Interest Group sessions at the Evergreen
 Conference, you know that there was a lot of rapid-fire sharing going on. 
 Someone would mention a problem, and someone else would say they had
 developed a workaround, modification, procedure or script to address the
 issue.  The Interest Group leaders will be posting their notes, but if you
 were one of the people who said you had something you were willing to
 share, it would be great if you sent a message to the list with a brief
 description of what the problem is and how you handle it.  A link would be
 great if your code or documentation is posted somewhere, but just saying
 contact me if you're interested would work just fine, too.  This should
 help others who weren't at the conference, too!
 
 And of course this also applies to tips that were shared in other
 sessions, in the halls, at the reception, etc.  Great conference,
 everyone!
 
 -- 
 Elizabeth Thomsen, Member Services Manager
 NOBLE: North of Boston Library Exchange
 26 Cherry Hill Drive
 Danvers Massachusetts 01923
 E-mail: e...@noblenet.org
 
 
 

Re: [OPEN-ILS-GENERAL] Push Time for 2.6 RC1 [RM2.6]

[Liam Whalen]

Hi Dan,

The following three bugs are important for Sitka because they require Staff 
Client modifications.  If they can make it into the rc1 release, then we will 
not have to push new staff clients to our libraries after our 2.6 upgrade.

These two have pull requests:

https://bugs.launchpad.net/evergreen/+bug/1282286

https://bugs.launchpad.net/evergreen/+bug/1282277

I am waiting to here from support on my fix for this issue.  I am pushing to 
get an answer before noon today.  I will integrate the changes into master 
either way today, so they will be there by tomorrow morning.

https://bugs.launchpad.net/evergreen/+bug/1282301

I will take a look at some of the blockers today.

Liam


On Mar 10, 2014, at 7:54 AM, Dan Wells d...@calvin.edu wrote:

 Hello all,
  
 Friday was the last day to assign bugs to RC1, and now it’s time for what we 
 hope will be the last big push for getting 2.6 polished up and out the door.  
 The goal is to have things squared up by end-of-day on Wednesday, March 12, 
 as that should give us plenty of time to get things packaged up before the 
 big event next week.
  
 The current blockers are, naturally, top priority.  You can see those here:
  
 https://bugs.launchpad.net/evergreen/+bugs?field.tag=2.6-rc-blocker
  
 Every branch there (so far) has a pullrequest, so it comes down to testing.  
 While the fixes for some of these are not particularly complex, they do tend 
 to be fairly deep, so we want as much testing and feedback as we can get.  
 This applies especially to the Postgresql bugs, since we need to verify 
 things still work across multiple known version differences.
  
 I will take some time today to scan through the other targeted bugs and see 
 if anything else seems like a blocker.  Please feel free to weigh in on this 
 matter if there is a bug report you feel strongly about.  You can see the 
 list of 2.6-RC bugs with pullrequests here:
  
 https://bugs.launchpad.net/evergreen/+bugs?field.status%3Alist=NEWfield.status%3Alist=CONFIRMEDfield.status%3Alist=TRIAGEDfield.status%3Alist=INPROGRESSfield.status%3Alist=INCOMPLETE_WITH_RESPONSEfield.status%3Alist=INCOMPLETE_WITHOUT_RESPONSEassignee_option=anyfield.milestone%3Alist=64164field.tag=pullrequestfield.tags_combinator=ANYsearch=Searchorderby=-importancestart=0
  
 Thanks for your help!
  
 Sincerely,
 Dan
  
  
 Daniel Wells
 Library Programmer/Analyst
 Hekman Library, Calvin College
 616.526.7133

Re: [OPEN-ILS-GENERAL] 2.6 RC Schedule [RM2.6]

[Liam Whalen]

I would like to have these included in rc1.

I have them working in Sitka's code base. I will move them into Master this 
week.

https://bugs.launchpad.net/evergreen/+bug/1282277

https://bugs.launchpad.net/evergreen/+bug/1282286

https://bugs.launchpad.net/evergreen/+bug/1282301

Liam Whalen
BC Libraries Cooperative - Sitka
Systems Specialist
855-383-5761 x1022
liam.wha...@bc.libraries.coop




On Mar 3, 2014, at 9:29 AM, Dan Wells d...@calvin.edu wrote:

 Hello all,
  
 I am working on a separate wrap up email for the 2.6 beta which was cut last 
 Tuesday, but since time is mercilessly marching on, I decided I should 
 highlight the planned schedule for the 2.6 RC which is nearly upon us.  This 
 Friday, March 7, is the last day for targeting medium and lower bugs for 
 inclusion in the release candidate (high and critical bugs are always 
 welcome).  You can see the current list here:
  
 https://launchpad.net/evergreen/+milestone/2.6.0-rc1
  
 The list is already pretty extensive, so I am hoping we won’t find too much 
 to add.  That said, the current list of blockers for the RC is rather short:
  
 https://bugs.launchpad.net/evergreen/+bugs?field.tag=2.6-rc-blocker
  
 The list currently stands at four items, three of which are problems related 
 to newer versions of PostgreSQL.  Those three bugs are going to require a 
 fair amount of testing and eyes, so please contribute in any way you can!  
 Also, please let me know if there is another bug you feel should be added to 
 the list of blockers.
  
 I am setting a goal of Wednesday, March 12, as the last day to commit 
 branches for inclusion in the RC.  I know this is a fairly aggressive 
 timeline, but it is important that we accomplish as much as we can before 
 turn our collective attention toward the conference the following week.
  
 As always, please let me know if you have any questions or concerns about the 
 release process.
  
 Thanks,
 Dan
  
  
 Daniel Wells
 Library Programmer/Analyst
 Hekman Library, Calvin College
 616.526.7133

Re: [OPEN-ILS-GENERAL] Reminder: Deadline is TODAY for 2.6 alpha targeting [RM2.6]

[Liam Whalen]

Hi Dan,

I have a few improvements to the staff client that I am still testing 
internally, but I plan to push them into 2.6 at some point.  Would it be best 
to create launchpad bugs for them now?

Liam Whalen
BC Libraries Cooperative - Sitka
Systems Specialist
855-383-5761 x1022
liam.wha...@bc.libraries.coop




On Jan 16, 2014, at 9:31 AM, Dan Wells d...@calvin.edu wrote:

 Hello all,
  
 Just a quick reminder that today is the last day to target bugs for inclusion 
 in 2.6 alpha.  As in past releases, new features will still be permitted 
 until beta, which is scheduled for early February.  That said, the sooner 
 something is ready and targeted, the more likely it will be reviewed and 
 included in 2.6, so please don’t miss this opportunity to get some attention 
 for your branch.
  
 Here is the current list of bug reports in the 2.6.0-alpha1 milestone which 
 also have pullrequest tags:
 https://bugs.launchpad.net/evergreen/+bugs?field.status%3Alist=NEWfield.status%3Alist=CONFIRMEDfield.status%3Alist=TRIAGEDfield.status%3Alist=INPROGRESSfield.status%3Alist=INCOMPLETE_WITH_RESPONSEfield.status%3Alist=INCOMPLETE_WITHOUT_RESPONSEassignee_option=anyfield.milestone%3Alist=62053field.tag=pullrequestfield.tags_combinator=ANYsearch=Searchorderby=idstart=0
  
 This is the list which I am asking reviewers focus on over the next few days, 
 but as you can see, the list is relatively small.  In contrast, here is a 
 list of *all* un-committed pullrequests:
 https://bugs.launchpad.net/evergreen/+bugs?field.status%3Alist=NEWfield.status%3Alist=CONFIRMEDfield.status%3Alist=TRIAGEDfield.status%3Alist=INPROGRESSfield.status%3Alist=INCOMPLETE_WITH_RESPONSEfield.status%3Alist=INCOMPLETE_WITHOUT_RESPONSEassignee_option=anyfield.tag=pullrequestfield.tags_combinator=ANYsearch=Searchorderby=-milestonememo=75start=0direction=backwards
  
 I couldn’t figure out a way to exclude the items already targeted at 2.6 (the 
 first list), but I was able to sort them to the bottom.  As you can see, we 
 (at the time of this writing) have 70+ pullrequests which are either targeted 
 only at old branches or not targeted at all.  Many of these are stale and 
 should probably be invalidated, but many others should rightly be targeted at 
 2.6.  If you are able, please take some time today to review the second list, 
 and apply the 2.6.0-alpha1 milestone (or invalidate) as you deem appropriate.
  
 As always, please reply to this thread if you have any questions or concerns.
  
 Thank you,
 Dan
  
  
  
 Daniel Wells
 Library Programmer/Analyst
 Hekman Library, Calvin College
 616.526.7133

Re: [OPEN-ILS-GENERAL] Building a 2.4 Mac Client

[Liam Whalen]

http://www.portents.ca/eg/staff_clients/Evergreen%202.4.2%20Staff%20Client.dmg

Here is a URL that works.

Liam



On Jan 9, 2014, at 11:57 AM, Suzanne Paterno pate...@noblenet.org wrote:

 We recently updated our system from 2.3.7 to 2.4.4. Although I had no trouble 
 with any of our 2.3 releases, I am running into some difficulties creating a 
 Mac client for 2.4.4.  Specifically I receive the attached pop up about field 
 mapper.AutoIDL when I try to log into the client. 
 
 Screen Shot 2014-01-09 at 12.51.22 PM.png
 
 PC versions of the client work on our system so it does not seem as though it 
 is a server problem. The directory structure and files match the instructions 
 at 
 http://evergreen-ils.org/dokuwiki/doku.php?id=mozilla-devel:building_the_staff_client.
   I have tried building the directory(app) from scratch as well as starting 
 with the previous working client then overlaying the new files. I am not sure 
 what else to try. Any ideas? 
 
 Has anyone experienced anything similar when building a Mac Client? How was 
 the problem resolved? Anyone have a 2.4.4 Mac client they’s be willing to 
 share?
 
 Thank you, 
 Suzanne 
 
 --
 Suzanne Paterno
 Systems Support Specialist
 North of Boston Library Exchange
 Danvers, Massachusetts
 pate...@noblenet.org
 www.noblenet.org

Re: [OPEN-ILS-GENERAL] Building a 2.4 Mac Client

[Liam Whalen]

I am not certain where I got the files from.  They most likely came from a 
linux 64 bit build because I was not responsible for the Windows client.  But, 
I am not sure anymore.

Liam

On Jan 9, 2014, at 12:17 PM, Ben Shum bs...@biblio.org wrote:

 One thing I'd be sure to check is that you're grabbing the build files from 
 the 64-bit Linux tarball staff client builds off your system.  Using the same 
 files from Windows wouldn't be good, and the 32-bit ones are known to be 
 broken for Mac.
 
 We've built clients since 2.3 times, so the process is generally known to be 
 working (if not fully fleshed out in detailed instructions).
 
 -- Ben
 
 
 On Thu, Jan 9, 2014 at 2:57 PM, Suzanne Paterno pate...@noblenet.org wrote:
 We recently updated our system from 2.3.7 to 2.4.4. Although I had no trouble 
 with any of our 2.3 releases, I am running into some difficulties creating a 
 Mac client for 2.4.4.  Specifically I receive the attached pop up about field 
 mapper.AutoIDL when I try to log into the client. 
 
 Screen Shot 2014-01-09 at 12.51.22 PM.png
 
 PC versions of the client work on our system so it does not seem as though it 
 is a server problem. The directory structure and files match the instructions 
 at 
 http://evergreen-ils.org/dokuwiki/doku.php?id=mozilla-devel:building_the_staff_client.
   I have tried building the directory(app) from scratch as well as starting 
 with the previous working client then overlaying the new files. I am not sure 
 what else to try. Any ideas? 
 
 Has anyone experienced anything similar when building a Mac Client? How was 
 the problem resolved? Anyone have a 2.4.4 Mac client they’s be willing to 
 share?
 
 Thank you, 
 Suzanne 
 
 --
 Suzanne Paterno
 Systems Support Specialist
 North of Boston Library Exchange
 Danvers, Massachusetts
 pate...@noblenet.org
 www.noblenet.org
 

Re: [OPEN-ILS-GENERAL] Evergreen on Mavericks

[Liam Whalen]

I have a new DMG if anyone needs it.  You can get it here:

http://www.portents.ca/Sitka/Evergreen.dmg

Liam Whalen
BC Libraries Cooperative - Sitka
Systems Specialist
855-383-5761 x1022
liam.wha...@bc.libraries.coop




On Oct 24, 2013, at 9:22 AM, Ben Shum bs...@biblio.org wrote:

 Just an advisory to any Evergreen groups running the staff client on
 their Macbooks.  With the latest Mac OS X 10.9 Mavericks upgrade, we
 noticed that our Evergreen staff clients crashed immediately upon
 startup.
 
 Looking closer, we discovered that the cause for us was a missing
 key/string in the info.plist file:
 
keyCFBundleIdentifier/key
stringorg.evergreen-ils.Evergreen/string
 
 The lack of CFBundleIdentifier as NULL was causing our crashes.
 Adding this key and string to our mac clients resolved the issue.
 Apparently it should have always been there but wasn't included in the
 original wiki page description of building a Mac client from scratch.
 I've since updated the wiki page describing in broad strokes how Mac
 clients are built for more recent Evergreen versions.  It's still
 missing a lot of specifics, but is slightly more accurate now.
 
 Hope this helps.
 
 -- Ben Shum

Re: [OPEN-ILS-GENERAL] Evergreen on Mavericks

[Liam Whalen]

Thanks Roger,

I forgot about that.  I will make one for the stock versions and STAMP_ID.

Liam

On Oct 24, 2013, at 10:53 AM, Rogan Hamby rogan.ha...@yclibrary.net wrote:

 Liam,
 
 Thanks for the DMG file.  Quick warning though, the version in the plist file 
 is for Sitka's server so change it to whatever your's is.
 
 
 On Thu, Oct 24, 2013 at 12:44 PM, Liam Whalen liam.wha...@bc.libraries.coop 
 wrote:
 I have a new DMG if anyone needs it.  You can get it here:
 
 http://www.portents.ca/Sitka/Evergreen.dmg
 
 Liam Whalen
 BC Libraries Cooperative - Sitka
 Systems Specialist
 855-383-5761 x1022
 liam.wha...@bc.libraries.coop
 
 
 
 
 On Oct 24, 2013, at 9:22 AM, Ben Shum bs...@biblio.org wrote:
 
  Just an advisory to any Evergreen groups running the staff client on
  their Macbooks.  With the latest Mac OS X 10.9 Mavericks upgrade, we
  noticed that our Evergreen staff clients crashed immediately upon
  startup.
 
  Looking closer, we discovered that the cause for us was a missing
  key/string in the info.plist file:
 
 keyCFBundleIdentifier/key
 stringorg.evergreen-ils.Evergreen/string
 
  The lack of CFBundleIdentifier as NULL was causing our crashes.
  Adding this key and string to our mac clients resolved the issue.
  Apparently it should have always been there but wasn't included in the
  original wiki page description of building a Mac client from scratch.
  I've since updated the wiki page describing in broad strokes how Mac
  clients are built for more recent Evergreen versions.  It's still
  missing a lot of specifics, but is slightly more accurate now.
 
  Hope this helps.
 
  -- Ben Shum
 
 
 
 
 -- 
 
 Rogan Hamby, MLS, CCNP, MIA
 Managers Headquarters Library and Reference Services, 
 York County Library System
 
 “You can never get a cup of tea large enough or a book long enough to suit 
 me.” 
 ― C.S. Lewis