Am 15.06.2026 um 16:47 schrieb Dave Fisher:
The rules for ASF release urls are more complicated than simply
downloads.apache.org/openoffice/.
We should look into official methods. Or other hosting where we can follow the
rules.
Good point.
I checked
# https://www.apache.org/legal/release-policy.html
# https://infra.apache.org/release-download-pages.html
# https://www.apache.org/info/verification.html
Here are the points i found:
# current release has to be uploaded to
https://downloads.apache.org/openoffice/ (check, i do suggest to use the
url https://downloads.apache.org/openoffice/deb for debian family
Distros and https://downloads.apache.org/openoffice/rpm for rpm based
distros.) # we must upload a source distribution (irrelevant to the
distro repository) # we need to present a download page (our download
page should stay unaffected, we could of course ) # A release artifact
should have a recommended size of 100MB but no more then 1GB. (we are at
~ 160MB per language / language files are all below 1 MB) # we should
only upload releases ( that is the case) # we should use a default lua
script for handling downloads, but we can use our own. - this should be
in accordance with infra (dont we use a special download script?) # we
should archive the older releases ( will be done automatically.) # we
may only upload binary/bytecode files that are the result of compiling
the release. (Files we add are txt files, and therefore not caught by
this restriction)
# All supplied packages MUST be cryptographically signed with an
ASCII-armored detached signature. (i assume that the method we use will
work for a repo. )
The following is an action item:
# If an Apache PMC wishes to publish additional materials through the
official distribution channel and there is any question about the
suitability of the materials, the PMC *must* consult with the ASF Board
before publishing.
(we would need to publish config files for the package manager, so we
must consult with the ASF board, before we do this. So we should be able
to describe what we need and if it works.)
Please add if i missed something.
All the best
Peter
On Jun 14, 2026, at 10:43 PM,[email protected] wrote:
Hi Dean!
Am 14.06.2026 um 10:34 schrieb Dean Webber:
Dear all,
Would be great to have access to AOO from the package manager. Perhaps it is
straightforward to create a repo?
A quick search found a guide
at,https://wiki.deimos.fr/creating-a-debian-repository/
Seems a few commands to create the files, then the repo can be hosted somewhere
on the server. I believe this would be helpful and enable another pathway for
access to AOO and updates.l
In order to do this within ASF project resources, we would need to think on our
release process.
We would need to restructure the files in folders.
|https://downloads.apache.org/openoffice/ ├── 4.1.15/ (existing release
tarballs/installers) ├── deb/ (NEW - Debian/Ubuntu apt repo) │ ├── dists/ │ ├──
pool/ │ └── apacheoo.gpg └── rpm/ (NEW - Fedora/RHEL/openSUSE repo) ├──
repodata/ └── x86_64/|
And we could then advice :
|# Debian/Ubuntu debhttps://downloads.apache.org/openoffice/deb stable main #
Fedora/RHEL baseurl=https://downloads.apache.org/openoffice/rpm/|
Since our download page still points to sf.net, we would not need to change
files there.
If we want to do this we should provide PRs to guru and AUR, because they need
new locations. I am not aware of other install resources that use download
links.
We should think about if we need to produce all language installers for Linux,
or if we could do some nice dependency definition that you must download a
language file, saving download space.
If people download per package manager that would simplify thing a lot.
At this stage I am still learning, and in the process of a few things that
should help improve my understanding.
But making progress. Slow as it may be, progress is progress.
Faithfully,
Dean
---------------------------------------------------------------------
To unsubscribe, e-mail:[email protected]
For additional commands, e-mail:[email protected]
