Re: Pkgsrc issue
Don Lee writes: > Mr Nestor has given me a good path for my needs. I’m wondering if I > can apply any of my resources to TNF efforts. I was thinking of > setting up a machine here, but I might do better by simply giving a > machine to TNF. (The NetBSD Foundation?) > > NetBSD has been good to me. I’d like to return the favor. Yes, TNF == The NetBSD Foundation. I'm not on the board and can't really speak for TNF, but from helping with pkgsrc and talking about bulk build setups, I know that hardware is one thing, and a place to put it, power, network, remote hands, and admin resources is much more. You might ask he@ who is doing powerpc builds if they could use more, but I would guess that's really not the limit. There is always a call for money which is used to pay people sometimes, and to buy hardware. (I don't know where it came from, but the x86_64/i386 bulk build setup is recently massively improved with new hardware, but it took a lot of work by many people to get it all done.) It is very useful if you figure out what's wrong and fix it and send patches. For that, it's best if you update to 10.
Re: Pkgsrc issue
Don Lee writes: > I have extra static IPs, and several PPC Mac mini machines. I wonder > how hard it would be for me to set one up with enough disk space to do > bulk builds. Would that even be helpful? I imagine that to be useful, > a machine would have to have some administrative massaging to set up > users/ssh/ftp/etc. You building our own packages is useful for you. You are welcome to make them available, and we list sets that are long-term maintained in SEE_ALSO. We have a rule that only packages built on machines controlled by TNF members are posted on ftp.netbsd.org. > I have not done the pkgsrc bootstrap for quite a while, and don’t know > how much disk space I would need. Fortunately, NetBSD 8.2 on PPC seem > to be very stable, so running for a couple of weeks on a build should > be fine. I meant that if you need a small subset of packages, then building those yourself is reasonable. If you try to build the entire set, it's going to take a very long time. For example, I build what I need for earmv7hf-el myself, but my setup would take years to build the full set, and it doens't have enough memory.
Re: Pkgsrc issue
Don Lee writes: > I have a PPC Mac Mini running NetBSD 8.2. It’s stable and functional. It > serves me well. > > I have been using pkgin to install packages and update them with "pkgin > upgrade”. > > My recent attempts to upgrade have been ended by pkgin telling me: > > +mercy$ pkgin upgrade > calculating dependencies...| > glib2>=2.76.4nb1 is not available in the repository > proceed ? [y/N] > > So I checked on glib2, and it really should be in the pkgsrc binary > packages, but it is not there in the 8.2 ppc pkgsrc binaries. I also > have amd64 machines and they have glib2. NetBSD has machines to do builds for some architectures, basically x86_64, i386, earmv[67]hf-el, and aarch64. Beyond that individual developers do bulk builds and publish the results. These are almost all "slow architectures", which means that the available compute resources are such that it takes a long time (more than 2 weeks) to complete a bulk build. For many, it takes a whole quarter. Thus the build currently pointed to for macppc/8 is 2023Q4. You are welcome to look at the ftp server and choose a build yourself -- but there isn't anything newere. > How should I go about reporting this issue and hopefully getting it fixed. You have reported it :-) There are a lot of reasons a package might not succeed: bulk build ran out of time that quarter before the hardware is used to start the next quarter hiccup or resource issue on the build system the package actually won't build on the branch The place to find bulk build reports is the pkgsrc-bulk mailing list, but I am not able to find the report for this build with quick search. So, you could check out pkgsrc, bootstrap it to a scratch prefix, and try to build glib2, see if it succeeds, and if not fix it. However: we no longer maintain 2023Q4, now that 2023Q1 was created pkgsrc no longer supports NetBSD 8, more or less right now, as NetBSD 8 is formally EOL on Tuesday. (The notion of "supports" is a bit funny, as people fix what they want, regardless.) > I *believe* I could fix this by upgrading NetBSD to > 9.0+. Unfortunately, that would be hard for me, at least now. Whether there are binary package sets for various versions is a question you might want to answer, but in general, you are now overdue for an upgrade. This query isn't, as far as I know, easy to 4un for the web, for in case it helps: $ ls -l pub/pkgsrc/packages/NetBSD/powerpc/*_20*Q*/All/glib2-2* -rw-r--r-- 1 he netbsd 5353306 Dec 18 08:33 pub/pkgsrc/packages/NetBSD/powerpc/10.0_2023Q3/All/glib2-2.76.5.tgz -rw-r--r-- 1 he netbsd 5301256 Oct 24 2023 pub/pkgsrc/packages/NetBSD/powerpc/8.0_2023Q3/All/glib2-2.76.5.tgz -rw-r--r-- 1 he netbsd 5372926 Oct 23 2023 pub/pkgsrc/packages/NetBSD/powerpc/9.0_2023Q3/All/glib2-2.76.5.tgz -rw-r--r-- 1 he netbsd 5435273 Feb 12 06:31 pub/pkgsrc/packages/NetBSD/powerpc/9.0_2023Q4/All/glib2-2.78.1nb1.tgz which shows that 9 has glib2 for 2023Q4, and that there isn't a 10.0 build for 2023Q4 on the ftp server. You of course can build your own packages. That might be more reasonable than you think, especially if you are operating in a lightweight old-school manner.
Re: need your advice before new Raspberry Pi purchase
El 24/4/24 a las 6:39, Ramiro Aceves escribió: Hello, My RPi4 arrived yesterday and everything worked and booted fine from the 128 GB SD using UEFI. Network was working fine also through ethernet without configuring anything. 3GB limit disabled. Today I will continue configuring the OS. The only nasty thing was that SD card reader in my NUC8i7 did not work in NetBSD and needed to flash it under Linux. I think I will buy a card reader for the next time. Should I fill a bug report? Thanks guys! Regards. Ramiro. Hello, I made the suggested somewhere symbolic link to avoid the "bwfm0: autoconfiguration error: NVRAM file not available", even that I am not going to use the WIFI interface. lrwxr-xr-x 1 root wheel 44 Apr 27 11:54 brcmfmac43455-sdio.Raspberry Pi 4 Model B.txt -> brcmfmac43455-sdio.raspberrypi,4-model-b.txt Will that fix be applied in next 10.1 release? Thanks. Ramiro
Pkgsrc issue
Hi guys, I have a PPC Mac Mini running NetBSD 8.2. It’s stable and functional. It serves me well. I have been using pkgin to install packages and update them with "pkgin upgrade”. My recent attempts to upgrade have been ended by pkgin telling me: +mercy$ pkgin upgrade calculating dependencies...| glib2>=2.76.4nb1 is not available in the repository proceed ? [y/N] So I checked on glib2, and it really should be in the pkgsrc binary packages, but it is not there in the 8.2 ppc pkgsrc binaries. I also have amd64 machines and they have glib2. How should I go about reporting this issue and hopefully getting it fixed. I *believe* I could fix this by upgrading NetBSD to 9.0+. Unfortunately, that would be hard for me, at least now. Thanks, -dgl-
NetBSD Nightly Trouble Ticket Report broken?
Hello, I am receiving empty email reports. Thanks.
