Re: openup service question

[Gonzalo L. Rodriguez]

On Mon, 16 Sep 2019 at 09:13:13 +, rsyk...@disroot.org wrote:
> Dear list,
> 
> 
> I have been using the "openup" service to keep my amd64 machine updated
> to the latest stable, i.e. 6.5, available at
> 
> https://www.mtier.org/solutions/apps/openup/
> 
> Recently I get:
> 
> odin# ./openup
>  
> ===> Checking for openup update
> ===> Installing/updating syspatches
> Get/Verify syspatch65-011_expat.tgz 100% |**|   588 KB00:00   
>  
> Installing patch 011_expat
> Errata can be reviewed under /var/syspatch
> ===> Updating package(s)
> https://stable.mtier.org/updates/6.5/amd64/: ftp: Error retrieving file: 401 
> Unauthorized
> https://stable.mtier.org/updates/6.5/amd64/: empty
> 
> If anybody here understands what is happening to me, I'd be grateful to know.
> The site claims the support for the most recent release is free. Yet, ...
> 
> I tried to contact their support twice, but got no reply.
> 
> 
> Thank you for any comments!
> Ruda
> 
> 
> PS.: Does using openup convey any advantage over running "syspatch" and
> "pkg_add -u" on amd64?
> 

Now you can switch:

https://undeadly.org/cgi?action=article;sid=20190814112133

-- 

- gonzalo

Re: Upgrade procedure (6.4 -> 6.5)

[Gonzalo L. Rodriguez]

On Thu, 02 May 2019 at 11:46:20 +0200, Noth wrote:
> 
> On 02/05/2019 11:02, Consus wrote:
> > On 10:27 Thu 02 May, Markus Hennecke wrote:
> > > Am 02.05.2019 um 09:52 schrieb Consus:
> > > > I've upgraded my systems from 6.4 to 6.5 without a glitch, but I see
> > > > that /etc/networks and some other files (like malloc.conf.5) are still
> > > > present, although there is no use for them in the new release.
> > > > 
> > > > Is there a reason why these files are not listed in "FIles to remove"?
> > > > Is there a way to track them? It's not like something gonna break, but
> > > > old configuration files (and manual pages) lying around can make
> > > > someone's life harder during the debug session.
> > > Take a look at the sysutils/sysclean port.
> > That's pretty much how I discovered this. But I want to know the
> > "official" way. Maybe there is a reason why e.g. perl files are to be
> > removed, but man pages are not.
> > 
> I set up a script for sysclean:
> 
> cat sysclean65.txt | while read line ; do rm -rf "${line}" ; done

You probably want some /etc/sysclean.ignore bits before that

> sysclean65.txt is obtained by running sysclean -a >>sysclean65.txt . I don't
> run that line in sysclean65.sh because the files have to be reviewed to
> prevent deletion of any additional files you may have added, like certs or
> scripts.
> 
> HTH
> 
> Noth
> 


-- 

- gonzalo

Re: NextCloud: failed integrity checks

[Gonzalo L. Rodriguez]

On [22/07/18] [08:32P], Johan Huldtgren wrote:

On 2018/07/22 15:39, Nicolas Schmidt wrote:

After installation on OpenBSD 6.3 with pkg_add, NextCloud complains about files 
failing the integrity checks. More specifically:

- occ
 * expected hash: 
7e3fce0d7b5c20a7775ed1b548cb2e29bed078d3ca77b01a83d438f671b3d473147d4e8217d2084e17b6fe23a18ba258b11ba60106e23381f1e2889ce14971c4
 * current hash:  
7693eb89c0bc218712d68ec58599efa46e5c3729814e2aad16bf2c0079be7ae1909f072ead7889883c0a89b6c51570800d9e8a71f35866cb4e0c47aeaa5a4b2b

- version.php
 * expected hash: 
4e9046aca4fd8e942ba7bd505374e22ddd500a99b3a46d57d629b99c3132a66206883053f22801894929e51fca307c740062b497d55639bcc9a3154ada3504ff
 * current hash:  
30cd43589fc8ab273fa25e1a477c8cbadb13bac5541daa6d3fa0490a0c2054c2c29a274fd50eec66934a9d9adc541dec8701e7463922d36174478ae3e9a64981

- apps/updatenotification/appinfo/info.xml
 * expected hash: 
bf7983ffe422ba215c04a0069081fab0c78ba81fa40a90cbdd3595182e011fb7f3e0bd1cd14cdea742cafb89f1da001582fe8d560749d98ea540b4ee76dd9898
 * current hash:  
d2984fa816b4cea71e7c09f36a4132e7cb88d357f22e1c795778deccdb4066beaef2876b95d849e6eeae37b879c0f63500b0958a6a61bab1c933736bf135c440


Anybody able to reproduce?


yeah this is known. The port modifies these files to work with OpenBSD
(if you look at the port these files are the ones we patch). You can
work around this by adding this to your config.php

'integrity.check.disabled' => true,

.jh




https://cvsweb.openbsd.org/cgi-bin/cvsweb/ports/www/nextcloud/Makefile?rev=1.17=text/x-cvsweb-markup

--
Sending from my toaster.

Re: NextCloud: failed integrity checks

[Gonzalo L. Rodriguez]

On [22/07/18] [07:39P], Nicolas Schmidt wrote:

After installation on OpenBSD 6.3 with pkg_add, NextCloud complains about files 
failing the integrity checks. More specifically:

- occ
* expected hash: 
7e3fce0d7b5c20a7775ed1b548cb2e29bed078d3ca77b01a83d438f671b3d473147d4e8217d2084e17b6fe23a18ba258b11ba60106e23381f1e2889ce14971c4
* current hash:  
7693eb89c0bc218712d68ec58599efa46e5c3729814e2aad16bf2c0079be7ae1909f072ead7889883c0a89b6c51570800d9e8a71f35866cb4e0c47aeaa5a4b2b

- version.php
* expected hash: 
4e9046aca4fd8e942ba7bd505374e22ddd500a99b3a46d57d629b99c3132a66206883053f22801894929e51fca307c740062b497d55639bcc9a3154ada3504ff
* current hash:  
30cd43589fc8ab273fa25e1a477c8cbadb13bac5541daa6d3fa0490a0c2054c2c29a274fd50eec66934a9d9adc541dec8701e7463922d36174478ae3e9a64981

- apps/updatenotification/appinfo/info.xml
* expected hash: 
bf7983ffe422ba215c04a0069081fab0c78ba81fa40a90cbdd3595182e011fb7f3e0bd1cd14cdea742cafb89f1da001582fe8d560749d98ea540b4ee76dd9898
* current hash:  
d2984fa816b4cea71e7c09f36a4132e7cb88d357f22e1c795778deccdb4066beaef2876b95d849e6eeae37b879c0f63500b0958a6a61bab1c933736bf135c440


Anybody able to reproduce?

--Nicolas



Hello,

This is fixed on -current, I disabled the patching on the nextcloud version to
avoid this error.

Cheers.-

--
Sending from my toaster.

Re: roundcube installation php modules

[Gonzalo L. Rodriguez]

On [10/07/18] [02:59P], Danny AwesomeRetro wrote:

No problem,that fixed the issue for me ;)

thank you,this has cost me around 18 hours of searching

Cheers,

Danny


On 07/10/2018 04:25 PM, Vijay Sankar wrote:

Sorry to interject -- just wondering if you read the instructions
towards the bottom in /usr/local/share/doc/pkg-readmes for php-5.6. It
specifically says

    # cd /etc/php-5.6.sample
    # for i in *; do ln -sf ../php-5.6.sample/$i ../php-5.6/; done

HTH,

Vijay

Quoting Teno Deuter :


actually I had to define the absolute path to the module. After doing
this it did work!

I still have the issue with Imagick though! There is no module for
that in OpenBSD repository as it's already integrated in php -
correct? In that case should I ignore that?

Thank you

On Tue, Jul 10, 2018 at 2:30 PM, Teno Deuter 
wrote:

sorry forgot to mention that after doing the below changes I did
restart the server!

Thank you

On Tue, Jul 10, 2018 at 2:29 PM, Teno Deuter 
wrote:

here are my current extension settings in php-5.6.ini:

;extension=php_bz2.dll
;extension=php_curl.dll
;extension=php_fileinfo.dll

extension=php_gd2.dll

;extension=php_gettext.dll
;extension=php_gmp.dll

extension=php_intl.dll

;extension=php_imap.dll
;extension=php_interbase.dll
;extension=php_ldap.dll
;extension=php_mbstring.dll
;extension=php_exif.dll  ; Must be after mbstring as it depends
on it
;extension=php_mysql.dll
;extension=php_mysqli.dll
;extension=php_oci8_12c.dll  ; Use with Oracle Database 12c Instant
Client
;extension=php_openssl.dll
;extension=php_pdo_firebird.dll
;extension=php_pdo_mysql.dll
;extension=php_pdo_oci.dll
;extension=php_pdo_odbc.dll
;extension=php_pdo_pgsql.dll

extension=php_pdo_sqlite.dll

;extension=php_pgsql.dll
;extension=php_shmop.dll
;extension=php_soap.dll
;extension=php_sockets.dll

extension=php_sqlite3.dll

;extension=php_sybase_ct.dll
;extension=php_tidy.dll
;extension=php_xmlrpc.dll
;extension=php_xsl.dll

but nothing happens. I still get the same error in the first
installer step.

Thank you

On Tue, Jul 10, 2018 at 2:07 PM,   wrote:

Have you altered your php.ini to load the extensions and restart
php-fpm?
On Jul 10, 2018 7:00 AM, Teno Deuter  wrote:


Dear list,

in a OpenBSD 6.3 machine I run httpd and opensmptd and try to intall
roundcubemail 1.3.5 from the OpenBSD packages repository.

When running the installer, in the first page, I get following
warnings:

FileInfo:  OK
Libiconv:  OK
Intl:  NOT AVAILABLE(See http://www.php.net/manual/en/book.intl.php)
Exif:  OK
LDAP:  NOT AVAILABLE(See http://www.php.net/manual/en/book.ldap.php)
GD:  NOT AVAILABLE(See http://www.php.net/manual/en/book.image.php)
Imagick:  NOT AVAILABLE(See
http://www.php.net/manual/en/book.imagick.php)

but pkg_info shows:

php-gd-5.6.34   image manipulation extensions for php
php-intl-5.6.34 intl library support for php

and I think php-imagick is already part of the php OpenBSD package.

Why do I get the above warnings?

Also, in the second installation page I get the following:

Mimetype to file extension mapping:  NOT OK

but in httpd.conf, on the top of the file, I have the following
entry:

types { include "/usr/share/misc/mime.types" }

Thank you







Vijay Sankar, M.Eng., P.Eng.
ForeTell Technologies Limited
vsan...@foretell.ca





You always can check /usr/local/share/doc/pkg-readmes for the README

--
Sending from my toaster.

Re: athn0: device timeout

[Gonzalo L. Rodriguez]

I have the same problem with a new macbookpro12,1 my urtwn adapter work 
just fine in a regular ehci(4) machine, but on xhci(4)'s macbookpro I 
need to reconnect like 10 times, and even that way, doesn't work. :/

On 28/11, Stefan Sperling wrote:
; On Sat, Nov 28, 2015 at 07:35:00AM -0700, bluesun08 wrote:
; > xhci0 at pci0 dev 20 function 0 "Intel Bay Trail xHCI" rev 0x0c: msi
; > usb0 at xhci0: USB revision 3.0
; > uhub0 at usb0 "Intel xHCI root hub" rev 3.00/1.00 addr 1
; > uhub2 at uhub0 port 2 "Genesys Logic USB2.0 Hub" rev 2.00/85.37 addr 3
; > athn1 at uhub2 port 2 configuration 1 interface 0 "ATHEROS USB2.0 WLAN" rev
; > 2.00/1.08 addr 6
; > athn1: could not load firmware
; 
; I believe your problems are rooted in xhci(4) not athn(4).
; There are several known problems with xhci, some of which
; don't have a known fix yet.
; 
; To confirm this theory, could you try this athn adapter in a
; machine with USB ports driven by ehci(4) instead of xhci(4)?
; 

-- 
Sending from my toaster.

Re: EFI: Booting from other (not the first) GPT partition possible? How? It's an Apple :-O

[Gonzalo L. Rodriguez]

Oh yes, so then on 8,2 still you can boot legacy, on 12,1 you don't :(

Enviado desde mi tostadora de mano

> El 19 nov 2015, a las 15:53, Marc  escribió:
>
> Thank you Gonzalo.
>
> Just to make sure we are talking about the same thing:
>
> I was already able to boot OpenBSD in BIOS legacy mode.
>
> What I want to achieve is booting OpenBSD current with the new EFI OpenBSD
boot loader.
>
> Are you sure that following the tutorial you mentioned can be of any help to
do this?
>
> I will be happy to get enlightened if I am just missing the point. :)
>
> Regards
> Marcel
>
>> Hello,
>>
>> I'm kinda at the same step, but in a macbookpro12,1
>>
>> I resize my OSX partition, burn a install58.fs on a usb stick, boot
>> holding ALT, install OpenBSD on the part of resize partition, and then
>> follow jcs@ tutorial:
>>
>> https://gist.github.com/jcs/5573685
>>
>> Now, "El Capitan" have like a 'Secure Level' thing that you can do the
>> step Mac OS X Encryption -> 3-6. So, you need to boot on Rescue Mode and
>> disable this new protection from the console on rescue mode:
>>
>> # csrutil disable
>>
>> Then reboot, and try the "Mac OS X Encryption" step. Install refind and
>> cross your fingers :)
>>
>>
>> On 16/11, Marcel Timm wrote:
>> ; Hi there,
>> ;
>> ; one thing I would like to try is to boot from created OpenBSD EFI USB
stick
>> ; with
>> ;
>> ; boot -a
>> ;
>> ; and enter the OpenBSD's root partition on the HD.
>> ;
>> ; Unfortunately neither the MacBook Pro 8,2 's integrated
>> ; nor an external USB keyboard work at the prompt where to enter the
>> ; root device's location. :(
>> ;
>> ; Is there another way of telling the kernel which root device to use
>> ; (maybe at boot's prompt - although I haven't found anything in man
page..)?
>> ;
>> ; If this seems to be a XY question to you, I am happy about other
proposals.
>> ;
>> ; Greetings
>> ; Marcel
>> ;
>> ; On 11.11.2015 16:01, Marcel Timm wrote:
>> ; >Hello!
>> ; >
>> ; >My computer is a MacBook Pro 8,2.
>> ; >
>> ; >There is a GPT on the HD (big surprise!) with four partitions,
>> ; >the last one being of type OpenBSD.
>> ; >
>> ; >I managed to put a recent OpenBSD 5.8 snapshot there
>> ; >by booting and installing from an USB stick via EFI created like that
(in
>> ; >OSX):
>> ; >
>> ; >dd if=~/install58.fs of=/dev/rdisk2 bs=1m
>> ; >
>> ; >After installing rEFInd 0.9.2 and putting OpenBSD 5.8 snapshot's
>> ; >BOOTX64.EFI file
>> ; >to the MacBook's EFI partition the rEFInd boot manager shows the
OpenBSD
>> ; >EFI option.
>> ; >
>> ; >Selecting that OpenBSD entry starts the boot programm showing hd0 hd1
hd2
>> ; >and hd3.
>> ; >
>> ; >Is it possible to boot my "EFI OpenBSD installation" from here?
>> ; >If so, how to proceed?
>> ; >
>> ; >I already played with
>> ; >
>> ; >set device hd0d
>> ; >
>> ; >etc. - but it did not work.
>> ; >
>> ; >I will gladly share more details, if of any help.
>> ; >
>> ; >Thanks in advance!
>> ; >
>> ; >Marcel
>> ;
>>
>> --
>> Sending from my toaster.

Re: EFI: Booting from other (not the first) GPT partition possible? How? It's an Apple :-O

[Gonzalo L. Rodriguez]

Hello,

I'm kinda at the same step, but in a macbookpro12,1

I resize my OSX partition, burn a install58.fs on a usb stick, boot 
holding ALT, install OpenBSD on the part of resize partition, and then 
follow jcs@ tutorial:

https://gist.github.com/jcs/5573685

Now, "El Capitan" have like a 'Secure Level' thing that you can do the 
step Mac OS X Encryption -> 3-6. So, you need to boot on Rescue Mode and 
disable this new protection from the console on rescue mode:

# csrutil disable

Then reboot, and try the "Mac OS X Encryption" step. Install refind and 
cross your fingers :)


On 16/11, Marcel Timm wrote:
; Hi there,
; 
; one thing I would like to try is to boot from created OpenBSD EFI USB stick
; with
; 
; boot -a
; 
; and enter the OpenBSD's root partition on the HD.
; 
; Unfortunately neither the MacBook Pro 8,2 's integrated
; nor an external USB keyboard work at the prompt where to enter the
; root device's location. :(
; 
; Is there another way of telling the kernel which root device to use
; (maybe at boot's prompt - although I haven't found anything in man page..)?
; 
; If this seems to be a XY question to you, I am happy about other proposals.
; 
; Greetings
; Marcel
; 
; On 11.11.2015 16:01, Marcel Timm wrote:
; >Hello!
; >
; >My computer is a MacBook Pro 8,2.
; >
; >There is a GPT on the HD (big surprise!) with four partitions,
; >the last one being of type OpenBSD.
; >
; >I managed to put a recent OpenBSD 5.8 snapshot there
; >by booting and installing from an USB stick via EFI created like that (in
; >OSX):
; >
; >dd if=~/install58.fs of=/dev/rdisk2 bs=1m
; >
; >After installing rEFInd 0.9.2 and putting OpenBSD 5.8 snapshot's
; >BOOTX64.EFI file
; >to the MacBook's EFI partition the rEFInd boot manager shows the OpenBSD
; >EFI option.
; >
; >Selecting that OpenBSD entry starts the boot programm showing hd0 hd1 hd2
; >and hd3.
; >
; >Is it possible to boot my "EFI OpenBSD installation" from here?
; >If so, how to proceed?
; >
; >I already played with
; >
; >set device hd0d
; >
; >etc. - but it did not work.
; >
; >I will gladly share more details, if of any help.
; >
; >Thanks in advance!
; >
; >Marcel
; 

-- 
Sending from my toaster.