Re: what's up with portsmon?

2014-08-26 Thread Mark Linimon 
On Tue, Aug 26, 2014 at 04:34:01PM -0700, Don Lewis wrote:
> What's going on with portsmon.freebsd.org these days?   A number of my
> ports have been updated quite a while ago, but there isn't any updated
> build status on portsmon.

portsmon suffered some bitrot when a vuxml URL grew a "|" in it.  This
caused index updates to not be updated.  I fixed the bitrot last Sunday
but I should probably do a force-rebuild of the metadata.

> I poked around on one of the pkg.freebsd.org, and stuff looks pretty
> old there as well.  For instance, the timestamps of the files under
> freebsd:10:x86:32/latest/ are 13-Aug-2014.

portsmon only knows about the packages provided by pkg.freebsd.org.
That's a question for the currently active portmgrs.

> But ... if I go to this page
>  and select the
> 84amd64-default link, I end up at
> .  If I then
> click on the "logs/" link, I find a bunch of build logs dated
> 24-Aug-2014.  Looking at protobuf-c-1.0.1.log, it looks like the build
> was a success.

IIUC, the build machines' outputs (e.g. *.isc.freebsd.org) are not automatically
uploaded to pkg.freebsd.org in order to provide a sanity check.

> Other observations:
> 
>   It would probably be helpful if the individual port pages reported
>   the status for the new_xorg versions.

portsmon never had the idea of "multiple repositories" engineered into it.
This would take a bit of retrofitting.  I'll put it on the todo list.

A shortcut would be to build a "new-xorg only" version of portsmon.  I
would need to get clusteradm to provision me a new, separate, jail to do
that.  (I have an outstanding request for another one anyways that seems
to be stalled.)

>   It would be nice if there was a way to find out what the ports build
>   cluster was currently working on.  Things like the svn revision of the
>   ports tree, what OS and ARCH versions were currently being built, and
>   how far along the build was (basically what you see when you type ^T
>   during a poudriere run), and what's next the the queue.

portsmon is not really tightly coupled to the build machines.  I suppose
I could teach it more about poudriere but that makes the code a lot more
specific than it is right now.

mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: mksh-r49_1

2014-08-26 Thread Kurt Jaeger 
Hi!

> Hello, can mksh be updated to R50?  Thanks.

Done. Thanks to olivierd for the patch!

-- 
p...@opsec.eu+49 171 3101372 6 years to go !
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: mksh-r49_1

2014-08-26 Thread Martin Wilke 
Feel free to commit it, am still on holiday till next week.


> On Aug 27, 2014, at 10:46 AM, Olivier Duchateau  
> wrote:
> 
> 2014-08-27 2:33 GMT+02:00 Brian N :
>> 
>> Hello, can mksh be updated to R50?  Thanks.
> 
> Hi,
> 
> Try patch, available here:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191582
> 
> Regards
> 
>> ___
>> freebsd-ports@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
>> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
> 
> 
> 
> -- 
> olivier

+-oOO--(_)--OOo-+
With best Regards,
   Martin Wilke (miwi_(at)_FreeBSD.org)

Mess with the Best, Die like the Rest

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: mksh-r49_1

2014-08-26 Thread Olivier Duchateau 
2014-08-27 2:33 GMT+02:00 Brian N :
>
> Hello, can mksh be updated to R50?  Thanks.

Hi,

Try patch, available here:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191582

Regards

> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"



-- 
olivier
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: I want to upgrade an old (8.3-RC2) FReeBSD installation, but can't install subversion

2014-08-26 Thread Alfred Perlstein 


On 8/26/14 5:22 PM, Kevin Oberman wrote:

On Tue, Aug 26, 2014 at 2:19 PM, Michelle Sullivan 
wrote:


And this is precisely why I think the killing of the old packaging
system on Sept 1, is the wrong thing to do.

If you don't have the new packaging system installed and setup by then,
you're screwed... royally...

Happened somewhere between 6.x and 7.x with the ports tree, pre 8.4...
the list goes on

FWIW Torfinn, get a amd64, 8.4 make binary (from the install disk) and
manually copy it over (just /usr/bin/make ) backing up the original first.

You'll find the ports tree will then work... well until Sept 1 when all
hell breaks loose if you use anything but the quarterly SVN tree...
and then you'll have 90 days more..

Michelle

Torfinn Ingolfsen wrote:

I have a machine which has an old installation of FreeBSD 8.3 on it:
root@kg-vm2# uname -a
FreeBSD kg-vm2 8.3-RC2 FreeBSD 8.3-RC2 #0: Sat Mar 24 16:15:47 UTC
2012 r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC
amd64

and I want to update it. Since FreeBSD this old doesn't have svnlite
installed, I fetch a ports tree (no, this machine didn't have one
already) and try to install the subversion port:
root@kg-vm2# cd /usr/ports/devel/subversion
root@kg-vm2# make install
Unknown modifier 't'

"/usr/ports/Mk/bsd.port.mk", line 1727: Malformed conditional
(defined(USE_RC_SUBR) && ${USE_RC_SUBR:tu} != "YES")
Unknown modifier 't'

Unknown modifier 't'

Unknown modifier 't'

"/usr/ports/Mk/bsd.sites.mk", line 956: Malformed conditional
(!empty(_PERL_CPAN_ID) && ${_PERL_CPAN_FLAG:tl} == "cpan")
Unknown modifier 't'

Unknown modifier 't'

"/usr/ports/Mk/bsd.port.mk", line 2858: Unclosed conditional/for loop
"/usr/ports/Mk/bsd.port.mk", line 2858: Unexpected end of file in for

loop.

"/usr/ports/Mk/bsd.port.mk", line 6574: Unclosed conditional/for loop
"/usr/ports/Mk/bsd.port.mk", line 6574: Unexpected end of file in for

loop.

make: fatal errors encountered -- cannot continue

So I google a bit and find this[1] thread.
Hmm, ok let's try to install bmake then:
root@kg-vm2# cd /usr/ports/devel/bmake
root@kg-vm2# make install
Unknown modifier 't'

Unknown modifier 't'

Unknown modifier 't'

Unknown modifier 't'

Unknown modifier 't'

"/usr/ports/Mk/bsd.sites.mk", line 956: Malformed conditional
(!empty(_PERL_CPAN_ID) && ${_PERL_CPAN_FLAG:tl} == "cpan")
Unknown modifier 't'

Unknown modifier 't'

"/usr/ports/Mk/bsd.port.mk", line 2858: Unclosed conditional/for loop
"/usr/ports/Mk/bsd.port.mk", line 2858: Unexpected end of file in for

loop.

"/usr/ports/Mk/bsd.port.mk", line 6574: Unclosed conditional/for loop
"/usr/ports/Mk/bsd.port.mk", line 6574: Unexpected end of file in for

loop.

1 open conditional:
  at line 1167 (evaluated to true)
make: fatal errors encountered -- cannot continue

Now, can anyone explain to me how I am going to get an updated source
(/usr/src) onto this machine, without resorting to (to me, totally
unnecessary) unconventional steps?

AFAICT, there is nothing in /usr/ports/UPDATING about this.
So much for POLA.
Bah.

References:
1) https://forums.freebsd.org/viewtopic.php?f=5&t=46291#p258936



--
Michelle Sullivan
http://www.mhix.org/



While I understandthe need to get rid of the old system, three needs ot be
a clear path for those wanting ot update old versions. I hit this yesterday
trying to upgrade a 9.0-RC2 system and it was a real pain.

Can't just do a checkout on an older machine and tar/rsync it over?

-Alfred
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

FreeBSD Port: mksh-r49_1

2014-08-26 Thread Brian N 

Hello, can mksh be updated to R50?  Thanks.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: I want to upgrade an old (8.3-RC2) FReeBSD installation, but can't install subversion

2014-08-26 Thread Kevin Oberman 
On Tue, Aug 26, 2014 at 2:19 PM, Michelle Sullivan 
wrote:

> And this is precisely why I think the killing of the old packaging
> system on Sept 1, is the wrong thing to do.
>
> If you don't have the new packaging system installed and setup by then,
> you're screwed... royally...
>
> Happened somewhere between 6.x and 7.x with the ports tree, pre 8.4...
> the list goes on
>
> FWIW Torfinn, get a amd64, 8.4 make binary (from the install disk) and
> manually copy it over (just /usr/bin/make ) backing up the original first.
>
> You'll find the ports tree will then work... well until Sept 1 when all
> hell breaks loose if you use anything but the quarterly SVN tree...
> and then you'll have 90 days more..
>
> Michelle
>
> Torfinn Ingolfsen wrote:
> > I have a machine which has an old installation of FreeBSD 8.3 on it:
> > root@kg-vm2# uname -a
> > FreeBSD kg-vm2 8.3-RC2 FreeBSD 8.3-RC2 #0: Sat Mar 24 16:15:47 UTC
> > 2012 r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC
> > amd64
> >
> > and I want to update it. Since FreeBSD this old doesn't have svnlite
> > installed, I fetch a ports tree (no, this machine didn't have one
> > already) and try to install the subversion port:
> > root@kg-vm2# cd /usr/ports/devel/subversion
> > root@kg-vm2# make install
> > Unknown modifier 't'
> >
> > "/usr/ports/Mk/bsd.port.mk", line 1727: Malformed conditional
> > (defined(USE_RC_SUBR) && ${USE_RC_SUBR:tu} != "YES")
> > Unknown modifier 't'
> >
> > Unknown modifier 't'
> >
> > Unknown modifier 't'
> >
> > "/usr/ports/Mk/bsd.sites.mk", line 956: Malformed conditional
> > (!empty(_PERL_CPAN_ID) && ${_PERL_CPAN_FLAG:tl} == "cpan")
> > Unknown modifier 't'
> >
> > Unknown modifier 't'
> >
> > "/usr/ports/Mk/bsd.port.mk", line 2858: Unclosed conditional/for loop
> > "/usr/ports/Mk/bsd.port.mk", line 2858: Unexpected end of file in for
> loop.
> >
> > "/usr/ports/Mk/bsd.port.mk", line 6574: Unclosed conditional/for loop
> > "/usr/ports/Mk/bsd.port.mk", line 6574: Unexpected end of file in for
> loop.
> >
> > make: fatal errors encountered -- cannot continue
> >
> > So I google a bit and find this[1] thread.
> > Hmm, ok let's try to install bmake then:
> > root@kg-vm2# cd /usr/ports/devel/bmake
> > root@kg-vm2# make install
> > Unknown modifier 't'
> >
> > Unknown modifier 't'
> >
> > Unknown modifier 't'
> >
> > Unknown modifier 't'
> >
> > Unknown modifier 't'
> >
> > "/usr/ports/Mk/bsd.sites.mk", line 956: Malformed conditional
> > (!empty(_PERL_CPAN_ID) && ${_PERL_CPAN_FLAG:tl} == "cpan")
> > Unknown modifier 't'
> >
> > Unknown modifier 't'
> >
> > "/usr/ports/Mk/bsd.port.mk", line 2858: Unclosed conditional/for loop
> > "/usr/ports/Mk/bsd.port.mk", line 2858: Unexpected end of file in for
> loop.
> >
> > "/usr/ports/Mk/bsd.port.mk", line 6574: Unclosed conditional/for loop
> > "/usr/ports/Mk/bsd.port.mk", line 6574: Unexpected end of file in for
> loop.
> >
> > 1 open conditional:
> >  at line 1167 (evaluated to true)
> > make: fatal errors encountered -- cannot continue
> >
> > Now, can anyone explain to me how I am going to get an updated source
> > (/usr/src) onto this machine, without resorting to (to me, totally
> > unnecessary) unconventional steps?
> >
> > AFAICT, there is nothing in /usr/ports/UPDATING about this.
> > So much for POLA.
> > Bah.
> >
> > References:
> > 1) https://forums.freebsd.org/viewtopic.php?f=5&t=46291#p258936
> >
>
>
> --
> Michelle Sullivan
> http://www.mhix.org/
>
>
While I understandthe need to get rid of the old system, three needs ot be
a clear path for those wanting ot update old versions. I hit this yesterday
trying to upgrade a 9.0-RC2 system and it was a real pain.
--
R. Kevin Oberman, Network Engineer, Retired
E-mail: rkober...@gmail.com
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

bsdadminscripts fixed!

2014-08-26 Thread Kevin Oberman 
Thank you for getting this port back up and running! I've really missed it.

Muchas gracias por conseguir este puerto vuelva a funcionar usted! Realmente
he perdido.
--
R. Kevin Oberman, Network Engineer, Retired
E-mail: rkober...@gmail.com
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Quarterly ports trees not getting security updates?

2014-08-26 Thread J David 
Hello,

When the quarterly ports trees were introduced, they were described as
including security, build, and runtime fixes for 3 months.

This is a great idea, and with 2014Q2 it seemed to work pretty well.
However, it doesn't seem like 2014Q3 is getting security fixes.

For example, the openssl port has never been updated since branch;
it's still on 1.0.1_13, which has 9 open CVE's against it.  Other
ports have similar issues (e.g. serf and subversion).

What could a non-expert such as myself do to help with this?  Is it
just a matter of trying to identify the relevant commits from the head
of the ports tree, or is there more to it?

Thanks!
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

what's up with portsmon?

2014-08-26 Thread Don Lewis 
What's going on with portsmon.freebsd.org these days?   A number of my
ports have been updated quite a while ago, but there isn't any updated
build status on portsmon.  For instance, devel/protobuf-c was updated
from version 0.15 to version 1.0.1 ten days ago on Sat Aug 16 21:04:52
2014 UTC.  Portsmon sees the new version of the port, but the packages
are still at 0.15 and there are no error logs indicating build failures.

I poked around on one of the pkg.freebsd.org, and stuff looks pretty old
there as well.  For instance, the timestamps of the files under
freebsd:10:x86:32/latest/ are 13-Aug-2014.  Some of the other OS/ARCH
combinations are a little bit newer, but only a day or so.  The
timestamps on the new_xorg directorys are 20-Aug, but the contents are
appear to be several days older than that.

But ... if I go to this page
 and select the
84amd64-default link, I end up at
.  If I then
click on the "logs/" link, I find a bunch of build logs dated
24-Aug-2014.  Looking at protobuf-c-1.0.1.log, it looks like the build
was a success.  If so, why isn't this reflected on the the status page
for protobuf-c, and isn't the new version of the package available on
the mirrors?

Other observations:

  It would probably be helpful if the individual port pages reported the
  status for the new_xorg versions.

  It would be nice if there was a way to find out what the ports build
  cluster was currently working on.  Things like the svn revision of the
  ports tree, what OS and ARCH versions were currently being built, and
  how far along the build was (basically what you see when you type ^T
  during a poudriere run), and what's next the the queue.

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: I want to upgrade an old (8.3-RC2) FReeBSD installation, but can't install subversion

2014-08-26 Thread Michelle Sullivan 
And this is precisely why I think the killing of the old packaging
system on Sept 1, is the wrong thing to do.

If you don't have the new packaging system installed and setup by then,
you're screwed... royally...

Happened somewhere between 6.x and 7.x with the ports tree, pre 8.4... 
the list goes on 

FWIW Torfinn, get a amd64, 8.4 make binary (from the install disk) and
manually copy it over (just /usr/bin/make ) backing up the original first.

You'll find the ports tree will then work... well until Sept 1 when all
hell breaks loose if you use anything but the quarterly SVN tree...
and then you'll have 90 days more..

Michelle

Torfinn Ingolfsen wrote:
> I have a machine which has an old installation of FreeBSD 8.3 on it:
> root@kg-vm2# uname -a
> FreeBSD kg-vm2 8.3-RC2 FreeBSD 8.3-RC2 #0: Sat Mar 24 16:15:47 UTC
> 2012 r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC
> amd64
>
> and I want to update it. Since FreeBSD this old doesn't have svnlite
> installed, I fetch a ports tree (no, this machine didn't have one
> already) and try to install the subversion port:
> root@kg-vm2# cd /usr/ports/devel/subversion
> root@kg-vm2# make install
> Unknown modifier 't'
>
> "/usr/ports/Mk/bsd.port.mk", line 1727: Malformed conditional
> (defined(USE_RC_SUBR) && ${USE_RC_SUBR:tu} != "YES")
> Unknown modifier 't'
>
> Unknown modifier 't'
>
> Unknown modifier 't'
>
> "/usr/ports/Mk/bsd.sites.mk", line 956: Malformed conditional
> (!empty(_PERL_CPAN_ID) && ${_PERL_CPAN_FLAG:tl} == "cpan")
> Unknown modifier 't'
>
> Unknown modifier 't'
>
> "/usr/ports/Mk/bsd.port.mk", line 2858: Unclosed conditional/for loop
> "/usr/ports/Mk/bsd.port.mk", line 2858: Unexpected end of file in for loop.
>
> "/usr/ports/Mk/bsd.port.mk", line 6574: Unclosed conditional/for loop
> "/usr/ports/Mk/bsd.port.mk", line 6574: Unexpected end of file in for loop.
>
> make: fatal errors encountered -- cannot continue
>
> So I google a bit and find this[1] thread.
> Hmm, ok let's try to install bmake then:
> root@kg-vm2# cd /usr/ports/devel/bmake
> root@kg-vm2# make install
> Unknown modifier 't'
>
> Unknown modifier 't'
>
> Unknown modifier 't'
>
> Unknown modifier 't'
>
> Unknown modifier 't'
>
> "/usr/ports/Mk/bsd.sites.mk", line 956: Malformed conditional
> (!empty(_PERL_CPAN_ID) && ${_PERL_CPAN_FLAG:tl} == "cpan")
> Unknown modifier 't'
>
> Unknown modifier 't'
>
> "/usr/ports/Mk/bsd.port.mk", line 2858: Unclosed conditional/for loop
> "/usr/ports/Mk/bsd.port.mk", line 2858: Unexpected end of file in for loop.
>
> "/usr/ports/Mk/bsd.port.mk", line 6574: Unclosed conditional/for loop
> "/usr/ports/Mk/bsd.port.mk", line 6574: Unexpected end of file in for loop.
>
> 1 open conditional:
>  at line 1167 (evaluated to true)
> make: fatal errors encountered -- cannot continue
>
> Now, can anyone explain to me how I am going to get an updated source
> (/usr/src) onto this machine, without resorting to (to me, totally
> unnecessary) unconventional steps?
>
> AFAICT, there is nothing in /usr/ports/UPDATING about this.
> So much for POLA.
> Bah.
>
> References:
> 1) https://forums.freebsd.org/viewtopic.php?f=5&t=46291#p258936
>   


-- 
Michelle Sullivan
http://www.mhix.org/

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [Patch] Using MACHINE_ARCH identifiers in pkg

2014-08-26 Thread olli hauer 
On 2014-08-26 18:01, Nathan Whitehorn wrote:
> On 08/18/14 15:02, olli hauer wrote:
>> On 2014-08-18 18:15, Nathan Whitehorn wrote:
>>> On 08/14/14 13:40, olli hauer wrote:
 On 2014-08-14 21:42, Bryan Drewery wrote:
> On 8/14/2014 2:38 PM, olli hauer wrote:
>> On 2014-08-14 17:35, Nathan Whitehorn wrote:
 ...

> Something I've mentioned to Bapt a few times is that pkg needs a way to
> have a list of accepted ABI strings. Then we could add both the old and
> the new style as accepted (internally) so that old and new repositories
> will continue to work.
>
 Ups, rollback is not possible after the client database was updated.

 Even by rollback and rebuild the package metadata the following error pops 
 up.

 ~/pkg-static.old_ABI update -f
 Updating repository catalogue
 pkg-static: Repository str has a wrong packagesite, need to re-create 
 database
 Fetching meta.txz: 100% of 584 B
 Fetching digests.txz: 100% of 43 kB
 Fetching packagesite.txz: 100% of 138 kB

 Adding new entries: 34%
 pkg-static: wrong architecture: FreeBSD:8:amd64 instead of freebsd:8:x86:64

 pkg-static: repository str contains packages with wrong ABI: 
 FreeBSD:8:amd64
 Adding new entries: 100%
 pkg-static: Unable to update repository str
>>>
>>> Hm. I'm not sure how to handle this. There are two places that emit hard 
>>> errors in such cases: pkg-add, which is fine since we have a workaround 
>>> there, and here. The check is at line 446 of libpkg/repo/binary/update.c 
>>> (you can comment it out for testing). For this one, there does not seem to 
>>> be any good solution and we need to find one since this is the same issue 
>>> you ran into the upgrade path.
>>>
>>> Here are the two options I see. They are similar to each other, and we 
>>> could do both for some time.
>>> 1. Make an intermediate pkg that is otherwise unaltered but doesn't have 
>>> this check during updates and keep it in the tree for some substantial 
>>> length of time so most people have it by the time we want upgrades to the 
>>> new ABI strings.
>>> 2. Set PKGNG_ALTABI globally on the ports tree for i386 and amd64 for some 
>>> period of time so that all built packages get the current ABI identifiers 
>>> rather than the new ones.
>>>
>>> Any preference here? Or other options?
>>
>> Hi Nathan,
>>
>> Your suggestion 2) could do the trick, at last for current ports.
>>
>> I will see if I can do some additional tests the next days, specially with 
>> mixed ABI strings in the packages.
>>
> 
> Did you have any chance to do the tests? I prepared a new version of the 
> patch at http://people.freebsd.org/~nwhitehorn/pkg-new-abi-v2.diff that marks 
> all built binary packages for i386 and amd64 with the freebsd:*:x86:* 
> identifiers and so should prevent the old version of pkg from bailing on a 
> repository with mixed ABI strings. Testing would be much appreciated.
> -Nathan


Hi Nathan,

if it is not to late I will setup the in next 24h two fresh builds (with / 
without your patch) and test again.

-- 
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: I want to upgrade an old (8.3-RC2) FReeBSD installation, but can't install subversion

2014-08-26 Thread Kurt Jaeger 
Hi!

> and I want to update it. Since FreeBSD this old doesn't have svnlite
> installed, I fetch a ports tree (no, this machine didn't have one
> already) and try to install the subversion port:
> root@kg-vm2# cd /usr/ports/devel/subversion
> root@kg-vm2# make install
> Unknown modifier 't'

Get the binary package from 8.4 and try to install it: (i386 or amd64?)

ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8.4-release/devel/subversion-static-1.7.9_1.tbz

This probably runs on 8.3-RC2.

-- 
p...@opsec.eu+49 171 3101372 6 years to go !
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

I want to upgrade an old (8.3-RC2) FReeBSD installation, but can't install subversion

2014-08-26 Thread Torfinn Ingolfsen 
I have a machine which has an old installation of FreeBSD 8.3 on it:
root@kg-vm2# uname -a
FreeBSD kg-vm2 8.3-RC2 FreeBSD 8.3-RC2 #0: Sat Mar 24 16:15:47 UTC
2012 r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC
amd64

and I want to update it. Since FreeBSD this old doesn't have svnlite
installed, I fetch a ports tree (no, this machine didn't have one
already) and try to install the subversion port:
root@kg-vm2# cd /usr/ports/devel/subversion
root@kg-vm2# make install
Unknown modifier 't'

"/usr/ports/Mk/bsd.port.mk", line 1727: Malformed conditional
(defined(USE_RC_SUBR) && ${USE_RC_SUBR:tu} != "YES")
Unknown modifier 't'

Unknown modifier 't'

Unknown modifier 't'

"/usr/ports/Mk/bsd.sites.mk", line 956: Malformed conditional
(!empty(_PERL_CPAN_ID) && ${_PERL_CPAN_FLAG:tl} == "cpan")
Unknown modifier 't'

Unknown modifier 't'

"/usr/ports/Mk/bsd.port.mk", line 2858: Unclosed conditional/for loop
"/usr/ports/Mk/bsd.port.mk", line 2858: Unexpected end of file in for loop.

"/usr/ports/Mk/bsd.port.mk", line 6574: Unclosed conditional/for loop
"/usr/ports/Mk/bsd.port.mk", line 6574: Unexpected end of file in for loop.

make: fatal errors encountered -- cannot continue

So I google a bit and find this[1] thread.
Hmm, ok let's try to install bmake then:
root@kg-vm2# cd /usr/ports/devel/bmake
root@kg-vm2# make install
Unknown modifier 't'

Unknown modifier 't'

Unknown modifier 't'

Unknown modifier 't'

Unknown modifier 't'

"/usr/ports/Mk/bsd.sites.mk", line 956: Malformed conditional
(!empty(_PERL_CPAN_ID) && ${_PERL_CPAN_FLAG:tl} == "cpan")
Unknown modifier 't'

Unknown modifier 't'

"/usr/ports/Mk/bsd.port.mk", line 2858: Unclosed conditional/for loop
"/usr/ports/Mk/bsd.port.mk", line 2858: Unexpected end of file in for loop.

"/usr/ports/Mk/bsd.port.mk", line 6574: Unclosed conditional/for loop
"/usr/ports/Mk/bsd.port.mk", line 6574: Unexpected end of file in for loop.

1 open conditional:
 at line 1167 (evaluated to true)
make: fatal errors encountered -- cannot continue

Now, can anyone explain to me how I am going to get an updated source
(/usr/src) onto this machine, without resorting to (to me, totally
unnecessary) unconventional steps?

AFAICT, there is nothing in /usr/ports/UPDATING about this.
So much for POLA.
Bah.

References:
1) https://forums.freebsd.org/viewtopic.php?f=5&t=46291#p258936
-- 
Regards,
Torfinn Ingolfsen
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

New message from SoundCloud PR

2014-08-26 Thread SoundCloud 
[letter.png]

Hey,

[1]SoundCloudPR sent you a message:

The SoundCloud Promotional Service offers Artists, DJ's, Singers and
   Managers a simple, cost-effective way to reach targeted followers,
   sales, comments, plays and downloads on SoundCloud. We target
   like-minded users who are interested in your new tracks, releases and
   sets.
   Artists that generate a lot of honest consistent feedbacks and traffic
   to their profiles are the ones who stand out from the crowd.

   To check this new service, go directly to the [2]SoundCloud Promotion
   Page

  [1eCW8gV]

   [3]SoundCloudPR

   [4]Promote your account

   [5]Unsubscribe

References

   Visible links
   1. http://bit.ly/scpromo
   2. http://bit.ly/scpromo
   3. http://bit.ly/scpromo
   4. http://bit.ly/scpromo
   5. mailto:soundcloud...@outlook.com?subject=NOMORE

   Hidden links:
   7. http://bit.ly/scpromo
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: SAT resolver problem - [CFT] SSP Package Repository available

2014-08-26 Thread Bryan Drewery 
On 8/26/2014 2:02 PM, Michael Jung wrote:
> On 2014-08-22 16:17, Bryan Drewery wrote:
>> On 8/22/2014 1:16 PM, mikej wrote:
>>> On , Bryan Drewery wrote:
 On 9/21/2013 5:49 AM, Bryan Drewery wrote:
> Ports now support enabling Stack Protector [1] support on FreeBSD 10
> i386 and amd64, and older releases on amd64 only currently.
>
> Support may be added for earlier i386 releases once all ports properly
> respect LDFLAGS.
>
> To enable, just add WITH_SSP=yes to your make.conf and rebuild all
> ports.
>
> The default SSP_CLFAGS is -fstack-protector, but -fstack-protector-all
> may optionally be set instead.
>
> Please help test this on your system. We would like to eventually
> enable
> this by default, but need to identify any major ports that have
> run-time
> issues due to it.
>
> [1] https://en.wikipedia.org/wiki/Buffer_overflow_protection
>

 We have not had any feedback on this yet and want to get it enabled by
 default for ports and packages.

 We now have a repository that you can use rather than the default to
 help test. We need your help to identify any issues before switching
 the
 default.

 This repository is available for:

 head
 10.0
 9.1,9.2,9.3

 It is not available for 8.4. If someone is willing to test on 8.4 I
 will
 build a repository for it.

 Place this in /usr/local/etc/pkgs/repos/FreeBSD_ssp.conf:

 FreeBSD: { enabled: no }
 FreeBSD_ssp: {
   url: "pkg+http://pkg.FreeBSD.org/${ABI}/ssp";,
   mirror_type: "srv",
   signature_type: "fingerprints",
   fingerprints: "/usr/share/keys/pkg",
   enabled: yes
 }

 Once that is done you should force reinstall packages from this
 repository:

   pkg update
   pkg upgrade -f

 Thanks for your help!
 Bryan Drewery
 On behalf of portmgr.
>>>
>>> I have been using this without issue on several machines until today.
>>>
>>> root@firewall:/usr/ports # pkg -v
>>> 1.3.6
>>> root@firewall:/usr/ports #
>>>
>>>
>>> Repositories:
>>>   FreeBSD_ssp: {
>>> url :
>>> "pkg+http://pkg.FreeBSD.org/freebsd:10:x86:64/ssp";,
>>> enabled : yes,
>>> mirror_type : "SRV",
>>> signature_type  : "FINGERPRINTS",
>>> fingerprints: "/usr/share/keys/pkg"
>>>   }
>>>
>>>
>>> root@firewall:/usr/ports # pkg update -f
>>> Updating repository catalogue
>>> pkg: http://pkg.FreeBSD.org/freebsd:10:x86:64/ssp/meta.txz: Not Found
>>> pkg: repository FreeBSD_ssp has no meta file, using default settings
>>> Fetching digests.txz: 100% of 1 MB
>>> Fetching packagesite.txz: 100% of 5 MB
>>>
>>> Adding new entries: 100%
>>> Incremental update completed, 23305 packages processed:
>>> 0 packages updated, 0 removed and 23305 added.
>>> root@firewall:/usr/ports # pkg install mdnsresponder
>>> Updating repository catalogue
>>> pkg: http://pkg.FreeBSD.org/freebsd:10:x86:64/ssp/meta.txz: Not Found
>>> pkg: repository FreeBSD_ssp has no meta file, using default settings
>>> FreeBSD_ssp repository is up-to-date
>>> All repositories are up-to-date
>>> Checking integrity... done (1 conflicting)
>>> pkg: Cannot solve problem using SAT solver:
>>> cannot install package mDNSResponder~net/mDNSResponder, remove it from
>>> request [Y/n]: y
>>> Checking integrity... done (0 conflicting)
>>> The most recent version of packages are already installed
>>> root@firewall:/usr/ports # uname -a
>>> FreeBSD firewall 10.0-STABLE FreeBSD 10.0-STABLE #0 r269366M: Fri Aug  1
>>> 00:35:49 EDT 2014 mikej@firewall:/usr/obj/usr/src/sys/GENERIC  amd64
>>> root@firewall:/usr/ports # date
>>> Fri Aug 22 14:12:30 EDT 2014
>>> root@firewall:/usr/ports #
>>>
>>> root@firewall:/usr/ports # pkg info | grep mdns
>>> root@firewall:/usr/ports #
>>>
>>> Regards,
>>>
>>> --mikej
>>
>> It looks like the (SSP) freebsd:10:x86:64 freebsd:11:x86:32 repositories
>> are stale from a month ago. Looking into why.
>>
>> Sadly this was not noticed and the instructions effectively will
>> downgrade packages. These 2 repositories have pkg-1.2 still as well.
> 
> 
> 
> Bryan,
> 
> Any update?  As you probably expect if I build the port locally with
> poudriere and install there is no issue.  I'm building with
> 
> WITH_SSP_PORTS=YES
> 
> in /etc/make.conf
> 
> Regards,
> 
> --mikej


The latest package set, along with pkg 1.3.7, should be getting
published later today.

As for the pkg issue with installing mDNSResponder, I am not 100% sure
it is fixed by new package set. We'll have to wait and see. There are
several issues to fix in the new pkg solver still.

-- 
Regards,
Bryan Drewery



signature.asc
Description: OpenPGP digital signature

Re: SAT resolver problem - [CFT] SSP Package Repository available

2014-08-26 Thread Michael Jung 

On 2014-08-22 16:17, Bryan Drewery wrote:

On 8/22/2014 1:16 PM, mikej wrote:

On , Bryan Drewery wrote:

On 9/21/2013 5:49 AM, Bryan Drewery wrote:

Ports now support enabling Stack Protector [1] support on FreeBSD 10
i386 and amd64, and older releases on amd64 only currently.

Support may be added for earlier i386 releases once all ports 
properly

respect LDFLAGS.

To enable, just add WITH_SSP=yes to your make.conf and rebuild all
ports.

The default SSP_CLFAGS is -fstack-protector, but 
-fstack-protector-all

may optionally be set instead.

Please help test this on your system. We would like to eventually 
enable
this by default, but need to identify any major ports that have 
run-time

issues due to it.

[1] https://en.wikipedia.org/wiki/Buffer_overflow_protection



We have not had any feedback on this yet and want to get it enabled 
by

default for ports and packages.

We now have a repository that you can use rather than the default to
help test. We need your help to identify any issues before switching 
the

default.

This repository is available for:

head
10.0
9.1,9.2,9.3

It is not available for 8.4. If someone is willing to test on 8.4 I 
will

build a repository for it.

Place this in /usr/local/etc/pkgs/repos/FreeBSD_ssp.conf:

FreeBSD: { enabled: no }
FreeBSD_ssp: {
  url: "pkg+http://pkg.FreeBSD.org/${ABI}/ssp";,
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/share/keys/pkg",
  enabled: yes
}

Once that is done you should force reinstall packages from this
repository:

  pkg update
  pkg upgrade -f

Thanks for your help!
Bryan Drewery
On behalf of portmgr.


I have been using this without issue on several machines until today.

root@firewall:/usr/ports # pkg -v
1.3.6
root@firewall:/usr/ports #


Repositories:
  FreeBSD_ssp: {
url : 
"pkg+http://pkg.FreeBSD.org/freebsd:10:x86:64/ssp";,

enabled : yes,
mirror_type : "SRV",
signature_type  : "FINGERPRINTS",
fingerprints: "/usr/share/keys/pkg"
  }


root@firewall:/usr/ports # pkg update -f
Updating repository catalogue
pkg: http://pkg.FreeBSD.org/freebsd:10:x86:64/ssp/meta.txz: Not Found
pkg: repository FreeBSD_ssp has no meta file, using default settings
Fetching digests.txz: 100% of 1 MB
Fetching packagesite.txz: 100% of 5 MB

Adding new entries: 100%
Incremental update completed, 23305 packages processed:
0 packages updated, 0 removed and 23305 added.
root@firewall:/usr/ports # pkg install mdnsresponder
Updating repository catalogue
pkg: http://pkg.FreeBSD.org/freebsd:10:x86:64/ssp/meta.txz: Not Found
pkg: repository FreeBSD_ssp has no meta file, using default settings
FreeBSD_ssp repository is up-to-date
All repositories are up-to-date
Checking integrity... done (1 conflicting)
pkg: Cannot solve problem using SAT solver:
cannot install package mDNSResponder~net/mDNSResponder, remove it from
request [Y/n]: y
Checking integrity... done (0 conflicting)
The most recent version of packages are already installed
root@firewall:/usr/ports # uname -a
FreeBSD firewall 10.0-STABLE FreeBSD 10.0-STABLE #0 r269366M: Fri Aug  
1
00:35:49 EDT 2014 mikej@firewall:/usr/obj/usr/src/sys/GENERIC  
amd64

root@firewall:/usr/ports # date
Fri Aug 22 14:12:30 EDT 2014
root@firewall:/usr/ports #

root@firewall:/usr/ports # pkg info | grep mdns
root@firewall:/usr/ports #

Regards,

--mikej


It looks like the (SSP) freebsd:10:x86:64 freebsd:11:x86:32 
repositories

are stale from a month ago. Looking into why.

Sadly this was not noticed and the instructions effectively will
downgrade packages. These 2 repositories have pkg-1.2 still as well.




Bryan,

Any update?  As you probably expect if I build the port locally with 
poudriere and install there is no issue.  I'm building with


WITH_SSP_PORTS=YES

in /etc/make.conf

Regards,

--mikej
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [Patch] Using MACHINE_ARCH identifiers in pkg

2014-08-26 Thread Nathan Whitehorn 

On 08/18/14 15:02, olli hauer wrote:

On 2014-08-18 18:15, Nathan Whitehorn wrote:

On 08/14/14 13:40, olli hauer wrote:

On 2014-08-14 21:42, Bryan Drewery wrote:

On 8/14/2014 2:38 PM, olli hauer wrote:

On 2014-08-14 17:35, Nathan Whitehorn wrote:

...


Something I've mentioned to Bapt a few times is that pkg needs a way to
have a list of accepted ABI strings. Then we could add both the old and
the new style as accepted (internally) so that old and new repositories
will continue to work.


Ups, rollback is not possible after the client database was updated.

Even by rollback and rebuild the package metadata the following error pops up.

~/pkg-static.old_ABI update -f
Updating repository catalogue
pkg-static: Repository str has a wrong packagesite, need to re-create database
Fetching meta.txz: 100% of 584 B
Fetching digests.txz: 100% of 43 kB
Fetching packagesite.txz: 100% of 138 kB

Adding new entries: 34%
pkg-static: wrong architecture: FreeBSD:8:amd64 instead of freebsd:8:x86:64

pkg-static: repository str contains packages with wrong ABI: FreeBSD:8:amd64
Adding new entries: 100%
pkg-static: Unable to update repository str


Hm. I'm not sure how to handle this. There are two places that emit hard errors 
in such cases: pkg-add, which is fine since we have a workaround there, and 
here. The check is at line 446 of libpkg/repo/binary/update.c (you can comment 
it out for testing). For this one, there does not seem to be any good solution 
and we need to find one since this is the same issue you ran into the upgrade 
path.

Here are the two options I see. They are similar to each other, and we could do 
both for some time.
1. Make an intermediate pkg that is otherwise unaltered but doesn't have this 
check during updates and keep it in the tree for some substantial length of 
time so most people have it by the time we want upgrades to the new ABI strings.
2. Set PKGNG_ALTABI globally on the ports tree for i386 and amd64 for some 
period of time so that all built packages get the current ABI identifiers 
rather than the new ones.

Any preference here? Or other options?


Hi Nathan,

Your suggestion 2) could do the trick, at last for current ports.

I will see if I can do some additional tests the next days, specially with 
mixed ABI strings in the packages.



Did you have any chance to do the tests? I prepared a new version of the 
patch at http://people.freebsd.org/~nwhitehorn/pkg-new-abi-v2.diff that 
marks all built binary packages for i386 and amd64 with the 
freebsd:*:x86:* identifiers and so should prevent the old version of pkg 
from bailing on a repository with mixed ABI strings. Testing would be 
much appreciated.

-Nathan
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

FreeBSD ports you maintain which are out of date

2014-08-26 Thread portscout 
Dear port maintainer,

The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you can
safely ignore the entry.

You will not be e-mailed again for any of the port/version combinations
below.

Full details can be found at the following URL:
http://portscout.freebsd.org/po...@freebsd.org.html


Port| Current version | New version
+-+
mail/amavis-logwatch| 1.51.02 | 1.51.03
+-+
mail/postfix-logwatch   | 1.40.00 | 1.40.01
+-+


If any of the above results are invalid, please check the following page
for details on how to improve portscout's detection and selection of
distfiles on a per-port basis:

http://portscout.freebsd.org/info/portscout-portconfig.txt

Thanks.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"