Changelog usage clarification
by Antonio Trande
-----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.org
www.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-----
6 years, 9 months
Summary/Minutes from today's FPC Meeting (2013-05-30 16:00 - 16:30 UTC)
by James Antill
=============================================
#fedora-meeting-1: Fedora Packaging Committee
=============================================
Meeting started by spot at 16:01:40 UTC. The full logs are available at
http://meetbot.fedoraproject.org/fedora-meeting-1/2013-05-30/fpc.2013-05-...
.
Meeting summary
---------------
* Roll Call (spot, 16:01:48)
* Bundling libxdiff in libgit2 - https://fedorahosted.org/fpc/ticket/276
(spot, 16:06:54)
* ACTION: spot needs more clones. (spot, 16:07:11)
* Add note about network access to guidelines -
https://fedorahosted.org/fpc/ticket/295 (spot, 16:08:12)
* ACTION: approved (+1:7, 0:0, -1:0) (spot, 16:10:46)
* Simplifying Ruby Guidelines - https://fedorahosted.org/fpc/ticket/296
(spot, 16:11:43)
* ACTION: draft rejected, tests must be unpacked in %prep to allow for
patching. (+1:0, 0:0, -1:7) (spot, 16:16:32)
* Open Floor (spot, 16:16:39)
Meeting ended at 16:29:24 UTC.
Action Items
------------
* spot needs more clones.
* approved (+1:7, 0:0, -1:0)
* draft rejected, tests must be unpacked in %prep to allow for patching.
(+1:0, 0:0, -1:7)
Action Items, by person
-----------------------
* spot
* spot needs more clones.
* **UNASSIGNED**
* approved (+1:7, 0:0, -1:0)
* draft rejected, tests must be unpacked in %prep to allow for
patching. (+1:0, 0:0, -1:7)
People Present (lines said)
---------------------------
* spot (29)
* RemiFedora (16)
* tibbs|w (13)
* limburgher (9)
* abadger1999 (6)
* SmootherFrOgZ (5)
* geppetto (5)
* zodbot (3)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
6 years, 9 months
Retired eclipse-wtp-jst-web, can't access rel-eng trac to file ticket
by Gerard Ryan
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi,
I've just retired eclipse-wtp-jst-web from rawhide and F19. I'm
following the instructions on the wiki[0], but I'm failing at the last
step.
It says:
File a ticket[1] for rel-eng (component koji) asking the package to be
blocked from the appropriate collections in which it is retired.
I'm getting an error on the trac page saying that "TICKET_CREATE
privileges are required to perform this operation".
Any suggestions?
Thanks a lot,
Gerard.
[0] https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
[1] https://fedorahosted.org/rel-eng/newticket
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
iQIcBAEBCAAGBQJRpRCaAAoJEG7cfkpivEoVIe8P/jj4GcIae6vL00FxI/r+b3b/
f9bgwOV+BrXpqzuLPoZ6ZAkjXR/evvQaGylkMvnDeW4Eu+lL42MfYuMW7rBmCzRm
Wif3+XSuw+XAuDYP6qbE1FcfzHs+RodR8nLgfbaGpqjJoDjJ4JEQRtGJYk0CzM8C
b7NdcrJrCn5ML0k0/hIxPJGGHXS0quEhPYaorTjLkC13skiinjUM/0JSyHCJXfLw
6ho93DW1t5PP2vm4OKtL7ZLC3liDwQZQANLu1laC2cgoq0XBan9vC6k0hXRjf7Wu
56AlxMlutV9fqLmLsEj0uO+D/NaFcSGojjuQxy0egjGT+Xkt9GQ6tK6xouE60IHl
4hba4C55gqwamMzT91mc1nGCZsks8RXETHtqWqt2Jxng2BRjEb58VVX+JebThxey
qota7BGw/2WMlVB3+VIsXa2H7krUsZ52d4rpFHf/rkzhcK3eqQ0UV47nrc78Sskj
ITcWbR7k7WfcO9NnGn4X44E6mySxrOhVAT+Bt7JuPqYW2UNctr4YOKYkli9Eq4tQ
ZQwtIhusN/niJcOI0tJWA22uNfHfMwGVFS0yOQ5SdiVgssEZwHcaF2fA5nGCsikC
1uX3EQK56y66JKMxU9CoUPs9TiJuBp1buSgnH1dZ8jRm4USCZnVAVcHkuTl/8b+6
Xm/nsk+FEmZOwp39lVE6
=udfR
-----END PGP SIGNATURE-----
6 years, 9 months
mod_security bundling code from 3rd party
by Athmane Madjoudj
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
6 years, 9 months
How to push updates more quickly?
by Christopher Meng
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.
6 years, 9 months
Summary/Minutes from today's FPC Meeting (2013-05-23 16:00 - 17:30 UTC)
by James Antill
=============================================
#fedora-meeting-1: Fedora Packaging Committee
=============================================
Meeting started by spot at 15:59:49 UTC. The full logs are available at
http://meetbot.fedoraproject.org/fedora-meeting-1/2013-05-23/fpc.2013-05-...
.
Meeting summary
---------------
* Roll Call (spot, 15:59:59)
* LINK:
https://fedoraproject.org/w/index.php?title=PackagingDrafts%
2FMinGWCrossCompiler&diff=337954&oldid=302743
is helpful (spot, 16:03:36)
* Updated MinGW Packaging Guidelines -
https://fedorahosted.org/fpc/ticket/294 -
https://fedoraproject.org/w/index.php?title=PackagingDrafts%
2FMinGWCrossCompiler&diff=337954&oldid=302743
(spot, 16:05:14)
* ACTION: Draft + "Executables which are required for proper
functionality of the libraries must be packaged in the matching
mingw32/mingw64 subpackage. All other executables are discouraged,
but may be packaged in optional (dependent) subpackages at a
packager's discretion." passes (+1:5, 0:0, -1:1) (spot, 16:33:15)
* LogFiles Guidelines - https://fedorahosted.org/fpc/ticket/142 -
https://fedoraproject.org/wiki/User:Johannbg/Packaging/LogFiles
(spot, 16:37:53)
* LINK: https://fedoraproject.org/wiki/User:Spot/Packaging/LogFiles
(spot, 16:56:48)
* ACTION: Revised spot logfile draft approved (+1:6, 0:0, -1:0)
(spot, 17:11:00)
* Open Floor (spot, 17:12:51)
Meeting ended at 17:28:26 UTC.
Action Items
------------
* Draft + "Executables which are required for proper functionality of
the libraries must be packaged in the matching mingw32/mingw64
subpackage. All other executables are discouraged, but may be packaged
in optional (dependent) subpackages at a packager's discretion."
passes (+1:5, 0:0, -1:1)
* Revised spot logfile draft approved (+1:6, 0:0, -1:0)
Action Items, by person
-----------------------
* spot
* Revised spot logfile draft approved (+1:6, 0:0, -1:0)
* **UNASSIGNED**
* Draft + "Executables which are required for proper functionality of
the libraries must be packaged in the matching mingw32/mingw64
subpackage. All other executables are discouraged, but may be
packaged in optional (dependent) subpackages at a packager's
discretion." passes (+1:5, 0:0, -1:1)
People Present (lines said)
---------------------------
* spot (96)
* tibbs|w (86)
* abadger1999 (45)
* geppetto (26)
* epienbro2 (20)
* racor (19)
* limburgher (17)
* RemiFedora (9)
* zodbot (3)
* nirik (2)
* epienbro (2)
* Ablu (2)
* SmootherFrOgZ (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
6 years, 9 months
Schedule for Thursday's FPC Meeting (2013-05-23 16:00 UTC)
by James Antill
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.
6 years, 9 months
