Titties and beer?
Titties and beer?
Before I bother to submit more bug reports for this pile of manure know as Os3.2 that is release by the esteemed enterprise of Ben “come drink beer with me or we meet in court” Hermans, I want to know if there’s any point - are there any masochist Hyperion monkeys even reading this?
Re: Titties and beer?
sure, but as they are monkeys, they can't respond.
Re: Titties and beer?
Charming as usual.
Go ahead and submit them. They are being read and will be fixed if possible.
e.g. The issue with a crash when setting a background on the screen itself has been fixed and will be in the next release.
Go ahead and submit them. They are being read and will be fixed if possible.
e.g. The issue with a crash when setting a background on the screen itself has been fixed and will be in the next release.
Re: Titties and beer?
More titties and beer is needed!!
Can someone please explain why it is that many (but not all!) of the binaries of 3.2.2 update are same version string as in 3.2 and 3.2.1, yet checksum and file size are different? Because they are now built with updated SDK/NDK/Toolchain, I presume - but this creates a maintenance and support headache - it would be MUCH BETTER if all components that are rebuilt with new toolchain also AT LEAST have their build date update, if not the version string bumped.
Now we have to live with stuff like...
- oh I have this weirdness happens with icon.library 47.5, it doesn't happen with 47.4
- ok, which icon.library 47.5?
- what do you mean?
- the icon.library from 3.2.1, or the one from 3.2.2?
- It just says icon.library 47.5 (28.May.21) - how do I know??
- if md5 checksum ends with e102 it is 3.2.1, if it ends with 3a8e it is 3.2.2
- whaaat?
Can someone please explain why it is that many (but not all!) of the binaries of 3.2.2 update are same version string as in 3.2 and 3.2.1, yet checksum and file size are different? Because they are now built with updated SDK/NDK/Toolchain, I presume - but this creates a maintenance and support headache - it would be MUCH BETTER if all components that are rebuilt with new toolchain also AT LEAST have their build date update, if not the version string bumped.
Now we have to live with stuff like...
- oh I have this weirdness happens with icon.library 47.5, it doesn't happen with 47.4
- ok, which icon.library 47.5?
- what do you mean?
- the icon.library from 3.2.1, or the one from 3.2.2?
- It just says icon.library 47.5 (28.May.21) - how do I know??
- if md5 checksum ends with e102 it is 3.2.1, if it ends with 3a8e it is 3.2.2
- whaaat?