well, its a standard Theo Response. However, reading between the lines, isn't there a method to compile those packages for yourself? Honestly, it shouldn't be all that hard. If I had a PPC machine here, I would start with the 6.0 ppc packages and then start the compile process to make the 6.1. At least, this is what I would do IF I had a machine here to do it on.
As an aside to Theo, its been a few years since I last mentioned this, but perhaps its time you added (or allowed it to be added) some braille/speech support to the install media. THis comment is definitely off topic for this list, but I felt it needed to be said. Perhaps next time you are at the next Las Vegas convention, I might be able to show up and have a pleasant chat with you about that. Perhaps seeing the situation in person might inspire you to make OpenBSD live up to the "Open" part of the name. -eric On Apr 16, 2017, at 9:56 AM, luca suriano wrote: > On Fri, 04/14/17, at 08:22:39, Theo de Raadt wrote: >>> I don't understand why release 6.1 if the packages are not ready! >> Because I decided. > > There is not doubt about that. > > The problem is that after upgrade from 6.0 to 6.1 the result is: > > $ doas pkg_add -u > https://ftp.openbsd.org/pub/OpenBSD/6.1/packages/powerpc/: no such dir > Couldn't find updates for ImageMagick-6.9.4.10 ProFont-2.2 amigafonts-1.0 > avahi-0.6.31p24 awesome-3.5.9p0 bash-4.3.46 bzip2-1.0.6p8 cabextract-1.6 > cairo-1.14.6p1 ccid-1.4.24 curl-7.49.0 cvsps-2.1p0 dbus-1.10.8v0 > dbus-daemon-launch-helper-1.10.8 desktop-file-utils-0.23 djvulibre-3.5.27p0 > [...] > startup-notification-0.12p4 terminus-font-4.40p0 tiff-4.0.6p1 tig-2.1.1p2 > ubuntu-fonts-0.83 unzip-6.0p9 vim-7.4.1467p1-no_x11-perl-python-ruby > xpdf-3.04p1 xz-5.2.2p0 zip-3.0p0 zsh-5.2p3 > > So I got back to the old version, otherwise I would have had the system > unusable. That's it. > > Thanks a lot for your awesome work. > > -- > "Information wants to be Free" >
