Re: Unable to update repository Synth

[Baho Utot]

On 06/10/17 17:29, Jonathan Chen wrote:

On 11 June 2017 at 01:13, Bob Willcox  wrote:

On Sat, Jun 10, 2017 at 10:14:46AM +1200, Jonathan Chen wrote:

On 10 June 2017 at 05:02, Bob Willcox  wrote:

I am running the drm-next-4.7 and when I ran synth recently on my system
up update the ports and at the end of the run received these errors:

pkg: wrong architecture: freebsd:10:x86:64 instead of FreeBSD:12:amd64
pkg: repository Synth contains packages with wrong ABI: freebsd:10:x86:64
Processing entries: 100%
Unable to update repository Synth
Error updating repositories!
Unfortunately, the system upgrade failed.


synth is complaining that one or more of the packages in the
configuration's package directory has packages built for
FreeBSD10/amd64 instead of FreeBSD12/amd64. If you have upgraded from
FreeBSD 10 to FreeBSD 12, you must remove all the packages that have
been built previously.


Are these the packages that currently reside in the repository?


Yes.


Is there some way to list the packages that are the problem?


A simple way, no. You'd have to unpack each package and inspect the
manifest file to determine the package's abi.


If not, can I simply delete all of the respository packages?


This is the easiest thing to do, and would be my recommendation. synth
will rebuild all the packages for your installed ports.

Cheers.



mkdir   package/repo.backup
mv  package/repo package/repo.backup
mkdir   package/repo
synth   prepare-system
synth   rebuild-repository
pkg update
pkg upgrade


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

Re: Unable to update repository Synth

[Bob Willcox]

On Sun, Jun 11, 2017 at 09:29:14AM +1200, Jonathan Chen wrote:
> On 11 June 2017 at 01:13, Bob Willcox  wrote:
> > On Sat, Jun 10, 2017 at 10:14:46AM +1200, Jonathan Chen wrote:
> >> On 10 June 2017 at 05:02, Bob Willcox  wrote:
> >> > I am running the drm-next-4.7 and when I ran synth recently on my system
> >> > up update the ports and at the end of the run received these errors:
> >> >
> >> > pkg: wrong architecture: freebsd:10:x86:64 instead of FreeBSD:12:amd64
> >> > pkg: repository Synth contains packages with wrong ABI: freebsd:10:x86:64
> >> > Processing entries: 100%
> >> > Unable to update repository Synth
> >> > Error updating repositories!
> >> > Unfortunately, the system upgrade failed.
> >>
> >> synth is complaining that one or more of the packages in the
> >> configuration's package directory has packages built for
> >> FreeBSD10/amd64 instead of FreeBSD12/amd64. If you have upgraded from
> >> FreeBSD 10 to FreeBSD 12, you must remove all the packages that have
> >> been built previously.
> >
> > Are these the packages that currently reside in the repository?
> 
> Yes.
> 
> > Is there some way to list the packages that are the problem?
> 
> A simple way, no. You'd have to unpack each package and inspect the
> manifest file to determine the package's abi.
> 
> > If not, can I simply delete all of the respository packages?
> 
> This is the easiest thing to do, and would be my recommendation. synth
> will rebuild all the packages for your installed ports.

Thanks Jonathan. That's what I'll do then...  :)

Bob

-- 
Bob Willcox| Lawsuit, n.: A machine which you go into as a pig and
b...@immure.com |come out as a sausage.
Austin, TX |-- Ambrose Bierce
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Unable to update repository Synth

[Jonathan Chen]

On 11 June 2017 at 01:13, Bob Willcox  wrote:
> On Sat, Jun 10, 2017 at 10:14:46AM +1200, Jonathan Chen wrote:
>> On 10 June 2017 at 05:02, Bob Willcox  wrote:
>> > I am running the drm-next-4.7 and when I ran synth recently on my system
>> > up update the ports and at the end of the run received these errors:
>> >
>> > pkg: wrong architecture: freebsd:10:x86:64 instead of FreeBSD:12:amd64
>> > pkg: repository Synth contains packages with wrong ABI: freebsd:10:x86:64
>> > Processing entries: 100%
>> > Unable to update repository Synth
>> > Error updating repositories!
>> > Unfortunately, the system upgrade failed.
>>
>> synth is complaining that one or more of the packages in the
>> configuration's package directory has packages built for
>> FreeBSD10/amd64 instead of FreeBSD12/amd64. If you have upgraded from
>> FreeBSD 10 to FreeBSD 12, you must remove all the packages that have
>> been built previously.
>
> Are these the packages that currently reside in the repository?

Yes.

> Is there some way to list the packages that are the problem?

A simple way, no. You'd have to unpack each package and inspect the
manifest file to determine the package's abi.

> If not, can I simply delete all of the respository packages?

This is the easiest thing to do, and would be my recommendation. synth
will rebuild all the packages for your installed ports.

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

Re: poudriere cross building to arm64.aarch64: Don't know how to make native-xtools

[Marcin Cieslak]

On Sat, 10 Jun 2017, Bryan Drewery wrote:

> On 6/10/17 1:14 PM, Marcin Cieslak wrote:
> > When running poudriere 3.1.17_1 on FreeBSD 11.1-PRERELEASE r319534 on amd64:
> > 
> > poudriere jail -c -j ksh-test-aarch64 -m svn -x -v stable/11 -a 
> > arm64.aarch64
> > 
> > I am getting an error that "make native-xtools" does not seem to be a 
> > failed target.
> > 
> > Unfortunately, I cannot see the state of the filesystem when it fails, 
> > because
> > zfs dataset gets removed on failure.
> > 
> > Any ideas where to look?
> > 
> > Marcin
> > 
> 
> It is trying to run 'make native-xtools' in your *host* /usr/src.  You
> need a source checkout matching your current system there and having
> already done a 'make buildworld' for it.
> 
> This is a bug in the native-xtools build that poudriere is working
> around until it is fixed.

Thank you, I am using poudriere in a small Xen VM which didn't even had 
/usr/src or /usr/obj
mounted.

Marcin

smime.p7s
Description: S/MIME Cryptographic Signature

Re: poudriere cross building to arm64.aarch64: Don't know how to make native-xtools

[Bryan Drewery]

On 6/10/17 1:14 PM, Marcin Cieslak wrote:
> When running poudriere 3.1.17_1 on FreeBSD 11.1-PRERELEASE r319534 on amd64:
> 
> poudriere jail -c -j ksh-test-aarch64 -m svn -x -v stable/11 -a arm64.aarch64
> 
> I am getting an error that "make native-xtools" does not seem to be a failed 
> target.
> 
> Unfortunately, I cannot see the state of the filesystem when it fails, because
> zfs dataset gets removed on failure.
> 
> Any ideas where to look?
> 
> Marcin
> 

It is trying to run 'make native-xtools' in your *host* /usr/src.  You
need a source checkout matching your current system there and having
already done a 'make buildworld' for it.

This is a bug in the native-xtools build that poudriere is working
around until it is fixed.

-- 
Regards,
Bryan Drewery



signature.asc
Description: OpenPGP digital signature

poudriere cross building to arm64.aarch64: Don't know how to make native-xtools

[Marcin Cieslak]

When running poudriere 3.1.17_1 on FreeBSD 11.1-PRERELEASE r319534 on amd64:

poudriere jail -c -j ksh-test-aarch64 -m svn -x -v stable/11 -a arm64.aarch64

I am getting an error that "make native-xtools" does not seem to be a failed 
target.

Unfortunately, I cannot see the state of the filesystem when it fails, because
zfs dataset gets removed on failure.

Any ideas where to look?

Marcin

smime.p7s
Description: S/MIME Cryptographic Signature

Re: Unable to upgrade from Samba43 to Samba44 or Samba45

[Dimitry Andric]

On 10 Jun 2017, at 06:56, Stefan Esser  wrote:
> 
> Am 08.06.17 um 21:15 schrieb Dimitry Andric:
>> On 8 Jun 2017, at 20:35, Mark Knight  wrote:
>>> 
>>> On 08/06/2017 18:35, Dimitry Andric wrote:
 I'm guessing that it is confused by an existing samba installation.  Try
 removing all other samba installations before attempting to build this
 port.
>>> 
>>> Having followed an off-list suggestion to create a package (thanks) as a 
>>> backup, I removed samba43 and established that your "guess" was right. 
>>> Thank you!
>>> 
>>> Presumably this implies a bug in the port?
>> 
>> Not really, more a deficiency in portmaster.  The port itself is marked
>> as conflicting with any other samba port:
>> 
>> CONFLICTS?= *samba3[2-6]-3.* samba4-4.0.* samba4[1-356]-4.* 
>> p5-Parse-Pidl-4.*
>> 
>> E.g., you should normally not be able to build it when samba43 is
>> installed.  Probably, portmaster is overriding this safety belt somehow.
> 
> I have always understood CONFLICTS to indicate, that some port
> can not be *installed* at the same time as some of the ports listed
> as conflicting.

In fact, you cannot even download the port sources in such a case, e.g:

$ make -C /usr/ports/net/samba44 fetch

===>  samba44-4.4.14 conflicts with installed package(s):
  samba46-4.6.4

  They install files into the same place.
  You may want to stop build with Ctrl + C.


> Building such a port while a conflicting version is installed, is
> possible most of the time. If such a build fails, it is most ofter
> due to the build preferring the already installed headers over those
> provided with the new version (i.e. a wrong ordering of include
> paths).

Yes, this is apparently one of the reasons lang/rust even conflicts with
*itself*.  There seems to be something very broken in its build process,
so that it cannot build correctly if any of its files are installed on
the system.

That said, things like this could probably be solved by adding separate
CONFLICTS_BUILD, CONFLICT_FETCH and so on, but it makes it all rather
complicated.

-Dimitry



signature.asc
Description: Message signed with OpenPGP

Re: Unable to update repository Synth

[Bob Willcox]

On Sat, Jun 10, 2017 at 10:14:46AM +1200, Jonathan Chen wrote:
> On 10 June 2017 at 05:02, Bob Willcox  wrote:
> > I am running the drm-next-4.7 and when I ran synth recently on my system
> > up update the ports and at the end of the run received these errors:
> >
> > pkg: wrong architecture: freebsd:10:x86:64 instead of FreeBSD:12:amd64
> > pkg: repository Synth contains packages with wrong ABI: freebsd:10:x86:64
> > Processing entries: 100%
> > Unable to update repository Synth
> > Error updating repositories!
> > Unfortunately, the system upgrade failed.
> 
> synth is complaining that one or more of the packages in the
> configuration's package directory has packages built for
> FreeBSD10/amd64 instead of FreeBSD12/amd64. If you have upgraded from
> FreeBSD 10 to FreeBSD 12, you must remove all the packages that have
> been built previously.

Are these the packages that currently reside in the repository?

Is there some way to list the packages that are the problem?

If not, can I simply delete all of the respository packages?

Thanks,
Bob

> 
> Cheers.
> -- 
> Jonathan Chen 

-- 
Bob Willcox| Lawsuit, n.: A machine which you go into as a pig and
b...@immure.com |come out as a sausage.
Austin, TX |-- Ambrose Bierce
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: bapt@ back on portmgr

[Thomas Mueller]

from Matthew Seaman and my previous post:

> > But what is happening with synth, supposed to make portupgrade and
> > portmaster obsolete?
> Synth is still being actively developed but the author is now working
> primarily on DFly.  There is a new maintainer for the synth port who
> will be porting the latest updates to FreeBSD, much like almost any
> other piece of software in the ports.

> At the moment there is a problem with synth on recent FreeBSD HEAD due
> to not having a working ada compiler.  This will be solved eventually as
> the bugs in various toolchains get worked out.

My understanding is that the trouble is related to the change to 64-bit inodes 
on FreeBSD HEAD.

lang/gcc5-aux and gcc6-aux won't build.

How are users supposed to know if and when this is fixed?

I looked in Makefile for ports-mgmt/synth and lang/gcc6-aux and gcc5-aux, and 
there was no indication of anything amiss.

There ought to be a BROKEN notice in the Makefile to save users from the 
exercise in frustration.

For now, I am not doing anything on FreeBSD HEAD; updating 11.1-PRERELEASE 
(stable branch) instead.


Tom

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