See https://github.com/ostreedev/ostree/pull/1984 where OSTree was
changed to try to set group write on directories. We need to set a more
permissive umask to take advantage of it.
This is all done to support writing to the OSTree repo from OpenShift
projects that run as a random UID, but have ftpsync (gid:263) in their
supplemental groups. For more context see: https://pagure.io/releng/issue/8811#comment-629051
Signed-off-by: Mohan Boddu <mboddu@bhujji.com>
Some of our automated testing falls over if the ref file and summary
file are out of sync. This should help.
Signed-off-by: Dusty Mabe <dusty@dustymabe.com>
If there's a problem, the changelog will be empty, which is not
particularly helpful to anybody. Instead of spamming devel@ list with
that, just send the traceback to rel-eng@ together with version of
compose-utils that was used.
Signed-off-by: Lubomír Sedlář <lsedlar@redhat.com>
sync the Everything variant for alt arches again, somehow it got dropped.
link t the alt arch Everything variant as well as the primary variant
makes sure noarch rpms are hardlinked and arch specific ones are as well.
Signed-off-by: Dennis Gilmore <dennis@ausil.us>
We'll do that now in a more centralized manner now that we are
moving to a unified ostree repo setup.
See https://pagure.io/releng/pull-request/7366
Signed-off-by: Dusty Mabe <dusty@dustymabe.com>
Move Atomic to AtomicHost and WorkstationOstree to
AtomicWorkstation. This is mostly to make things align
more with the names of the things we actually put out.
Signed-off-by: Dusty Mabe <dusty@dustymabe.com>
spam-o-matic does not understand rich deps, lets run it stioll but not
have its output emailed out as it is broken
Signed-off-by: Dennis Gilmore <dennis@ausil.us>
Sync the new Modular variant, primary aarch64, armhfp, x86_64
alt: i386, ppc64, ppc64le, s390x
rename the syncing from Docker to Container for recent change
Signed-off-by: Dennis Gilmore <dennis@ausil.us>
As an earlier commit did for the primary rsync target location,
define variables for the alt and secondary target locations for
nightly composes.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
We set $DESTDIR in all these scripts, but then use its value
several times without just...using it. Let's use it!
Signed-off-by: Adam Williamson <awilliam@redhat.com>
For fedmsg_meta we have to provide a 'link'. At present we do
this with a rather large and icky pile of conditionals which
doesn't work properly. It's much simpler to figure out the URL
in the compose script and emit it in the fedmsg, then meta can
just...use it. For older fedmsgs we'll just point to the base
kojipkgs location for the link.
For synced composes, we use the synced URL on dl (this matches
what the meta stuff tried to do before). For non-synced composes
we just use the kojipkgs location.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
The main point here is to include the compose 'shortname' in
compose fedmsgs, as #484 does for post-release compose types.
While doing this I noticed there's rather a lot of mess and
cruft in the various version-related variables here (and a few
others).
`GIT_BRANCH` variable is never used anywhere any more, so it's
removed.
`BRANCH` was never used anywhere, so it is gone. (It appears
to have been added in a25b08c7 but never used). There seemed
to be no useful distinction between `DIST` and `BRANCHED`, and
both actually seem to be used mainly to specify a release
version. The exception is that `BRANCHED` was set to
"Modular-Bikeshed" in nightly-modular.sh , but there is no
justification for this that I can find, and its only practical
use was as the value of the `branch` key in fedmsgs. So far as
I can figure out, the original purpose of the `branch` key was
for when we sent out `compose.branched.(foo)` fedmsgs - it
was e.g. 'f18' when Branched was Fedora 18. As we now don't
send out `compose.branched` messages any more, but include the
release number in the message topic for Branched messages
(e.g. `compose.27`), this purpose no longer applies. So the
key just doesn't seem to have any particular use at all any
more, and I don't think changing its value will have any real
consequences.
Thus, `BRANCH`, `BRANCHED` and `DIST` are replaced by `RELEASE`
and `RELEASE_TITLE`, which specify the release version. Their
values will be identical for numerical release versions, but
for Rawhide and Bikeshed we need to know both the lower-case
and title-case versions of the name; RELEASE_TITLE is the
title-case version.
We use `$SHORT-$RELEASE_TITLE` to replace several instances
of hardcoding in the scripts (e.g. Fedora-Modular-Bikeshed).
The `ATOMIC`, `ATOMICREPO` and `ATOMICDEST` variables that were
blindly copied from nightly.sh to nightly-modular.sh, but never
actually used in it, are also removed.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
