notbugAs an Amazon Associate I earn from qualifying purchases.
Want a good read? Try FreeBSD Mastery: Jails (IT Mastery Book 15)

Why was the website so slow for so long?

The cause of the slowdown was a change to the ZFS dataset. In conjunction with the database server, very little caching was being done. This combination resulted in increased disk I/O as the system churned through the database. Details in the blog post which outlines the various things which changed. Many graphs.

non port: security/libassuan-1/pkg-descr
SVNWeb

Number of commits found XX: 2

Sun, 8 Aug 2010
[ 20:36 dougb ] Original commit 
1.2193 MOVED
1.1117 security/Makefile
1.2 security/libassuan-1/Makefile
1.2 security/libassuan-1/distinfo
1.2 security/libassuan-1/pkg-descr
As previously advertised, remove the old libassuan port now that all
consumers have moved to libassuan 2.0.0, or dropped the dependency
Mon, 14 Jun 2010
[ 00:42 dougb ] Original commit 
1.943 UPDATING
1.111 deskutils/kdepim4/Makefile
1.1113 security/Makefile
1.42 security/dirmngr/Makefile
1.126 security/gnupg/Makefile
1.40 security/gpa/Makefile
1.1 security/libassuan-1/Makefile
1.1 security/libassuan-1/distinfo
1.1 security/libassuan-1/pkg-descr
1.16 security/libassuan/Makefile

(Only the first 10 of 13 ports in this commit are shown above. View all ports for this commit)
Update security/libassuan to version 2.0.0, which is required by gnupg 2.0.15

Unfortunately version 2.0.0 is largely incompatible with version 1.x, so it
is necessary to have a stopgap measure while ports that depend on libassuan
can be updated. In conversation with the maintainers of the dependent ports
it was originally considered ideal to prepare updates for the ports first,
then upgrade everything to libassuan 2.x en masse. Since no action has
arisen on that front, go with plan B:

Copy security/libassuan to security/libassuan-1, and update the dependent
ports accordingly. Because this is (intended to be) a _temporary_ measure,
and because no updates for libassuan 1.x are anticipated, and because the
hope is that it can be removed sooner rather than later, it's a copy instead
of a repocopy.

Number of commits found XX: 2

Login
User Login
Create account

Servers and bandwidth provided by
New York Internet, iXsystems, and RootBSD

This site
What is FreshPorts?
About the authors
Issues
FAQ
How big is it?
The latest upgrade!
Privacy
Blog
Contact

Search
Enter Keywords:
 
more...

Latest Vulnerabilities
apache24Apr 02
cactiApr 02
chromiumApr 02
haproxyApr 02
haproxy18Apr 02
haproxy19Apr 02
haproxy21Apr 02
rubygem-json*Apr 02
gnutlsMar 31
postgresql10-serverMar 29
postgresql11-serverMar 29
postgresql12-serverMar 29
postgresql96-serverMar 29
gitlab-ceMar 26
jenkinsMar 25

12 vulnerabilities affecting 110 ports have been reported in the past 14 days

* - modified, not new

All vulnerabilities

Last updated:
2020-04-02 20:42:28


Ports
Home
Categories
Deleted ports
Sanity Test Failures
Newsfeeds

Statistics
Graphs
NEW Graphs (Javascript)
Traffic

Calculated hourly:
Port count 39008
Broken 591
Deprecated 529
Ignore 862
Forbidden 5
Restricted 150
No CDROM 72
Vulnerable 24
Expired 3
Set to expire 498
Interactive 0
new 24 hours 13
new 48 hours23
new 7 days58
new fortnight105
new month165

Servers and bandwidth provided by
New York Internet, iXsystems, and RootBSD
Valid HTML, CSS, and RSS.
Copyright © 2000-2020 Dan Langille. All rights reserved.