patchdeb
DE EN

This is a convenience translation. Only the German version is legally binding: Nutzungsbedingungen (AGB). In the event of any discrepancy, the German wording prevails.

Terms of use for repository access

patchdeb · As of: October 2026

1. Parties and subject matter

  1. These terms govern the use of the APT repository “patchdeb” (the “repository”) between Eduard Mehrtens e.K., Am Hagen 15, 28790 Schwanewede, Germany (“provider”) and the customer (“customer”).
  2. The subject matter of the contract is solely access to the repository and to the packages provided there at the time of the order, in their respective state. The service is provided digitally only: credentials by email, packages for download over the internet. No physical goods are delivered. The software itself, further or updated packages, support and consulting are not subject matter of the contract.
  3. The packages provided in the repository contain open-source software, in particular PHP under the PHP License, as well as further components under their respective licences. The customer's rights to this software arise solely from those licences and are neither extended nor restricted by these terms. The provider does not sell the software.
  4. The offer is directed at entrepreneurs within the meaning of § 14 BGB, legal persons under public law and special funds under public law. By placing an order the customer confirms that they are acting as an entrepreneur. Should, exceptionally, a consumer place an order, the statutory consumer protection provisions and the information under Refunds & withdrawal apply in addition.

2. Conclusion of contract and payment processing

  1. Sale, invoicing and payment processing are handled by the reseller and merchant of record Paddle.com Market Ltd., Judd House, 18–29 Mora Street, London EC1V 8BT, United Kingdom (“Paddle”). The purchase contract for the access is concluded between the customer and Paddle; Paddle's buyer terms apply to the purchase in addition.
  2. The provider performs the service, namely the provision of access, towards the customer in accordance with these terms.
  3. All prices stated on the website exclude statutory VAT. With a valid VAT identification number, Paddle bills EU customers under the reverse-charge procedure.

3. Plans and scope of access

  1. Access is offered in plans that differ by the permitted number of servers: up to 100, up to 300 or up to 1,000 servers. The plan chosen at the time of the order is decisive.
  2. A server is any physical or virtual host that accesses the repository with the customer's credentials, regardless of how many PHP versions are installed on it.
  3. Access covers all distributions and PHP versions provided in the repository. There is no restriction to individual distributions or versions.
  4. If the number of accessing servers permanently exceeds the limit of the plan booked, the provider will notify the customer in text form. The customer may then move to a larger plan or reduce the number of servers. If they do not do so within 14 days, the provider may restrict access until the matter is resolved.

4. Activation and credentials

  1. The provider activates access within 24 hours of receiving the order confirmation from Paddle and sends the credentials (customer identifier and access token) and the public repository key to the email address given at the time of the order.
  2. The credentials are assigned to the customer and may be used only on servers the customer operates themselves or whose administration they are responsible for. Passing them on to third parties, publishing them or making the access available to third parties (for example as a mirror or proxy for third-party systems) is not permitted. The customer keeps the credentials secret and informs the provider without delay if they suspect misuse; the provider then issues new credentials.
  3. The customer keeps the email address on file valid and able to receive mail. Credentials, notices under clause 3.4 and communications concerning the contract are sent to that address. The customer ensures that messages from the provider actually reach them and are not filtered out by spam filters, a full mailbox or forwarding rules.

5. State of the packages, no updates, security notice

  1. The customer receives access to the repository in the state it has at the time of the order. The packages described on this website were built between 21 and 26 October 2026 from the source packages named. The repository's package indexes (Release files) are signed with the provider's repository key; apt uses it to verify the authenticity of the index and the checksums (SHA256) of every package. The individual .deb files carry no signature of their own.
  2. The provider owes no further packages, no new PHP releases, no updates to existing packages and no security updates. Should the provider nevertheless add further packages to the repository, this is done voluntarily and establishes no claim to future additions.
  3. The packages of the PHP branches 8.2, 8.3 and 8.4 correspond to the official releases of the PHP Group that contain the fixes for CVE-2026-109618 and CVE-2026-109619. The packages of the branches 8.1 and older correspond to the last official release of the respective branch, supplemented solely by the fixes for these two vulnerabilities backported by the provider (emergency patch). Other vulnerabilities that have become known in these branches since the PHP Group ended their maintenance, or that become known in future, are not fixed in these packages. The customer acknowledges this.
  4. The customer alone is responsible for assessing whether the packages are suitable for their systems, applications and security requirements. They test the packages in a suitable test environment before production use, keep backups of their systems and have apt verify the signature of the package index using the repository key provided.

6. Availability

  1. The provider endeavours to achieve high availability of the repository but owes no particular availability. Where possible, the provider announces maintenance work in advance in text form.
  2. The customer may cache downloaded packages within their own infrastructure (for example with an apt cache or a mirror for their own servers) in order to be independent of the repository's availability. Clause 4.2 remains unaffected.

7. Term and termination

  1. The contract runs for twelve months from activation and renews for a further twelve months each time unless it is terminated before the end of the respective term. Termination is possible at any time with effect from the end of the term through the Paddle customer portal or in text form to the provider.
  2. The right to terminate for cause remains unaffected. Cause exists for the provider in particular where the customer passes on credentials contrary to clause 4.2 or, despite notice under clause 3.4, continues to use the access beyond the plan booked.
  3. At the end of the contract, access is deactivated. Packages already installed on the customer's servers are unaffected; they remain subject to the licences named in clause 1.3.

8. Warranty

  1. The provider warrants that the repository is reachable with the customer's credentials during the term and that the packages correspond to the descriptions on the website at the time of the order. Otherwise the statutory warranty rules apply.
  2. The open-source software contained in the packages is provided in the state in which it exists in the respective release. The provider gives no guarantee of characteristics beyond that, in particular none as to freedom from vulnerabilities other than those named in clause 5.3.

9. Liability

  1. The provider is liable without limitation for intent and gross negligence and for injury to life, body or health.
  2. In cases of simple negligence the provider is liable only for the breach of material contractual obligations (cardinal obligations), limited to the foreseeable damage typical of the contract. To that extent liability for lost profit and indirect consequential loss is excluded.
  3. Liability under the Product Liability Act remains unaffected.
  4. For loss of data the provider is liable only to the extent that the damage would also have occurred had the customer performed proper data backup.
  5. If the customer has omitted the checks under clause 5.4 or has not carried them out properly, § 254 BGB applies. Fault on the part of the customer may reduce the claim for compensation or, where the damage would have been avoidable had the check been carried out properly, exclude it.

10. Data protection

The provider processes personal data only in so far as this is necessary for the performance of the contract and the operation of the repository. Access to the repository is logged for access control and for compliance with the number of servers. Details including data categories, legal bases and retention periods: privacy policy.

11. Final provisions

  1. German law applies, excluding the UN Convention on Contracts for the International Sale of Goods.
  2. If the customer is a merchant, a legal person under public law or a special fund under public law, the place of jurisdiction is the provider's registered office.
  3. Should individual provisions be invalid, the remainder of the contract remains effective.
  4. The German version of these terms is authoritative.

Contact: info@patchdeb.com