-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all.
I need a clarification about the Changelog section in a spec file
during a package review process.
In particular, pursuant to
http://fedoraproject.org/wiki/Packaging:Guidelines#Changelogs guidelines:
> Every time you make changes, that is, whenever you increment the
E-V-R >of a package, add a changelog entry.
> ... Changelog entries should provide a brief summary of the changes
> done to the package between releases, including noting updating to
> a new version, adding a patch, fixing other spec sections, note
> bugs fixed, and CVE's if any
In https://bugzilla.redhat.com/show_bug.cgi?id=966201, David says that
Changelog changes' list is not necessary during package review process
because it is still a "initial package" state.
For all my packages and not only, every one always asks me to update
the Changelog, also for a minimal modification in a package
pre-review/review process. To be sure and to resolve this issue with
David, I need some clarification regard to how to use properly the
Changelog section since the first package review submit.
Greetings.
- --
Antonio Trande
mailto: sagitter AT fedoraproject.orgwww.fedora-os.org
GPG Key: D400D6C4
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJRqMTHAAoJED2vIvfUANbEkDUP/RmG69AYhO4OyzDhkeqI+EW1
55OmsuFP6TuYaXsP3F5aFTiYFqIUrb2GtH58cWIX8Ou3jmUDjTZGbVKGgCa97O/W
7ONDTX2elc25ZdSoz9iehBOY/SafokRM8ZxSDUIWWzxCVnSrkygAw8fDnWIXEIoF
lIC0pdt/B8BL/BY/2sxKJW8MSQT42LWp2ym67HpmPU3lTQLsJz/TUzFrRBl+fEi0
AojmiT/EUGt1PWqMxvp/n2ASG29/VAag+8heiV7B/08xX+/W2pq1URPBBfO2YIf6
VWQ1jBNHYs7lhvbOov3KKHLsZ57Mz2K8tTeCwHYEWBTOfuTiGbFy1OwuuhBLTQs9
Yb6M8eXCiy646/cOXvNeUyE3Rp1Z5doJYB/Fr2fgXeBpVZa1sqDX8tfJrW1poRpb
97WXsn7Rs23QVu+eU5Dngh7ZJjNOnVHI31e9qVuUGnUnGHmDj3eVeKr0dyEIkZvI
7V3qpLJYwzXcS+Ugz8d+2CvMOqAzZ4fMZZz6sYGt5N4RGYboWdlhJtZezqhevAXS
uzi9328o3RCJMg7dMGzCUAfNxzYLevFWEZ4D3fmpJGJvF4c8YFc/wqmuBLjS03Nq
6AESQsZ9tjAUbiO3FQni1zs95q6fRaQbT/K19kcaCbJxQDPNhhrafF4Rzqoe9FkT
iG6dlsQKqNuBEZZ1HHbB
=HLdP
-----END PGP SIGNATURE-----

Hi
The new version of mod_security (2.7.4) includes a 3rd party code: libinjection
an SQL/SQL injection tokenizer parser analyzer, according to the parser
developer, libinjection is supposed to be embedded into your code [1]
and does not seem to be compiled as shared lib.
In mod_security this library is used as an alternative approach for
detecting SQL injection (vs. regex-based whitelist/blacklist).
My question is: do we consider this code as a Copylibs or I should
proceed with unbundling it from mod_security code.
[1] https://github.com/client9/libinjection#embedding
PS.
I'm one of mod_security maintainer, ccing Peter and Daniel
Thanks.
-- Athmane

Hi,
I'm maintaining youtube-dl, however this software often has updates.
So I want to know if there is an quicker way to push them to stable?
Currently when I update it to x version in testing channel, it just
released y version before x becomes stable. So after many times this
package still roll in the testing.
Thanks.

Following is the list of topics that will be discussed in the FPC
meeting Thursday at 2013-05-23 16:00 UTC in #fedora-meeting-1 on
irc.freenode.net.
Local time information (via. rktime):
2013-05-23 09:00 Thu US/Pacific
2013-05-23 12:00 Thu US/Eastern
2013-05-23 16:00 Thu UTC <-
2013-05-23 17:00 Thu Europe/London
2013-05-23 18:00 Thu Europe/Paris
2013-05-23 18:00 Thu Europe/Berlin
2013-05-23 21:30 Thu Asia/Calcutta
------------------new day----------------------
2013-05-24 00:00 Fri Asia/Singapore
2013-05-24 00:00 Fri Asia/Hong_Kong
2013-05-24 01:00 Fri Asia/Tokyo
2013-05-24 02:00 Fri Australia/Brisbane
Links to all tickets below can be found at:
https://fedorahosted.org/fpc/report/12
= Open Floor =
For more complete details, please visit each individual ticket. The
report of the agenda items can be found at:
https://fedorahosted.org/fpc/report/12
If you would like to add something to this agenda, you can reply to
this e-mail, file a new ticket at https://fedorahosted.org/fpc,
e-mail me directly, or bring it up at the end of the meeting, during
the open floor topic. Note that added topics may be deferred until
the following meeting.