4:49 p.m.
Hi,
Please find below the list of topics that are likely to come up in the
next FESCo meeting that is scheduled for tomorrow, Thursday at 18:00 UTC
in #fedora-meeting on irc.freenode.org:
/topic FESCO-Meeting -- Page size on PPC/PPC64 builders -
https://www.redhat.com/archives/fedora-devel-list/2008-March/msg00072.html - dwmw2
/topic FESCo-Meeting -- New Features -
http://fedoraproject.org/wiki/Features/Dashboard - poelcat
* http://fedoraproject.org/wiki/Releases/FeatureXULRunner
* http://fedoraproject.org/wiki/Features/SecurityAudit
* http://fedoraproject.org/wiki/Features/NetworkManager-MobileBroadband
* http://fedoraproject.org/wiki/Features/GlobalMenu
/topic FESCo meeting -- Free discussion around Fedora
You want something to be discussed? Send a note to the list in reply to
this mail and I'll add it to the schedule. You can also propose topics
in the meeting while it is in the "Free discussion around Fedora" phase.
If your name/nick is on above list please update the status on the
Extras schedule pages in the wiki ahead of the meeting. That way all the
other FESCo members and interested contributors know what up ahead of
the meeting. And we will avoid long delays in the meeting -- those often
arise if someone describes the recent happenings on a topic directly in
the meeting while all the others have to wait for his slow typing...
Later,
/B
--
Brian Pepple <bpepple(a)fedoraproject.org>
http://fedoraproject.org/wiki/BrianPepple
gpg --keyserver pgp.mit.edu --recv-keys 810CC15E
BD5E 6F9E 8688 E668 8F5B CBDE 326A E936 810C C15E
4:54 p.m.
On Wed, Mar 05, 2008 at 10:49:15AM -0500, Brian Pepple wrote:
Hi,
Please find below the list of topics that are likely to come up in the
next FESCo meeting that is scheduled for tomorrow, Thursday at 18:00 UTC
in #fedora-meeting on irc.freenode.org:
In the buildsys call last week, Jesse said he would bring a proposal
to make tags in CVS "immutable", which the 'correspondingsource'
project on fedorahosted will require.
--
Matt Domsch
Linux Technology Strategist, Dell Office of the CTO
linux.dell.com & www.dell.com/linux
4:58 p.m.
On Wed, 2008-03-05 at 09:54 -0600, Matt Domsch wrote:
On Wed, Mar 05, 2008 at 10:49:15AM -0500, Brian Pepple wrote:
> Hi,
>
> Please find below the list of topics that are likely to come up in the
> next FESCo meeting that is scheduled for tomorrow, Thursday at 18:00 UTC
> in #fedora-meeting on irc.freenode.org:
In the buildsys call last week, Jesse said he would bring a proposal
to make tags in CVS "immutable", which the 'correspondingsource'
project on fedorahosted will require.
OOps, yes, thanks for bringing this up again. Please add it to the
schedule.
--
Jesse Keating
Fedora -- All my bits are free, are yours?
4:54 p.m.
Jesse Keating wrote:
On Wed, 2008-03-05 at 09:54 -0600, Matt Domsch wrote:
> On Wed, Mar 05, 2008 at 10:49:15AM -0500, Brian Pepple wrote:
>> Hi,
>>
>> Please find below the list of topics that are likely to come up in the
>> next FESCo meeting that is scheduled for tomorrow, Thursday at 18:00 UTC
>> in #fedora-meeting on irc.freenode.org:
> In the buildsys call last week, Jesse said he would bring a proposal
> to make tags in CVS "immutable", which the 'correspondingsource'
> project on fedorahosted will require.
OOps, yes, thanks for bringing this up again. Please add it to the
schedule.
Ugh,
Can we _not_ do this please, sometimes one forgets to "cvs add foo-bar.patch",
being able to then just add it once the srpm build has failed in koji and do a
make force-tag is _very_ convenient. Is there actual proof that people are
using force-tag for other reasons then to fix build errors. If there is no
proof for this then why immediately use the immutable big hammer, for a
theoretical problem?
Regards,
Hans
5:14 p.m.
On Wed, Mar 05, 2008 at 04:54:48PM +0100, Hans de Goede wrote:
Jesse Keating wrote:
>On Wed, 2008-03-05 at 09:54 -0600, Matt Domsch wrote:
>>On Wed, Mar 05, 2008 at 10:49:15AM -0500, Brian Pepple wrote:
>>>Hi,
>>>
>>>Please find below the list of topics that are likely to come up in the
>>>next FESCo meeting that is scheduled for tomorrow, Thursday at 18:00 UTC
>>>in #fedora-meeting on irc.freenode.org:
>>In the buildsys call last week, Jesse said he would bring a proposal
>>to make tags in CVS "immutable", which the
'correspondingsource'
>>project on fedorahosted will require.
>
>
>OOps, yes, thanks for bringing this up again. Please add it to the
>schedule.
>
Ugh,
Can we _not_ do this please, sometimes one forgets to "cvs add
foo-bar.patch", being able to then just add it once the srpm build has
failed in koji and do a make force-tag is _very_ convenient. Is there
actual proof that people are using force-tag for other reasons then to fix
build errors. If there is no proof for this then why immediately use the
immutable big hammer, for a theoretical problem?
I didn't want the big hammer, but the buildsys folks don't want Koji
to be able to write into CVS at all, such as to create a new tag, and
there's no way to make a koji-created tag immutable, while letting the
other tags be mutable, AFAIK.
Yes, it's a theoretical problem, but if we hit it, it becomes a legal
problem.
--
Matt Domsch
Linux Technology Strategist, Dell Office of the CTO
linux.dell.com & www.dell.com/linux
6:51 p.m.
On Wed, 2008-03-05 at 10:14 -0600, Matt Domsch wrote:
I didn't want the big hammer, but the buildsys folks don't
want Koji
to be able to write into CVS at all, such as to create a new tag, and
there's no way to make a koji-created tag immutable, while letting the
other tags be mutable, AFAIK.
Yes, it's a theoretical problem, but if we hit it, it becomes a legal
problem.
I suppose that's one way in which using git for the packages would be an
improvement over CVS -- tags are easy to generate and keep out-of-band.
--
dwmw2
5:17 p.m.
On Wed, 2008-03-05 at 16:54 +0100, Hans de Goede wrote:
Can we _not_ do this please, sometimes one forgets to "cvs add
foo-bar.patch",
being able to then just add it once the srpm build has failed in koji and do a
make force-tag is _very_ convenient.
I believe we can identify cases like this where force-tag is currently
being used and develop methods of avoiding the scenario all together,
obviating the need for a force-tag.
--
Jesse Keating
Fedora -- All my bits are free, are yours?
7:46 p.m.
Jesse Keating wrote:
On Wed, 2008-03-05 at 16:54 +0100, Hans de Goede wrote:
> Can we _not_ do this please, sometimes one forgets to "cvs add
foo-bar.patch",
> being able to then just add it once the srpm build has failed in koji and do a
> make force-tag is _very_ convenient.
I believe we can identify cases like this where force-tag is currently
being used and develop methods of avoiding the scenario all together,
obviating the need for a force-tag.
I'm pretty sure you want catch all cases, but if we go this way, shall we do
that then _before_ making the tags immutable?
Thanks & Regards,
Hans
7:52 p.m.
On Wed, 2008-03-05 at 19:46 +0100, Hans de Goede wrote:
I'm pretty sure you want catch all cases, but if we go this way, shall we do
that then _before_ making the tags immutable?
Yes, that would be part of the process. Put out a call to find users of
force-tag and come up with clever ways to avoid those situations.
--
Jesse Keating
Fedora -- All my bits are free, are yours?
8:01 p.m.
Jesse Keating wrote:
On Wed, 2008-03-05 at 19:46 +0100, Hans de Goede wrote:
> I'm pretty sure you want catch all cases, but if we go this way, shall we do
> that then _before_ making the tags immutable?
Yes, that would be part of the process. Put out a call to find users of
force-tag and come up with clever ways to avoid those situations.
I think the ones which can be catched automatically is easy, parse.spec files
for all PatchX: and SourceX: lines and make sure they are either in cvs or in
the sources file. This could even also do a check for files in sources/cvs no
longer referenced from the .spec file.
As for other issues like adding a configure switch to use a certain library,
but forgetting to add the BuildRequires, and being lucky that configure bails
ebcause of this, I don't think we would be able to detect those. But I guess a
that to have to do a release bump in those rare circumstances would be ok.
Regards,
Hans
8:04 p.m.
On Wed, 2008-03-05 at 20:01 +0100, Hans de Goede wrote:
As for other issues like adding a configure switch to use a certain
library,
but forgetting to add the BuildRequires, and being lucky that configure bails
ebcause of this, I don't think we would be able to detect those. But I guess a
that to have to do a release bump in those rare circumstances would be ok.
And for that we yell at you for not doing a local mock build before
throwing it at the build system (:
--
Jesse Keating
Fedora -- All my bits are free, are yours?
9:42 p.m.
On Wed March 5 2008, Jesse Keating wrote:
On Wed, 2008-03-05 at 20:01 +0100, Hans de Goede wrote:
> As for other issues like adding a configure switch to use a certain
> library, but forgetting to add the BuildRequires, and being lucky that
> configure bails ebcause of this, I don't think we would be able to detect
> those. But I guess a that to have to do a release bump in those rare
> circumstances would be ok.
And for that we yell at you for not doing a local mock build before
throwing it at the build system (:
With my Makefile addons[1] it is possible to do:
make scratch-head-build tag build
which would only tag and build the package, if the scratch build succeeded.
Regards,
Till
[1]
http://fedoraproject.org/wiki/PackageMaintainers/UsefulScripts#head-74286...
8:09 p.m.
On Wednesday 05 March 2008, Hans de Goede wrote:
Can we _not_ do this please, sometimes one forgets to "cvs add
foo-bar.patch", being able to then just add it once the srpm build has
failed in koji and do a make force-tag is _very_ convenient. Is there
actual proof that people are using force-tag for other reasons then to fix
build errors. If there is no proof for this then why immediately use the
immutable big hammer, for a theoretical problem?
for this case a need to add a automated step to make tag that does a check
and ensures all sources and patches are checked in first.
Dennis
5:04 p.m.
On Wed, 2008-03-05 at 10:58 -0500, Jesse Keating wrote:
On Wed, 2008-03-05 at 09:54 -0600, Matt Domsch wrote:
>
> In the buildsys call last week, Jesse said he would bring a proposal
> to make tags in CVS "immutable", which the 'correspondingsource'
> project on fedorahosted will require.
OOps, yes, thanks for bringing this up again. Please add it to the
schedule.
Done.
Later,
/B
--
Brian Pepple <bpepple(a)fedoraproject.org>
http://fedoraproject.org/wiki/BrianPepple
gpg --keyserver pgp.mit.edu --recv-keys 810CC15E
BD5E 6F9E 8688 E668 8F5B CBDE 326A E936 810C C15E
5910
days inactive
5910
days old
14 comments
8 participants
participants (8)
-
Brian Pepple -
David Woodhouse -
Dennis Gilmore -
Hans de Goede -
Jesse Keating -
Matt Domsch -
Ralf Ertzinger -
Till Maas