On Jan 5, 2011, at 06:07, Rainer Müller wrote:
> On 2011-01-05 03:06 , Ryan Schmidt wrote:
>> The problem here was I think that you were using a
>> BitBucket-generated distfile, and they did not keep the distfile
>> around anywhere; they re-generated it later, after you had already
>> recorded its
On 2011-01-05 03:06 , Ryan Schmidt wrote:
> The problem here was I think that you were using a
> BitBucket-generated distfile, and they did not keep the distfile
> around anywhere; they re-generated it later, after you had already
> recorded its checksums into the portfile. I recall there was at le
On Jan 2, 2011, at 13:36, Marko Käning wrote:
>> Personally I'd go with just using the macports mirrors for now. That at
>> least puts the problem off until the next upstream release.
>
> Yeah, it's annoying. Heck, I should have learnt about where and how to put it
> in a MacPorts mirror right a
> Personally I'd go with just using the macports mirrors for now. That at
> least puts the problem off until the next upstream release.
Yeah, it's annoying. Heck, I should have learnt about where and how to put it
in a MacPorts mirror right at the start and not played around with BB
downloads. :
On 2011-1-3 06:25 , Marko Käning wrote:
>> The other option is to upload the bz2 in question to BitBucket and use that
>> file instead of the file created on the fly by BB itself. This approach
>> would not even require a change to the portfile.
> Not true, the link to the file would be different
> The other option is to upload the bz2 in question to BitBucket and use that
> file instead of the file created on the fly by BB itself. This approach would
> not even require a change to the portfile.
Not true, the link to the file would be different. So the portfile needs a
change anyway.
__
> No, see the message I just posted regarding pTeX.
I see. I have to contact Bill in this case… Not very convenient though...
The other option is to upload the bz2 in question to BitBucket and use that
file instead of the file created on the fly by BB itself. This approach would
not even requir
On 2011-1-3 06:14 , Marko Käning wrote:
>> You don't want to do that. Change the dist_subdir to include the
>> revision number and update the checksums. Or, stop using bitbucket as a
>> download location for this version by changing master_sites to just
>> 'macports'.
>>
>> It's not a great idea to
> You don't want to do that. Change the dist_subdir to include the
> revision number and update the checksums. Or, stop using bitbucket as a
> download location for this version by changing master_sites to just
> 'macports'.
>
> It's not a great idea to use non-static sources in general for reason
On 2011-1-3 05:16 , Marko Käning wrote:
> I have a problem with the dist file for makeicns. (See
> ticket https://trac.macports.org/ticket/27843 !)
>
> The file cached at a MacPorts mirror
> http://lil.fr.distfiles.macports.org/makeicns/1.4.tar.bz2 differs from
> the original one hosted at BitBuck
I have a problem with the dist file for makeicns. (See ticket
https://trac.macports.org/ticket/27843 !)
The file cached at a MacPorts mirror
http://lil.fr.distfiles.macports.org/makeicns/1.4.tar.bz2 differs from the
original one hosted at BitBucket
(https://bitbucket.org/mkae/makeicns/get/1.4.
11 matches
Mail list logo
