00:24:28 <nahamu> uh, copy pasta from other manifests? :(
00:24:52 <bahamat> pjustice: I use smfgen, but it doesn't cover all cases.
00:25:01 <nahamu> https://github.com/TritonDataCenter/smfgen
00:25:11 <bahamat> And...I really wish I had a copy of manifold :-/
00:25:25 <nahamu> I probably have a copy lying around. what happened to it?
00:26:08 <bahamat> Looks like the author just deleted the repo and package.
00:27:55 <nahamu> ah. I don't have the repo, just an installed package.
00:28:16 <rmustacc> What was it written in?
00:28:24 <nahamu> probably lots of copies in the pkgsrc repos
00:28:26 <nahamu> python
00:28:37 <rmustacc> If you have it, even though you may not have the history, you can still probably repackage it.
00:28:49 <nahamu> *copies in the package repos, not of the upstream repo
00:28:58 <nahamu> yes, we could certainly resurrect it if need be.
00:29:03 <rmustacc> Yeah, I was just trying to check if it was in there (but unfortunately the index isn't loading)
00:29:14 <bahamat> Yeah, I don't have a copy of it anywhere.
00:29:40 <nahamu> that's because you're too polite to poke around in customer instances :)
00:29:46 <bahamat> Oh, hey, it's in pkgsrc!
00:29:50 <nahamu> yes
00:30:14 <nahamu> sorry, I thought I said that. I must not have been clear.
00:30:48 <bahamat> You may have, I've got my attention in like 6 places right now :-)
00:31:30 <nahamu> haha
00:38:43 <nahamu> bahamat: if for some reason you have trouble finding a copy, let me know.
00:52:43 <pjustice> There's a python package listed on pypi that hasn't been updated since like 2009, and has python2 behavior
00:58:42 <pjustice> i.e. you can just pip install manifold, more or less
00:58:53 <pjustice> Then set about fixing it. :)
01:09:46 <nahamu> wait, what about this version? https://github.com/timotheosh/Manifold
01:13:39 <bahamat> I guess we need to figure out how to et that into pypi
02:56:57 <pjustice> Oh, nice.
06:44:14 <jperkin> yeh I just copy/paste from existing manifests I've written for pkgsrc
06:45:00 <jperkin> one of the things I wasn't so keen about with the generation tools is the format they use, I like to write manifests in the same style as 'svccfg export' so that you can easily diff to see changes
13:14:46 <pjustice> The plethora of blank lines isn't ideal.
13:29:21 <openstandards> Hi all, thank you for the help in getting my mellanox cards working flashed the cards with a newer firmware and seems a lot better now
13:30:47 <openstandards> I've enabled link link aggregation and seems good, 
16:47:49 <openstandards> Ok
17:01:25 <Smithx10> openstandards:  what card?
17:02:01 <openstandards> mellanox connectx-4  
17:38:13 <papertigers> jperkin: are there no bootstrap pkgsrc tars for anything 2023Q# ?
17:48:37 <jperkin> papertigers: no I stopped doing non-Q4 builds a number of years ago
17:50:58 <papertigers> jperkin: ah, didn't realize that I guess.  Do the Q4 builds get upates until the following Q4 update comes out?
17:51:33 <jperkin> for important security fixes yeh, trunk is what most people should use
17:52:24 <papertigers> perfect; best thing to do is take note of whats installed and do a fresh trunk bootstrap and reinstall what I need?
17:58:16 <jperkin> yeh if you need to, pkgin export / pkgin import can help with that
18:17:09 <papertigers> jperkin: oh neat, I had not used that before.  Thanks -- I now have my zone updated from 2022Q4