search for: portmgr

...g in the commit message. Any commit that is sweeping, i.e. touches a large number of ports, infrastructural changes, commts to ports with unusually high number of dependent ports, and any other commit that requires the rebuilding of many packages is not allowed without prior explicit approval from portmgr after that date. When in doubt, please do not hesitate to contact portmgr. -erwin -- Erwin Lansing http://droso.org Prediction is very difficult especially about the future erwin@FreeBSD.org -------------- next part -------------- A non-text...

...laid down to mark the last point in the ports tree that officially supported FreeBSD 5.X. Port Manager asks that you not rush to remove 5.X support right away as we'd like a settling-down period, and we want secteam to have a chance to make their EOL announcements as well. Marcus on behalf of portmgr Bcc: ports, developers, portmgr -- Joe Marcus Clarke FreeBSD GNOME Team :: gnome@FreeBSD.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195...

...ory and that's why > > I didn't get the error when I tried 'make readmes'. > > > > Okay, here's the fix for bsd.port.mk. This is the same fix that I > > used about 3 years ago for the do-package: target. > > > > Here's another patch for portmgr to review _in addition to_ the one > > in the previous email for bsd.port.subdir.mk. > > > > Please let me know if you see any more problems. Thanks, > > Oops, I forgot about this patch when I did the last bsd.port.mk run; > this code has now changed. Can you please r...

...2. Implement more drivers. __________________________________________________________________ FreeBSD Port Managers URL: http://www.FreeBSD.org/ports/ URL: http://www.freebsd.org/doc/en/articles/contributing-ports/ URL: http://portsmon.freebsd.org/ URL: http://www.freebsd.org/portmgr/ URL: http://blogs.freebsdish.org/portmgr/ URL: http://www.twitter.com/freebsd_portmgr/ URL: http://www.facebook.com/portmgr Contact: Thomas Abthorpe <portmgr-secretary at FreeBSD.org> Contact: Port Management Team <portmgr at FreeBSD.org> The ports tree contains app...

...ports now. Please update your repository configurations to now only track the /latest repository. This is the default from /etc/pkg/FreeBSD.conf. Remove any overrides from /usr/local/etc/pkg/repos/ for the "ssp" or "new_xorg" repositories. Regards, Bryan Drewery on behalf of portmgr

...mirror_type: "srv", signature_type: "fingerprints", fingerprints: "/usr/share/keys/pkg", enabled: yes } Once that is done you should force reinstall packages from this repository: pkg update pkg upgrade -f Thanks for your help! Bryan Drewery On behalf of portmgr. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: <http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20140820/69ef232c/attachment.sig>

...ports now. Please update your repository configurations to now only track the /latest repository. This is the default from /etc/pkg/FreeBSD.conf. Remove any overrides from /usr/local/etc/pkg/repos/ for the "ssp" or "new_xorg" repositories. Regards, Bryan Drewery on behalf of portmgr

...mirror_type: "srv", signature_type: "fingerprints", fingerprints: "/usr/share/keys/pkg", enabled: yes } Once that is done you should force reinstall packages from this repository: pkg update pkg upgrade -f Thanks for your help! Bryan Drewery On behalf of portmgr. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: <http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20140820/69ef232c/attachment.sig>

...ports now. Please update your repository configurations to now only track the /latest repository. This is the default from /etc/pkg/FreeBSD.conf. Remove any overrides from /usr/local/etc/pkg/repos/ for the "ssp" or "new_xorg" repositories. Regards, Bryan Drewery on behalf of portmgr

...URL: https://www.FreeBSD.org/ports/ How to Contribute URL: https://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html Ports Monitoring Website URL: http://portsmon.FreeBSD.org/index.html Ports Management Team Website URL: https://www.FreeBSD.org/portmgr/index.html Ports Management Team on Twitter URL: https://twitter.com/FreeBSD_portmgr/ Ports Management Team on Facebook URL: https://www.facebook.com/portmgr Ports Management Team on Google+ URL: https://plus.google.com/communities/108335846196454338383 Contact: Ren? Ladan...

...URL: https://www.FreeBSD.org/ports/ How to Contribute URL: https://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html Ports Monitoring Website URL: http://portsmon.FreeBSD.org/index.html Ports Management Team Website URL: https://www.FreeBSD.org/portmgr/index.html Ports Management Team on Twitter URL: https://twitter.com/FreeBSD_portmgr/ Ports Management Team on Facebook URL: https://www.facebook.com/portmgr Ports Management Team on Google+ URL: https://plus.google.com/communities/108335846196454338383 Contact: Ren? Ladan...

> On 21 Dec, 2017, at 14:37, Stephan Bosch <stephan at rename-it.nl> wrote: > > Op 12/19/2017 om 8:41 AM schreef Adam Weinberger: >> I'm getting a behaviour with pigeonhole that I wasn't expecting. Am I >> misunderstanding the design? >> >> I run my messages through a vnd.dovecot.filter. It's essentially this: >> >> filter

...ch_count = 5 namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox FreeBSD { autoexpunge = 17 weeks } mailbox FreeBSD/TodaysCommits { autoexpunge = 2 days } mailbox FreeBSD/automation { autoexpunge = 1 days } mailbox FreeBSD/portmgr { autoexpunge = 26 weeks } mailbox FreeBSD/ports { autoexpunge = 12 weeks } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { autoexpunge = 30 days special_use = \Trash } mailbox spam/probably {...

Hi, Just two quick questions: 1. Would it be possible or difficult to upgrade FreeBSD 4.8 -STABLE to 5.2 -STABLE when it comes out? 2. Which is the best for a production environment, -STABLE or -RELEASE Someone told me they think the latter is better because it doesn't require as much downtime for an upgrade. Thanks Joe

Jacques A. Vidrine wrote: > On Mon, Mar 29, 2004 at 08:14:29PM +0200, Oliver Eikemeier wrote: > >>Jacques A. Vidrine wrote: >> >>>On Sun, Mar 28, 2004 at 03:44:06PM -0800, Oliver Eikemeier wrote: >>> >>>>eik 2004/03/28 15:44:06 PST >>>> >>>>FreeBSD ports repository >>>> >>>>Modified files:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everyone, On October 31st, FreeBSD 5.3 and FreeBSD 5.4 will have reached their End of Life and will no longer be supported by the FreeBSD Security Team. Users of either of those FreeBSD releases are strongly encouraged to upgrade to FreeBSD 5.5 or FreeBSD 6.1 before that date. In addition, the FreeBSD 6.0 End of Life is presently scheduled