Forum .LRN Q&A: Broken dependencies between oacs-4-6-2-b1 and dotlrn-1-0 ?

I have checked out from the CVS with the following tags:
oacs-4-6-2-b1 and dotlrn-1-0

When Installing the packages I get:

dotLRN Calendar Applet 0.1a
Requires calendar-portlet of version >= 0.1a.
Requires dotlrn-fs of version >= 0.1a.

dotLRN File Storage Applet 0.1a
Requires dotlrn of version >= 1.0.
Requires file-storage of version >= 4.6.2.

Thanks for any help.

You may want to try the beta 1 release of OpenACS 4.6.2 and dotLRN 1.0 released recently - you'll find the download links on the openacs.org front page. I successfully installed these sources, and you can see the result here. You could also use our test servers (login as site wide admin) to compare the package version numbers and dependencies with what you have on your server.
Thanks for your answer, but isn't that what I have done?
oacs-4-6-2-b1?
Alex,
yes, that is correct, the release is based on tag oacs-4-6-2-b1 for OpenACS and on tag dotlrn-1-0-b1 for dotLRN.
I have just tried it with same results, =(

I did an CVS update -r dotlrn-1-0-b1 on packages directory.
Then I went directly to the Package Manager and it recognized all this new files, but still complained about those two.

I shouldn't need to reinstall everything, right?
Not that I have anything important in the db, it is just that I want to konw when it is necesary.

If I were in your shoes I would reinstall with the release.
I have droped the database and done a new cvs checkout.
I still get the same problem.
Let's check that I'm using the right tags ...
Is this how you check which release you are using?

[alex@jimmy dotlrn]$ cvs log -h dotlrn.info

RCS file: /dotlrn-cvsroot/dotlrn/dotlrn.info,v
Working file: dotlrn.info
head: 1.107
branch:
locks: strict
access list:
symbolic names:
        dotlrn-1-0-b1: 1.104.2.5
        dotlrn-1-0-merged-to-i18n-on-head: 1.104
        pre-i18n: 1.104
        dotlrn-1-0: 1.104.0.2
        sloan-phase-1: 1.97
        dotlrn-2002-01-18: 1.24
        start: 1.1.1.1
        of: 1.1.1
keyword substitution: kv
total revisions: 113
============================================

[alex@jimmy demo]$ cvs log -h readme.txt

RCS file: /cvsroot/openacs-4/readme.txt,v
Working file: readme.txt
head: 1.5
branch:
locks: strict
access list:
symbolic names:
        oacs-4-6-2-b1: 1.3.2.4
        oacs-4-6-1-final: 1.3.2.3
        oacs-4-6-1-b2: 1.3.2.3
        oacs-4-6-1-b1: 1.3.2.2
        jcd-merge-2: 1.3.2.1
        oacs-4-6-final: 1.3.2.1
        oacs-4-6-beta-1: 1.3.2.1
        jcd-premerge: 1.3
        oacs-4-6: 1.3.0.2
        oacs-4-5-final: 1.2
        oacs-4-5-rc-1: 1.2
        don-merge-1: 1.2
        oacs-4-5-beta-1-2: 1.2
        oacs-4-5-beta-1-1: 1.2
        oacs-4-5-beta-1: 1.2
        oacs-4-5: 1.2.0.2
        initial-dev: 1.1.1.1
        OpenACS: 1.1.1
keyword substitution: kv
total revisions: 10

Alex,
you check which branch you are on by using cvs status and the Sticky Tag that it outputs.
I guess this command is better, =)
It looks to me as I have the right tags ...

[alex@jimmy dotlrn]$ cvs status dotlrn.info
=======================
File: dotlrn.info      Status: Up-to-date

  Working revision:    1.104.2.5
  Repository revision: 1.104.2.5      /dotlrn-cvsroot/dotlrn/dotlrn.info,v
  Sticky Tag:          dotlrn-1-0-b1 (revision: 1.104.2.5)
  Sticky Date:        (none)
  Sticky Options:      (none)

[alex@jimmy dotlrn]$

[alex@jimmy demo]$ cvs status readme.txt
=======================
File: readme.txt        Status: Up-to-date

  Working revision:    1.3.2.4
  Repository revision: 1.3.2.4 /cvsroot/openacs-4/readme.txt,v
  Sticky Tag:          oacs-4-6-2-b1 (revision: 1.3.2.4)
  Sticky Date:        (none)
  Sticky Options:      (none)

From this file:

[alex@jimmy file-storage]$ cvs status file-storage.info
===================================================================
File: file-storage.info Status: Up-to-date

  Working revision:    1.20
  Repository revision: 1.20    /cvsroot/openacs-4/packages/file-storage/file-storage.info,v
  Sticky Tag:          HEAD (revision: 1.20)
  Sticky Date:        (none)
  Sticky Options:      (none)

I read: <provides url="file-storage" version="4.6.1"/>

But this file:
[alex@jimmy dotlrn-fs]$ cvs status dotlrn-fs.info
=======================
File: dotlrn-fs.info    Status: Up-to-date

  Working revision:    1.18.2.1
  Repository revision: 1.18.2.1        /dotlrn-cvsroot/dotlrn-fs/dotlrn-fs.info,v
  Sticky Tag:          dotlrn-1-0-b1 (revision: 1.18.2.1)
  Sticky Date:        (none)
  Sticky Options:      (none)

[alex@jimmy dotlrn-fs]$

Says: <requires url="file-storage" version="4.6.2"/>

Alex,
your dotlrn-fs package is on the 4.6 branch but file-storage is probably on head. You're all mixed up. To save yourself from further headache I recommend using the release and then move on to using cvs when you are more familiar with OpenACS and dotlrn.
Peter,

I have only checked out file-storage package from the HEAD to try to see if there was a newer release of that package (4.6.2).

I can take your advice, no problem.
What do you mean by using the release ?

Anyway, i still think there is a problem.

alex@jimmy dotlrn-fs]$ cvs status dotlrn-fs.info
=======================
File: dotlrn-fs.info    Status: Up-to-date

   Working revision:    1.18.2.1
   Repository revision: 1.18.2.1        /dotlrn-cvsroot/dotlrn-fs/dotlrn-fs.info,v
   Sticky Tag:          dotlrn-1-0-b1 (revision: 1.18.2.1)
   Sticky Date:         (none)
   Sticky Options:      (none)

[alex@jimmy dotlrn-fs]$

Says: <requires url="file-storage" version="4.6.2"/>

Am I wrong or this means that dotlrn-fs 1-0-b1 requires file-storage 4.6.2?

How do I check out the latest on 4-6 branch?

Thanks for your help

We make release tarballs for a reason - we expect people to use them.

Visit the "download" link at the top of this page and download OpenACS 4.6.2 beta1.  Visit the "projects" link at the top of this page, visit the dotLRN project and then the "download" link for it and download dotLRN 1.0 beta1.

Many of us have installed these without problem.  None of us are likely to help you through your CVS woes when a simple solution lies at hand - download the beta1 tarballs and install them, as Peter has suggested.

If you download these and still have problems - then we'll listen.  That's the point of releasing tarballs.