Related to closed #10 - Midori 7.0 #11
Comments
|
Hello pin,
pin writes:
[...]
I've follow the work around Midori-7.0 here, https://wip.pkgsrc.org/cgi-bin/gitweb.cgi?p=pkgsrc-wip.git&a=search&h=HEAD&st=commit&s=midori
Thx!
Also, I can see it in http://pkgsrc.se/www/midori
But can't seem to find it in order to build the package on my machine??
```
***@***.*** $ sudo find / -name midori
Password:
/usr/pkgsrc/www/midori
***@***.*** $ pwd
/usr/pkgsrc/wip
***@***.*** $ sudo git pull -r
Already up to date.
Current branch master is up to date.
```
Where do I find the directory?
Thx once again.
wip/midori was used to update www/midori and now it is Midori 7.0,
building and installing www/midori should do the trick.
Have fun!
|
|
Thank you for the quick answer. I didn't wait and updated pkgsrc to the current branch and attempted to build the package... but, other things have changed and it doesn't build. I guess, I have two choices now. Thanks anyway. |
|
You also need security/gcr from current. That should allow it to build.
pin <notifications@github.com> schrieb am Mi. 12. Dez. 2018 um 14:04:
… Thank you for the quick answer. I didn't wait and updated pkgsrc to the
current branch and attempted to build the package... but, other things have
changed and it *doesn't* build. I guess, I have two choices now.
Either move over my whole system to current or build all the needed
dependencies.
Thanks anyway.
Please feel free to close this issue. I'll think about which way I want to
take.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#11 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA04GnKtd_SelxfODTlQnN-iotjtxMdDks5u4P7LgaJpZM4ZPWSf>
.
|
|
@bsiegert One again, thx, you have been amazing. |
ghost
closed this as
wip-sync
pushed a commit
that referenced
this issue
Jul 23, 2020
July 21st, 2020
CHANGES:
* audit: Token TTL and issue time are now provided in the auth portion of
audit logs. [GH-9091]
* auth/gcp: Changes the default name of the entity alias that gets created
to be the role ID for both IAM and GCE authentication. [GH-99]
* core: Remove the addition of newlines to parsed configuration when using
integer/boolean values [GH-8928]
* cubbyhole: Reject reads and writes to an empty ("") path. [GH-8971]
* storage/gcs: The credentials_file config option has been removed. The
GOOGLE_APPLICATION_CREDENTIALS environment variable or default
credentials may be used instead [GH-9424]
* storage/raft: The storage configuration now accepts a new max_entry_size
config that will limit the total size in bytes of any entry committed via
raft. It defaults to "1048576" (1MiB). [GH-9027]
* token: Token creation with custom token ID via id will no longer allow
periods (.) as part of the input string. The final generated token value
may contain periods, such as the s. prefix for service token
indication. [GH-8646]
* token: Token renewals will now return token policies within the
token_policies , identity policies within identity_policies, and the full
policy set within policies. [GH-8535]
FEATURES:
* Monitoring: We have released a Splunk App [9] for Enterprise
customers. The app is accompanied by an updated monitoring guide and a
few new metrics to enable OSS users to effectively monitor Vault.
* Password Policies: Allows operators to customize how passwords are
generated for select secret engines (OpenLDAP, Active Directory, Azure,
and RabbitMQ).
* Replication UI Improvements: We have redesigned the replication UI to
highlight the state and relationship between primaries and secondaries
and improved management workflows, enabling a more holistic understanding
of multiple Vault clusters.
* Resource Quotas: As of 1.5, Vault supports specifying a quota to rate
limit requests on OSS and Enterprise. Enterprise customers also have
access to set quotas on the number of leases that can be generated on a
path.
* OpenShift Support: We have updated the Helm charts to allow users to
install Vault onto their OpenShift clusters.
* Seal Migration: We have made updates to allow migrations from auto unseal
to Shamir unseal on Enterprise.
* AWS Auth Web Identity Support: We've added support for AWS Web
Identities, which will be used in the credentials chain if present.
* Vault Monitor: Similar to the monitor command for Consul and Nomad, we
have added the ability for Vault to stream logs from other Vault servers
at varying log levels.
* AWS Secrets Groups Support: IAM users generated by Vault may now be added
to IAM Groups.
* Integrated Storage as HA Storage: In Vault 1.5, it is possible to use
Integrated Storage as HA Storage with a different storage backend as
regular storage.
* OIDC Auth Provider Extensions: We've added support to OIDC Auth to
incorporate IdP-specific extensions. Currently this includes expanded
Azure AD groups support.
* GCP Secrets: Support BigQuery dataset ACLs in absence of IAM endpoints.
IMPROVEMENTS:
* audit: Replication status requests are no longer audited. [GH-8877]
* audit: Added mount_type field to requests and responses. [GH-9167]
* auth/aws: Add support for Web Identity credentials [GH-7738]
* auth/jwt: Support users that are members of more than 200 groups on Azure
[GH-120]
* auth/kerberos: Support identities without userPrincipalName [GH-44]
* auth/kubernetes: Allow disabling iss validation [GH-91]
* auth/kubernetes: Try reading the ca.crt and TokenReviewer JWT from the
default service account [GH-83]
* cli: Support reading TLS parameters from file for the vault operator raft
join command. [GH-9060]
* cli: Add a new subcommand, vault monitor, for tailing server logs in the
console. [GH-8477]
* core: Add the Go version used to build a Vault binary to the server
message output. [GH-9078]
* core: Added Password Policies for user-configurable password generation
[GH-8637]
* core: New telemetry metrics covering token counts, token creation, KV
secret counts, lease creation. [GH-9239] [GH-9250] [GH-9244] [GH-9052]
* physical/gcs: The storage backend now uses a dedicated client for HA lock
updates to prevent lock table update failures when flooded by other
client requests. [GH-9424]
* physical/spanner: The storage backend now uses a dedicated client for HA
lock updates to prevent lock table update failures when flooded by other
client requests. [GH-9423]
* plugin: Add SDK method, Sys.ReloadPlugin, and CLI command, vault plugin
reload, for reloading plugins. [GH-8777]
* plugin (enterprise): Add a scope field to plugin reload, which when
global, reloads the plugin anywhere in a cluster. [GH-9347]
* sdk/framework: Support accepting TypeFloat parameters over the API
[GH-8923]
* secrets/aws: Add iam_groups parameter to role create/update [GH-8811]
* secrets/database: Add static role rotation for MongoDB Atlas database
plugin [GH-11]
* secrets/database: Add static role rotation for MSSQL database plugin
[GH-9062]
* secrets/database: Allow InfluxDB to use insecure TLS without cert bundle
[GH-8778]
* secrets/gcp: Support BigQuery dataset ACLs in absence of IAM endpoints
[GH-78]
* secrets/pki: Allow 3072-bit RSA keys [GH-8343]
* secrets/ssh: Add a CA-mode role option to specify signing algorithm
[GH-9096]
* secrets/ssh: The Vault SSH Helper can now be configured to reference a
mount in a namespace [GH-44]
* secrets/transit: Transit requests that make use of keys now include a new
field key_version in their responses [GH-9100]
* secrets/transit: Improving transit batch encrypt and decrypt latencies
[GH-8775]
* sentinel: Add a sentinel config section, and
"additional_enabled_modules", a list of Sentinel modules that may be
imported in addition to the defaults.
* ui: Update TTL picker styling on SSH secret engine [GH-8891]
* ui: Only render the JWT input field of the Vault login form on mounts
configured for JWT auth [GH-8952]
* ui: Add replication dashboards. Improve replication management
workflows. [GH-8705].
* ui: Update alert banners to match design systems black text. [GH-9463].
BUG FIXES:
* auth/oci: Fix issue where users of the Oracle Cloud Infrastructure (OCI)
auth method could not authenticate when the plugin backend was mounted at
a non-default path. [GH-7]
* core: Extend replicated cubbyhole fix in 1.4.0 to cover case where a
performance primary is also a DR primary [GH-9148]
* seal/awskms: fix AWS KMS auto-unseal when AWS_ROLE_SESSION_NAME not set
[GH-9416]
* sentinel: fix panic due to concurrent map access when rules iterate over
metadata maps
* secrets/aws: Fix issue where performance standbys weren't able to
generate STS credentials after an IAM access key rotation in AWS and root
IAM credential update in Vault [GH-9186]
* secrets/database: Fix issue where rotating root database credentials
while Vault's storage backend is unavailable causes Vault to lose access
to the database [GH-8782]
* secrets/database: Fix issue that prevents performance standbys from
connecting to databases after a root credential rotation [GH-9129]
* secrets/gcp: Fix issue were updates were not being applied to the
token_scopes of a roleset. [GH-90]
* secrets/kv: Return the value of delete_version_after when reading
kv/config, even if it is set to the default. [GH-42]
* ui: Add Toggle component into core addon so it is available in KMIP and
other Ember Engines.[GH-8913]
* ui: Disallow max versions value of large than 9999999999999999 on kv2
secrets engine. [GH-9242]
* ui: Add and upgrade missing dependencies to resolve a failure with make
static-dist. [GH-9277]
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Sorry if this is a stupid question, or even just a noob question...
I've follow the work around Midori-7.0 here, https://wip.pkgsrc.org/cgi-bin/gitweb.cgi?p=pkgsrc-wip.git&a=search&h=HEAD&st=commit&s=midori
Thx!
Also, I can see it in http://pkgsrc.se/www/midori
But can't seem to find it in order to build the package on my machine??
Where do I find the directory?
Thx once again.
EDIT: Ops! I found it... it's in current/pkgsrc. Wow! That was fast...
Is it possible to build it on 8.0 formal?
The text was updated successfully, but these errors were encountered: