Re: Who uses abi-compliance-checker?

2013-07-03 Thread Remi Collet
Le 03/07/2013 22:03, Richard Shaw a écrit : > I initially got abi-compliance-checker into Fedora because one of my > packages does not maintain any sort of API/ABI compatibility or even > versioning for that matter. That way I could always check a new release > to see if any of its dependencies nee

Re: Who uses abi-compliance-checker?

2013-07-03 Thread Sérgio Basto
On Qui, 2013-07-04 at 00:00 +0200, Xavier Bachelot wrote: > On 07/03/2013 10:03 PM, Richard Shaw wrote: > > I initially got abi-compliance-checker into Fedora because one of my > > packages > > does not maintain any sort of API/ABI compatibility or even versioning for > > that > > matter. That w

Re: Who uses abi-compliance-checker?

2013-07-03 Thread Mathieu Bridon
On Wed, 2013-07-03 at 15:03 -0500, Richard Shaw wrote: > If anyone is curious about it, I don't mind typing up the process I go > through to make the checks. I think I've found a pretty good path of least > resistance method :) I've never used it, but I'd certainly be interested in reading that if

Re: Who uses abi-compliance-checker?

2013-07-03 Thread Richard Shaw
This is an extreme example, but after removing the offending headers I got this: https://dl.dropboxusercontent.com/u/34775202/compat_reports/ffmpeg/0.10.7_to_1.2.1/compat_report.html Thanks, Richard -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listi

Re: Who uses abi-complian. V. I UVce-checker?

2013-07-03 Thread Paulo César Pereira de Andrade
/ lo" m' Em 03/07/2013 21:16, "Richard Shaw" escreveu: > On Wed, Jul 3, 2013 at 4:33 PM, Sérgio Basto wrote: > >> On Qua, 2013-07-03 at 15:03 -0500, Richard Shaw wrote: >> > I initially got abi-compliance-checker into Fedora because one of my >> > packages does not maintain any sort of API/

Re: Who uses abi-compliance-checker?

2013-07-03 Thread Paulo César Pereira de Andrade
IBook. 'Kiomjm Em 03/07/2013 19:00, "Xavier Bachelot" escreveu: > On 07/03/2013 10:03 PM, Richard Shaw wrote: > > I initially got abi-compliance-checker into Fedora because one of my > packages > > does not maintain any sort of API/ABI compatibility or even versioning > for that > > matter. That

Re: Who uses abi-compliance-checker?

2013-07-03 Thread Richard Shaw
On Wed, Jul 3, 2013 at 4:33 PM, Sérgio Basto wrote: > On Qua, 2013-07-03 at 15:03 -0500, Richard Shaw wrote: > > I initially got abi-compliance-checker into Fedora because one of my > > packages does not maintain any sort of API/ABI compatibility or even > > versioning for that matter. That way I

Re: More unhelpful update descriptions

2013-07-03 Thread Michael Catanzaro
On Wed, 2013-07-03 at 16:33 +0100, Richard W.M. Jones wrote: > > SuSE too ... > > Rich. But they reformat everything by hand. For a representative example, compare: https://git.gnome.org/browse/evolution/tree/NEWS with https://build.opensuse.org/package/view_file/openSUSE:Factory/evolution?expan

Re: Who uses abi-compliance-checker?

2013-07-03 Thread Xavier Bachelot
On 07/03/2013 10:03 PM, Richard Shaw wrote: > I initially got abi-compliance-checker into Fedora because one of my packages > does not maintain any sort of API/ABI compatibility or even versioning for > that > matter. That way I could always check a new release to see if any of its > dependencies

Re: Heads up: Upcoming python-pillow 2.2 breaks "import _imaging"

2013-07-03 Thread Sandro Mani
On 03.07.2013 18:49, Kevin Fenzi wrote: On Mon, 01 Jul 2013 01:35:14 +0200 Sandro Mani wrote: Hello all, As described here [1], the upcoming python-pillow 2.2 will break "import _imaging", and "from PIL.Image import core as _imaging" should be used instead). This does not break backwards com

Re: Who uses abi-compliance-checker?

2013-07-03 Thread Sérgio Basto
On Qua, 2013-07-03 at 15:03 -0500, Richard Shaw wrote: > I initially got abi-compliance-checker into Fedora because one of my > packages does not maintain any sort of API/ABI compatibility or even > versioning for that matter. That way I could always check a new > release to see if any of its depe

Re: vote for systemd: Nay (now working but still Voting Nay)

2013-07-03 Thread Lennart Poettering
On Tue, 02.07.13 16:57, Jean-Marc Pigeon (j...@safe.ca) wrote: > As expected the problem stand on a very small detail (within /etc/fstab) > > Not working > /vzgot/ ext4defaults0 0 > proc /proc procdefaults0 0 > sysfs

Re: More unhelpful update descriptions

2013-07-03 Thread Ian Malone
On 3 July 2013 20:48, Adam Williamson wrote: > On 2013-07-03 2:28, Ian Malone wrote: > >> Tooling issues aside (and it is undesireable that bugs should get >> marked fixed if they haven't been) I think this rule is wrong under a >> strict reading. If an update claims to fix two bugs and fixes neit

Re: vote for systemd: Nay.

2013-07-03 Thread Lennart Poettering
On Tue, 02.07.13 10:08, Jean-Marc Pigeon (j...@safe.ca) wrote: > This little project gave satisfactory results with various distributions when > I designed and tested it 2 years ago. First I checked it with a standard > EL6.4 template (400 Megs) under this new kernel (3.9.4, HOST > EL6.4) to see

Who uses abi-compliance-checker?

2013-07-03 Thread Richard Shaw
I initially got abi-compliance-checker into Fedora because one of my packages does not maintain any sort of API/ABI compatibility or even versioning for that matter. That way I could always check a new release to see if any of its dependencies needed to be rebuilt. Since then, I've started using i

Re: More unhelpful update descriptions

2013-07-03 Thread Kevin Fenzi
On Wed, 03 Jul 2013 12:55:11 -0700 Adam Williamson wrote: > As discussed up thread, this is not the current policy and I'd really > prefer people don't do this. -1 is a Serious Thing, not to be used > lightly. Sorry, you are right. > If an update claims to fix multiple bugs and *does* fix so

Re: More unhelpful update descriptions

2013-07-03 Thread Adam Williamson
On 2013-07-03 10:54, Kevin Fenzi wrote: On Wed, 03 Jul 2013 19:38:00 +0200 Reindl Harald wrote: Am 03.07.2013 18:21, schrieb Matthew Miller: > On Wed, Jul 03, 2013 at 10:25:12AM +0200, Reindl Harald wrote: >>> Could be, but if the still broken bugs are going to be closed, >>> when the update

Re: More unhelpful update descriptions

2013-07-03 Thread Adam Williamson
On 2013-07-03 8:21, Panu Matilainen wrote: On 07/03/2013 03:12 PM, Richard W.M. Jones wrote: On Wed, Jul 03, 2013 at 12:28:19AM +0200, Björn Persson wrote: Richard W.M. Jones wrote: %changelog -f %changelog -g And, I suppose: %changelog -s %changelog -c %changelog -m %changelog -h %ch

Re: More unhelpful update descriptions

2013-07-03 Thread Adam Williamson
On 2013-07-03 2:28, Ian Malone wrote: Tooling issues aside (and it is undesireable that bugs should get marked fixed if they haven't been) I think this rule is wrong under a strict reading. If an update claims to fix two bugs and fixes neither then neither is the *only* change (highlighting is o

Summary/Minutes from today's FESCo Meeting (2013-07-03)

2013-07-03 Thread Stephen Gallagher
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 === #fedora-meeting: FESCO (2013-07-03) === Meeting started by sgallagh at 18:01:28 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2013-07-03/fesco.2

Re: More unhelpful update descriptions

2013-07-03 Thread Adam Williamson
On 2013-07-03 1:11, Michael Scherer wrote: Then we could decide on : - better process, ie "if you happen to notice a bug is not fixed by update, please reopen it" - better tooling, ie a way to say "do not close this bug" to bodhi. Either a message in bodhi, or something on bugzilla side. The m

Re: More unhelpful update descriptions

2013-07-03 Thread Adam Williamson
On 2013-07-03 0:54, Johannes Lips wrote: If it doesn't fix the bugs, the update should fix, it is appropriate to give negative karma. Otherwise the bugs would be closed, when it becomes stable, but won't be fixed. That's not what the guidelines say : https://fedoraproject.org/wiki/QA:Up

Re: Problem with abrt update on F18?

2013-07-03 Thread Richard Vickery
On Jul 2, 2013 2:20 PM, "Richard Shaw" wrote: > > I saw this during the update: > > Updating : abrt-libs-2.1.5-1.fc18.x86_64 10/76 > cp: cannot create regular file â/var/tmp/abrt/ccpp-2013-03-27-09:24:26-2877/environâ: No such file or directory > cp: cannot create regular file â/var/tmp/abrt/cc

Re: More unhelpful update descriptions

2013-07-03 Thread drago01
On Wed, Jul 3, 2013 at 7:54 PM, Kevin Fenzi wrote: > On Wed, 03 Jul 2013 19:38:00 +0200 > Reindl Harald wrote: > >> >> >> Am 03.07.2013 18:21, schrieb Matthew Miller: >> > On Wed, Jul 03, 2013 at 10:25:12AM +0200, Reindl Harald wrote: >> >>> Could be, but if the still broken bugs are going to be

Re: More unhelpful update descriptions

2013-07-03 Thread Reindl Harald
Am 03.07.2013 19:54, schrieb Kevin Fenzi: > On Wed, 03 Jul 2013 19:38:00 +0200 > Reindl Harald wrote: >> a new upstream-release does not implicitly close any bug >> >> on the other hand it makes hardly sense to hold back a update >> not fixing all bugreports - this all makes no sense for me > >

Re: More unhelpful update descriptions

2013-07-03 Thread Kevin Fenzi
On Wed, 03 Jul 2013 19:38:00 +0200 Reindl Harald wrote: > > > Am 03.07.2013 18:21, schrieb Matthew Miller: > > On Wed, Jul 03, 2013 at 10:25:12AM +0200, Reindl Harald wrote: > >>> Could be, but if the still broken bugs are going to be closed, > >>> when the update becomes stable > >> since when

Re: More unhelpful update descriptions

2013-07-03 Thread Reindl Harald
Am 03.07.2013 18:21, schrieb Matthew Miller: > On Wed, Jul 03, 2013 at 10:25:12AM +0200, Reindl Harald wrote: >>> Could be, but if the still broken bugs are going to be closed, when the >>> update becomes stable >> since when do bugs get magically closed? > > Since 2007 or so? what sense makes

python-setuptools-0.7.7 built for rawhide; hold off on mass rebuilds

2013-07-03 Thread Toshio Kuratomi
I've just built python-setuptools-0.7.7 for rawhide. As mentioned in the Changes Planning page: https://fedoraproject.org/wiki/Changes/Python_setuptools_0.7#Summary This is a switch of code base so there is the possibility of failures however it isn't a major change of API so it should hopefully

Re: Schedule for Wednesday's FESCo Meeting (2013-07-03)

2013-07-03 Thread Josh Boyer
On Wed, Jul 3, 2013 at 1:04 PM, Stephen Gallagher wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Sorry for the lateness of this email. FESCo meeting *IS* scheduled for > today. > > Following is the list of topics that will be discussed in the FESCo > meeting Wednesday at 18:00UTC in

Schedule for Wednesday's FESCo Meeting (2013-07-03)

2013-07-03 Thread Stephen Gallagher
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sorry for the lateness of this email. FESCo meeting *IS* scheduled for today. 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,

Re: Self Introduction / Sponsor Request

2013-07-03 Thread Christopher Meng
I've left some candies there :-D -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel

[389-devel] Please review: Ticket #47384 - Plugin library path validation

2013-07-03 Thread Noriko Hosoi
https://fedorahosted.org/389/ticket/47384 https://fedorahosted.org/389/attachment/ticket/47384/0001-Ticket-47384-Plugin-library-path-validation.3.patch Description: commit a4b81c0ae59a4246d2d44790efea093a62fc972c o

Re: Heads up: Upcoming python-pillow 2.2 breaks "import _imaging"

2013-07-03 Thread Kevin Fenzi
On Mon, 01 Jul 2013 01:35:14 +0200 Sandro Mani wrote: > Hello all, > > As described here [1], the upcoming python-pillow 2.2 will break > "import _imaging", and "from PIL.Image import core as _imaging" > should be used instead). This does not break backwards compatibility > with python-pillow <

Self Introduction / Sponsor Request

2013-07-03 Thread Ed Santiago
Hi, I've submitted a package review request for rpmgrill: https://bugzilla.redhat.com/show_bug.cgi?id=980960 rpmgrill is yet another QA tool for catching problems in koji builds. About me: I've been writing UNIXy software tools in one form or another since the late 80s, open-sourcing when p

Fedora ARM Weekly Status Meeting 2013-07-03 Canceled

2013-07-03 Thread Brendan Conoboy
Hi everybody, Yesterday we made a simultaneous release of F19 on ARM and x86, a first ever. Thank you to everybody who contributed- it was truly a great team effort, and it produced the best Fedora on ARM release yet. It's a holiday week in the US and Canada and half the members of the ARM

Re: More unhelpful update descriptions

2013-07-03 Thread Matthew Miller
On Wed, Jul 03, 2013 at 10:25:12AM +0200, Reindl Harald wrote: > > Could be, but if the still broken bugs are going to be closed, when the > > update becomes stable > since when do bugs get magically closed? Since 2007 or so? -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ -- devel mail

Re: fedup performance

2013-07-03 Thread Alexey I. Froloff
On Wed, Jul 03, 2013 at 12:25:19AM -0500, Alex G. wrote: > aptitude has something called "deferred ldconfig processing", and > annoyingly, aptitude updates faster than yum. I've always wondered how > yum/rpm can be smartized to speed things up this way. But this > discussion is for a brighter day.

Re: More unhelpful update descriptions

2013-07-03 Thread Reindl Harald
Am 03.07.2013 09:54, schrieb Johannes Lips: > Could be, but if the still broken bugs are going to be closed, when the > update becomes stable since when do bugs get magically closed? signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org ht

Re: More unhelpful update descriptions

2013-07-03 Thread Richard W.M. Jones
On Wed, Jul 03, 2013 at 06:21:51PM +0300, Panu Matilainen wrote: > On 07/03/2013 03:12 PM, Richard W.M. Jones wrote: > >On Wed, Jul 03, 2013 at 12:28:19AM +0200, Björn Persson wrote: > >>Richard W.M. Jones wrote: > >>>%changelog -f > >>>%changelog -g > >> > >>And, I suppose: > >> > >>%changelog -

Re: More unhelpful update descriptions

2013-07-03 Thread Panu Matilainen
On 07/03/2013 03:12 PM, Richard W.M. Jones wrote: On Wed, Jul 03, 2013 at 12:28:19AM +0200, Björn Persson wrote: Richard W.M. Jones wrote: %changelog -f %changelog -g And, I suppose: %changelog -s %changelog -c %changelog -m %changelog -h %changelog -a %changelog -b No. Just imple

Re: abi-compliance-checker and abi-dumper to track API/ABI

2013-07-03 Thread Richard Shaw
Review request submitted: https://bugzilla.redhat.com/show_bug.cgi?id=980937 It took me a bit to work some txt2man magic to get a decent manpage. Thanks, Richard -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel

Announcing the release of Fedora 19 for Power

2013-07-03 Thread Phil Knirsch
The Fedora Secondary Arch Team for Power is delighted to announce the release of Fedora 19 ("Schrödinger's Cat") for Power architecture. Open the box and take a look for yourself! Fedora is a leading-edge, free and open source operating system that continues to deliver innovative features to m

Reminder: Fedora 17 end of life on 2013-07-30

2013-07-03 Thread Dennis Gilmore
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Greetings. This is a reminder email about the end of life process for Fedora 17. Fedora 17 will reach end of life on 2013-07-30, and no further updates will be pushed out after that time. Additionally, with the recent release of Fedora 19, no new p

Re: libgd breakage

2013-07-03 Thread Orion Poplawski
On 07/01/2013 03:52 PM, Orion Poplawski wrote: See https://bugzilla.redhat.com/show_bug.cgi?id=959696. Renaming ht to t4ht was clearly the wrong thing to do. I'm reverting it for now. texlive and gnuplot now have been rebuilt in rawhide. -- Orion Poplawski Technical Manager

Re: find-lang.sh search path

2013-07-03 Thread Antonio Trande
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/02/2013 09:02 AM, Michael Schwendt wrote: > On Mon, 01 Jul 2013 23:28:00 +0200, Antonio Trande wrote: > > Then let's not hack the paths, but find out why %find_lang doesn't > find the files. If %name is not part of the filenames, normally > you

Re: abi-compliance-checker and abi-dumper to track API/ABI

2013-07-03 Thread Richard Shaw
I've got it packaged up and ready for review request. I'm assuming there is interest in automating this. Thanks, Richard -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel

rawhide report: 20130703 changes

2013-07-03 Thread Fedora Rawhide Report
Compose started at Wed Jul 3 08:15:02 UTC 2013 Broken deps for x86_64 -- [avgtime] avgtime-0-0.6.git20130201.fc20.x86_64 requires libphobos-ldc.so.60()(64bit) [contour] contour-0.3-2.fc19.x86_64 requires libsolidcontroliface

Re: More unhelpful update descriptions

2013-07-03 Thread Michael Catanzaro
On Wed, 2013-07-03 at 09:32 +0200, drago01 wrote: > This is also a perfect example of useless "does not fix bug x" karma. > If it is not *worse* then the previous package there is no reason to > give it negative karma. Yes, that is a problem too. Particularly so with selinux updates. But getting b

Re: More unhelpful update descriptions

2013-07-03 Thread Richard W.M. Jones
On Wed, Jul 03, 2013 at 12:28:19AM +0200, Björn Persson wrote: > Richard W.M. Jones wrote: > > %changelog -f > > %changelog -g > > And, I suppose: > > %changelog -s > %changelog -c > %changelog -m > %changelog -h > %changelog -a > %changelog -b No. Just implementing -f (local file) solv

excellent work!

2013-07-03 Thread Neal Becker
Just want to say I updated 2 machines using fedup, and everything seems to have gone perfectly. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel

Self Introduction + Sponsor Needed

2013-07-03 Thread Dario Faggioli
Hi everyone, I have just submitted a package review request for xen-tools (http://www.xen-tools.org/software/xen-tools/) here: https://bugzilla.redhat.com/show_bug.cgi?id=980851 From the same website, you can easily reach other Xen related tools, like xen-shell, and also rinse, which I plan to b

Re: More unhelpful update descriptions

2013-07-03 Thread Ian Malone
On 3 July 2013 08:47, Michael Scherer wrote: > Le mercredi 03 juillet 2013 à 09:44 +0200, Johannes Lips a écrit : >> >> >> >> On Wed, Jul 3, 2013 at 9:32 AM, drago01 wrote: >> On Mon, Jul 1, 2013 at 11:54 PM, Dan Mashal >> wrote: >> > On Mon, Jul 1, 2013 at 2:52 PM, Pierr

Re: fedup performance

2013-07-03 Thread Panu Matilainen
On 07/03/2013 11:29 AM, Alex G. wrote: On 07/03/2013 03:23 AM, Panu Matilainen wrote: On 07/03/2013 09:59 AM, Panu Matilainen wrote: On 07/03/2013 07:42 AM, Alex G. wrote: On 07/02/2013 08:28 PM, Neal Becker wrote: Not d/l speed related. I just want to share. I update a very fast 8 core ser

Re: fedup performance

2013-07-03 Thread Alex G.
On 07/03/2013 03:23 AM, Panu Matilainen wrote: > On 07/03/2013 09:59 AM, Panu Matilainen wrote: >> On 07/03/2013 07:42 AM, Alex G. wrote: >>> On 07/02/2013 08:28 PM, Neal Becker wrote: Not d/l speed related. I just want to share. I update a very fast 8 core server, with a conventio

Re: fedup performance

2013-07-03 Thread Panu Matilainen
On 07/03/2013 09:59 AM, Panu Matilainen wrote: On 07/03/2013 07:42 AM, Alex G. wrote: On 07/02/2013 08:28 PM, Neal Becker wrote: Not d/l speed related. I just want to share. I update a very fast 8 core server, with a conventional disk drive. Took 2-3 hours, not including d/l. I update my la

abi-compliance-checker and abi-dumper to track API/ABI

2013-07-03 Thread Andrey Ponomarenko
Hi, There is a new simple way to track changes in API/ABI of system libraries using a new ABI dumper [1] tool. Just compile two library versions with -g additional option (to contain DWARF debug info) or take them from the appropriate debug packages and create ABI dumps of both: abi-dumper

Re: More unhelpful update descriptions

2013-07-03 Thread Michael Scherer
Le mercredi 03 juillet 2013 à 09:54 +0200, Johannes Lips a écrit : > > > > On Wed, Jul 3, 2013 at 9:47 AM, Michael Scherer wrote: > Le mercredi 03 juillet 2013 à 09:44 +0200, Johannes Lips a > écrit : > > > > > > > > On Wed, Jul 3, 2013 at 9:32 AM

Re: More unhelpful update descriptions

2013-07-03 Thread Johannes Lips
On Wed, Jul 3, 2013 at 9:47 AM, Michael Scherer wrote: > Le mercredi 03 juillet 2013 à 09:44 +0200, Johannes Lips a écrit : > > > > > > > > On Wed, Jul 3, 2013 at 9:32 AM, drago01 wrote: > > On Mon, Jul 1, 2013 at 11:54 PM, Dan Mashal > > wrote: > > > On Mon, Jul 1, 2013

Re: More unhelpful update descriptions

2013-07-03 Thread Michael Scherer
Le mercredi 03 juillet 2013 à 09:44 +0200, Johannes Lips a écrit : > > > > On Wed, Jul 3, 2013 at 9:32 AM, drago01 wrote: > On Mon, Jul 1, 2013 at 11:54 PM, Dan Mashal > wrote: > > On Mon, Jul 1, 2013 at 2:52 PM, Pierre-Yves Luyten > wrote: > >> Not sur

Re: More unhelpful update descriptions

2013-07-03 Thread Johannes Lips
On Wed, Jul 3, 2013 at 9:32 AM, drago01 wrote: > On Mon, Jul 1, 2013 at 11:54 PM, Dan Mashal wrote: > > On Mon, Jul 1, 2013 at 2:52 PM, Pierre-Yves Luyten wrote: > >> Not sure if it makes any sense but maybe could we have something like > >> "freeze tag changes until desc is better". > >> > >>

Re: More unhelpful update descriptions

2013-07-03 Thread drago01
On Mon, Jul 1, 2013 at 11:54 PM, Dan Mashal wrote: > On Mon, Jul 1, 2013 at 2:52 PM, Pierre-Yves Luyten wrote: >> Not sure if it makes any sense but maybe could we have something like >> "freeze tag changes until desc is better". >> >> I propose this because testers will not _really_ want to -1 k