SysCallError: (-1, 'Unexpected EOF')
by Parag Nemade
Hi rel-eng,
I am frequently submitting package reviews and since a month using
fedora-create-review to submit a package review. I know the error
given in the subject is happening since long time but its breaking the
"fedora-create-review --user abc --koji-target f24 xyz.spec
xyz.src.rpm" command.
Another thing I found is that only scratch build fails with this
error but the same is not always true for real build.
I then searched on google and found this bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1186994 which gives me
https://lists.fedoraproject.org/pipermail/buildsys/2015-January/004484.html
patch. This patch worked for me. My question, is there something else
I am missing that we have not used that patch yet in koji?
Regards,
Parag Nemade.
8 years, 8 months
Rawhide plans
by Kevin Fenzi
Greetings.
We had some nice discussions about rawhide in my friday workshop at
flock. I thought I would post here to get input from folks not there,
and also allow people who were there to comment more now that it's not
after 5pm on a friday of the 3rd day of flock. ;)
* The problems/issues:
First we talked about current issues we see.
I think most everyone was in agreement that once you had a rawhide
install and were just applying updates, you were in pretty good shape.
Much better than you would have been a few years ago. There are bugs,
but they are often easy to workaround with downgrades until they are
fixed, etc. Also dnf tries very hard to not install anything thats part
of a set of broken deps, so while it might take longer to get some
packages you won't break your local install.
I think everyone also agreed that the pain points were around getting a
rawhide install in the first place:
1. boot/netinstall iso is often broken or not produced. Live media
likewise.
2. Upgrading from a stable release is also often hard due to broken
deps, resulting in having to remove packages just to get upgraded.
There was some mention of rawhide not being fully signed (which we
cannot do until we have gating of some kind and the sigul batch signing
bug fixed).
There was mention of larger rebuilds that didn't use side tags. It's
pretty easy to request a side tag from releng and use it to do all your
rebuilds and then get it tagged back in. When larger stacks don't do
this, they break things for a few days while they sort out all the
packages.
Finally there was mention of the baggage associated with the name
"rawhide". To this day I see people telling others that "rawhide will
eat your babies" or "rawhide is a methlab and will blow up in your face
every day".
Do you all see other issues ?
Next I divided things up into 3 time periods. What could we do to make
things better short term (in the next few weeks), medium term (next few
months), longer term (next year).
Short term:
* Hook up openqa to run on rawhide every night and give us data on how
often things are broken on the install path. This could be a seperate
report, or we could hook it up to the rawhide compose.
* Hook up taskotron to run checks on packages as they are built and
send at least to the maintainer about the broken deps. If the
maintainer sees their build causing lots of broken deps they can
untag it or get someone to rebuild all the other packages.
* pungi4 landing. pungi4 is a big re-write of our pungi tool. When we
enable this in rawhide it's going to make rawhide look a lot more
like release trees. Instead of having a rawhide/ dir with just trees
and boot isos, we will have Everything tree like we do at release
time, and server/cloud/workstation trees each with their own branded
netinstall isos, the server dvd and such. Also, pungi4 emits json
logs with exactly what was produced, so we can easily parse from day
to day and know what broke, etc.
* Matt opened a thread on the marketing list about renaming rawhide. It
sounds like most people would prefer us to make the changes first,
then and only then look at renaming.
Medium term:
* Setup some gating. I think it should work like this:
today you build a rawhide build and it tags into f24 tag, which is used
by the daily compose.
I'd like to change that to build into a f24-candidate tag. At that
point taskotron or other tests are run. If the package passes it goes
to f24-pending tag. When a compose happens we run taskotron or other
tests on the f24-pending packages and if they pass, they tag into f24
and the compose happens.
This gives us two points to check/test things. If someone needs to
override due to a check thats wrong or some other need, they can simply
use the existing koji command line client to tag their package over and
it will go out in the compose anyhow. Note that we will then have a log
of who did this. ;)
This will also hopefully allow us to enable autosign for rawhide
packages (if we can get the batch signing bug fixed) since we can sign
them at one of the above points.
Longer term:
* Put in place something so we can tell if a just rebuilt package is:
- in the mock init root
- in the deps for pungi4/mock/etc
- on the boot/netinstall isos
- on live media/images
- not on/used by anything in composes
If it is, then fire off a test rebuild of that thing, test it and only
let the new thing in if it doesn't fail. We can also then relax
requirements for leaf node type packages if we wish.
* Possibly drop daily rawhide composes in favor of just rebuilding
things when something in them changes. ie, new kernel build? then
rebuild images/trees, new cowsay, just rebuild the repo.
Feedback welcome.
kevin
8 years, 8 months
Canceled Event: Fedora Docker & Atomic Tools Demo (Live Broadcast) @ Tue Aug 18, 2015 12pm - 1pm (acarter@redhat.com)
by Amanda Carter
This event has been canceled and removed from your calendar.
Title: Fedora Docker & Atomic Tools Demo (Live Broadcast)
** Note: due to Flock this demo may be brief or cancelled pending decision
made Monday the 17th. **
Hangout: https://plus.google.com/events/c2j57tjpqr8a3h2f2abnl1e4pas
The hangout will be broadcast live & posted at
http://www.youtube.com/watch?v=9Rt5uJFocX0
Q&A - #fedora-meeting-1
--
Purpose: The purpose of a demo is to show our stakeholders what we
completed this iteration, get feedback from them about the changes & set
some context and expectation with them about our direction.
Agenda
* Our focus / priorities this iteration
* Demos
* Q&A
* Focus next iteration
When: Tue Aug 18, 2015 12pm - 1pm Eastern Time
Where: Hangout on Air / YouTube live stream
Calendar: acarter(a)redhat.com
Who:
* acarter(a)redhat.com - organizer
* jkrieger(a)redhat.com
* twaugh(a)redhat.com
* bkabrda(a)redhat.com
* mmcgrath(a)redhat.com
* maherber(a)redhat.com
* jrieden(a)redhat.com
* server(a)lists.fedoraproject.org
* rel-eng(a)lists.fedoraproject.org
* ttomecek(a)redhat.com
* desktop(a)lists.fedoraproject.org
* kasingh(a)redhat.com
* rcm-tools(a)redhat.com
* cloud(a)lists.fedoraproject.org
Invitation from Google Calendar: https://www.google.com/calendar/
You are receiving this courtesy email at the account
rel-eng(a)lists.fedoraproject.org because you are an attendee of this event.
To stop receiving future updates for this event, decline this event.
Alternatively you can sign up for a Google account at
https://www.google.com/calendar/ and control your notification settings for
your entire calendar.
Forwarding this invitation could allow any recipient to modify your RSVP
response. Learn more at
https://support.google.com/calendar/answer/37135#forwarding
8 years, 8 months
#6229: Live ISO image for F23 l10n test day
by Fedora Release Engineering
#6229: Live ISO image for F23 l10n test day
-----------------------------+------------------------
Reporter: anipeter | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 22 Final | Component: koji
Keywords: | Blocked By:
Blocking: |
-----------------------------+------------------------
Hi,
Kindly create a live image for Fedora 23 L10n test day. The test day is
scheduled as below:-
L10n test day: 18th August 2015
Ticket: https://fedorahosted.org/fedora-qa/ticket/473
Please if we can have the image ready by 16th August (Sunday) it would be
really good.
Thanks [[BR]]
Ani Peter [[BR]]
FLTG (https://fedoraproject.org/wiki/FLTG)
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6229>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
8 years, 8 months
#6231: bodhi love to submit batched boost update(s)
by Fedora Release Engineering
#6231: bodhi love to submit batched boost update(s)
----------------------------+------------------------
Reporter: rdieter | Owner: rel-eng@…
Type: defect | Status: new
Milestone: Fedora 23 Beta | Component: other
Keywords: | Blocked By:
Blocking: |
----------------------------+------------------------
On IRC today, I trying to help redi submit all the boost rebuilds to bodhi
in small batches (~50 packages each)... because his previous attempt at
doing all ~321 of them met with much slowness and eventual failure (he
ultimately deleted the update from bodhi).
But now I think both tags and bodhi db are confused. From what I can
tell, there are 132 packages (of the 321) that are still tagged f23
-updates-testing-pending and at least some of them won't allow to be
included in any new update after tagging only f23-updates-candidate, with
an error of the form:
compat-qpid-cpp-0.24-24.fc23 update already exists!
alternatively, should I be submitting this to
https://fedorahosted.org/bodhi instead?
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6231>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
8 years, 8 months
#6233: Secondary arched F23 not signed
by Fedora Release Engineering
#6233: Secondary arched F23 not signed
-----------------------------+------------------------
Reporter: msuchy | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 23 Alpha | Component: other
Keywords: | Blocked By:
Blocking: |
-----------------------------+------------------------
Copr user reported that F23 packages on PPC64LE are not signed:
DEBUG util.py:377: tar ppc64le 2:1.28-6.fc23
fedora 948 k
DEBUG util.py:377: trousers ppc64le 0.3.13-5.fc23
fedora 141 k
DEBUG util.py:377: trousers-lib ppc64le 0.3.13-5.fc23
fedora 165 k
DEBUG util.py:377: tzdata noarch 2015e-1.fc23
fedora 422 k
DEBUG util.py:377: unzip ppc64le 6.0-22.fc23
fedora 178 k
DEBUG util.py:377: ustr ppc64le 1.0.4-18.fc22
fedora 96 k
DEBUG util.py:377: util-linux ppc64le 2.26.2-3.fc23
fedora 2.1 M
DEBUG util.py:377: which ppc64le 2.20-12.fc23
fedora 47 k
DEBUG util.py:377: xkeyboard-config noarch 2.15-2.fc23
fedora 760 k
DEBUG util.py:377: xz ppc64le 5.2.1-3.fc23
fedora 150 k
DEBUG util.py:377: xz-libs ppc64le 5.2.1-3.fc23
fedora 107 k
DEBUG util.py:377: zip ppc64le 3.0-15.fc23
fedora 269 k
DEBUG util.py:377: zlib ppc64le 1.2.8-8.fc23
fedora 98 k
DEBUG util.py:377: Transaction Summary
DEBUG util.py:377:
================================================================================
DEBUG util.py:377: Install 222 Packages
DEBUG util.py:377: Total download size: 141 M
DEBUG util.py:377: Installed size: 590 M
DEBUG util.py:377: Downloading Packages:
DEBUG util.py:377:
--------------------------------------------------------------------------------
DEBUG util.py:377: Total 23
MB/s | 141 MB 00:06
DEBUG util.py:377: Error: Package tar-1.28-6.fc23.ppc64le.rpm is not
signed
Full log is here:
https://copr-
be.cloud.fedoraproject.org/results/thofmann/openrave/fedora-23-ppc64le/00...
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6233>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
8 years, 8 months