From: Doug Barton on
On 05/16/10 20:35, Aristedes Maniatis wrote:
> On 5/05/10 1:54 AM, Doug Barton wrote:
>> Is there an apache-2.2.13 package in packages/All? And what do the links
>> in packages/www and packages/Latest refer to?
>
> I did some more digging in the script itself. You have some code like this:
>
> if [ -r "${LOCAL_PACKAGEDIR}/All/${new_port}.tbz" ]; then
> local_package=${LOCAL_PACKAGEDIR}/All/${new_port}.tbz
> latest_pv=${local_package##*/}
> fi
>
> But I'm guessing the confusion is that we have ..../Latest/apache22.tgz,
> but ...../All/apache-worker-2.2.15.tgz

No, the Latest doesn't enter into it with --index-only.

> That is, the package name is different between Latest and All. This
> particular code path is only invoked if you are using INDEX rather than
> the ports directories. When running without forcing the index, the
> problem does not occur.

The original problem you reported had nothing to do with the index, so
now I'm confused. :)

> I like the INDEX-only approach since we can have deployment servers with
> no /usr/ports directories to keep updated. A special build server is
> responsible for creating packages and pushing them out to other machines.

That was the idea, yes.


Doug

--

... and that's just a little bit of history repeating.
-- Propellerheads

Improve the effectiveness of your Internet presence with
a domain name makeover! http://SupersetSolutions.com/

_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: Aristedes Maniatis on
On 17/05/10 3:49 PM, Doug Barton wrote:
> On 05/16/10 20:35, Aristedes Maniatis wrote:
>> On 5/05/10 1:54 AM, Doug Barton wrote:
>>> Is there an apache-2.2.13 package in packages/All? And what do the links
>>> in packages/www and packages/Latest refer to?
>>
>> I did some more digging in the script itself. You have some code like this:
>>
>> if [ -r "${LOCAL_PACKAGEDIR}/All/${new_port}.tbz" ]; then
>> local_package=${LOCAL_PACKAGEDIR}/All/${new_port}.tbz
>> latest_pv=${local_package##*/}
>> fi
>>
>> But I'm guessing the confusion is that we have ..../Latest/apache22.tgz,
>> but ...../All/apache-worker-2.2.15.tgz
>
> No, the Latest doesn't enter into it with --index-only.


Perhaps I've confused the threads. But this issue appears to be a simple one: I've installed the www/apache22 port but with certain settings it installs the package called apache-worker. And with the index-only option, it thinks it can see 2.2.13 but that version package doesn't even exist in /All.

I'm assuming that ${new_port} is confused between the real package name and the 'other' name, but that could be an incorrect guess on my part. Certainly the problem goes away if I remove the index-only option from portmaster.rc. I've also tried using portsnap fetch update to update to a current INDEX file.

If /Latest isn't being used, and portmaster is using the reference in the INDEX file to know which package to try and install, it is certainly finding the right version number, but just failing to find the package I can see sitting right there in /All.


Regards

Ari




--
-------------------------->
Aristedes Maniatis
ish
http://www.ish.com.au
Level 1, 30 Wilson Street Newtown 2042 Australia
phone +61 2 9550 5001 fax +61 2 9550 4001
GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: Doug Barton on
On 05/16/10 23:14, Aristedes Maniatis wrote:
>
> Perhaps I've confused the threads. But this issue appears to be a simple
> one: I've installed the www/apache22 port but with certain settings it
> installs the package called apache-worker. And with the index-only
> option, it thinks it can see 2.2.13 but that version package doesn't
> even exist in /All.

The INDEX has to be generated with the same settings as the packages
were created with.


hth,

Doug

--

... and that's just a little bit of history repeating.
-- Propellerheads

Improve the effectiveness of your Internet presence with
a domain name makeover! http://SupersetSolutions.com/

_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: Aristedes Maniatis on
On 17/05/10 4:17 PM, Doug Barton wrote:
> The INDEX has to be generated with the same settings as the packages
> were created with.

Well, before we tried to run portsnap to update it, we also just copied /usr/ports/INDEX* from the build machine to the production server. We tried portsnap since we thought that might be copying corrupted files.


Ari

--
-------------------------->
Aristedes Maniatis
ish
http://www.ish.com.au
Level 1, 30 Wilson Street Newtown 2042 Australia
phone +61 2 9550 5001 fax +61 2 9550 4001
GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: Doug Barton on
On 05/17/10 00:51, Aristedes Maniatis wrote:
> On 17/05/10 4:17 PM, Doug Barton wrote:
>> The INDEX has to be generated with the same settings as the packages
>> were created with.
>
> Well, before we tried to run portsnap to update it, we also just copied
> /usr/ports/INDEX* from the build machine to the production server.

But did you _generate_ the INDEX* on the build server, or did you copy
it from somewhere else? And by "generate" I don't mean fetch, I mean did
you actually run 'make index'?


Doug

--

... and that's just a little bit of history repeating.
-- Propellerheads

Improve the effectiveness of your Internet presence with
a domain name makeover! http://SupersetSolutions.com/

_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"