In order to help someone build an "open source" project that was built with windows-only proprietary tools, I need to install Windows on a computer at least for a while. I think I spent at least an hour trying to create bootable media on someone else's windows computer before finding a comment buried somewhere that the windows media tool just silently fails to work with sandisk thumbdrives, with no information shown.
Compare that to Linux iso images that can just be written to a USB drive and still work (thanks to H. Peter Anvin's work many years ago) and work just fine on those same sandisk drives.
Just as the new KP.2 covid variant takes off in the US, North Carolina sends anti-masking legislation through the legislature and passes at least one chamber. We have some immoral legislators.
North Carolina gets some things quite right, but this is not one of them. 😬
@chrishuck They get this right for lockpicks. Locksport is legal here as long as you aren't remunerated in any way without being licensed, but using lockpicks to do crime is an additional count.
You'd think they could do this for masks too, but they explicitly rejected it. Republican senators said they didn't intend it to cover health reasons and said you should expect not to be cited (claiming that there had been no abusive use in 70 years prior), but still refused to carve out any form of exception.
How long has #FreeCAD had the TechDraw dimension repair tool? Have I been replacing instead of repairing dimensions for a long time needlessly? Will the TNP mitigations make it into TechDraw and make dimension repair infrequently needed?
@mcdanlj hopefully yes! TNP mitigation is there already, and will be enabled by default in 1.0. It will then affect just about everything in FreeCAD. But we'll need time to fully assess where it works well and where it needs further refinements.
I just spent an hour putting together a detailed bug report on a 100% repeatable SIGSEGV in a local build of #FreeCAD from a few hours ago, and before hitting submit, I pulled the latest code and rebuilt it.
I've finally built #FreeCAD for myself, with the TNP mitigation enabled. Now every time I see something cool in the @FreeCAD WIP Wednesday posts I can play with it without waiting for a new weekly build. ☺
In the meantime, I have learned also that I could have created a Fedora 38 container. But now I have Fedora Silverblue 40 as my host OS running a Fedora 39 container and a Debian Bookworm container, so now I am quite the cool kid.
I decided to try building #FreeCAD from source. I used a F39 toolbox on my #Fedora 40 #Silverblue and installed the prereqs; most from packages, but pyside2 from pip (inside the toolbox) since it hasn't been packaged in Fedora for years. The segfault I'm getting from libshiboken isn't illuminating to me. I could imagine a missing dependency on a package causing a segfault, or maybe no one is building FreeCAD on Fedora and it just doesn't work on F39. 🤔
Not clear that I'm close enough to the beaten path for this to be worth a bug report, though. Quite likely PEBCAK...
@garrett Yeah, it's the same pyside2 problem I ran into in toolbox. Pyside2 has been dropped from Fedora, I think that was because it's not working on current Python.
I think this is a temporary state, and when FreeCAD moves to Pyside6 along with the Qt6 framework, it will be easier. But that's not going to come before FreeCAD 1.0 I think.
So I think at least currently I'll start from a Debian container since @yorik is using Debian.
@yorik Building and running it in a debian:latest container is working, thank you! I used both shiboken and pyside as packaged, not using pip. The current docker build instructions are missing three packages. But one seems to have been intentionally removed, so I just put the information in github for someone who knows what's intended to decide what to do about it.
Want your Discourse community to join the list and help bring in new community members? There's a link at the bottom of the sidebar documenting how to join the party.
I'm a novice on Lattice2, so I'd appreciate testing of all the functionality of the workbench both on recent development builds and on stable FreeCAD. I want to make sure that the fix is complete and correct on both stable and development versions before suggesting that it is ready to merge.
If you use git to install workbenches, you can do something like this if you want to test and help:
cd .local/share/FreeCAD/Mod/lattice2<br></br>git remote add johnsonm git@github.com:johnsonm/Lattice2.git<br></br>git fetch johnsonm<br></br>git checkout johnsonm/mkj-attachment-support<br></br>
Feel free to comment on the pull request itself or here, I'll see it either way.
DeepSOIC gave me helpful feedback, and ultimately merged my PR and fixed a bug I introduced in the process. Lattice2 should work again on development builds of FreeCAD. 🎉
I'm on #Fedora#Silverblue 40, and I'm now seeing a lot of "No video with supported format and MIME type found" errors.
I don't have mozilla-openh264 installed, so I guess that might make sense? Let's fix that...
# rpm-ostree install mozilla-openh264<br></br>...<br></br>error: Could not depsolve transaction; 1 problem detected:<br></br> Problem: package noopenh264-0.1.0~openh264_2.4.0-1.fc40.x86_64 from @System conflicts with openh264 provided by openh264-2.4.0-2.fc40.x86_64 from fedora-cisco-openh264<br></br> - package openh264-2.4.0-2.fc40.x86_64 from fedora-cisco-openh264 obsoletes noopenh264 < 1:0 provided by noopenh264-0.1.0~openh264_2.4.0-1.fc40.x86_64 from @System<br></br> - package mozilla-openh264-2.4.0-2.fc40.x86_64 from fedora-cisco-openh264 requires openh264(x86-64) = 2.4.0-2.fc40, but none of the providers can be installed<br></br> - conflicting requests<br></br># rpm -qa | grep noopenh264<br></br>noopenh264-0.1.0~openh264_2.4.0-1.fc40.x86_64<br></br># rpm-ostree install --uninstall noopenh264 mozilla-openh264<br></br>error: Package/capability 'noopenh264' is not currently requested<br></br>
There's clearly something I don't understand here. I don't know how noopenh264 is installed but not requested and still causes a conflict. I must be alone in having this problem based on lack of bugs that I can find in RH's bugzilla.
I don't think I saw this problem on Silverblue 39, but I was using that for only a few days before rebasing on 40, and was previously on my "classic" Fedora 39 installation where it definitely wasn't showing up with the rpmfusion packages installed.
FreeCAD has plenty of paths in configuration. Some of them might not work and still need fixing. It would still be better than starting over entirely from scratch, speaking as a user.
Please feel free to describe specific examples where you feel that this would be damaging so we can have a conversation about specifics rather than sweeping generalities.
@siosm@swick@adamw@garrett@notting I'm not ignoring this, by the way — my idea is to use this thread of conversation to think through and do a better job of writing up a more coherent feature suggestion.
After being inflicted with this dubious feature for months, I've wondered whether Product Management in Google's Android group has a problem with child labor laws... 🙄
Monport spam has shown up with a new tactic. In response to someone asking for help with an Omtech machine, they wrote some vague "well try something else" and praised Monport tech support, and suggested reaching out to Monport for support. For an Omtech machine. The text appeared to be designed to poison consumer sentiment AI summaries to favor Monport.
I don't care whether this is currently considered fraud by a legal definition. It is clearly a morally corrupt attempt to manipulate buyers. Before you buy anything from #monport please consider whether you want to support this kind of behavior.
It's still less work to manually approve every legit post on Maker Forums about Monport than confirm and clean up all the arriving spam about Monport.
@aardvarksagus I'm making forward-looking suggestions here, not punishing anyone for having bought from them in the past.
But for others who are considering options for future purchases, they do exist at similar price points.
I suggest to those considering future purchases asking on Maker Forums Discourse where you can get advice from folks with years of experience, and some meaningful expertise.
I hoped that by copying the #restic cache to my new computer the first backup after the move would be as fast as normal. It's not; it has to re-read all the files.
But at least Restic doesn't store redundant copies of all the files! 🎉
@mcdanlj moving all your files to your new computer possibly changed their mtimes, so Restic felt compelled to check them again and thereby ignored the cache…
First papercut with #Silverblue — I have roughly forever kept a symlink /m → /media/johnsonm because I really don't like typing all that.
I built a local package with that symlink to get my symlink back, and then when I tried to install it immediately hit https://github.com/projectatomic/rpm-ostree/issues/233 which it says to "see" but that's not super useful.
As far as I can tell that's "u kant haz" and I'll have to retrain my fingers to something else. 😢
I have upgraded my personal laptop to #Fedora#Silverblue just in time for the upgrade to Fedora 40 to be an update in the background and then a trivial, quick reboot into the upgraded system with an option to roll back if something goes wrong.
I started this update in December, by starting with a new (larger) drive. I put it into a USB-3 NVME carrier, attached it to a VM, and did an install and updates until it looked like I got the software I wanted complete.
Then an unrelated hardware failure made me back-burner it until tonight. I booted the VM, did a quick rpm-ostree upgrade, and rebooted the VM into the latest release. Four months of updates and it was fast and trivial. Copied my home directory over from the old drive to the new drive, popped it in, and I'm up and running.
I'm really looking forward to not watching minutes of updates scroll by with the system unusable at the boot screen.
And if I need any files from the old install, I have the old drive in the USB-3 NVME carrier. ☺
Huh. I have totally done this, and I'll bet that at least one broken tap was a result. I thought I didn't need to make some tap holders. But I was wrong. One more rite of passage after the tap followers I made!
@mcdanlj I agree that the direct drive is a nice approach but this isn't a good test. The loss of concentricity seen in the t-handle is because he has the tap extended much farther out of the t-handle than necessary and he doesn't show how he's driving it. I was taught to hold and turn both sides of the t-handle, apply a gentle force toward the work, and to use the follower as just a starting guide and a distance signal. I've seen many successfully tapped tiny holes this way. It's all technique.