<Not-ff83>
[haikuports/haikuports] davidkaroly 340bcad - stress-ng: bump to version 0.14.06 (#7240)
rennj has quit [Ping timeout: 480 seconds]
rennj has joined #haiku
rennj has quit [Ping timeout: 480 seconds]
Begasus has joined #haiku
<Begasus>
g'morning peeps
<Duggan>
greetings, earth creature
<Begasus>
howdy Duggan :)
<Duggan>
howdy
<Duggan>
long time
<Begasus>
indeed, how are things there
<Duggan>
doing alright, just work as usual... got a little more free time these days, I figured I'd try to do something productive
<Duggan>
how about yourself?
<Begasus>
still busy with the dogs and work
<Duggan>
fun hehe
<Duggan>
I forgot how much of a pain it is to get everything set up just so in a fresh install
<Begasus>
I did 2 thubmdrives install (32bit and 64bit) with default setup, if need be I can use those for a fresh install, saves me that pain :)
<Duggan>
haha, well, it's getting the repos really and getting a build set up
<Duggan>
and just plain being out of the loop and not seeming able to do the simplest tasks
<Begasus>
I got those setup on another partition so I don't need to adjust/re-download those :)
<Begasus>
only thin is doing a full-sync after a fresh install
<Duggan>
well I lost the machine I used to work on
<Duggan>
I think this is the first real try I've given it since
<Duggan>
so everything's fresh
<Duggan>
that being said, I've built somewhat of a small supercomputer and I can't wait to see how fast it can build lol
rennj has joined #haiku
<Begasus>
having a machine running Haiku if fine enough for me, doesn't need to be a blaster (though for some builds it would be nice to have) :)
<Duggan>
it's a gaming rig, I'm running in hyper-v
Begasus_32 has joined #haiku
<Duggan>
between an SSD drive (first I've had), 64 gigs of ram and an intel 12gen core i9 (24 logical cores), it's somewhat of a beast
<Begasus>
whoot!
<Duggan>
I only gave the vm 16 gigs of ram and 16 cores... I think that should be enough... for now...
<Duggan>
actually have 3 vms set up and they all share the same 3 drives so I can install/copy across installs
<Duggan>
across vms*
<Begasus>
that handy :)
<Begasus>
I use (when running VBox) one shared drive for that too
<Begasus>
but now running native
<Duggan>
I only ever ran native before... all my attempts at running in a VM were highly disappointing
<Duggan>
I actually have a laptop that i could dedicate to it, but there's that uefi security garbage I need to get around... there's a way to do it, I've done it for a different OS for reasons, but that was a couple years ago and I forgot the tool I used to do it
<Begasus>
using an external drive here, so didn't fiddle with uefi
<Duggan>
I couldn't boot off of a stick.... I suspect it was because of the security junk
<Duggan>
you know... supposed to have that valid OS key that microsoft approves of and all...
<Begasus>
got a partition setup and Haiku is installed there, still haven't manage to get uefi to work here
<Duggan>
ah
<Duggan>
and hyper-v is blocking ctrl+alt+up and down.... so I can only use horizontal workspaces :/
<Duggan>
and I forgot scroll wheels don't work :''''(
<Begasus>
can't you use Alt+Fn keys to swith workspaces?
<Begasus>
I still use it like that
<Duggan>
I didn't know :/ lol
<Duggan>
it's kind of the same really, the spatial direction is irrelevant
<Begasus>
One of the things I liked in BeOS :)
<Duggan>
what I liked was how blazing fast, stable, and reliable it was on the metal it was running on.... it literally amazed me lol
<Begasus>
Ctrl-Alt-arrow is the linux way :P
<Begasus>
right!
<Duggan>
well that's how I always did it... I'm not really a linux user...
<Duggan>
once every few years maybe, but never as frequently as Haiku
<Begasus>
It's the main OS on this laptop
<Duggan>
cool.... not that I haven't used it... everything's windows here so that's what I use
<Begasus>
Windows still on the other laptop, but hardly boot into it
<Duggan>
I'm a .net dev and that's all there is around here... east coast (US) problems lol
<Duggan>
west coast is all linux
<Begasus>
didn't know that :)
<Duggan>
yep... nobody seems to know why, that's just how it is
<x512[m]>
Somebody tried to run .NET on Haiku...
<Begasus>
k, build started for pythonn3.10
<Begasus>
some mentions of mono also I thought x512[m] (not into those so don't know anything there) :)
<Duggan>
x512[m] I mean, it would be nice.... from my perspective...
<Duggan>
don't think it'd work too well without a whole lot of work
<x512[m]>
There is official .NET UNIX version from Microsoft.
<Duggan>
yeah true
<Duggan>
ok, about to jam... giving it 24 threads, lets see how long this takes...
<Duggan>
nah, 32.... lol
<Duggan>
aw man, forgot it has to download a bunch of stuff....
<Begasus>
hehe
nephele has joined #haiku
<nephele>
you can use a passwordtoken fine for https with github
<nephele>
unless they changed something reall recently...
<Not-ff83>
[haiku/haikuwebkit] xeenon 829b721 - WebRTC build fixes needed since adding new files to Sources.txt.
<Not-ff83>
[haiku/haikuwebkit] cdumez 4500a5a - Land stubs for the Screen Wake Lock API
<Not-ff83>
[haiku/haikuwebkit] alanbujtas 392ebdc - [LFC][IFC] Do no try to break before a whitespace content when "line-break: after-white-space" is present
<Not-ff83>
[haiku/haikuwebkit] ... and 246 more commits.
<LinuxUserHaiku>
@Not-ff83 hi!
<augiedoggie>
Not-ff83 isn't an actual person, it's just a bot
frkzoid has quit [Ping timeout: 480 seconds]
<LinuxUserHaiku>
oh
rennj has quit [Ping timeout: 480 seconds]
AlaskanEmily has quit [Remote host closed the connection]
<nekobot>
[haiku/haiku] eb198a09e940 - checkstyle.py: Python 3 compatibility, part two.
matt3 has joined #haiku
<LinuxUserHaiku>
@matt3 hi!!!!!
<matt3>
hi LinuxUserHaiku
<matt3>
peace
<LinuxUserHaiku>
@matt3 nice to meet you'
<matt3>
hi LinuxUserHaiku : nice to meet you too !!!
<LinuxUserHaiku>
@matt3 did you know what's Samsung DeX
<matt3>
no ...
<LinuxUserHaiku>
@matt3 Samsung DeX is desktop mode of android
<matt3>
ah, nice ...
<LinuxUserHaiku>
@matt3 there's Linux on DeX but it doesnt support my devie :/
<LinuxUserHaiku>
device
<matt3>
np
<LinuxUserHaiku>
@matt3 cool mode i should say
<matt3>
install linux mint ... if you want
<LinuxUserHaiku>
@matt3 cu!
<matt3>
cu
LinuxUserHaiku has left #haiku [#haiku]
matt3 has left #haiku [#haiku]
euandreh has quit [Read error: No route to host]
freakazoid332 has joined #haiku
gouchi has joined #haiku
euandreh has joined #haiku
frkzoid has quit [Ping timeout: 480 seconds]
FreeFull has joined #haiku
gouchi has quit [Quit: Quitte]
jmairboeck has quit [Ping timeout: 480 seconds]
OscarL has joined #haiku
xiku has joined #haiku
BrunoSpr has joined #haiku
matt3 has joined #haiku
<OscarL>
Begasus: Should I open PRs for bumping Python packages 3.7.12 -> 3.7.14, 3.8.12 -> 3.8.14, and 3.9.10 -> 3.9.14? Those are security fixes only. (Got them working here already for 64 bits, but I'll rebuild them today after moving "libedit" around, as per your comment on the 3.10.7 PR)
<OscarL>
I ask because because I don't know if that would cause too many packages to be rebuilt, or something. If that's even a concern... Better to ask :-D
vdamewood has joined #haiku
<OscarL>
Anyone: Any tips for a Haikuporter noob like me on the best way to try to apply the patchsets from, say Python 3.10 to a newly created recipe for Python 3.11?
<OscarL>
I saw that HP already creates a git repo for my new python311.3.11.0rc2.recipe, I'm guessing I should be applying the patches in commits to that repo (that HP will then extract?). Not sure how to work with the ".patchset" files, basically. Any links to relevant docs will be much appreciated!
<Begasus>
OscarL, if there are security issues it's good to bump version for those
<Begasus>
PS, congrats on your merge for bumping python 3.10 :)
Anarchos has quit [Ping timeout: 480 seconds]
<OscarL>
Begasus: Thanks :-)
<OscarL>
Yeah, those python ".14" are all security fixes. Already sent a PR for 3.7.14, will do the rest now.
<Begasus>
OscarL, if you start working on python3.11 and patches should be needed, try to see if previous patches are confirmed and if so, keep credits to those creating the earlier patches :)
<OscarL>
Begasus: will do!
<Begasus>
will do a check for python3.7 on 32bit, but think it should be OK
<OscarL>
That why I was asking about how to work with the .patchset files (trying to keep the proper credits and stuff).
<OscarL>
PR for 3.8.14 already up (sorry for testing only on 64 bits, have some issues with my 32 install)
<Begasus>
First thing you could do is see if the patchset for python3.10 applies cleanly
<Begasus>
if so, things are fine, if not you need to re-create the patchset :)
<Begasus>
np, that's why I'm around mostly (to check up on 32bit PR's) :)
<OscarL>
Thanks for the help (and tips) Begasus! Much appreciated!
<Begasus>
np, always nice to see new contributers OscarL :)
<Begasus>
And in this case, someone that is familiar with python
<OscarL>
I wish I rembember more of it... or that I had a better functioning brain, but... oh well, "worse is nothing" (as we say in Argentina) :-D
<Begasus>
As you said earlier, baby steps, it's fine to tackle things you got a personal interest in
<ermo[m]>
Remind me, is the current 3.10 a LTS release (2 years of support)?
<OscarL>
About to start building 3.19.14 (again, just to re-check)
<Begasus>
3.7 build almost ready to start here OscarL
<Begasus>
PS, nice fix on the python3.10 version OscarL , annoyed me also to not being able to use bash history :)
HaikuUser has joined #haiku
HaikuUser2 has joined #haiku
HaikuUser2 has quit []
HaikuUser has quit []
<OscarL>
Just happy to have an usable REPL now! Non working line-editing and lack of completion was making me rage-quit too often :-D
<OscarL>
Too bad in only wors on 3.10 and up
<Begasus>
It's progress :)
<OscarL>
I've tried 3.7, 3.8. and 3.9 before finding out it only worked for libedit with 3.10+ . Oh well, at least it was good practice, and we get some version bumps :-D
<Begasus>
So yes, would be good to have those figured out also :)
<OscarL>
Mmm, 3.9.14 fails while applying the patches... Well... I guess that will help me learn the process (if I can figure it out :-P). Will come in handy for the 3.11.0 recipe.
<OscarL>
Begasus: I guess not. Let's add all the speeds ups to 3.11 :-D
<Begasus>
OK, will wait untill python3 and python38 are build on buildmaster before merging python39
<OscarL>
(should encourage people to update their python3 requirements)
<Begasus>
Out with the dogs for a while, bbl
<OscarL>
see you!
<OscarL>
And thanks again!
Vidrep_64 has joined #haiku
<Vidrep_64>
Hi waddlesplash
<Vidrep_64>
Hi humdinger too
<humdinger>
hullo
<Vidrep_64>
...and Begasus :)
<humdinger>
gotta reboot...
humdinger has quit [Quit: Vision[]: Oi with the poodles already!!]
humdinger has joined #haiku
<andreasdr[m]>
Good morning Sirs.
<Begasus>
hi Vidrep_64 !
<Begasus>
Moin andreasdr[m] :)
<andreasdr[m]>
Moin Begasus!
freakazoid332 has joined #haiku
<Begasus>
1 to go before python3 OscarL :)
<Begasus>
at least on 32bit buildmaster, I don't see any progress on 64bit buildmaster :/
<OscarL>
Time to get a coffee while we wait then! (and to keep me a wake a little longer, to see if I make any progress on 3.11)
<Vidrep_64>
humdinger, I did another build of ArtPaint with clang static analyser, and attached the zip. For what it's worth, bugs found have dropped from 58 to 49
<Anarchos>
hello
<Begasus>
Hi Anarchos
frkzoid has quit [Ping timeout: 480 seconds]
<Vidrep_64>
waddlesplash, have we included the updated wpa_supplicant with the nightly image yet, or is it still only available as an update?
<humdinger>
Vidrep_64: thanks. those I leave of course forDale to figure out. I suspect most are false positives...
<Vidrep_64>
Are you having any luck getting translations completed?
<Begasus>
Haven't finished the one for Dutch there yet, not sure if I get around to it before tomorrow
<humdinger>
We'll just release what we've got. As Dale is still very active, I expect frequent minor updates that allows for updated translations to be included.
<Begasus>
+1
<humdinger>
again with the reboot...
humdinger has quit [Quit: Vision[]: Oi with the poodles already!!]
humdinger has joined #haiku
<Anarchos>
Begasus long time no see, but i moved from house into another
jmairboeck has joined #haiku
<Begasus>
Indeed Anarchos long time no see
<Begasus>
hope the move went well
<Begasus>
OscarL, I think more patching will be needed for python3.11 ;)
<Begasus>
So I leave that up to you :P
<phschafft>
python for workgroups.
<Begasus>
hehe
<Begasus>
nice one phschafft :)
<phschafft>
:)
<OscarL>
Begasus: Good thing that I made the coffee extra strong then :-P
<Begasus>
right! :)
<Begasus>
python3 ok on buildmaster (32bit), python38 building atm
Begasus_32 has quit [Quit: Vision[]: Gone to the dogs!]
<OscarL>
bbjimmy: I assume it does not depends on where you start to drill down? (like ... on a Disk icon, mounted volume, etc?)
<OscarL>
(might help to narrow the search)
<bbjimmy>
OscarL It only happened to me twice, and both times from the Desktop so I cannot say.
<OscarL>
understood.
FreeFull_ has joined #haiku
<bbjimmy>
It had to happen twice to connect it to drill-down navigation.
<bbjimmy>
and that might not even be true.
FreeFull has quit [Ping timeout: 480 seconds]
<OscarL>
An NTFS partition seems to be involved?
<OscarL>
The KDL screenshot shows kernel calls to "<ntfs> fs_lookup", for example.
<waddlesplash>
Vidrep_64: only as update
FreeFull_ has quit [Ping timeout: 480 seconds]
rennj has quit [Ping timeout: 480 seconds]
<bbjimmy>
OscarL I have an ntfs partition mounted, yes.
AlaskanEmily has joined #haiku
rennj has joined #haiku
<bbjimmy>
The NTFS partition should not be an issue. It has never caused any problem in the past, and I can drill down directories there just as on any other file system.
<Vidrep_64>
waddlesplash, the problem is that anyone downloading a nightly image for a fresh install won't be able to connect to the internet or to get the update
<Vidrep_64>
Once the update is installed then it works
cocobean has joined #haiku
<OscarL>
bbjimmy: just mentioned because it appears in the KDL image. It shows Tracker-> Drilling-down menu -> and the vm_page_fault after some calls to ntfs related code.
vdamewood has quit [Quit: Life beckons.]
<OscarL>
if it only happens when that ntfs partition is mounted, maybe it needs some file system check/repair? (should not cause a KDL, I guess, but might help narrow down the cause)
<OscarL>
might also explain why it is so hard to reproduce.
<cocobean>
x512: N/A for the current Open POSIX Testing. From my review, Haiku R1-dev is passing with the same/or better results than on Linux.
<OscarL>
(if that NTFS partition is shared with a Windows or even a Linux install... sometimes they get "dirty"... Linux at least usually complains about it)
<bbjimmy>
OscarL I always have this partition mounted. All my camera images are stored there/
<bbjimmy>
I have a Windows install, but havent booted it in about 6 months.
<OscarL>
I had Haiku installs kill some ntfs partitions of mine in the past (more than once). I guess I'm just scarred :-) (I would still run a filesystem check, just to be sure)
<x512[m]>
OscarL: NTFS implementation was reworked recently.
<waddlesplash>
yeah, I rewrote the ntfs driver, much more stable now
<OscarL>
Yup!
<andreasdr[m]>
Nice.
ravi has joined #haiku
<bbjimmy>
OscarL unless waddlesplash messed up, I think the NTFS partition is not the isue.
<waddlesplash>
bbjimmy: the kdl clearly shows the ntfs driver is the fault location
<OscarL>
Ok. Just going with what I could gather from that KDL image (and not being able to reproduce it here either).
<bbjimmy>
waddlesplash I never had this issue before, did I expose an edge case?
<waddlesplash>
it's possible. never saw a kdl like this either
<bbjimmy>
Why would tracker be touching the NTFS volume when drilling down from the Desktop?
<bbjimmy>
OK, the NTFS volume is in the drill down menu and trackeer may have read its root directory entries.
<OscarL>
Also... didn't Tracker created some folder under RECYCLED (or Recycle.bin) due to the Trash icon?
<OscarL>
(at least I remember that even from BeOS days :-D)
bbjimmy has quit [Remote host closed the connection]
bbjimmy has joined #haiku
<OscarL>
build.haiku-os.org/buildmaster/master/x86_64/ still stuck on "waiting for build package havoc-0.2.0-1 to be activated" :-D
gouchi has joined #haiku
<OscarL>
Maybe some good old "Have you tried turning it off and on again?" might help there?
gouchi has quit []
<Begasus>
Turning off here ;)
<Begasus>
g'night peeps!
Begasus has quit [Quit: Leaving]
cocobean has quit [Quit: Page closed]
<Vidrep_64>
waddlesplash, just got back home
<Vidrep_64>
What do we want to do with the open ticket for wpa_supplicant?
<waddlesplash>
is it fixed with the new wpa_supplicant?
<Vidrep_64>
Only once you are able to connect to the internet and install the update. However, that cannot be done with the nightly image until that package is included
<waddlesplash>
that's fine, the ticket is about the issue itself
<waddlesplash>
please comment that it's fixed in the wpa_supplicant update then
<waddlesplash>
there will be a new package set before the beta
<Vidrep_64>
OK, will do
<Vidrep_64>
waddlesplash, since I've got you here...
<Vidrep_64>
Is there a possibility of updating to the latest Gutenprint printer drivers so I can test them before the next release?
<Vidrep_64>
Currently we're using Gutenprint 5.31 - August 2019
<Vidrep_64>
libgutenprint8 needs to be updated to libgutenprint9
<Vidrep_64>
There's already an open ticket for this
frkazoid333 has joined #haiku
freakazoid332 has quit [Ping timeout: 480 seconds]
Anarchos has joined #haiku
<waddlesplash>
send a link or comment on it to bump