Fixed my broken packages in rawhide:
* libjingle - http://koji.fedoraproject.org/koji/taskinfo?taskID=3623092
* rekall - http://koji.fedoraproject.org/koji/taskinfo?taskID=3623152
* xbase - http://koji.fedoraproject.org/koji/taskinfo?taskID=3623229
* xsupplicant - http://koji.fedoraproject.org/koj
On 12/31/2011 12:56 PM, Jakub Jelinek wrote:
Hi!
As part of preparations to switch GCC in F17 to GCC 4.7.0, I've performed
a test mass rebuild of rawhide (December 23th package list) using
gcc-4.7.0-0.1.fc17 on x86_64, and for those packages that failed also
rebuilt the same package with gcc-4.6
Jan Kratochvil wrote:
> Once you do a first Rawhide build I do not know how to revert it.
Untag all the Rawhide builds with koji untag-pkg f17 NVR.
Be warned that rel-eng is going to yell at you if you do this without
ensuring that the EVR inherited from F16 is newer. FESCo decided that EVRs
ar
On Wed, Jan 04, 2012 at 10:22:21PM +0200, Ville Skyttä wrote:
> On 2012-01-03 16:07, Jan Kratochvil wrote:
> >
> > If you never do a build in Rawhide - your latest build is the F16 one
> > - Rawhide automatically inherits the F16 (or older) builds.
> > I find it useful.
>
> Me too, but beware, so
On 2012-01-03 16:07, Jan Kratochvil wrote:
>
> If you never do a build in Rawhide - your latest build is the F16 one
> - Rawhide automatically inherits the F16 (or older) builds.
> I find it useful.
Me too, but beware, sometimes the inheritance is explicitly disabled.
http://lists.fedoraproject.o
> Thanks for the pointers.
>
> By running this command, I have signed up for iwhd-related
> notifications in F-16 and rawhide:
>
> ssh fedorapeople.org autoqa-optin iwhd devel F-16
With this command you will subscribe for rpmlint and rpmguard test results for
every new build [1].
Depcheck
Denis Arnaud wrote:
> Hi Jim,
>
> 2012/1/3
>
> Is there some sort of reminder service that could be configured to nag the
> maintainers of a package in a situation like this? Personally, I would
> appreciate it, and I think Fedora would benefit if we could do something
> to
> mini
Jakub Jelinek wrote:
> On Mon, Jan 02, 2012 at 07:03:44PM +0100, Jim Meyering wrote:
>>
>> I have just tried to build iwhd on F16 using a pretty recent gcc-4.7.x
>> (built manually: 4.7.0 20111202), and it worked fine, so I'm not quite
>> sure why iwhd is on the list. Maybe the gcc-4.7.x that Jaku
On Mon, Jan 02, 2012 at 07:03:44PM +0100, Jim Meyering wrote:
>
> I have just tried to build iwhd on F16 using a pretty recent gcc-4.7.x
> (built manually: 4.7.0 20111202), and it worked fine, so I'm not quite
> sure why iwhd is on the list. Maybe the gcc-4.7.x that Jakub used
> lacks something t
Hi Jim,
2012/1/3
>
> Is there some sort of reminder service that could be configured to nag the
> maintainers of a package in a situation like this? Personally, I would
> appreciate it, and I think Fedora would benefit if we could do something to
> minimize reverse-version skew between Fedora-la
2012/1/3 Pádraig Brady :
> On 01/02/2012 06:03 PM, Jim Meyering wrote:
>> Nils Philippsen wrote:
>> ...
>>> I've attached a list of packages and (co)maintainers, to easily find if
>>> one of your packages is affected or not.
>> ...
>>> iwhd: meyering - clalance,zaitcev
>>
>> Thank you for the list.
On Mon, 02 Jan 2012 19:03:44 +0100, Jim Meyering wrote:
> The tested version (the one in rawhide) is iwhd-1.1,
> while the latest is 1.2 (which is in F16). Shame on me
> for not putting the latest also in rawhide.
If you never do a build in Rawhide - your latest build is the F16 one
- Rawhide aut
On 01/02/2012 06:03 PM, Jim Meyering wrote:
> Nils Philippsen wrote:
> ...
>> I've attached a list of packages and (co)maintainers, to easily find if
>> one of your packages is affected or not.
> ...
>> iwhd: meyering - clalance,zaitcev
>
> Thank you for the list.
>
> I have just tried to build i
Nils Philippsen wrote:
...
> I've attached a list of packages and (co)maintainers, to easily find if
> one of your packages is affected or not.
...
> iwhd: meyering - clalance,zaitcev
Thank you for the list.
I have just tried to build iwhd on F16 using a pretty recent gcc-4.7.x
(built manually: 4
On Mon, Jan 02, 2012 at 09:09:29AM -0700, Nathanael Noblet wrote:
>
> On Jan 2, 2012, at 5:30 AM, Nils Philippsen wrote:
> > I've attached a list of packages and (co)maintainers, to easily find if
> > one of your packages is affected or not.
>
> It seems one of my packages has an issue, the gcc
On Jan 2, 2012, at 5:30 AM, Nils Philippsen wrote:
> I've attached a list of packages and (co)maintainers, to easily find if
> one of your packages is affected or not.
Hello,
It seems one of my packages has an issue, the gcc unistd.h include one. How
do I reproduce the build issues? Is there
On Sat, 2011-12-31 at 12:56 +0100, Jakub Jelinek wrote:
> Hi!
>
> As part of preparations to switch GCC in F17 to GCC 4.7.0, I've performed
> a test mass rebuild of rawhide (December 23th package list) using
> gcc-4.7.0-0.1.fc17 on x86_64, and for those packages that failed also
> rebuilt the same
El Sat, 31 Dec 2011 16:35:00 +0100
Jakub Jelinek escribió:
> On Sat, Dec 31, 2011 at 08:55:53AM -0600, Dennis Gilmore wrote:
> > if we plan to do a mass rebuild for gcc 4.7 we need to start it
> > next week.
>
> IMHO a mass rebuild is highly desirable, but (with the exception of
> a few gcj/objc
On Sat, Dec 31, 2011 at 04:25:06PM +, Peter Robinson wrote:
> On Sat, Dec 31, 2011 at 3:35 PM, Jakub Jelinek wrote:
> > On Sat, Dec 31, 2011 at 08:55:53AM -0600, Dennis Gilmore wrote:
> >> if we plan to do a mass rebuild for gcc 4.7 we need to start it next week.
> >
> > IMHO a mass rebuild is
=?UTF-8?B?VmlsbGUgU2t5dHTDpA==?= writes:
> On 2011-12-31 13:56, Jakub Jelinek wrote:
>> gcc-4.7.0-0.1.fc17 on x86_64
> Is this package available somewhere?
It'd be a lot easier for packagers to work on fixing their packages for
it if there were a build available for F16.
On 2011-12-31 13:56, Jakub Jelinek wrote:
> gcc-4.7.0-0.1.fc17 on x86_64
Is this package available somewhere?
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
On Sat, Dec 31, 2011 at 3:35 PM, Jakub Jelinek wrote:
> On Sat, Dec 31, 2011 at 08:55:53AM -0600, Dennis Gilmore wrote:
>> if we plan to do a mass rebuild for gcc 4.7 we need to start it next week.
>
> IMHO a mass rebuild is highly desirable, but (with the exception of
> a few gcj/objc dependent p
On Sat, Dec 31, 2011 at 16:35:00 +0100,
Jakub Jelinek wrote:
> On Sat, Dec 31, 2011 at 08:55:53AM -0600, Dennis Gilmore wrote:
> > if we plan to do a mass rebuild for gcc 4.7 we need to start it next week.
>
> IMHO a mass rebuild is highly desirable, but (with the exception of
> a few gcj/objc
On Sat, Dec 31, 2011 at 08:55:53AM -0600, Dennis Gilmore wrote:
> if we plan to do a mass rebuild for gcc 4.7 we need to start it next week.
IMHO a mass rebuild is highly desirable, but (with the exception of
a few gcj/objc dependent packages not strictly required). We still have
lots of *.fc15,
if we plan to do a mass rebuild for gcc 4.7 we need to start it next week.
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
Jakub Jelinek wrote:
Hi!
As part of preparations to switch GCC in F17 to GCC 4.7.0, I've performed
a test mass rebuild of rawhide (December 23th pac
Hi!
As part of preparations to switch GCC in F17 to GCC 4.7.0, I've performed
a test mass rebuild of rawhide (December 23th package list) using
gcc-4.7.0-0.1.fc17 on x86_64, and for those packages that failed also
rebuilt the same package with gcc-4.6.2-1.fc16 to quickly remove from the
list packa
26 matches
Mail list logo
