Re: Guidance: How often to update -current?
My upgrades usually follow chromium pkg upgrades. In fact, I have a script on my phone that greps the chromium pkg version. I test on my own laptop first.
Re: Guidance: How often to update -current?
On Sat Mar 21, 2020 at 6:23 PM PST, Paco Esteban wrote: > On Sat, 21 Mar 2020, j3s wrote: > > > On Sat Mar 21, 2020 at 8:59 AM PST, Theodore Wynnychenko wrote: > > > But, this got me thinking (I am better with schedules): What is a > > > reasonable amount of time between updates of -current? > > > > > Just looking for opinions. > > > > My opinion is at least twice a month if you're following -current. > > > > With that said, People's opinions will vary, and unfortunately you're > > unlikely to find consensus here. > > > > -current is meant to be experimental, and if possible I'd recommend > > following the stable releases instead - that way you're on a 6 month > > schedule. > > Some of us use -current daily even for work stuff and rely on it, so > I would not call it experimental. >From https://www.openbsd.org/faq/current.html > Aggressive changes are sometimes pushed in this branch, and > complications can arise when building the latest code or upgrading > from a previous point in time. Sounds experimental to me, but like I said, do what you like. If you don't need to run on -current, just stick to the main releases, that's my point.
Re: Guidance: How often to update -current?
On Sat, 21 Mar 2020, j3s wrote: > On Sat Mar 21, 2020 at 8:59 AM PST, Theodore Wynnychenko wrote: > > But, this got me thinking (I am better with schedules): What is a > > reasonable amount of time between updates of -current? > > > Just looking for opinions. > > My opinion is at least twice a month if you're following -current. > > With that said, People's opinions will vary, and unfortunately you're > unlikely to find consensus here. > > -current is meant to be experimental, and if possible I'd recommend > following the stable releases instead - that way you're on a 6 month > schedule. Some of us use -current daily even for work stuff and rely on it, so I would not call it experimental. You may find an occasional glitch here and there, but -current tends to be pretty stable if you stick to supported hardware. As for the update schedule, it really depends on your use case. I update once a week (sometimes more often), but that's because I do some work on ports and I want to be sure that, when something fails, is not because of some out-of-sync problem in my environment, but because of the port itself or the chair-to-keyboard interface. -- Paco Esteban. 0x5818130B8A6DBC03
Re: ports: pkg_add as root
On 2020-03-21, putridsou...@gmail.com wrote: > I'm have never tried the ports system before. > I have read through the faq and the man pages, > but I get stuck at building dependencies. > I follow through the fetch,checksum steps and then > for 'make prepare' as local user, > I'm greeted with following message. > This is for the 'rsnapshot' package You have had some other answers about how to do this from the ports infrastructure, but I'm not sure if anyone checked: are you just trying to *use* rsnapshot (or whatever else)? If so, there's no benefit to building from ports. You will just end up building a load of things that you don't otherwise need as build dependencies, wasting time and electricity, and the end result will be the same anyway. Unless you want to make changes to the port then there's very little reason to do anything other than just pkg_add.
Re: Guidance: How often to update -current?
On 2020-03-21, Theodore Wynnychenko wrote: > Hello > I have been following -current since (about) 5.6. > At first, I was pretty good. Probably no more than about 1 month between > updates. > But, life gets in the way... > Recently, I had a prolonged (probably >4-6 month) period where I did not > update, although I have recovered. > Since then, I have been reasonably good, I think. No more than 2 months > between updates. > This last one seemed not to have too many changes/things I needed to deal > with, and went quickly. > > But, this got me thinking (I am better with schedules): What is a > reasonable amount of time between updates of -current? > > I think if I have a firm time limit in my head, I would be better able at > sticking to it. > Just looking for opinions. > > Thanks > Ted > > If you're following -current, it's best to update frequently enough that you don't have too much bisecting to do to figure out when a bug was introduced if you happen to bump into one :-)
Re: Guidance: How often to update -current?
On Sat Mar 21, 2020 at 8:59 AM PST, Theodore Wynnychenko wrote: > But, this got me thinking (I am better with schedules): What is a > reasonable amount of time between updates of -current? > Just looking for opinions. My opinion is at least twice a month if you're following -current. With that said, People's opinions will vary, and unfortunately you're unlikely to find consensus here. -current is meant to be experimental, and if possible I'd recommend following the stable releases instead - that way you're on a 6 month schedule.
Guidance: How often to update -current?
Hello I have been following -current since (about) 5.6. At first, I was pretty good. Probably no more than about 1 month between updates. But, life gets in the way... Recently, I had a prolonged (probably >4-6 month) period where I did not update, although I have recovered. Since then, I have been reasonably good, I think. No more than 2 months between updates. This last one seemed not to have too many changes/things I needed to deal with, and went quickly. But, this got me thinking (I am better with schedules): What is a reasonable amount of time between updates of -current? I think if I have a firm time limit in my head, I would be better able at sticking to it. Just looking for opinions. Thanks Ted
Re: ports: pkg_add as root
On Sat, Mar 21, 2020 at 02:26:18PM +0530, putridsou...@gmail.com wrote: > I'm have never tried the ports system before. > I have read through the faq and the man pages, > but I get stuck at building dependencies. > I follow through the fetch,checksum steps and then > for 'make prepare' as local user, > I'm greeted with following message. > This is for the 'rsnapshot' package > > ===> Building package for rsync-3.1.3 > Create /usr/ports/packages/amd64/all/rsync-3.1.3.tgz > Creating package rsync-3.1.3 > Link to /usr/ports/packages/amd64/ftp/rsync-3.1.3.tgz > ===> Cleaning for rsync-3.1.3 > ===> Verifying specs: c > ===> found c.95.1 > ===> Installing rsync-3.1.3 from /usr/ports/packages/amd64/all/ > pkg_add: pkg_add must be run as root > *** Error 1 in /usr/ports/net/rsync > (/usr/ports/infrastructure/mk/bsd.port.mk:2028 > '/var/db/pkg/rsync-3.1.3/+CONTENTS': @/usr/bin/env -i PKG...) > *** Error 1 in /usr/ports/net/rsync > (/usr/ports/infrastructure/mk/bsd.port.mk:2451 'install') > *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2135 > '/usr/ports/pobj/rsnapshot-1.4.2/.dep-net-rsync') > *** Error 1 in /usr/ports/net/rsnapshot > (/usr/ports/infrastructure/mk/bsd.port.mk:2451 'prepare') > > I have successfully installed programs > with no dependencies using command > 'doas make install' as the final step, > after fetch,patch,gen,configure,etc. > Is this the right way? > > Why doesn't a make install command as a local user > while in 'net/rsnapshot' call doas on it's own? > make install, make update, pkg_add are basically the same thing. doas will follow what is set as ok in /etc/doas.conf doas itself is a much improved version of sudo. sudo is in packages if you want it for some other port, but doas is better. /etc/mk.conf has SUDO=doas which reflects the past usage of sudo before doas was created. OpenBSD has a lot of distinguishing characteristics different than other OS's. One high priority is security. Installing software means that only a user given the right to do so, may do it. If you have no /etc/doas.conf allowing any user to act as root, then no one else except root can install programs. Having anything that overrides that is disastrous for security. evil_user $ make install my_erase_all_files_malware would really be a bit of a problem. evil_user $ doas pkg_add my_erase_all_files_malware will fail unless you have mistakenly given evil_user such broad powers. Please read and re-read all of the manual pages involved. doas doas.conf mk.conf bsd.port.mk pkg_add, pkg_create, pkg_ anything. The main site has a man page program that you can setup to give you the proper (base system) man pages online for whichever version of OpenBSD you are running. also, if you haven't, read all those links on the home page. Search the mailing list history too. https://marc.info and many other sites. Personally, I have found doing general searches about OpenBSD to not be very helpful. The information is often very old or not useful. Your reults may vary. You can do everything with any port except install it. Play around with building and testing and all the different make clean variations. When you hit a dependency that insn't installed, then you would need to use doas manually. Have fun! Chris Bennett
ports: pkg_add as root
I'm have never tried the ports system before. I have read through the faq and the man pages, but I get stuck at building dependencies. I follow through the fetch,checksum steps and then for 'make prepare' as local user, I'm greeted with following message. This is for the 'rsnapshot' package ===> Building package for rsync-3.1.3 Create /usr/ports/packages/amd64/all/rsync-3.1.3.tgz Creating package rsync-3.1.3 Link to /usr/ports/packages/amd64/ftp/rsync-3.1.3.tgz ===> Cleaning for rsync-3.1.3 ===> Verifying specs: c ===> found c.95.1 ===> Installing rsync-3.1.3 from /usr/ports/packages/amd64/all/ pkg_add: pkg_add must be run as root *** Error 1 in /usr/ports/net/rsync (/usr/ports/infrastructure/mk/bsd.port.mk:2028 '/var/db/pkg/rsync-3.1.3/+CONTENTS': @/usr/bin/env -i PKG...) *** Error 1 in /usr/ports/net/rsync (/usr/ports/infrastructure/mk/bsd.port.mk:2451 'install') *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2135 '/usr/ports/pobj/rsnapshot-1.4.2/.dep-net-rsync') *** Error 1 in /usr/ports/net/rsnapshot (/usr/ports/infrastructure/mk/bsd.port.mk:2451 'prepare') I have successfully installed programs with no dependencies using command 'doas make install' as the final step, after fetch,patch,gen,configure,etc. Is this the right way? Why doesn't a make install command as a local user while in 'net/rsnapshot' call doas on it's own?
