Re: FTBFS if "-Werror=format-security" flag is used
On Tue, Dec 10, 2013 at 3:00 AM, Kevin Kofler wrote: > [...] and removes functionality No it does not. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Anaconda Addon Development Guide almost finished, needs review
For a few last months I've been line after line putting together the Anaconda Addon Development Guide [1] -- a short and straightforward guide describing how an addon for the Anaconda installer can be implemented, tested, deployed and packaged. I believe it is now almost finished, but it needs review and probably a lot of tweaks based on the feedback, I'll hopefully get, before I'll propose it as a part of the official Fedora project documentation. So comments, suggestions, issue reports or patches [2] are more than welcomed! [1] http://vpodzime.fedorapeople.org/anaconda-addon-development-guide/ [2] https://github.com/vpodzime/anaconda-addon-development-guide -- Vratislav Podzimek Anaconda Rider | Red Hat, Inc. | Brno - Czech Republic -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[Bug 1037518] perl-Archive-Zip-1.34 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1037518 Jitka Plesnikova changed: What|Removed |Added Status|ASSIGNED|CLOSED Fixed In Version||perl-Archive-Zip-1.34-1.fc2 ||1 Resolution|--- |RAWHIDE Last Closed||2013-12-10 04:50:56 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=XsREWO0wtW&a=cc_unsubscribe -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[Test-Announce] Fedora 20 Final Go/No-Go Meeting #2, Thursday, December 12 @ 17:00 UTC
Join us on irc.freenode.net in #fedora-meeting-2 for this important meeting, wherein we shall determine the readiness of the Fedora 20. Thursday, December 12, 2013 17:00 UTC (12 PM EST, 9 AM PST, 18:00 CET) "Before each public release Development, QA and Release Engineering meet to determine if the release criteria are met for a particular release. This meeting is called the Go/No-Go Meeting." "Verifying that the Release criteria are met is the responsibility of the QA Team." For more details about this meeting see: https://fedoraproject.org/wiki/Go_No_Go_Meeting In the meantime, keep an eye on the Fedora 20 Final Blocker list: http://qa.fedoraproject.org/blockerbugs/milestone/20/final/buglist This is the second attempt to release final Fedora 20 and we're really very close to holidays. Please, help us with the release by working on the bugs assigned to you - the very, very deadline to create and validate RC on time is Wednesday... Thanks everyone! Jaroslav ___ test-announce mailing list test-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/test-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
F-20 Branched report: 20131210 changes
Compose started at Tue Dec 10 07:15:02 UTC 2013 Broken deps for armhfp -- [avro] avro-mapred-1.7.5-1.fc20.noarch requires hadoop-mapreduce avro-mapred-1.7.5-1.fc20.noarch requires hadoop-client [blueman] blueman-1.23-7.fc20.armv7hl requires obex-data-server >= 0:0.4.3 blueman-1.23-7.fc20.armv7hl requires gvfs-obexftp [cloud-init] cloud-init-0.7.2-7.fc20.noarch requires dmidecode [cobbler] cobbler-2.4.0-2.fc20.noarch requires syslinux [fts] fts-server-3.1.1-1.fc20.armv7hl requires libactivemq-cpp.so.14 [ghc-hjsmin] ghc-hjsmin-devel-0.1.4.3-2.fc20.armv7hl requires ghc-devel(language-javascript-0.5.8-28fa88554adf134b03284de53334e91d) [gofer] ruby-gofer-0.75-4.fc20.noarch requires rubygem(qpid) >= 0:0.16.0 [gtkd] gtkd-geany-tags-2.0.0-29.20120815git9ae9181.fc18.noarch requires gtkd = 0:2.0.0-29.20120815git9ae9181.fc18 [kawa] 1:kawa-1.11-5.fc19.armv7hl requires servlet25 [koji] koji-vm-1.8.0-2.fc20.noarch requires python-virtinst [kyua-cli] kyua-cli-0.5-3.fc19.armv7hl requires liblutok.so.0 kyua-cli-tests-0.5-3.fc19.armv7hl requires liblutok.so.0 [msp430-libc] msp430-libc-20120224-2.fc19.noarch requires msp430-gcc >= 0:4.6.3 [nifti2dicom] nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtksys.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkWidgets.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkVolumeRendering.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkViews.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkTextAnalysis.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkRendering.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkParallel.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkInfovis.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkImaging.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkIO.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkHybrid.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkGraphics.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkGeovis.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkGenericFiltering.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkFiltering.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkCommon.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libvtkCharts.so.5.10 nifti2dicom-0.4.6-3.fc20.armv7hl requires libQVTK.so.5.10 [nocpulse-common] nocpulse-common-2.2.7-2.fc20.noarch requires perl(RHN::DBI) [openbox] gdm-control-3.5.2-2.fc20.armv7hl requires gnome-panel gnome-panel-control-3.5.2-2.fc20.armv7hl requires gnome-panel [openpts] openpts-0.2.6-7.fc20.armv7hl requires tboot [owncloud] owncloud-5.0.13-1.fc20.noarch requires php-pear(pear.symfony.com/Routing) [perl-Language-Expr] perl-Language-Expr-0.19-4.fc19.noarch requires perl(:MODULE_COMPAT_5.16.2) [php-Assetic] php-Assetic-1.1.2-1.fc20.noarch requires php-pear(pear.symfony.com/Process) < 0:3.0 php-Assetic-1.1.2-1.fc20.noarch requires php-pear(pear.symfony.com/Process) >= 0:2.1 [php-Metadata] php-Metadata-1.5.0-1.fc20.noarch requires php-pear(pear.symfony.com/DependencyInjection) [php-SymfonyCmfRouting] php-SymfonyCmfRouting-1.1.0-1.fc20.noarch requires php-pear(pear.symfony.com/Routing) < 0:3.0 php-SymfonyCmfRouting-1.1.0-1.fc20.noarch requires php-pear(pear.symfony.com/Routing) >= 0:2.2 php-SymfonyCmfRouting-1.1.0-1.fc20.noarch requires php-pear(pear.symfony.com/HttpKernel) < 0:3.0 php-SymfonyCmfRouting-1.1.0-1.fc20.noarch requires php-pear(pear.symfony.com/HttpKernel) >= 0:2.2 php-SymfonyCmfRouting-1.1.0-1.fc20.noarch requires php-pear(pear.symfony.com/EventDispatcher) < 0:3.0 php-SymfonyCmfRouting-1.1.0-1.fc20.noarch requires php-pear(pear.symfony.com/EventDispatcher) >= 0:2.2 [php-doctrine-DoctrineDBAL] php-doctrine-DoctrineDBAL-2.3.4-4.fc20.noarch requires php-pear(pear.symfony.com/Console) < 0:3.0 php-doctrine-DoctrineDBAL-2.3.4-4.fc20.noarch requires php-pear(pear.symfony.com/Console) >= 0:2.0 [php-doctrine-DoctrineORM] php-doctrine-DoctrineORM-2.3.3-2.fc20.noarch requires php-pear(pear.symfony.com/Yaml) < 0:3.0 php-doctrine-DoctrineORM-2.3.3-2.fc20.noarch requires php-pear(pear.symfony.com/Yaml) >= 0:2.0 php-doctrine-DoctrineORM-2.3.3-2.fc20.noarch requires php-pear(pear.symfony.com/Console) < 0:3.0 php-doctrine-DoctrineORM-2.3.3-2.fc20.noarch requires php-pear(pear.symfony.com/Console) >= 0:2.0 [php-guzzle-Guzzle] php-guzzle-Guzzle-3.7.4-2.fc20.noarch requires php-pear(pear.symfony.com/EventDispatcher) >= 0:2.1.0 [php-phpunit-DbUnit] php-phpunit-DbUnit-1.3.0-1.fc20.noarch require
Re: [pkgdb2] call for testers, bug reports and RFE
On Wed, Nov 13, 2013 at 02:52:27PM +0100, Pierre-Yves Chibon wrote: > I am at a point where I think it starts to look good, the unit-tests are > passing > and I seem to be able to do what I want with it. Thus I thought this would be > a > good time to call for testers and collect bug reports and RFE. > > The development instance of pkgdb2 is at: > > http://209.132.184.188/ [...] > So please, have a look at it, play with it, break it (no seriously, do, but > don't > forget to report how you did it afterward) and if you have any problem/RFE > feel > free to note them at: Just a heads-up, christmas holidays are coming our way and our agenda is to push pkgdb2 in production as soon as possible after the release of F20. This means that if you want to poke at it, if you find bugs or have any RFE you should really do this as early as possible so that there is time to fix/improve before we release. Pierre -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Meeting minutes - today's Env-and-Stacks WG meeting (2013-12-10)
#fedora-meeting: Env and Stacks (2013-12-10) Meeting started by bkabrda at 13:02:36 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2013-12-10/env_and_stacks.2013-12-10-13.02.log.html . Meeting summary --- * IDEA: pkovar will send analysis of what we should do with docs/wiki to ML before Jan 7. (bkabrda, 13:23:42) * ACTION: pkovar will send analysis of what we should do with docs/wiki to ML before Jan 7. (bkabrda, 13:25:23) * ACTION: hhorak will examine what tutorials/howtos regarding webstack/databases are available now and what should we add/improve (till jan 7) (hhorak, 13:32:06) Meeting ended at 13:40:27 UTC. Action Items * pkovar will send analysis of what we should do with docs/wiki to ML before Jan 7. * hhorak will examine what tutorials/howtos regarding webstack/databases are available now and what should we add/improve (till jan 7) Action Items, by person --- * hhorak * hhorak will examine what tutorials/howtos regarding webstack/databases are available now and what should we add/improve (till jan 7) * pkovar * pkovar will send analysis of what we should do with docs/wiki to ML before Jan 7. * **UNASSIGNED** * (none) People Present (lines said) --- * pkovar (40) * bkabrda (22) * hhorak (12) * zodbot (5) * vpavlin (1) * samkottler (0) * abadger1999 (0) -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: FTBFS if "-Werror=format-security" flag is used
drago01 wrote:
> On Tue, Dec 10, 2013 at 3:00 AM, Kevin Kofler
> wrote:
>> [...] and removes functionality
>
> No it does not.
Yes, it does, see my example:
| a printf wrapper for logging which adds a timestamp in front of the
| format string, e.g.
| log("processed %d items", foo);
| which would be printed as
| 2013-12-06 19:00:00: processed 123 items
| to some logfile (using vfprintf with a format string like
| "2013-12-06 19:00:00: processed %d items"
| concatenated at runtime).
-Werror=format-security removes the functionality of building format strings
at runtime, and there are legitimate uses for such functionality.
And it has been mentioned elsewhere in this thread that GCC doesn't even
recognize cases where the format string is constant, but not a string
literal, where it is picked from a list of constant formats, etc.
Kevin Kofler
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: FTBFS if "-Werror=format-security" flag is used
On Tue, Dec 10, 2013 at 3:50 PM, Kevin Kofler wrote:
> drago01 wrote:
>
>> On Tue, Dec 10, 2013 at 3:00 AM, Kevin Kofler
>> wrote:
>>> [...] and removes functionality
>>
>> No it does not.
>
> Yes, it does, see my example:
> | a printf wrapper for logging which adds a timestamp in front of the
> | format string, e.g.
> | log("processed %d items", foo);
> | which would be printed as
> | 2013-12-06 19:00:00: processed 123 items
> | to some logfile (using vfprintf with a format string like
> | "2013-12-06 19:00:00: processed %d items"
> | concatenated at runtime).
>
> -Werror=format-security removes the functionality of building format strings
> at runtime, and there are legitimate uses for such functionality.
(info gcc) says that format-security only applies to calls "where the
format string is not a string literal _and there are no format
arguments_", which is not the case for the wrapper above. Is the
documentation incorrect?
Mirek
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Schedule for Wednesday's FESCo Meeting (2013-12-11)
Following is the list of topics that will be discussed in the FESCo meeting Wednesday at 18:00UTC in #fedora-meeting on irc.freenode.net. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/UTCHowto or run: date -d '-MM-DD HH:MM UTC' Links to all tickets below can be found at: https://fedorahosted.org/fesco/report/9 = Followups = #topic #1185 Enable "-Werror=format-security" by default .fesco 1185 https://fedorahosted.org/fesco/ticket/1185 = New business = #topic #1210 F21 System Wide Change: Format Security .fesco .1210 https://fedoraproject.org/wiki/Changes/FormatSecurity https://fedorahosted.org/fesco/ticket/1210 #topic #1211 F21 System Wide Change: Headless Java https://fedoraproject.org/wiki/Changes/HeadlessJava https://fedorahosted.org/fesco/ticket/1211 = Open Floor = For more complete details, please visit each individual ticket. The report of the agenda items can be found at https://fedorahosted.org/fesco/report/9 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/fesco, 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. -- Matthew Miller -- Fedora Project Architect -- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Schedule for Wednesday's FESCo Meeting (2013-12-11)
On Tue, Dec 10, 2013 at 11:02 AM, Matthew Miller wrote: > Following is the list of topics that will be discussed in the FESCo > meeting Wednesday at 18:00UTC in #fedora-meeting on irc.freenode.net. > > To convert UTC to your local time, take a look at > http://fedoraproject.org/wiki/UTCHowto > > or run: > date -d '-MM-DD HH:MM UTC' > > > Links to all tickets below can be found at: > https://fedorahosted.org/fesco/report/9 > > = Followups = > > #topic #1185 Enable "-Werror=format-security" by default > .fesco 1185 > https://fedorahosted.org/fesco/ticket/1185 https://fedorahosted.org/fesco/ticket/1201 is not resolved yet. josh -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Schedule for Wednesday's FESCo Meeting (2013-12-11)
On Tue, Dec 10, 2013 at 11:02:15AM -0500, Matthew Miller wrote: > #topic #1211 F21 System Wide Change: Headless Java > https://fedoraproject.org/wiki/Changes/HeadlessJava > https://fedorahosted.org/fesco/ticket/1211 For this feature I want to point out, that there are JVM-based languages with swing support. This packages need a rework to separate the swing part into an extra subpackage. Best Regards: Jochen Schmitt -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: FTBFS if "-Werror=format-security" flag is used
On 12/10/2013 04:35 PM, Miloslav Trmač wrote:
On Tue, Dec 10, 2013 at 3:50 PM, Kevin Kofler wrote:
drago01 wrote:
On Tue, Dec 10, 2013 at 3:00 AM, Kevin Kofler
-Werror=format-security removes the functionality of building format strings
at runtime, and there are legitimate uses for such functionality.
(info gcc) says that format-security only applies to calls "where the
format string is not a string literal _and there are no format
arguments_", which is not the case for the wrapper above. Is the
documentation incorrect?
The documentation seems right in the sense as GCC seems to be doing what
the documentation tells.
The problems are elsewhere:
1. There are legitimate use-cases where GCC's assumption does not hold,
.e.g.:
#include
void foo( int a )
{
char hello0[] = "hello0";
char hello1[] = "hello1";
char *ptr;
switch (a % 2) {
case 0: ptr = hello0;
break;
case 1: ptr = hello1;
break;
}
printf( ptr );
}
=> The warning GCC issues is plain wrong.
=> -Werror=format-security removes the functionality of assigning
pointers to format strings even if they are constant.
2. Raising warnings to errors (-Werror) at distribution scope is a silly
undertaking in general. -Werror is a debugging/development/testing aid
aimed at developers but is entirely inadequate at distribution (or
package scope).
Ralf
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Fedora 20 Final blocker - Please add symfony packages.
Le 06/12/2013 11:51, Remi Collet a écrit : > Le 28/11/2013 03:25, Adam Williamson a écrit : >> Hi, folks. We have just over one week to the Fedora 20 Go/No-Go meeting, >> and a big happy pile of blocker bugs - everyone's having fun! In order >> to be able to complete testing in time for the go/no-go meeting > > Please consider for F20Final: > > https://bugzilla.redhat.com/show_bug.cgi?id=1021749 > https://admin.fedoraproject.org/updates/FEDORA-2013-22356 > > Having a broken PHPUnit in F20 will make most of the PHP packages FTBFS. > > Note: retiring a package before the new one is pushed is just a VERY bad > idea (despite comment#34 on bz) Please consider this update for Freeze exception. I really don't want to see F20 released with a broken PHP stack. Remi. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: FTBFS if "-Werror=format-security" flag is used
Once upon a time, Ralf Corsepius said: > printf( ptr ); Aside from everything else, using the printf() family of functions when you don't want formatted output is bad practice. There's really no excuse for calling printf(foo); if you don't want formatted output (i.e. you don't pass a format string with additionalarguments to be converted), then use the correct function for the job such as puts(foo). -- Chris Adams -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: FTBFS if "-Werror=format-security" flag is used
Once upon a time, Chris Adams said: > Aside from everything else, using the printf() family of functions when > you don't want formatted output is bad practice. There's really no > excuse for calling printf(foo); if you don't want formatted output (i.e. > you don't pass a format string with additionalarguments to be > converted), then use the correct function for the job such as puts(foo). And before anybody jumps on it, I meant fputs(foo, stdout) (I forgot puts() appends a newline). -- Chris Adams -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: FTBFS if "-Werror=format-security" flag is used
On Sat, Dec 07, 2013 at 07:12:03AM +0100, Mattias Ellert wrote: > fre 2013-12-06 klockan 15:06 -0500 skrev Darryl L. Pierce: > > Additionally, some code (like my package, qpid-cpp) uses code that's > > generated by another app like Swig. We have no control over what that > > code is. So enabling this as an error would be unresolvable by our > > project and we'd be blocked until the Swig team decided to change their > > code generation bits. > > Don't use swig as an excuse not to fix things. Sorry, where am I using any excuses? > Of all the packages I > maintain, only one was affected by this issue. That one was easily > solvable by deleting the bundled swig generated code in the sources and > have the build regenerate it with a newer swig version that doesn't > produce broken code. Our project isn't bundling any Swig generated code. It's generated as a part of the build process. Try not to make assumptions in future. -- Darryl L. Pierce http://mcpierce.fedorapeople.org/ "What do you care what people think, Mr. Feynman?" pgpuIThY41QMB.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: FTBFS if "-Werror=format-security" flag is used
On Fri, Dec 06, 2013 at 03:58:21PM -0500, David Malcolm wrote: > On Fri, 2013-12-06 at 15:06 -0500, Darryl L. Pierce wrote: > > Additionally, some code (like my package, qpid-cpp) uses code that's > > generated by another app like Swig. We have no control over what that > > code is. So enabling this as an error would be unresolvable by our > > project and we'd be blocked until the Swig team decided to change their > > code generation bits. > > So have you filed a bug against swig yet? ;) > > [ideally, attaching an example of the problematic generated code, and > the inputs] I have not, no. I wanted to see what's going to happen WRT this proposal first. -- Darryl L. Pierce http://mcpierce.fedorapeople.org/ "What do you care what people think, Mr. Feynman?" pgpsUOb8_Ihb8.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Fedora 20 Final blocker - Please add symfony packages.
On Tue, 2013-12-10 at 17:42 +0100, Remi Collet wrote: > Le 06/12/2013 11:51, Remi Collet a écrit : > > Le 28/11/2013 03:25, Adam Williamson a écrit : > >> Hi, folks. We have just over one week to the Fedora 20 Go/No-Go meeting, > >> and a big happy pile of blocker bugs - everyone's having fun! In order > >> to be able to complete testing in time for the go/no-go meeting > > > > Please consider for F20Final: > > > > https://bugzilla.redhat.com/show_bug.cgi?id=1021749 > > https://admin.fedoraproject.org/updates/FEDORA-2013-22356 > > > > Having a broken PHPUnit in F20 will make most of the PHP packages FTBFS. > > > > Note: retiring a package before the new one is pushed is just a VERY bad > > idea (despite comment#34 on bz) > > Please consider this update for Freeze exception. It would've worked better if you'd nominated it as one before the meeting :/ -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Fedora 20 Final blocker - Please add symfony packages.
Le 10/12/2013 18:20, Adam Williamson a écrit : > It would've worked better if you'd nominated it as one before the > meeting :/ I have raised the issue on ML Dec 6th. And bug blocks #980657 (Final 20 freeze exception tracker) since this date. NB: I just tried to have F20 in a correct state... Remi. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: FTBFS if "-Werror=format-security" flag is used
> 1. There are legitimate use-cases where GCC's assumption does not hold, .e.g.:
>
> #include
>
> void foo( int a )
> {
> char hello0[] = "hello0";
foo.c line 5: warning: 'const' omitted
> char hello1[] = "hello1";
foo.c line 6: warning: 'const' omitted
>
> char *ptr;
foo.c line 8: warning: 'const' omitted
>
> switch (a % 2) {
> case 0: ptr = hello0;
> break;
> case 1: ptr = hello1;
> break;
> }
>
> printf( ptr );
> }
>
> => The warning GCC issues is plain wrong.
>
> => -Werror=format-security removes the functionality of assigning pointers to
> format strings even if they are constant.
The example does not support this argument because the example omitted the
'const' (three places.)
gcc-4.[89] isn't advanced enough to distinguish, but the example does not match
the argument.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: FTBFS if "-Werror=format-security" flag is used
On 12/06/2013 08:11 PM, Kevin Kofler wrote:
Adam Jackson wrote:
On Fri, 2013-12-06 at 02:21 +0100, Kevin Kofler wrote:
QString line;
line.fill( '-', 60 );
qDebug( line.ascii() );
As you can see, the format string being passed here is provably constant.
So fix the compiler.
I don't think GCC will ever be able to prove that it is a constant. It would
at least have to do intermodule inlining on the linked qstring.o to do that,
which means qt3 would have to use the LTO support. Even then, I wouldn't
count on it. Plus, if this construct were found in application code rather
than in qt3 itself, GCC would even have to do the intermodule inlining on
libqt-mt, which would also have negative consequences on binary
compatibility.
But knowing the contract of QString (Qt 3's in this case, but it's the same
in Qt 4 and Qt 5), it's trivial for a human to prove it.
Kevin Kofler
What is the best way to handle this case:
qWarning(QObject::tr("Client name '%1' occupied.").arg(name).toUtf8());
something like, or can I make it simpler:
qWarning("%s",qPrintable(QObject::tr("Client name '%1'
occupied.").arg(name).toUtf8()));
regards
Brendan
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Retiring: R-RScaLAPACK
This package makes baby seals wish they could be clubbed. Upstream has killed it. I disavow any knowledge of it. Retired: R-RScaLAPACK ~tom == ¸.·´¯`·.´¯`·.¸¸.·´¯`·.¸><(((º> OSAS @ Red Hat University Outreach || Fedora Special Projects || Fedora Legal -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [pkgdb2] call for testers, bug reports and RFE
On Tue, Dec 10, 2013 at 5:20 AM, Pierre-Yves Chibon wrote: > On Wed, Nov 13, 2013 at 02:52:27PM +0100, Pierre-Yves Chibon wrote: >> I am at a point where I think it starts to look good, the unit-tests are >> passing >> and I seem to be able to do what I want with it. Thus I thought this would >> be a >> good time to call for testers and collect bug reports and RFE. >> >> The development instance of pkgdb2 is at: >> >> http://209.132.184.188/ > > [...] > >> So please, have a look at it, play with it, break it (no seriously, do, but >> don't >> forget to report how you did it afterward) and if you have any problem/RFE >> feel >> free to note them at: > > Just a heads-up, christmas holidays are coming our way and our agenda is to > push > pkgdb2 in production as soon as possible after the release of F20. > > This means that if you want to poke at it, if you find bugs or have any RFE > you > should really do this as early as possible so that there is time to > fix/improve > before we release. Can we get a "my packages" button? Or am I blind and not seeing one? Dan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: FTBFS if "-Werror=format-security" flag is used
tis 2013-12-10 klockan 12:18 -0500 skrev Darryl L. Pierce: > > Of all the packages I > > maintain, only one was affected by this issue. That one was easily > > solvable by deleting the bundled swig generated code in the sources and > > have the build regenerate it with a newer swig version that doesn't > > produce broken code. > > Our project isn't bundling any Swig generated code. It's generated as a > part of the build process. Try not to make assumptions in future. Where did I make this assumption? The description of my experience was supposed to tell something about swig. That older versions had problems but newer does not. No reflection on your project was intended whatsoever. Mattias smime.p7s Description: S/MIME cryptographic signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [pkgdb2] call for testers, bug reports and RFE
On 12/10/2013 02:20 PM, Pierre-Yves Chibon wrote: > >> So please, have a look at it, play with it, break it (no seriously, do, but >> don't >> forget to report how you did it afterward) and if you have any problem/RFE >> feel >> free to note them at: > > Just a heads-up, christmas holidays are coming our way and our agenda is to > push > pkgdb2 in production as soon as possible after the release of F20. > > This means that if you want to poke at it, if you find bugs or have any RFE > you > should really do this as early as possible so that there is time to > fix/improve > before we release. > Wow, looks great in general. I'd love to see a feature, where it's possible to search for sub-packages as well. It would make many things easier. Matthias -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Schedule for Wednesday's FESCo Meeting (2013-12-11)
On Tue, Dec 10, 2013 at 11:05:34AM -0500, Josh Boyer wrote: > > #topic #1185 Enable "-Werror=format-security" by default > > .fesco 1185 > > https://fedorahosted.org/fesco/ticket/1185 > https://fedorahosted.org/fesco/ticket/1201 is not resolved yet. After the last meeting the 'meeting' keyword was removed from the ticket so it didn't show up in the agenda. There's clearly more to work out -- I'll add it back, and to the agenda for tomorrow. -- Matthew Miller -- Fedora Project Architect -- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Self-introduction
Hi all- I've been using Fedora for quite a few years as my main desktop OS, and I think it's time I contributed back by writing some packages. (Also, there are packages I want -- I might as well create them.) For my day job, I work at a trading company, writing algorithmic trading software. I dabble in quantum cryptography and occasionally even in classical cryptography. I'm also a sometime kernel hacker (with particular interest in the vDSO, timing, some arch stuff, and the bits of page cache that I can understand). I have two packages pending review: capnproto-c++: https://bugzilla.redhat.com/show_bug.cgi?id=1040243 capnproto is really neat. I expect that it will be the best (and maybe even the dominant) serialization format for new apps someday. I've talked to Kenton (i.e. the upstream) about this package, and he's happy about it as long as the packages track actual releases. fish: https://bugzilla.redhat.com/show_bug.cgi?id=974852 Fish is a nice shell. Christopher Meng has told me that he's happy with my taking over this package as long as I'm proactive about finding a sponsor. If anyone would be willing to sponsor me as a package maintainer, that would be great! Thanks, Andy -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[Test-Announce] 2013-12-11 @ 17:00 UTC - F20 Final Blocker Bug Review #5
# F20 Final Blocker Review meeting #5 # Date: 2013-12-11 # Time: 17:00 UTC (12:00 EST, 09:00 PST) # Location: #fedora-blocker-review on irc.freenode.net Sadly we didn't build an RC yet and we still have proposed blockers to consider, so please folks, come out and help us review the new crop. Input from outside the usual suspects is always welcome... We'll be reviewing the five proposed blocker and one proposed freeze exception bugs and checking that accepted blocker bugs are getting the attention they need. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting See you soon! [1] https://fedoraproject.org/wiki/Fedora_20_Final_Release_Criteria -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net ___ test-announce mailing list test-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/test-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
