00:52:32 <ndut7> hi all l33t
05:53:47 <trisk> divansantana: see the inetconv(8) man page
05:59:00 <szilard> I just have noticed right now the smartos pkgsrc tree got updated.
10:02:00 <warden> szilard: thanks, I just updated a couple of pkgsrc zones. Sorry for the stupid and maybe OT question (I'm a newbie of pkgsrc): it's normal that 'pkgin upgrade' removes a package which is in the "keep" list?
10:02:34 <szilard> I haven't noticed behaviour like you have described.
10:05:35 <warden> just an example: the new matrix-synapse package needed py312-psycopg2, which in turns needed postgresql16-client. But its previous version needed postgresql14-client. So the upgrade command removed postgresql14-client in favor to postgresql16-client, and removed all packages which depended from the it! :(
10:06:45 <warden> I searched in pkgin(8), but I found nothing about recursive checking of dependencies during full pkgsrc upgrade
10:09:21 <warden> I read also pkg_add(1), maybe I should have run 'pkg_add -uu matrix-synapse' in order not to have my Synapse server removed? But sorry, this is a pkgsrc question, not related to OmniOS!
18:36:32 <m1ari> warden: that sounds like strange behaviour but it's been a while since I used pkgsrc. I can imagine that the later client might have a conflicts with type of dependency with the older client. But I'd hope a package manager gives some warning in that case rather than removing a lot of things.
20:58:31 <warden> I’ll try to reproduce that behavior in a test bed to better understand what happened, but I bet that the cause is in my poor knowledge of pkgsrc package management :)