Le 21/11/2016 à 04:25, Bruce Albrecht a écrit :
> I was wondering why the port which is now default is version 5.24-RC4
> instead of 5.24.0? Perl 5.24.0 was released on 2016-05-09 (May 9th).
> Even if RC4 and 5.24.0 have no code differences besides the
> versioning, I fail to understand why you
I was wondering why the port which is now default is version 5.24-RC4
instead of 5.24.0? Perl 5.24.0 was released on 2016-05-09 (May 9th).
Even if RC4 and 5.24.0 have no code differences besides the versioning,
I fail to understand why you would not update the perl 5.24 port to use
the final
On 07/11/2016 06:47, Mark Millard wrote:
> Here is what I found looking back in 5.22 after switching to 5.24:
>
>> > # find /usr/local/lib/perl5/site_perl/mach/5.22/ -print | grep packlist |
>> > more
>> > /usr/local/lib/perl5/site_perl/mach/5.22/auto/File/Listing/.packlist
>> >
On 06.11.2016 12:43, Andrey Chernov wrote:
> On 06.11.2016 12:34, Mathieu Arnold wrote:
>> Le 05/11/2016 à 16:00, Andrey Chernov a écrit :
>>> The instruction posted to UPDATING is a bit incomplete.
>>> Additionlly
>>> portupgrade -f "p5-*"
>>> should run to move all ports still sitting in 5.20
On 06.11.2016 12:34, Mathieu Arnold wrote:
> Le 05/11/2016 à 16:00, Andrey Chernov a écrit :
>> The instruction posted to UPDATING is a bit incomplete.
>> Additionlly
>> portupgrade -f "p5-*"
>> should run to move all ports still sitting in 5.20 directory, even if
>> they are not depending on perl
Hi,
audio/logitechmediaserver is really not fine with 5.24. How to I set it to use
a previous version in the mean time?
Thanks,
Mark
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe,
On 11/05/16 08:12, Piotr Szafarczyk wrote:
It looks like the same problem I encountered with 5.20 under 10.3 (just
one box). Links are not created during port building (with other than
perl too). With perl, two links are missing under /usr/local/bin.
Creating them manually allows for a
Le 05/11/2016 à 16:00, Andrey Chernov a écrit :
> The instruction posted to UPDATING is a bit incomplete.
> Additionlly
> portupgrade -f "p5-*"
> should run to move all ports still sitting in 5.20 directory, even if
> they are not depending on perl lib.
That should not happen, what ports are
The instruction posted to UPDATING is a bit incomplete.
Additionlly
portupgrade -f "p5-*"
should run to move all ports still sitting in 5.20 directory, even if
they are not depending on perl lib.
___
freebsd-ports@freebsd.org mailing list
On 2016-11-05 15:33, tech-lists wrote:
On 05/11/2016 14:18, Tijl Coosemans wrote:
It's probably caused by pkg not copying hardlinks:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213255
What version of pkg are we using?
Mine is 1.9.3
My problems were because of 1.8.7. With 1.9.3 (and
On 05/11/2016 14:48, tech-lists wrote:
On second thoughts, I don't think it was this because the portupgrade
tool builds a package, removes the old one then installs the new one.
The bug you posted says the problem doesn't happen when one makes the
package.
edit: i think my issue was slightly
On 05/11/2016 14:18, Tijl Coosemans wrote:
It's probably caused by pkg not copying hardlinks:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213255
On second thoughts, I don't think it was this because the portupgrade
tool builds a package, removes the old one then installs the new one.
On 2016-11-05 15:18, Tijl Coosemans wrote:
It's probably caused by pkg not copying hardlinks:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213255
Hi,
Wonderful! This is exactly my problem. Using pkg add installs all the files.
Thanks a lot.
Regards,
Piotr
On 05/11/2016 14:18, Tijl Coosemans wrote:
It's probably caused by pkg not copying hardlinks:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213255
What version of pkg are we using?
Mine is 1.9.3
--
J.
___
freebsd-ports@freebsd.org mailing list
On Fri, 4 Nov 2016 23:00:56 + tech-lists wrote:
> On 04/11/2016 22:58, tech-lists wrote:
>> On 03/11/2016 15:00, Mathieu Arnold wrote:
>>> Instructions on how to switch are in UPDATING.
>>>
>>> If you do not want to switch, you do not have to do anything.
>>
>> I
On 2016-11-05 14:51, tech-lists wrote:
Everything? Could you try any other port that creates links? Are links
created?
By "links" do you mean "installed usable links into /usr/local/bin"
then yes. A little earlier today I built and installed libreoffice
from ports, without issue.
$ ls -lah
On 05/11/2016 11:46, Piotr Szafarczyk wrote:
Everything? Could you try any other port that creates links? Are links
created?
By "links" do you mean "installed usable links into /usr/local/bin" then
yes. A little earlier today I built and installed libreoffice from
ports, without issue.
$
On 05/11/2016 11:46, Piotr Szafarczyk wrote:
Everything? Could you try any other port that creates links? Are links
created?
Seems so. What port(s) would you like me to try?
--
J.
___
freebsd-ports@freebsd.org mailing list
On 2016-11-05 10:58, tech-lists wrote:
It looks like the same problem I encountered with 5.20 under 10.3 (just
one box). Links are not created during port building (with other than
perl too). With perl, two links are missing under /usr/local/bin.
Creating them manually allows for a successful
On 05/11/2016 07:12, Piotr Szafarczyk wrote:
Hi,
It looks like the same problem I encountered with 5.20 under 10.3 (just
one box). Links are not created during port building (with other than
perl too). With perl, two links are missing under /usr/local/bin.
Creating them manually allows for a
On 2016-11-05 00:00, tech-lists wrote:
On 04/11/2016 22:58, tech-lists wrote:
On 03/11/2016 15:00, Mathieu Arnold wrote:
I followed the instructions in /usr/ports/UPDATING for portupgrade. I
have found that numerous ports will not build:
edit: the error I get now when I try to rebuild an
On 04/11/2016 22:58, tech-lists wrote:
On 03/11/2016 15:00, Mathieu Arnold wrote:
Instructions on how to switch are in UPDATING.
If you do not want to switch, you do not have to do anything.
EVERYTHING IS FINE.
-- Mathieu Arnold
Hello,
I followed the instructions in /usr/ports/UPDATING
On 03/11/2016 15:00, Mathieu Arnold wrote:
Instructions on how to switch are in UPDATING.
If you do not want to switch, you do not have to do anything.
EVERYTHING IS FINE.
-- Mathieu Arnold
Hello,
I followed the instructions in /usr/ports/UPDATING for portupgrade. I
have found that
On 04/11/2016 15:40, Marko Cupać wrote:
> I guess I came to positive conclusion too early. Everything did
> compile, install and start without problems. But so far I had problems
> with amavisd-new which would die with the following message:
>
> Nov 4 15:20:52 mx1 amavis[38170]: (!)_DIE: Suicide
2016-11-04 15:40, Marko Cupać wrote:
I guess I came to positive conclusion too early. Everything did
compile, install and start without problems. But so far I had problems
with amavisd-new which would die with the following message:
Nov 4 15:20:52 mx1 amavis[38170]: (!)_DIE: Suicide in
On Fri, 4 Nov 2016 10:41:29 +0100
Marko Cupać wrote:
> On Thu, 3 Nov 2016 16:00:57 +0100
> Mathieu Arnold wrote:
>
> > Instructions on how to switch are in UPDATING.
> >
> > If you do not want to switch, you do not have to do anything.
> >
> >
On Thu, 3 Nov 2016 16:00:57 +0100
Mathieu Arnold wrote:
> Instructions on how to switch are in UPDATING.
>
> If you do not want to switch, you do not have to do anything.
>
> EVERYTHING IS FINE.
>
Thank you for the information, upgrade using poudriere and pkg finished
27 matches
Mail list logo