Anton Hvornum

Workaround is obviously to `dd` the affected disk.

Could it be that it's in use? Mounted or otherwise?

Could you try: `# python -c "with open('/dev/yourDevice', 'wb') as p:; p.write(bytearray(1024))"` And if that fails, which it should, try: `# dd if=/dev/zero of=/dev/yourDevice bs=1 count=1024` And if that fails,...

Weird, the first command is just a copy paste from our source code oÔ. I can give it a try with vmware workstation or something.

> Generally I am wondering why these files live in here at all and why this has not been a merge request towards the package repository instead: It's because: ```...

Thank you for bringing this to our attention, this will be fixed!

We created a `/boot` partition with a size of `513 MiB` by default. The only time we do not do this, is if you are dual booting Windows. In which...

In spirit of other [Red Hat communications *(molecule#4067)*](https://github.com/ansible/molecule/discussions/4067), as a packager I would very much appreciate if we could get [v3.13.0](https://github.com/dcantrell/pyparted/releases/tag/v3.13.0) pushed to PyPi.

Tbh setting up a GitHub runner that does PyPi publishing for you is the smarter way from what I'm hearing. Our runner isn't the gold standard, but it works: https://github.com/archlinux/archinstall/blob/master/.github/workflows/python-publish.yml...

The pypi docs for local publishing was a bit meh to follow. Perhaps it's tricky to get the local conf sorted?