#6286: Please sign all RC and TC images
-------------------------+------------------------
Reporter: genodeftest | Owner: rel-eng@…
Type: enhancement | Status: new
Milestone: | Component: koji
Keywords: | Blocked By:
Blocking: |
-------------------------+------------------------
Current situation: TC and RC images are provided on an server that does
not force encryption ( http://dl.fedoraproject.org/pub/alt/stage/ ) and
does not provide any signatures (see e.g.
http://dl.fedoraproject.org/pub/alt/stage/23_RC10/Workstation/x86_64/iso/
).
Attacker model:
* many government intelligence agencies including (but not limited to) NSA
and GCHQ
* some companies
* criminals
have an interest to intrude PCs of most people in the world. Especially
testers (often software developers themselves) are at risk for being
attacked since they are a high-value target for redistributing malware.
Having unsigned software to download is one way to make this possible.
Please provide Signatures for all RC and TC images in the future.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6286>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#6262: drop rawhide-stable tag and consider master branch to be always stable
-------------------------+------------------------
Reporter: till | Owner: rel-eng@…
Type: enhancement | Status: new
Milestone: | Component: other
Keywords: meeting | Blocked By:
Blocking: |
-------------------------+------------------------
Since we require patch reviews for the rel-eng pagure repo and use it for
running buildbranched/buildrawhide, we can IMHO drop using the rawhide-
stable tag and just consider the master branch to be always stable enough
to run the scripts from it directly.
AFAICS only ansible needs to be adjusted to change the crontab to not
checkout rawhide-stable but master for primary and secondaries systems.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6262>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#6302: Please whitelist nosync for multilib
----------------------+------------------------
Reporter: msimacek | Owner: rel-eng@…
Type: task | Status: new
Milestone: | Component: mash
Keywords: | Blocked By:
Blocking: |
----------------------+------------------------
nosync is a small library used by mock. It is installed in
/usr/lib/nosync/nosync.so, because it's supposed to be used only via
LD_PRELOAD (mock first copies it to buildroot). It seems that mash doesn't
recognize it as multilib, because it's not in standard library location.
Could it be whitelisted for being multilib?
See also: https://bugzilla.redhat.com/show_bug.cgi?id=1283736
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6302>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#6290: new side tag for rawhide llvm builds
---------------------+------------------------
Reporter: airlied | Owner: rel-eng@…
Type: task | Status: new
Milestone: | Component: koji
Keywords: | Blocked By:
Blocking: |
---------------------+------------------------
Hi,
upstream llvm is moving to cmake, and I want to start staging some rawhide
builds so we can track it, before we move it into the main repo.
Can I get a tag created for this.
Thanks,
Dave.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6290>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#6274: Enable keepcache in koji dnf conf
--------------------+------------------------
Reporter: rjones | Owner: rel-eng@…
Type: task | Status: new
Milestone: | Component: koji
Keywords: | Blocked By:
Blocking: |
--------------------+------------------------
Supermin needs access to the pristine RPMs from which the buildroot is
installed, in order to grab the `/etc` (configuration) files into the
libguestfs appliance (the binaries etc are not baked into the appliance
for obvious security/maintainability reasons).
For years we got these from the yum cache, but problem: dnf defaults to
`keepcache=0` and so doesn't save these RPMs.
Therefore please enable keepcache like yum.
I believe the only way to do this is to patch koji, unfortunately:
{{{
diff --git a/koji/__init__.py b/koji/__init__.py
index 612bfd5..0665481 100644
--- a/koji/__init__.py
+++ b/koji/__init__.py
@@ -1324,6 +1324,7 @@ retries=20
obsoletes=1
gpgcheck=0
assumeyes=1
+keepcache=1
# repos
}}}
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6274>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#6268: Arm prevents F23+ builds of gcc
-----------------------------+------------------------
Reporter: jakub | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 23 Alpha | Component: koji
Keywords: | Blocked By:
Blocking: |
-----------------------------+------------------------
I have not been able to successfully build gcc in Fedora 23+ since June,
19th, all the builds fail because on 32-bit arm we trigger the 24 hour
timeout.
Back in June, the Fedora 22 as well as Fedora 23 builds took both around
18 hours on 32-bit arm, which is terrible (compared to 3-8 hours for other
architectures), but still it was possible for the builds to succeed.
The Fedora 22 gcc builds (same source) always succeed even now, still
around 18 hours build time.
The only major difference between F22 and F23 gcc is the default libstdc++
ABI (gcc4-compatible vs. the new one), but that really shouldn't result in
many hours of difference and in the past it didn't result in that.
So, the question is, are F22 and F23/F24 gcc builds (eclipse build target)
going to approximately same hw, or significantly different? Are the
kernels in between those approximately the same?
I've already tried to
%undefine _hardened_build
(which is desirable for gcc in any case, slowing down the compiler for the
address randomization is undesirable), which didn't help, similarly am
doing:
%if 0%{?fedora} >= 23
%ifnarch %{arm}
RUNTESTFLAGS="--target_board=unix/'{,-fstack-protector-strong}'" \
%endif
%else
RUNTESTFLAGS="--target_board=unix/'{,-fstack-protector-strong}'" \
%endif
which should on arm F23+ significantly reduce the amount of gcc testing by
not testing -fstack-protector-strong, only the default options, but it
timed out anyway. So I'm afraid I'm out of ideas what it might be; note,
the compiler is the same, and really should dominate the build time.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6268>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#6308: Requesting side-tag for Node.js 4.x update in Rawhide
----------------------+------------------------
Reporter: sgallagh | Owner: rel-eng@…
Type: task | Status: new
Milestone: | Component: koji
Keywords: | Blocked By:
Blocking: |
----------------------+------------------------
The Node.js SIG would like to start the process of upgrading Rawhide/F24
to use the latest LTS version of Node.js. In order to avoid significant
breakage, we would like to build in a side-tag until a sufficient set of
the core packages are prepped and ready to be merged.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6308>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#6246: FEDORA-2015-14271 update seems botched and stuck :(
----------------------------+------------------------
Reporter: rdieter | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 23 Beta | Component: koji
Keywords: | Blocked By:
Blocking: |
----------------------------+------------------------
https://bodhi.fedoraproject.org/updates/FEDORA-2015-14271
update has been stuck queue'd for stable updates for over a week now...
Hard to tell what exactly is wrong, except for bodhi error:
"...ejected from the push because u"Cannot find relevant tag for
kf5-frameworkintegration-5.13.0-2.fc23: ['f23-updates-candidate', 'f23
-updates-testing-pending', 'f23-updates-pending', 'f23-kde']"
I'm not sure what that means or more to the point, how to fix it.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6246>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#6303: 2015-11-25 - cloud images are failing to build
-----------------------------+------------------------
Reporter: dustymabe | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 23 Final | Component: koji
Keywords: | Blocked By:
Blocking: |
-----------------------------+------------------------
Image builds are failing in rel-eng. One job that failed is:
http://koji.fedoraproject.org/koji/taskinfo?taskID=11974867
The erorr message we are seeing is:
curl: (7) Failed to connect to infrastructure.fedoraproject.org port 80:
Connection timed out
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6303>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project