<jaeger>
The original portdb automatically hides repos which fail to sync
<jaeger>
Mine doesn't
<jaeger>
I bet that's most or all of the difference
<SiFuh>
Yet yours has less
<SiFuh>
Oh sorry, idiot I am
<jaeger>
how do you figure? 4700 is still > 4118 last I checked :D
<SiFuh>
:-P
<jaeger>
I was very confused, heh
<SiFuh>
Hah, sorry for your confusion :-P
<jaeger>
All good. If the portdb has a real issue I want to fix it, so just had to make sure I was understanding
<SiFuh>
Understoor
<SiFuh>
*d
<farkuhar>
jaeger: isn't the original portdb also different from yours in that it only supports httpup and rsync? If a repository is only accessible by git, then it shows up on the unofficial portdb but not the official one.
<farkuhar>
sigma's repository, for example.
<SiFuh>
.. and bubby
<SiFuh>
Discrimination!
<SiFuh>
farkuhar: good catch.
<SiFuh>
Guess jaeger has a fix now ;-)
<jaeger>
yeah, that's correct
<SiFuh>
Mine has no issue since I provide both httpup and git
<SiFuh>
But I prefer the git engine, it is much faster for github/gitlab and other git repos
<ukky>
Hi! What is the recomendation on full system update from sources? There are 153 packages to update after fresh install.
<ente`>
compiler party \o/
pitill0 has quit [Ping timeout: 246 seconds]
pitillo has quit [Ping timeout: 264 seconds]
ppetrov^ has quit [Quit: Leaving]
<jaeger>
ukky: the usual way is 'prt-get sysup' after updating your ports
<jaeger>
Then use rejmerge to update config files and revdep to check that linking didn't break