Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

synth just deleted 290 ports on my machine on second try ;)

102 views
Skip to first unread message

Mathias Picker

unread,
Mar 31, 2016, 2:26:08 PM3/31/16
to
Very funny, for a system that advertises as "just install and run".

What happened: I installed synth (out of curiosity) and did a sudo
synth upgrade-system on my FreeBSD 10.2-RELEASE-p9 system a few days
ago. Synth then build aboout 800 packages, then deleted many of them
again (???) citing a "failed dependency check", then installed a few
updated ones.

I started synth again yesterday to see if it was just something strange
in ports the first time, and it was allmost the same, building about
800 packages, deleting many of them, only now synth then had pkg delete
a few hundred installed packages on my machine. WTF? I mean, deleting
kdelibs and evolution is not a nice action.

The system was mostly using the FreeBSD repository before. I only build
password-store, blender and apache24 from ports, all because of some
non-standard settings.

Any tips on what to do now? Trying to reinstall evolution makes pkg
want to downgrade itself (1.6.4 to 1.6.2, which doesn't really work all
that well, it goes into and endless loop after pkg 1.6.2 is installed.
I've fixed this, but I guess the same will happen when I try to install
kde via pkg.

What can I do now, other than using portmaster to rebuild all ports?

Thanks, Mathias

P.S.: synth logs, terminal output and pkg info are at http://virtual
-earth.de/synth-logs.txz
_______________________________________________
freebs...@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-port...@freebsd.org"

Torsten Zuehlsdorff

unread,
Apr 1, 2016, 7:18:08 AM4/1/16
to
On 31.03.2016 20:20, Mathias Picker wrote:

> What can I do now, other than using portmaster to rebuild all ports?

You can use poudriere to rebuild all the ports and use its local
repository for pkg.

Greetings,
Torsten

Kevin Oberman

unread,
Apr 2, 2016, 2:18:03 AM4/2/16
to
On Fri, Apr 1, 2016 at 4:17 AM, Torsten Zuehlsdorff <
mailin...@toco-domains.de> wrote:

> On 31.03.2016 20:20, Mathias Picker wrote:
>
> What can I do now, other than using portmaster to rebuild all ports?
>>
>
> You can use poudriere to rebuild all the ports and use its local
> repository for pkg.
>
> Greetings,
> Torsten


But that's the whole point of synth. It exists to allow you to build
packages for customized ports without the heavier weight of poudriere.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkob...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683

Torsten Zuehlsdorff

unread,
Apr 4, 2016, 3:34:50 AM4/4/16
to
On 02.04.2016 08:17, Kevin Oberman wrote:
> On Fri, Apr 1, 2016 at 4:17 AM, Torsten Zuehlsdorff <
> mailin...@toco-domains.de> wrote:
>
>> On 31.03.2016 20:20, Mathias Picker wrote:
>>
>> What can I do now, other than using portmaster to rebuild all ports?
>>>
>>
>> You can use poudriere to rebuild all the ports and use its local
>> repository for pkg.
>>
>> Greetings,
>> Torsten
>
>
> But that's the whole point of synth. It exists to allow you to build
> packages for customized ports without the heavier weight of poudriere.

That is true. But that is the answer because you would not build
everything from the portstree.

This is quite easy. synth failed. Next option is poudriere. The other
option is to contact marino@ and report the issue and wait for the fix.
Till then you could not use your machines.

My answer gives you back a working machine, the possibility to report
the issue and wait for the issue. And at least switch back to synth
again. :)

Greetings,
Torsten
0 new messages