Re: [RDD] Upgrade problem

2022-04-21 Thread Rob Landry 


Ok, so I am an idiot.

The problem was neither with the database nor with the installation. I 
absent mindedly made a change in /etc/hosts that affected the entry for 
127.0.0.1.


That entry has to include "localhost localhost.localdomain", or else 
Rivendell will misbehave exactly as it did for me these past three days. 
You won't be able to see logs in rdlogedit, nor any audio files in 
rdlibrary, and the user name will always be ''.


I'm posting this primarily for the benefit of the next person to 
experience what I did, although at the rate I'm forgetting things these 
days, that next person might well be me a few months from now.



Rob

--
Не думай что всё пропели,
Что бури все отгремели;
Готовься к великой цели,
А слава тебя найдёт.


On Wed, 20 Apr 2022, Rob Landry wrote:



I'm wrong. It's not a database problem.

It occurred to me that since I have two machines running the same version of 
Rivendell, I should be able to backup the database from vipera (the machine 
that doesn't have the problem) and restore it to farancia (the one that does 
have the problem).


So, I did that. The problem persists even with the restored database from the 
other machine, so it's not a database problem.


Next, I tried creating a new, blank Rivendell database on farancia using 
rddbconfig. When I do that, rddbconfig crashes with a segmentation fault.


There must be something wrong with this Rivendell install. I'm going to blow 
it out, reinstall Rivendell, and see if the problem is still there.



Rob

--
Не думай что всё пропели,
Что бури все отгремели;
Готовься к великой цели,
А слава тебя найдёт.


On Wed, 20 Apr 2022, Rob Landry wrote:


On Wed, 20 Apr 2022, Fred Gleason wrote:

I’d start by taking a look in RDAdmin->ManageUsers. Are all of the 
expected

users there? Does the data look sane?


Yes.


(The data in those dialogs mostly live
in a table called ‘USERS’, but looking directly at that won’t be
particularly helpful without a good understanding of the schema design. 
And,

remember, the schema has changed quite a bit between v2.1x and v2.19.x)!


I have actually looked at the USERS table on the machine (farancia) 
exhibiting the problem and compared it with the USERS table on another 
machine (vipera) I built for WZBC. Both are running 3.6.5 and have the same 
schema. I looked for differences between the two that might explain why 
farancia has the problem but vipera does not.


I did not see any differences in the USERS tables that might account for 
the problem.


And then, take a look at the Station entry in RDAdmin. Does the default 
user

exist?


I can't find a Station entry in rdadmin.

I did look at the STATIONS table in both machines' databases. Here, too, I 
found no differences between the two tables that might account for the 
problem. There were some fields like JACK_COMMAND_LINE that were blank in 
one table but NULL in the other, but since I'm not using JACK on either 
machine, I didn't think those differences were meaningful.



Rob___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Upgrade problem

2022-04-20 Thread Rob Landry 


I'm wrong. It's not a database problem.

It occurred to me that since I have two machines running the same version 
of Rivendell, I should be able to backup the database from vipera (the 
machine that doesn't have the problem) and restore it to farancia (the one 
that does have the problem).


So, I did that. The problem persists even with the restored database from 
the other machine, so it's not a database problem.


Next, I tried creating a new, blank Rivendell database on farancia using 
rddbconfig. When I do that, rddbconfig crashes with a segmentation fault.


There must be something wrong with this Rivendell install. I'm going to 
blow it out, reinstall Rivendell, and see if the problem is still there.



Rob

--
Не думай что всё пропели,
Что бури все отгремели;
Готовься к великой цели,
А слава тебя найдёт.


On Wed, 20 Apr 2022, Rob Landry wrote:


On Wed, 20 Apr 2022, Fred Gleason wrote:


I’d start by taking a look in RDAdmin->ManageUsers. Are all of the expected
users there? Does the data look sane?


Yes.


(The data in those dialogs mostly live
in a table called ‘USERS’, but looking directly at that won’t be
particularly helpful without a good understanding of the schema design. 
And,

remember, the schema has changed quite a bit between v2.1x and v2.19.x)!


I have actually looked at the USERS table on the machine (farancia) 
exhibiting the problem and compared it with the USERS table on another 
machine (vipera) I built for WZBC. Both are running 3.6.5 and have the same 
schema. I looked for differences between the two that might explain why 
farancia has the problem but vipera does not.


I did not see any differences in the USERS tables that might account for the 
problem.


And then, take a look at the Station entry in RDAdmin. Does the default 
user

exist?


I can't find a Station entry in rdadmin.

I did look at the STATIONS table in both machines' databases. Here, too, I 
found no differences between the two tables that might account for the 
problem. There were some fields like JACK_COMMAND_LINE that were blank in one 
table but NULL in the other, but since I'm not using JACK on either machine, 
I didn't think those differences were meaningful.



Rob___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Upgrade problem

2022-04-20 Thread Rob Landry 

On Wed, 20 Apr 2022, Fred Gleason wrote:


I’d start by taking a look in RDAdmin->ManageUsers. Are all of the expected
users there? Does the data look sane?


Yes.


(The data in those dialogs mostly live
in a table called ‘USERS’, but looking directly at that won’t be
particularly helpful without a good understanding of the schema design. And,
remember, the schema has changed quite a bit between v2.1x and v2.19.x)!


I have actually looked at the USERS table on the machine (farancia) 
exhibiting the problem and compared it with the USERS table on another 
machine (vipera) I built for WZBC. Both are running 3.6.5 and have the 
same schema. I looked for differences between the two that might explain 
why farancia has the problem but vipera does not.


I did not see any differences in the USERS tables that might account for 
the problem.



And then, take a look at the Station entry in RDAdmin. Does the default user
exist?


I can't find a Station entry in rdadmin.

I did look at the STATIONS table in both machines' databases. Here, too, I 
found no differences between the two tables that might account for the 
problem. There were some fields like JACK_COMMAND_LINE that were blank in 
one table but NULL in the other, but since I'm not using JACK on either 
machine, I didn't think those differences were meaningful.



Rob___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Upgrade problem

2022-04-20 Thread Fred Gleason 
On Apr 19, 2022, at 17:15, Rob Landry <41001...@interpring.com> wrote:

> When I run rdlogin, it says "Current user: unknown".
> 
> If I select a user, or press the Default User button, the program immediately 
> quits.
> 
> If I run it again, it still says "Current user: unknown".
> 
> So, the problem appears to be some database value that isn't letting it set 
> the user.

Sounds like a reasonable diagnosis.


> This Rivendell installation was done under CentOS 7, following the Paravel 
> Web site instructions. Since I followed the same procedure for two other 
> machines, neither of which have the problem, it must be something in this 
> database rather than a software issue. If I were to do a table-by-table 
> comparison with one of the other machines, which table should I start with?

I’d start by taking a look in RDAdmin->ManageUsers. Are all of the expected 
users there? Does the data look sane? (The data in those dialogs mostly live in 
a table called ‘USERS’, but looking directly at that won’t be particularly 
helpful without a good understanding of the schema design. And, remember, the 
schema has changed quite a bit between v2.1x and v2.19.x)!

And then, take a look at the Station entry in RDAdmin. Does the default user 
exist?

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Upgrade problem

2022-04-19 Thread Kit Haskins 
Are able to create another user to login with ?   Does another account work ?



RDAdmin -> Manage Users ...    





Here's an out there --

Is the account set up with Administrative Rights ?  I've learned that using an 
admin account to 

do non-admin stuff can break your system.   While troubleshooting an install, 
extra user accounts were created and one of them was set with admin rights and 
was the default login.   After the reboot and it came up with the adrmin set 
default user, we noticed weird behavior with importing carts, running logs on 
RDAirPlay, editing logs with RDLogEdit ...    Just an out there idea ...   We 
were curious and did it ... 



---

Thru the Ethernet, past the Gateway, off the modem pool, nothing but NET .

mailto:k...@ka0wuc.org



When I was 10, I caught the radio bug, it appears to be over ...






 On Tue, 19 Apr 2022 15:15:53 -0600 Rob Landry <41001...@interpring.com> 
wrote 




When I run rdlogin, it says "Current user: unknown". 
 
If I select a user, or press the Default User button, the program 
immediately quits. 
 
If I run it again, it still says "Current user: unknown". 
 
So, the problem appears to be some database value that isn't letting it 
set the user. 
 
This Rivendell installation was done under CentOS 7, following the Paravel 
Web site instructions. Since I followed the same procedure for two other 
machines, neither of which have the problem, it must be something in this 
database rather than a software issue. If I were to do a table-by-table 
comparison with one of the other machines, which table should I start 
with? 
 
 
Rob 
 
-- 
Не думай что всё пропели, 
Что бури все отгремели; 
Готовься к великой цели, 
А слава тебя найдёт. 
 
 
On Tue, 19 Apr 2022, Fred Gleason wrote: 
 
> On Apr 19, 2022, at 14:34, Rob Landry  wrote: 
>   It says "User: " with nothing after it, and then "Log: wcvr-tuesday”. 
> 
> 
> There’s your problem with sound panel play-out then (and a slew of other 
> stuff not working as well). 
> 
> Can you use RDLogin to log in as other users? How about the default user? The 
> titlebar displays should update in real 
> time as the users change. 
> 
> Cheers! 
> 
> 
> |-| 
> | Frederick F. Gleason, Jr. |             Chief Developer             | 
> |                           |             Paravel Systems             | 
> |-| 
> |         A room without books is like a body without a soul.         | 
> |                                                                     | 
> |                                                         -- Cicero   | 
> |-| 
> 
>___ 
Rivendell-dev mailing list 
mailto:Rivendell-dev@lists.rivendellaudio.org 
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Upgrade problem

2022-04-19 Thread Rob Landry 


When I run rdlogin, it says "Current user: unknown".

If I select a user, or press the Default User button, the program 
immediately quits.


If I run it again, it still says "Current user: unknown".

So, the problem appears to be some database value that isn't letting it 
set the user.


This Rivendell installation was done under CentOS 7, following the Paravel 
Web site instructions. Since I followed the same procedure for two other 
machines, neither of which have the problem, it must be something in this 
database rather than a software issue. If I were to do a table-by-table 
comparison with one of the other machines, which table should I start 
with?



Rob

--
Не думай что всё пропели,
Что бури все отгремели;
Готовься к великой цели,
А слава тебя найдёт.


On Tue, 19 Apr 2022, Fred Gleason wrote:


On Apr 19, 2022, at 14:34, Rob Landry <41001...@interpring.com> wrote:
  It says "User: " with nothing after it, and then "Log: wcvr-tuesday”.


There’s your problem with sound panel play-out then (and a slew of other stuff 
not working as well).

Can you use RDLogin to log in as other users? How about the default user? The 
titlebar displays should update in real
time as the users change.

Cheers!


|-|
| Frederick F. Gleason, Jr. |             Chief Developer             |
|                           |             Paravel Systems             |
|-|
|         A room without books is like a body without a soul.         |
|                                                                     |
|                                                         -- Cicero   |
|-|

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Upgrade problem

2022-04-19 Thread Fred Gleason 
On Apr 19, 2022, at 14:34, Rob Landry <41001...@interpring.com> wrote:

> It says "User: " with nothing after it, and then "Log: wcvr-tuesday”.

There’s your problem with sound panel play-out then (and a slew of other stuff 
not working as well).

Can you use RDLogin to log in as other users? How about the default user? The 
titlebar displays should update in real time as the users change.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Upgrade problem

2022-04-19 Thread Rob Landry 


It says "User: " with nothing after it, and then "Log: wcvr-tuesday".


Rob

--
Не думай что всё пропели,
Что бури все отгремели;
Готовься к великой цели,
А слава тебя найдёт.


On Tue, 19 Apr 2022, Fred Gleason wrote:


On Apr 19, 2022, at 10:29, Rob Landry <41001...@interpring.com> wrote:
  Unfortunately, upgrading the old database to 2.19.3 and then upgrading it 
to 3.6.5 didn't solve the problem.
  I am still experiencing the same symptoms.

  If I start rdairplay in a terminal window, select Sound Panel. click on 
Setup to start it slashing, and then
  click on [S:1] Panel S:1 to change its name, the following message 
appears in the terminal window:

  QSqlQuery::value: not positioned on a valid record
  for query: select `CONFIG_PANELS_PRIV` from `USERS` where `LOGIN_NAME`=""

  LOGIN_NAME = ""? Shouldn't it default to 'user’?



Do you have a valid user context? Look on the titlebar of RDAirPlay; you should 
see something like ‘User: user’.

Cheers!


|-|
| Frederick F. Gleason, Jr. |             Chief Developer             |
|                           |             Paravel Systems             |
|-|
|         A room without books is like a body without a soul.         |
|                                                                     |
|                                                         -- Cicero   |
|-|


___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Upgrade problem

2022-04-19 Thread Fred Gleason 
On Apr 19, 2022, at 10:29, Rob Landry <41001...@interpring.com> wrote:

> Unfortunately, upgrading the old database to 2.19.3 and then upgrading it to 
> 3.6.5 didn't solve the problem. I am still experiencing the same symptoms.
> 
> If I start rdairplay in a terminal window, select Sound Panel. click on Setup 
> to start it slashing, and then click on [S:1] Panel S:1 to change its name, 
> the following message appears in the terminal window:
> 
> QSqlQuery::value: not positioned on a valid record
> for query: select `CONFIG_PANELS_PRIV` from `USERS` where `LOGIN_NAME`=""
> 
> LOGIN_NAME = ""? Shouldn't it default to 'user’?


Do you have a valid user context? Look on the titlebar of RDAirPlay; you should 
see something like ‘User: user’.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Upgrade problem

2022-04-19 Thread Rob Landry 


Unfortunately, upgrading the old database to 2.19.3 and then upgrading it 
to 3.6.5 didn't solve the problem. I am still experiencing the same 
symptoms.


If I start rdairplay in a terminal window, select Sound Panel. click on 
Setup to start it slashing, and then click on [S:1] Panel S:1 to change 
its name, the following message appears in the terminal window:


QSqlQuery::value: not positioned on a valid record
for query: select `CONFIG_PANELS_PRIV` from `USERS` where `LOGIN_NAME`=""

LOGIN_NAME = ""? Shouldn't it default to 'user'?


Rob

--
Не думай что всё пропели,
Что бури все отгремели;
Готовься к великой цели,
А слава тебя найдёт.


On Tue, 19 Apr 2022, Fred Gleason wrote:


On Apr 18, 2022, at 16:12, Rob Landry <41001...@interpring.com> wrote:
  I have an old machine installed at WCVR running RD 2.1.5 under Centos 6. 
It was built in 2017.

  I want to replace it with a new machine I've just built that runs RD 
3.6.5 under CentOS 7. Both machines
  have the same name ("farancia.sugarrivermedia.com") but different IP 
addresses.

  In pursuit of that goal, I backed up the old RD 2.1.5 database, copied it 
to the new system, imnported it
  with rddbmgr, and converted it to the current database version.

  I'm finding that some things don't work; in particular, rdlibrary sees no 
groups and no carts.

  The SoundPanel buttons in rdairplay don't work properly. The System panel 
buttons are all blank, and cannot
  be modified from rdairplay. The User panels are likewise blank, but can 
be modified.

  Has anyone else experienced these issues?


Sounds like something got borked in the database conversion. That’s a very old 
Rivendell version that you upgraded from
(schema version 205). The DB converter routines in v3.x (and v4.x, for that 
matter) support schema versions all the way
back to 159 [v1.0.x], but only schema versions 242 [v2.10.x] and later are 
really well tested. If possible, I would try
converting that DB using the latest v2.x version (v2.19.3), *then* use v3.6.5 
to convert it to ‘current’.

Cheers!


|-|
| Frederick F. Gleason, Jr. |             Chief Developer             |
|                           |             Paravel Systems             |
|-|
|         A room without books is like a body without a soul.         |
|                                                                     |
|                                                         -- Cicero   |
|-|

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Upgrade problem

2022-04-19 Thread Rob Landry 


This may be a clue. Running rdairplay from a terminal window, when I 
select Sound Panel and press the Setup button, then click on Panel S:1 to 
rename it, the following message appears in the terminal window:


QSqlQuery::value: not positioned on a valid record
for query: select `CONFIG_PANELS_PRIV` from `USERS` where `LOGIN_NAME`=""

That suggests that rather than defaulting to the user 'user', it thinks 
I'm logged in as a user with a blank name.


I'll see if there's away to upgrade the old database to 2.19.3.


Rob

--
Не думай что всё пропели,
Что бури все отгремели;
Готовься к великой цели,
А слава тебя найдёт.


On Tue, 19 Apr 2022, Fred Gleason wrote:


On Apr 18, 2022, at 16:12, Rob Landry <41001...@interpring.com> wrote:
  I have an old machine installed at WCVR running RD 2.1.5 under Centos 6. 
It was built in 2017.

  I want to replace it with a new machine I've just built that runs RD 
3.6.5 under CentOS 7. Both machines
  have the same name ("farancia.sugarrivermedia.com") but different IP 
addresses.

  In pursuit of that goal, I backed up the old RD 2.1.5 database, copied it 
to the new system, imnported it
  with rddbmgr, and converted it to the current database version.

  I'm finding that some things don't work; in particular, rdlibrary sees no 
groups and no carts.

  The SoundPanel buttons in rdairplay don't work properly. The System panel 
buttons are all blank, and cannot
  be modified from rdairplay. The User panels are likewise blank, but can 
be modified.

  Has anyone else experienced these issues?


Sounds like something got borked in the database conversion. That’s a very old 
Rivendell version that you upgraded from
(schema version 205). The DB converter routines in v3.x (and v4.x, for that 
matter) support schema versions all the way
back to 159 [v1.0.x], but only schema versions 242 [v2.10.x] and later are 
really well tested. If possible, I would try
converting that DB using the latest v2.x version (v2.19.3), *then* use v3.6.5 
to convert it to ‘current’.

Cheers!


|-|
| Frederick F. Gleason, Jr. |             Chief Developer             |
|                           |             Paravel Systems             |
|-|
|         A room without books is like a body without a soul.         |
|                                                                     |
|                                                         -- Cicero   |
|-|

___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Upgrade problem

2022-04-19 Thread Fred Gleason 
On Apr 18, 2022, at 16:12, Rob Landry <41001...@interpring.com> wrote:

> I have an old machine installed at WCVR running RD 2.1.5 under Centos 6. It 
> was built in 2017.
> 
> I want to replace it with a new machine I've just built that runs RD 3.6.5 
> under CentOS 7. Both machines have the same name 
> ("farancia.sugarrivermedia.com ") but 
> different IP addresses.
> 
> In pursuit of that goal, I backed up the old RD 2.1.5 database, copied it to 
> the new system, imnported it with rddbmgr, and converted it to the current 
> database version.
> 
> I'm finding that some things don't work; in particular, rdlibrary sees no 
> groups and no carts.
> 
> The SoundPanel buttons in rdairplay don't work properly. The System panel 
> buttons are all blank, and cannot be modified from rdairplay. The User panels 
> are likewise blank, but can be modified.
> 
> Has anyone else experienced these issues?

Sounds like something got borked in the database conversion. That’s a very old 
Rivendell version that you upgraded from (schema version 205). The DB converter 
routines in v3.x (and v4.x, for that matter) support schema versions all the 
way back to 159 [v1.0.x], but only schema versions 242 [v2.10.x] and later are 
really well tested. If possible, I would try converting that DB using the 
latest v2.x version (v2.19.3), *then* use v3.6.5 to convert it to ‘current’.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Re: [RDD] Upgrade problem

2022-04-18 Thread Rob Landry 


I also can't see any logs or services in rdlogedit. And yes, I have the 
service permissions for user set.


I eveb tried creating a new user 'bozo' and assigned it all group and 
service permissions... but it can't see anything, either.


Curiously, logs and audio cuts are available in rdairplay, and play as 
they should.



Rob

--
Не думай что всё пропели,
Что бури все отгремели;
Готовься к великой цели,
А слава тебя найдёт.


On Mon, 18 Apr 2022, Rob Landry wrote:



I have an old machine installed at WCVR running RD 2.1.5 under Centos 6. It 
was built in 2017.


I want to replace it with a new machine I've just built that runs RD 3.6.5 
under CentOS 7. Both machines have the same name 
("farancia.sugarrivermedia.com") but different IP addresses.


In pursuit of that goal, I backed up the old RD 2.1.5 database, copied it to 
the new system, imnported it with rddbmgr, and converted it to the current 
database version.


I'm finding that some things don't work; in particular, rdlibrary sees no 
groups and no carts.


The SoundPanel buttons in rdairplay don't work properly. The System panel 
buttons are all blank, and cannot be modified from rdairplay. The User panels 
are likewise blank, but can be modified.


Has anyone else experienced these issues?


Rob

--
Не думай что всё пропели,
Что бури все отгремели;
Готовься к великой цели,
А слава тебя найдёт.
___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

[RDD] Upgrade problem

2022-04-18 Thread Rob Landry 


I have an old machine installed at WCVR running RD 2.1.5 under Centos 6. 
It was built in 2017.


I want to replace it with a new machine I've just built that runs RD 3.6.5 
under CentOS 7. Both machines have the same name 
("farancia.sugarrivermedia.com") but different IP addresses.


In pursuit of that goal, I backed up the old RD 2.1.5 database, copied it 
to the new system, imnported it with rddbmgr, and converted it to the 
current database version.


I'm finding that some things don't work; in particular, rdlibrary sees no 
groups and no carts.


The SoundPanel buttons in rdairplay don't work properly. The System 
panel buttons are all blank, and cannot be modified from rdairplay. The 
User panels are likewise blank, but can be modified.


Has anyone else experienced these issues?


Rob

--
Не думай что всё пропели,
Что бури все отгремели;
Готовься к великой цели,
А слава тебя найдёт.
___
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev