#6039: koji database read-only access request
by Fedora Release Engineering
#6039: koji database read-only access request
-----------------------------+------------------------
Reporter: till | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 20 Final | Component: koji
Keywords: meeting | Blocked By:
Blocking: |
-----------------------------+------------------------
I would like to improve the status information about packages with broken
dependencies. For this is would be helpful if I can access a database that
contains information about which RPM provided what. Then in case of broken
dependencies, it is easier to properly identifiy which package provided a
dependency for another package. AFAICS only koji contains information
about every RPM ever shipped but there seems to be no other way to access
this information than to crawl once through koji or accessing the
database.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6039>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
9 years, 3 months
#5922: skip 32-bit arches for fedora-cloud-atomic.ks and fedora-cloud-bigdata.ks
by Fedora Release Engineering
#5922: skip 32-bit arches for fedora-cloud-atomic.ks and fedora-cloud-bigdata.ks
-----------------------------+------------------------
Reporter: mattdm | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 20 Final | Component: other
Keywords: | Blocked By:
Blocking: |
-----------------------------+------------------------
The Cloud SIG decided that the Atomic and Big Data images will be 64-bit
only. (Docker currently only works in 64 bits, and while big data tools
might work, the target audience is almost always on 64 bits).
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5922>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
9 years, 3 months
#5859: Releng improvements ideas 2014
by Fedora Release Engineering
#5859: Releng improvements ideas 2014
-----------------------------+------------------------
Reporter: till | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 20 Final | Component: other
Keywords: meeting | Blocked By:
Blocking: |
-----------------------------+------------------------
Ideas to improve releng:
- Properly announce in advance if meetings are skipped
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5859>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
9 years, 3 months
#5891: Deliverables and release engineering changes for Fedora.Next/Fedora 21
by Fedora Release Engineering
#5891: Deliverables and release engineering changes for Fedora.Next/Fedora 21
-----------------------------+------------------------
Reporter: jreznik | Owner: rel-eng@…
Type: enhancement | Status: new
Milestone: Fedora 21 Alpha | Component: other
Keywords: | Blocked By:
Blocking: |
-----------------------------+------------------------
Fedora Working Groups are discussing different options how to deliver
specific Fedora Products. These deliverables has to be collected (and
agreed on) to plan changes in Fedora release engineering process.
This ticket should serve to collect requirements from WGs in a centralized
way (as there's possible overlap etc). For specific implementation
details, new tickets will be created.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5891>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
9 years, 3 months
#5944: drop "bigdata" from build-cloud-images for f21 -- feature was postponed
by Fedora Release Engineering
#5944: drop "bigdata" from build-cloud-images for f21 -- feature was postponed
-----------------------------+------------------------
Reporter: mattdm | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 20 Final | Component: other
Keywords: | Blocked By:
Blocking: |
-----------------------------+------------------------
Big Data cloud image isn't going to make the milestone, so we should stop
trying to make the image.
Still hoping to do this for F22, so if we can keep the rawhide one,
awesome.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5944>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
9 years, 3 months
#6004: Trigger new Atomic builds based on bash vulnerability
by Fedora Release Engineering
#6004: Trigger new Atomic builds based on bash vulnerability
-----------------------------+------------------------
Reporter: jzb | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 21 Alpha | Component: koji
Keywords: security | Blocked By:
Blocking: |
-----------------------------+------------------------
We have packages out for the bash vulnerability for Fedora 21 alpha, but
users cannot "yum update" the Atomic images. We need to spin + push out
new images and/or an update tree for users who are on Atomic.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6004>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
9 years, 3 months
#6031: Create Fedora 21 Final test compose (TC) and release candidate (RC)
by Fedora Release Engineering
#6031: Create Fedora 21 Final test compose (TC) and release candidate (RC)
-----------------------------+------------------------
Reporter: adamwill | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 21 Final | Component: koji
Keywords: | Blocked By:
Blocking: |
-----------------------------+------------------------
It's time - sort of - for 21 Final TC1. Yes, even though Beta isn't quite
out yet. Yes, we have laid in extra whisky. The schedule hasn't been
updated, but sgallagh's been pushing to do an earlier TC1, QA and releng
aren't opposed, and it'll give us a fixed upgrade.img mirrormanager can
point at for fedup purposes, so let's just do it.
About that fedup thing, that's the only build we explicitly want to pull
in for TC1:
* [https://admin.fedoraproject.org/updates/systemd-216-8.fc21
systemd-216-8.fc21] for
[https://bugzilla.redhat.com/show_bug.cgi?id=1159292 #1159292]
please make sure whatever needs doing to make the tree's upgrade.img
images be built with that systemd happen. Thanks!
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6031>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
9 years, 3 months
rhel_to_json
by Pierre-Yves Chibon
Hi all,
This morning I wrote a small script that converts yum's medata into a small json
blob that can be used to check if a package is present in RHEL before creating a
branch for it in EPEL, or to restrict building the package on EPEL for certain
arch.
What is does it basically:
- For a list of RHEL version
- For a list of directories specific to that RHEL version
- Find all the primary.sqlite database
- Decompress them if needed
- For all the packages listed in the database
- get the base package (using the srpm info)
- get the epoch, version, release (does nothing w/ it atm)
- get the arch - As more arch are found the list grows
- Store of the info in a json
- Dump the json into a text file
So using this, we are quickly able to check if a package is in RHELX, for
example:
>>> import json
>>> with open('pkg_el7.json') as stream:
... data = json.load(stream)
>>> 'python-zope-interface' in data
True
>>> data['python-zope-interface']
{u'release': u'4.el7', u'epoch': u'0', u'version': u'4.0.5', u'arch': [u'ppc64',
u'x86_64']}
The script is fairly quick to run:
time python rhel_to_json.py
...
2316 packages retrieved in el6
Output File: pkg_el6.json
...
2514 packages retrieved in el7
Output File: pkg_el7.json
...
1395 packages retrieved in el5
Output File: pkg_el5.json
real 0m47.411s
user 0m16.989s
sys 0m5.888s
And its output:
du -sh pkg_*
144K pkg_el5.json
240K pkg_el6.json
252K pkg_el7.json
Hope this helps,
Pierre
9 years, 3 months
[PATCH 0/2] Adjust mkbranch for automating git branch creation
by Pierre-Yves Chibon
Hi all,
Here is a proposed set of changes to the mkbranch script.
The first patch is just replacing all tabs in the file by spaces (simple
clean-up).
The second is the more important one. It drops the use/support of the
-s/--source argument.
This argument is currently used to specify from which point to branch when
creating a branch in the repo.
We argeed that instead of pointing to a specific branch (which would require
keeping a mapping somewhere of which branch should be branched from which other
branch), we would create the new branch by pointing them to the first commit in
the repository.
That's what this commit (hopefully) does :)
Thanks,
Pierre
Pierre-Yves Chibon (2):
Replace tab with spaces
Drop the -s/--source branch argument in mkbranch
roles/distgit/files/mkbranch | 102 +++++++++++++++++++------------------------
1 file changed, 44 insertions(+), 58 deletions(-)
--
1.9.3
9 years, 3 months
#6049: Long running packages in F21 that 'MUST enable the PIE compiler flags'
by Fedora Release Engineering
#6049: Long running packages in F21 that 'MUST enable the PIE compiler flags'
-----------------------------+------------------------
Reporter: moezroy | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 20 Final | Component: git
Keywords: | Blocked By:
Blocking: |
-----------------------------+------------------------
Here https://fedoraproject.org/wiki/Packaging:Guidelines#PIE it says
If your package meets any of the following criteria you MUST enable the
PIE compiler flags:
Your package is long running. This means it's likely to be started and
kept running until the machine is rebooted...
{{{
[root@localhost liveuser]# checksec --proc-all | grep "No PIE"
Xorg.bin 1037 Partial RELRO Canary found NX
enabled No PIE
gnome-session 1227 Partial RELRO Canary found NX
enabled No PIE
at-spi-bus-laun 1300 Partial RELRO Canary found NX
enabled No PIE
at-spi2-registr 1308 Partial RELRO Canary found NX
enabled No PIE
gvfsd 1318 Partial RELRO Canary found NX
enabled No PIE
gvfsd-fuse 1322 Partial RELRO Canary found NX
enabled No PIE
gnome-settings- 1339 Partial RELRO Canary found NX
enabled No PIE
gnome-keyring-d 1344 Partial RELRO Canary found NX
enabled No PIE
gnome-shell 1455 Partial RELRO Canary found NX
enabled No PIE
gsd-printer 1486 Partial RELRO Canary found NX
enabled No PIE
dconf-service 1504 Partial RELRO Canary found NX
enabled No PIE
gnome-shell-cal 1514 Partial RELRO Canary found NX
enabled No PIE
evolution-sourc 1520 Partial RELRO Canary found NX
enabled No PIE
goa-daemon 1526 Partial RELRO Canary found NX
enabled No PIE
ibus-daemon 1530 Partial RELRO Canary found NX
enabled No PIE
mission-control 1534 Partial RELRO Canary found NX
enabled No PIE
ibus-dconf 1541 Partial RELRO Canary found NX
enabled No PIE
ibus-x11 1543 Partial RELRO Canary found NX
enabled No PIE
caribou 1571 Partial RELRO Canary found NX
enabled No PIE
gvfs-udisks2-vo 1586 Partial RELRO Canary found NX
enabled No PIE
gvfs-afc-volume 1594 Partial RELRO Canary found NX
enabled No PIE
gvfs-mtp-volume 1600 Partial RELRO Canary found NX
enabled No PIE
gvfs-gphoto2-vo 1605 Partial RELRO Canary found NX
enabled No PIE
gvfs-goa-volume 1610 Partial RELRO Canary found NX
enabled No PIE
evolution-alarm 1662 Partial RELRO Canary found NX
enabled No PIE
tracker-miner-a 1665 Partial RELRO Canary found NX
enabled No PIE
tracker-store 1670 Partial RELRO Canary found NX
enabled No PIE
seapplet 1671 Partial RELRO Canary found NX
enabled No PIE
tracker-extract 1676 Partial RELRO Canary found NX
enabled No PIE
tracker-miner-u 1680 Partial RELRO Canary found NX
enabled No PIE
gnome-software 1681 Partial RELRO Canary found NX
enabled No PIE
tracker-miner-f 1683 Partial RELRO Canary found NX
enabled No PIE
evolution-calen 1710 Partial RELRO Canary found NX
enabled No PIE
ibus-engine-sim 1740 Partial RELRO No canary found NX
enabled No PIE
gnome-terminal- 1870 Partial RELRO Canary found NX
enabled No PIE
gconfd-2 1876 Partial RELRO Canary found NX
enabled No PIE
bash 1879 Partial RELRO Canary found NX
enabled No PIE
bash 1910 Partial RELRO Canary found NX
enabled No PIE
firefox 5931 Partial RELRO Canary found NX
enabled No PIE
gvfsd-metadata 6054 Partial RELRO Canary found NX
enabled No PIE
oosplash 6140 Partial RELRO Canary found NX
enabled No PIE
gvfsd-burn 6166 Partial RELRO Canary found NX
enabled No PIE
soffice.bin 6227 Partial RELRO No canary found NX
enabled No PIE
evince 6278 Partial RELRO Canary found NX
enabled No PIE
gvfsd-trash 6296 Partial RELRO Canary found NX
enabled No PIE
nautilus 6319 Partial RELRO Canary found NX
enabled No PIE
bash 6339 Partial RELRO Canary found NX
enabled No PIE
python 6366 Partial RELRO No canary found NX
enabled No PIE
sedispatch 678 Partial RELRO Canary found NX
enabled No PIE
firewalld 722 Partial RELRO No canary found NX
enabled No PIE
mcelog 728 Partial RELRO Canary found NX
enabled No PIE
grep 8620 Partial RELRO Canary found NX
enabled No PIE
[root@localhost liveuser]#
}}}
The above packages don't seem to have PIE enabled.
Can someone from releng enable hardening on as many "Long running
packages" as possible before the next F21 Release Candidate.
I am thinking probably a script that adds "%global _hardened_build 1" to
the start of the spec file?
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6049>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
9 years, 4 months