Re: List of packages upgraded last time `pkg upgrade` was executed
On Wed, 27 Jan 2021, Yasuhiro Kimura wrote:
From: Freddie Cash
Subject: Re: List of packages upgraded last time `pkg upgrade` was executed
Date: Tue, 26 Jan 2021 17:26:29 -0800
/var/log/messages and I think /var/log/daemon include the output of the pkg
commands. If you have the log files backed up from the last time it was
run, you could grep for pkg in those.
No idea if this info is also stored in the sqlite databases pkg uses.
Thank you for reply. But my intention is to write shell script that
gets the list of upgraded packages and does something by using
it. Because of that the list need to be gotton without any user
interaction. So unfortunately your method is not applicable to my
case.
Try something like this as a starting point for a shell script:
sqlite3 /var/db/pkg/local.sqlite \
"select datetime(time,'unixepoch'),origin,version from packages \
where datetime(time,'unixepoch')>=date('now','-7 day') \
order by time desc"
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: poudriere + bdb6 build issue (maybe newbie stupidity)
On Wed, 10 May 2017, Adam Weinberger wrote: On 10 May, 2017, at 10:59, Mike Andrews <mandr...@bit0.com> wrote: I’m experimenting with poudriere for the first time and running into an issue with some ports that use BDB. With this in make.conf: DEFAULT_VERSIONS= bdb=6 I get this for four ports that use BDB 6: [00:00:47] >> [04][00:00:00] Finished build of databases/p5-BerkeleyDB: Ignored: cannot install: no eligible BerkeleyDB version. Requested: 6, incompatible: . Try: make debug-bdb [00:00:47] >> [03][00:00:00] Finished build of databases/ruby-bdb: Ignored: cannot install: no eligible BerkeleyDB version. Requested: 6, incompatible: . Try: make debug-bdb [00:00:48] >> [06][00:00:01] Finished build of www/webalizer: Ignored: cannot install: no eligible BerkeleyDB version. Requested: 6, incompatible: . Try: make debug-bdb [00:00:49] >> [01][00:00:01] Finished build of textproc/redland: Ignored: cannot install: no eligible BerkeleyDB version. Requested: 6, incompatible: . Try: make debug-bdb Installing the ports manually from source works just fine. Am I missing something stupid/obvious here, or is it an issue with those specific four ports? There's a licensing-related peculiarity with bdb 6. Add WITH_BDB6_PERMITTED=yes to your make.conf and it should build for you. That fixed it, thanks! Now where is that documented? Anywhere? Now that I Google that option, okay, it's in bdb.mk, but... hard to do that if you don't know it's there. :) I did (do) have DISABLE_LICENSES=yes in there, but that's more to disable prompts at 'poudriere options' time, I guess. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
poudriere + bdb6 build issue (maybe newbie stupidity)
I’m experimenting with poudriere for the first time and running into an issue with some ports that use BDB. With this in make.conf: DEFAULT_VERSIONS= bdb=6 I get this for four ports that use BDB 6: [00:00:47] >> [04][00:00:00] Finished build of databases/p5-BerkeleyDB: Ignored: cannot install: no eligible BerkeleyDB version. Requested: 6, incompatible: . Try: make debug-bdb [00:00:47] >> [03][00:00:00] Finished build of databases/ruby-bdb: Ignored: cannot install: no eligible BerkeleyDB version. Requested: 6, incompatible: . Try: make debug-bdb [00:00:48] >> [06][00:00:01] Finished build of www/webalizer: Ignored: cannot install: no eligible BerkeleyDB version. Requested: 6, incompatible: . Try: make debug-bdb [00:00:49] >> [01][00:00:01] Finished build of textproc/redland: Ignored: cannot install: no eligible BerkeleyDB version. Requested: 6, incompatible: . Try: make debug-bdb Installing the ports manually from source works just fine. Am I missing something stupid/obvious here, or is it an issue with those specific four ports? ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: amavisd-new crashing
On Sat, 12 Sep 2009, GalaxyPC.Net Administrator wrote: Eric, I battled this all morning and found some helpful posts on the amavisd-new sourceforge lists. In the decoders section of amavisd.conf, look for the following lines. Comment out one at a time, reloading amavisd each time, of course, until you are able to flush your queue successfully. In my case it was 'asc', but in yours I would try 'uue' first. There were suggestions on SF to comment all the 'ascii' lines out. ['asc', \do_ascii], ['uue', \do_ascii], ['hqx', \do_ascii], ['ync', \do_ascii], Yep, I had the same problem on two different machines (one 8.0 one 7.2), and the same fix. The problem is actually in Convert::UUlib, rather than specifically in amavisd-new... commenting out those lines removes all calls to Convert::UUlib thus working around the problem. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: mysql51-server won't start after upgrade
On Sun, 14 Oct 2007, Jeffrey Williams wrote: I just upgraded mysql51-server with cvsup and portupgrade. Now it won't start, and the error I am getting is: [ERROR] /usr/local/libexec/mysqld: unknown variable 'innodb_log_arch_dir=/var/db/mysql/' I have been scanning the release notes, but I haven't found anything yet, that indicates that this variable has been deprecated, and it still appears in the example my.cnf files. I ran into this last week, too. I had to poke around in the InnoDB source for this (as far as I can tell this isn't documented anywhere), but apparently innodb_log_group_home_dir has superceded innodb_log_arch_dir since 4.0, so just change the latter to the former and everything works. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD Port: courier-imap-4.2.0 ssl failure on port 993
Edward Buck wrote: Edward Buck wrote: This is regarding the recent update courier-imap-4.2.0. Not sure if something has changed in functionality or perhaps there was an incompatible configuration change but the update broke my imaps setup. I admit that my SSL libraries might be the problem since there was recently a security update for SSL. I updated SSL using freebsd-update (binary updates) which before today has been pretty reliable. Afterwards, my old courier-imap still worked fine (perhaps because it was still using the old libraries?). Then last night, I updated courier and imaps stopped working (I don't run anything on the standard imap port). The error is: Oct 5 09:40:00 kafka imapd-ssl: couriertls: connect: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number Here's an update on this issue. I forgot to mention earlier than the system is FreeBSD 6.2 p8. The problem seems to be specific to imapd-ssl running on port 993. I didn't spend a lot of time troubleshooting different clients. Previous to the update, I used Thunderbird with SSL/port 993 without problems. Strangely, Korn (KDE mail notifier) seemed to work okay on port 993. It could be a client thing but I suspect they just default to different SSL versions. TLS works just fine on port 143, which is the configuration I've been meaning to switch to for some time. The update forced the issue and thus, this problem is not really one anymore. But for those who are still using imaps on port 993, the update (either the courier-imap update or the SSL update) may cause some problems. I ran into this yesterday. Changing TLS_PROTOCOL=SSL3 to =SSL23 in /usr/local/etc/courier-imap/imapd-ssl (and pop3d-ssl) fixed it. In my case it was client-specific: Pine, and Nagios' check_imap plugin, would generate that exact error... but Thunderbird 2.0 would be fine. I didn't test any other clients. Some Googling showed that this was a change in Courier, not FreeBSD specific -- but it might be worth a note in /usr/ports/UPDATING? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading to amd64 requires recompilation of ports?
On Sat, 16 Jun 2007, Kris Kennaway wrote: I may have had to use the statically linked /rescue to do some things, I don't remember. It's not completely trivial, but someone who knows their way around a FreeBSD system can do it. We did it by using miniroot on swap partition of the system disk. This approach has an advantage of keeping at least one good bootable base system installation in any moment. Also, it allows move in both directions, i.e. i386 - amd64. Yeah, that's a neat trick to remember. Another trick for doing i386-amd64 is to install your new world into a DESTDIR, tar it up, put the tarball onto the root filesystem, boot the new amd64 kernel into single-user mode and use /rescue/tar to spam the amd64 tarball over the i386 world. I've used the miniroot-on-swap approach before. Another trick I used this week (when I had to do four i386-amd64 migrations) was to build a netbootable amd64 system, PXE-boot that, and then installworld to the local disks that way. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
