REVIEW/RFC: https://fedoraproject.org/wiki/User:Kevin/Updates_Policy_Draft
by Kevin Fenzi
Greetings.
I'd like to ask for feedback and helping cleaning up an updates policy
draft page:
https://fedoraproject.org/wiki/User:Kevin/Updates_Policy_Draft
How can we clarify the language or the layout of the page to be more
clear? Are there places that it could be more like the existing package
update howto page? Could we be more detailed about what bodhi enforces
and whats just good practice?
Are there other exceptions cases that could be covered that you can
think of?
NOTE that this is a draft. I'd like constructive feedback.
If we can get something that looks ok by next week, FESCo would like to
approve this and put it in place.
Please do try and keep technical and constructive in replies, pretty
please? With a cherry on top?
kevin
13 years, 6 months
Review request: Nice-to-have bug process documentation proposal
by Adam Williamson
Hi, everyone. So we partly used the proposed new nice-to-have bug
tracking system during the F14 Beta process, and it seemed to go well.
In a quick burst of airport productivity, I've quickly written up a
bunch of proposed new wiki pages and modifications to existing ones to
document the nice-to-have process (and, incidentally, extend
documentation of the blocker process, since we don't seem to have much
of it beyond the blocker meeting SOP right now). All the pages can be
found here:
https://fedoraproject.org/wiki/Category:NTH_adjustment_drafts
it should be pretty obvious which are new and which are modifications of
existing pages. I hope this is mostly straightforward and
non-controversial.
A quick five-minute summary is that we will now have (in fact, we
already do) trackers for nice-to-have bugs for Alpha, Beta and Final
releases as well as trackers for blocker bugs. Bugs on these NTH lists
will be given priority after blocker bugs for QA, devel and releng work
for releases. Fixes for these bugs - and *only* these bugs, if a fix is
to be taken through a freeze, there must be a matching accepted NTH bug
- will be taken through release freezes. Proposing, reviewing and
monitoring NTH bugs will work exactly as it does for blocker bugs, and
mostly happen in the blocker meetings, but of course after consideration
of the blocker lists.
In practice this is a formalization of existing procedure - until F14
Beta, QA and releng did much the same process but entirely informally,
we just kept lists of bugs we'd take fixes for either in our heads or in
the RC creation trac tickets. This process is meant to be more robust,
documented and discoverable.
Some releng SOP pages may require minor updates, I figured I'd leave
that to releng. The process for creating blocker trackers should also be
updated to cover creating NTH trackers (I couldn't find that; poelcat,
where is it?)
Comments, questions, suggestions welcome!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
13 years, 6 months
Lookaside failure. Check your cert.
by Chitlesh GOORAH
Hello there,
I'm having the following error with some of my packages (iverilog and
perl-Verilog-Perl) since last week, even after updating my certs.
$ fedpkg import
/home/chitlesh/rpmbuild/SRPMS/iverilog-0.9.20100928-1.el6.src.rpm
Uploading: d004408ea595b13780c4c036f8188b66 verilog-0.9.3.tar.gz
Could not import srpm: Lookaside failure. Check your cert.
However, I managed to build verilator on koji somehow.
Can you please tell me what it may cause this ?
Chitlesh
13 years, 6 months
bodhi v0.7.9 deployed
by Luke Macken
A new version of bodhi has just hit production. This release contains a number
of bugfixes and enhancements.
https://admin.fedoraproject.org/updates
Web UI Changes
==============
- Improved editing functionality
- Only unpush edited updates when builds are altered
- Make a note in the comments of which builds were added/removed
- Allow people to revert their karma vote more than once
- Add mouseover tooltips to the update status with more details
- Prevent different versions of a package from being added to the same update
- Handle more types of bugzilla auto-linking in comments (ex: rhbz#1234)
- Link to the newer update in the obsoleted ones
- Link to gitweb instead of viewvc
- Set default (un)stable karma values if re-enabled
- Anonymous karma has never effected karma, so we now mark them as being ignored
in the interface to make it obvious
- Get the 'suggest reboot' flag working again
- Allow non-critpath updates to be pushed to stable after meeting our critpath
requirements
- Allow maintainers to request that their update be pushed to stable before the
automatic approval job runs, if it already meets the time-in-testing
requirements.
Client Changes
==============
- Add --stablekarma, --unstablekarma, and --disable-autokarma client arguments
- Fix a bug in using `bodhi --push-build=` on multi-build updates
- Add a --bodhi-url command-line option
- Instead of requiring only one argument with a comma separated list of updates,
support several builds as several arguments.
API Changes
===========
- Remove our API pagination query limit of 1000
- Add a new 'author_group' field to each comment in our JSON API
Backend Changes
===============
- Add the new 'dist-fN-updates{-testing,}-pending' tags to builds so AutoQA can
start testing them before they get pushed
- List security & critpath testing updates in our updates-testing digest emails
- Download and inject the pkgtags sqlite db into our repodata from the pkgdb
(which will be utilized by `yum search`)
- Email the proventesters about stale unapproved critical path updates
- Update the bug titles for all security updates before pushing (since security
bug titles frequently change after the update is submitted to reflect the CVE id)
- Improved sanity checking in the masher when resuming pushes
- Properly capture & log stderr from our mash subprocess
- Improved metrics report generator (soon to be integrated into the web
interface)
Bugs & RFEs
===========
Please file and bug reports or enhancement requests here:
https://fedorahosted.org/bodhi/newticket
_______________________________________________
devel-announce mailing list
devel-announce(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-announce
13 years, 6 months
Getting more info about updates on headless server
by Richard Fearn
Hi,
I have yum-updatesd installed on a headless Fedora server, so every so
often I get the email saying there are updates available.
The email itself doesn't tell me much about the updates (e.g. for
iproute tonight it said it was a "bugfix"). Running yum update on the
server doesn't tell me much either.
In the past I modified yum-updatesd-helper to look in the
package-announce list archives
(http://lists.fedoraproject.org/pipermail/package-announce/) to find
each update, and to build a bodhi search URL, using the package
name/version. Then there were at least 1 or 2 links in the
yum-updatesd email that I could click on to get some more information.
Is there a more standard way of getting this info? (Not the links, but
the information about the updates.)
If not, I'll get my modified yum-updatesd-helper working on F13 (I
upgraded from F11 the other day).
Regards,
Rich
13 years, 6 months
systemd and network service
by Patrick Monnerat
Until now (with upstart), my rawhide system started the network service
but not the NetworkManager service.
With systemd, neither of these are started by default.
I've read some previous discussions about creating missing links,
defaults, etc. There is a listed solution based on NetworkManager, but
it is not applicable on the network service, because the file
"/lib/systemd/system/network.service" does not exist and thus cannot be
linked to from a *.wants directory.
Does anybody has resolved this problem ? Thanks for any hints.
Patrick
13 years, 6 months
poppler update to 0.15.0 (0.16 alpha)
by Marek Kasik
Hi all,
I plan to update update poppler in rawhide (Fedora 15) to new
development version 0.15 next week (at Monday, October 4th). Changes
against 0.14.x are:
core:
* Remove exception support
* Improve creation of Annotations
* Fix failure to parse PDF with damaged internal structure.
(Bugs #29189 #3870)
* Add a way to access the raw text of a page
* Speed improvements when reading multiple characters from a
given Stream
* Speed improvements in the Splash backend
* Speed improvement in gray color space calculations
* Speed improvement in ICC color space calculations
* Speed improvement when reading some fonts
* Make GBool a bool instead of an int
glib:
* Add GObject introspection support
* Improve creation of Annotations
* Add a way to get the coordinates of each character of a page
* Add a way to get the page label
* Documentation improvements
* Support password protected documents in the demo
* Support for selection in the demo
* Support for adding annotationss in the demo
* Misc improvements in the internals
qt4:
* Add a way to access the raw text of a page
* Recognize "Print" as named action
* Documentation improvements
build system:
* Add option for autogen.sh to skip configure
* Nicer autogen.sh output
* Improvements when build the glib frontend with CMake
utils:
* pdftohtml: Use splash instead of external gs invocation to
render the background
* pdftohtml: Let the user specify the resolution of the
background. (Bug #29551)
cpp:
* Add a way to access the raw text of a page
+ 2 soname bumps in libpoppler.so.* and libpoppler.glib.so.*.
Please check whether your package builds against this new version of
poppler correctly if you maintain a package which requires it. The new
version has been pushed to git already but not built yet.
Regards
Marek
_______________________________________________
devel-announce mailing list
devel-announce(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-announce
13 years, 6 months
Graphics Test Week final stretch: Intel
by Adam Williamson
Graphics Test Week moves into its final stretch today / tomorrow
(depending where you are!) with Intel graphics Test Day -
https://fedoraproject.org/wiki/Test_Day:2010-09-30_Intel . As with the
others, this event runs all day in #fedora-test-day on Freenode IRC, and
testing instructions and live images (same as for the other two days)
are on the Wiki page. Intel graphics users, please come out and help us
make sure Fedora 14's graphics support is as good as it can be!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
13 years, 6 months