| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
66056
|
Mon Nov 17 12:07:18 2008 |
 | Steve Williamson | StephenWilliamson@Barnsley.gov.uk | Request | Linux | 2.7.5 | Re: Sorting Museremail |
| Stefan Ritt wrote: |
|
| Steve Williamson wrote: |
|
Hi
I've just upgraded to 2.7.5 mainly because I wanted to have Museremail sorted. We use this to list contacts on an RFC form and it's much easier to find the ones you want when they are in a predictable sequence. As an extension to this it would be great if they could be sorted by the last part of their real name - typical user, give him a sweetie and he wants jam on it!
cheers
Steve
|
That's a bit hard since different groups enter their names differently. While for a human it's easy to figure out what the family name is (usually), this must not be true for a computer. So I would propose that you enter the real names in the sequence family name, given name like
Ritt, Stefan
Doe, John
then sorting will work as you like.
|
Good point! However, the current sorting appears to be done on email address rather than name. Having the option to sort on name, where we are in control of the format so could structure it accordingly, would be great.
regards
Steve
|
|
66057
|
Mon Nov 17 12:20:17 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Linux | 2.7.5 | Re: Sorting Museremail |
| Steve Williamson wrote: |
|
| Stefan Ritt wrote: |
|
| Steve Williamson wrote: |
|
Hi
I've just upgraded to 2.7.5 mainly because I wanted to have Museremail sorted. We use this to list contacts on an RFC form and it's much easier to find the ones you want when they are in a predictable sequence. As an extension to this it would be great if they could be sorted by the last part of their real name - typical user, give him a sweetie and he wants jam on it!
cheers
Steve
|
That's a bit hard since different groups enter their names differently. While for a human it's easy to figure out what the family name is (usually), this must not be true for a computer. So I would propose that you enter the real names in the sequence family name, given name like
Ritt, Stefan
Doe, John
then sorting will work as you like.
|
Good point! However, the current sorting appears to be done on email address rather than name. Having the option to sort on name, where we are in control of the format so could structure it accordingly, would be great.
regards
Steve
|
Can you give me an example on how names an email addresses look in your case? If the email address has no fix relation to the real name, I personally find it much harder to find an email address on a Muserlist, since the real name is not shown there. I guess what you really want is a display of the email addres in the form
real name <email address>
then sort by real name. Right? |
|
66058
|
Mon Nov 17 13:03:19 2008 |
| Steve Williamson | StephenWilliamson@Barnsley.gov.uk | Request | Linux | 2.7.5 | Re: Sorting Museremail |
| Stefan Ritt wrote: |
|
| Steve Williamson wrote: |
|
| Stefan Ritt wrote: |
|
| Steve Williamson wrote: |
|
Hi
I've just upgraded to 2.7.5 mainly because I wanted to have Museremail sorted. We use this to list contacts on an RFC form and it's much easier to find the ones you want when they are in a predictable sequence. As an extension to this it would be great if they could be sorted by the last part of their real name - typical user, give him a sweetie and he wants jam on it!
cheers
Steve
|
That's a bit hard since different groups enter their names differently. While for a human it's easy to figure out what the family name is (usually), this must not be true for a computer. So I would propose that you enter the real names in the sequence family name, given name like
Ritt, Stefan
Doe, John
then sorting will work as you like.
|
Good point! However, the current sorting appears to be done on email address rather than name. Having the option to sort on name, where we are in control of the format so could structure it accordingly, would be great.
regards
Steve
|
Can you give me an example on how names an email addresses look in your case? If the email address has no fix relation to the real name, I personally find it much harder to find an email address on a Muserlist, since the real name is not shown there. I guess what you really want is a display of the email addres in the form
real name <email address>
then sort by real name. Right?
|
We currently have 24 users set up which, using a normal font size, takes 6 lines to display Museremail. Having realname+emailaddress would double the space - a bit much for us but may suit other users.
You ask about how our email addresses look. These are very simple, e.g. John Smith's email address would be "JohnSmith@mycompany.co.uk". The are some exceptions, e.g. one or two people have a middle initial,or have a department name as a suffix and some people have abbreviated names because that is how they are known, so John's brother Joseph, known as Joe, might be JoeSoap@mycompany.co.uk and one or two users have a different domain. So the ordering looks a bit odd sometimes, e.g.:
* StanleySmith@mycompany.co.uk * StellaEvans@mycompany.co.uk * StephenJones@mycompany.co.uk * StephenSmith@myothercompany.co.uk
* SterlingGold@mycompany.co.uk * SteuartEvans@mycompany.co.uk * SteveSmythe@mycompany.co.uk * SylviaJones@mycompany.co.uk ...
where Steve Smythe has shifted down the ranks because of the abbreviation.
However, the main reason for the request was that the I was so pleased with the ordering introduced in 2.7.5 but, as it is more normal for me to look down a list of names ordered by last-name/first-name than the other way about, I thought it worth asking if there was any way to do this sensibly. I appreciate that it isn't simple and what suits me may well not suit others - so thanks for taking time to consider the possibilities. I guess the only real solution is to define users differently, e.g. by structuring the name data into first name(s) and last name (not a global solution but would suit most of western europe and the USA at least!) but that is bound to have lots of impacts both on the application and on existing setups - so not really feasible, and probably not worth the disruption.
regards
Steve
|
|
66059
|
Mon Nov 17 19:56:04 2008 |
| Carl Shirey | carl.shirey@pw.utc.com | Question | Linux | 2.7.2-3 | Re: Error: Failed dependencies: |
| Stefan Ritt wrote: |
|
| Carl Shirey wrote: |
|
I went to upgrade to the new version of elog I receive a error message that is.
error: Failed dependencies:
libssl.so.6 is needed by elog-2.7.5-1.i386
rtld(GNU_HASH) is needed by elog-2.7.5-1.i386
Do I need these dependencies for elog to work? If I do need them where do I get them for Suse 10.2.
Thank you for any help.
Carl
|
Starting from 2.7.5, elog needs libssl for any https:// connection. Just install the RPM like you install any other RPM. Now I'm not familar with SUSE, but I found links like that:
http://lenz.homelinux.org/RPMs/
from where you can obtain RPMs. You might have to adjust your YaST installation sources. The package you need should be named opensll-xxx where xxx is some number.
|
Thank you
I will look into it.
Carl |
|
66060
|
Tue Nov 18 09:13:26 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Linux | 2.7.5 | Re: Sorting Museremail |
| Steve Williamson wrote: |
|
However, the main reason for the request was that the I was so pleased with the ordering introduced in 2.7.5 but, as it is more normal for me to look down a list of names ordered by last-name/first-name than the other way about, I thought it worth asking if there was any way to do this sensibly. I appreciate that it isn't simple and what suits me may well not suit others - so thanks for taking time to consider the possibilities. I guess the only real solution is to define users differently, e.g. by structuring the name data into first name(s) and last name (not a global solution but would suit most of western europe and the USA at least!) but that is bound to have lots of impacts both on the application and on existing setups - so not really feasible, and probably not worth the disruption.
|
That's correct. Adding first name(s), last name(s) requires major modifications which are not se easy and I don't have time for that in the moment. So we'll keep it for the time being. |
|
66061
|
Tue Nov 18 13:56:59 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.7.5-2130 | Re: Select -> Edit wipes dates |
| T. Ribbrock wrote: |
|
I just ran into the following bug:
I have a logbook where entries have several attributes, among which several dates. All of these are set to "Type <attr> = date". If I use the "Select" action, tag several entries and subsequently chose "Edit", the values of all date attributes are wiped. All other attributes are kept at their original values, unless changed explicitly. For the date entries, the date choosers are shown (as when editing a single entry), but all set to blank.
Editing single entries works fine.
|
This problem has been fixed in revision 2.7.5-2143. Please upgrade. |
|
66062
|
Thu Nov 20 10:29:39 2008 |
| Steve Williamson | StephenWilliamson@Barnsley.gov.uk | Request | Linux | 2.7.5 | Re: Sorting Museremail |
| Stefan Ritt wrote: |
|
| Steve Williamson wrote: |
|
However, the main reason for the request was that the I was so pleased with the ordering introduced in 2.7.5 but, as it is more normal for me to look down a list of names ordered by last-name/first-name than the other way about, I thought it worth asking if there was any way to do this sensibly. I appreciate that it isn't simple and what suits me may well not suit others - so thanks for taking time to consider the possibilities. I guess the only real solution is to define users differently, e.g. by structuring the name data into first name(s) and last name (not a global solution but would suit most of western europe and the USA at least!) but that is bound to have lots of impacts both on the application and on existing setups - so not really feasible, and probably not worth the disruption.
|
That's correct. Adding first name(s), last name(s) requires major modifications which are not se easy and I don't have time for that in the moment. So we'll keep it for the time being.
|
That's fine. Thanks for listenening - and for keeping on with elog
regards
Steve
|
|
66065
|
Fri Nov 21 10:53:09 2008 |
 | Niklas | niklas@hoglund.pp.se | Bug report | Linux | 2.7.5 2142 | Elogd crashes with: *** stack smashing detected *** | Hi,
elogd sometimes crashes when there are large cookies. Or I'd guess it has something to do with the cookies, elogd crashed over and over again until I cleaned out cookies and authenticated sessions in firefox, then it stopped.
When I run "elogd -v" in gdb, and someone does:
GET / HTTP/1.1
Host: bba.eld.ki.sw.home.se:8080
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; sv-SE; rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Cookie: urem=0; TWIKISID=ecaa5a39e8446a27ec5a34bcbb9d4bcb; unm=erirone; upwd=c3w5MTg1; ipplanNoAuth=yes; SMSESSION=oKvAAv/J9WoCo6KoVdEJkhxz44G10x7TXigffOaAjLrSf0iOFrRJq97oWl32/UBQMvFslc4BgxN/VCz2K7/IRaKdFgmU4CHq/1UUv2RvdHB2HUbYbph+JgKUpAG+kN6Cc4BTwRWhmemUNhONXMRJUCfa6Tq9/osID2AT1wBFInFNww2xVmJPDSi1oltxtT345RgdGQIZbHzG2HBi1GijpiaD+4FI3WLLRzJOj3Art92BLlVDWSaPxKSdSZgVNfRSw33SupUqwD0Is2pc+ufKn4cg0azyOTLNDFOl0U5RI7K9AVgYM0NBsfDoEyBfK8pYIZTMqFFQsnWAdwYz9M2RLDBKyfMXdfGb3rrnOdPH0zvvkkoT01pZObI7dSqHD7IXLbjN/8Pt0O4eo5/SSQ7uKRGpBip0pKe3mxZYI4hsJejYwVBFegovS4qSUiL8UGDhG+lB20WEmDwIQfTG2ZtpckLC6t1CNfa5eFLWCOm+yESU+3AmP4zdJLJSqbznEl2SQTePP5NzI1R5WTAvBbsgX+N9Ab1g0Yui/i042qWNQPLg3/5c/WCHqzImi45+ov42C4mj9OcjGcAf7kaWBMwfdwfChREWkSpMrC2RRndlw+iVbShSK7lVfoCvIqk4491uQBT3bz3S0e56Vin+Oj8qbmEA/5Hp1x9b80qTRy/8lj7KLgbhV60BBvX7ahOkrIFCSjTi8y87K/u4b3KQHesNZgA7SyWRuT+vY4XCb8ANVl8eIui7vK5NNSiFFqLZ1IoeFaVu+gS/hhDu3m/rmK2t5iR2YW/aKmnGTVQsPPy/POVY/zXWgf7c6ps/sSMwTk9sy5Yr8yGYBSUrtZkn1/gK0wpqlRCcjuG991sfgr/UKbhK1dU0rI9E9PBPhvLQpjUHT49AAHL9A9S3FOs66CAFsoVo00WNqKuZcmLpEgXdpbW+mj43tiNugCT98Ec8+Iq0rZYKhYdqFu9AUOdJVXk2udBx9VkOVcRYteFICtwz3fvR02KCU3Sn3a0HKZ4wWOujUnH4nThZGVlUNyg/Of+9GKXY4mxqv/5ocEkO4q8xmAP/OJHrvgJ42kTAjaVgjlSG3b5iJTcu4jvqfC/yKU88Sw==
*** stack smashing detected ***: /root/elogd_2.7.5_2142 terminated
*** stack smashing detected ***: /root/elogd_2.7.5_2142 terminated
Program received signal SIGABRT, Aborted.
0xffffe410 in __kernel_vsyscall ()
(gdb) bt
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb7dad875 in raise () from /lib/tls/i686/cmov/libc.so.6
#2 0xb7daf201 in abort () from /lib/tls/i686/cmov/libc.so.6
#3 0xb7de4e5c in ?? () from /lib/tls/i686/cmov/libc.so.6
#4 0x00000000 in ?? ()
(gdb)
|
|