FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora Development

 
 
LinkBack Thread Tools
 
Old 06-15-2008, 03:43 PM
Neal Becker
 
Default automating updates

I'm trying to automate the upstream updates of my packages (somewhat). The
procedure seems to be:

1. In devel:
1.1 make new-sources
1.2 update .spec
1.3 cvs ci -m 'update to xxx'
1.4 make tag build

2. cp -l -f .spec sources .cvsignore ../F9
cp -l -f .spec sources .cvsignore ../F9

3. for n in 9 8; do ( cd F-$n; cvs ci -m 'update to 1.0.1' && make tag build
&& bodhi -n -r F$n -t enhancement mercurial-1.0.1-4.fc$n ); done

What's not automated?

Howto get the current tag (e.g., mercurial-1.0.1-4.fc9)?
Optional - extract cvs ci message from spec changelog

Howto get bodhi to stop asking for a password?

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 06-15-2008, 03:53 PM
Hans Ulrich Niedermann
 
Default automating updates

Neal Becker wrote:

I'm trying to automate the upstream updates of my packages (somewhat). The
procedure seems to be:

1. In devel:
1.1 make new-sources
1.2 update .spec
1.3 cvs ci -m 'update to xxx'


make clog && cvs commit -F clog


1.4 make tag build

2. cp -l -f .spec sources .cvsignore ../F9
cp -l -f .spec sources .cvsignore ../F9


Those two cp lines should probably end with F-9 and F-8, right?


3. for n in 9 8; do ( cd F-$n; cvs ci -m 'update to 1.0.1' && make tag build
&& bodhi -n -r F$n -t enhancement mercurial-1.0.1-4.fc$n ); done


Shouldn't "make update" do some of the bodhi part?


What's not automated?


"make help" may help.


Howto get the current tag (e.g., mercurial-1.0.1-4.fc9)?


make verrel


Optional - extract cvs ci message from spec changelog


make clog

--
Hans Ulrich Niedermann

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 06-15-2008, 09:04 PM
Jeroen van Meeuwen
 
Default automating updates

Neal Becker wrote:

I'm trying to automate the upstream updates of my packages (somewhat). The
procedure seems to be:

1. In devel:
1.1 make new-sources
1.2 update .spec
1.3 cvs ci -m 'update to xxx'
1.4 make tag build

2. cp -l -f .spec sources .cvsignore ../F9
cp -l -f .spec sources .cvsignore ../F9

3. for n in 9 8; do ( cd F-$n; cvs ci -m 'update to 1.0.1' && make tag build
&& bodhi -n -r F$n -t enhancement mercurial-1.0.1-4.fc$n ); done

What's not automated?



Hmm... although I'm not much of a packager nor a frequent user of the
CVS system:


common/cvs-import.sh -b devel -m "update to x.x.x" /path/to/srpm
common/cvs-import.sh -b F-9 -m "update to x.x.x" /path/to/srpm
cvs up
cd devel; make build; cd ..
cd F-9; make build; make update [options]^1; cd ..

^1: takes the latest completed koji build of the appropriate tag even
without specifying the package name -doesn't it?


Looks to me is a little easier to script... don't you think?

Kind regards,

Jeroen van Meeuwen
-kanarip

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 06-16-2008, 12:06 AM
Christoph Wickert
 
Default automating updates

Am Sonntag, den 15.06.2008, 23:04 +0200 schrieb Jeroen van Meeuwen:
> Neal Becker wrote:
> > I'm trying to automate the upstream updates of my packages (somewhat). The
> > procedure seems to be:
> >
> > 1. In devel:
> > 1.1 make new-sources
> > 1.2 update .spec
> > 1.3 cvs ci -m 'update to xxx'

As Ulrich already suggested yesterday:
1.3.1 make clog
1.3.2 cvs commit -F clog

> > 1.4 make tag build
> >
> > 2. cp -l -f .spec sources .cvsignore ../F9
> > cp -l -f .spec sources .cvsignore ../F9
> >
> > 3. for n in 9 8; do ( cd F-$n; cvs ci -m 'update to 1.0.1' && make tag build
> > && bodhi -n -r F$n -t enhancement mercurial-1.0.1-4.fc$n ); done
> >
> > What's not automated?
> >
>
> Hmm... although I'm not much of a packager nor a frequent user of the
> CVS system:
>
> common/cvs-import.sh -b devel -m "update to x.x.x" /path/to/srpm
> common/cvs-import.sh -b F-9 -m "update to x.x.x" /path/to/srpm

Jeroen, please don't do that. We had this discussion back in Feb 2007
on the maintainers list, please search for the thread named "Discourage
cvs-import (was: Re: Plan for tomorrows (20070222) FESCO meeting)".

As a result of this discussion we set up a wiki page:
https://fedoraproject.org/wiki/PackageMaintainers/UpdatingPackageHowTo

Regards,
Christoph


--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 06-16-2008, 07:01 AM
pingou
 
Default automating updates

Neal Becker wrote:

I'm trying to automate the upstream updates of my packages (somewhat). The
procedure seems to be:

1. In devel:
1.1 make new-sources
1.2 update .spec
1.3 cvs ci -m 'update to xxx'
1.4 make tag build

2. cp -l -f .spec sources .cvsignore ../F9
cp -l -f .spec sources .cvsignore ../F9

3. for n in 9 8; do ( cd F-$n; cvs ci -m 'update to 1.0.1' && make tag build
&& bodhi -n -r F$n -t enhancement mercurial-1.0.1-4.fc$n ); done

What's not automated?

Howto get the current tag (e.g., mercurial-1.0.1-4.fc9)?
Optional - extract cvs ci message from spec changelog

Howto get bodhi to stop asking for a password?



Not long ago I wrote a small python script for automatic update of
package needing few work.

You can find the new version there:
http://pingoured.fr/public/updateCVS_0.2.py

I also published it there
http://pingoured.fr/blog/index.php?post/2008/06/01/UpdateCVSc_01
and Spot came with the answer to the
"How to start build and not wait that he has finished ?"


If that can help...

Regards,

Pierre

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 06-16-2008, 07:44 AM
Jeroen van Meeuwen
 
Default automating updates

Christoph Wickert wrote:

Am Sonntag, den 15.06.2008, 23:04 +0200 schrieb Jeroen van Meeuwen:
Hmm... although I'm not much of a packager nor a frequent user of the
CVS system:


common/cvs-import.sh -b devel -m "update to x.x.x" /path/to/srpm
common/cvs-import.sh -b F-9 -m "update to x.x.x" /path/to/srpm


Jeroen, please don't do that. We had this discussion back in Feb 2007
on the maintainers list, please search for the thread named "Discourage
cvs-import (was: Re: Plan for tomorrows (20070222) FESCO meeting)".

As a result of this discussion we set up a wiki page:
https://fedoraproject.org/wiki/PackageMaintainers/UpdatingPackageHowTo



Euh, OK! ;-)

-Jeroen

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 06-16-2008, 08:23 AM
"Nicolas Mailhot"
 
Default automating updates

Le Lun 16 juin 2008 02:06, Christoph Wickert a écrit :
>
> Am Sonntag, den 15.06.2008, 23:04 +0200 schrieb Jeroen van Meeuwen:

>> Hmm... although I'm not much of a packager nor a frequent user of
>> the
>> CVS system:
>>
>> common/cvs-import.sh -b devel -m "update to x.x.x" /path/to/srpm
>> common/cvs-import.sh -b F-9 -m "update to x.x.x" /path/to/srpm
>
> Jeroen, please don't do that. We had this discussion back in Feb 2007
> on the maintainers list, please search for the thread named
> "Discourage
> cvs-import (was: Re: Plan for tomorrows (20070222) FESCO meeting)".
>
> As a result of this discussion we set up a wiki page:
> https://fedoraproject.org/wiki/PackageMaintainers/UpdatingPackageHowTo

Discourage does not mean forbid.

For the record I do all my package changes with cvs-import.sh and I've
never had a tenth of the tagging (or other) cvs problems people
complain on the list every month.

So do not use cvs-import.sh, it's discouraged (official line). That is
unless you have no wish to be exposed to cvs quirks, and find
cvs-import.sh a nice simple interface.

--
Nicolas Mailhot

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 06-16-2008, 08:24 AM
"Thomas Moschny"
 
Default automating updates

2008/6/16 Christoph Wickert <christoph.wickert@googlemail.com>:
> Am Sonntag, den 15.06.2008, 23:04 +0200 schrieb Jeroen van Meeuwen:
>> Hmm... although I'm not much of a packager nor a frequent user of the
>> CVS system:
>>
>> common/cvs-import.sh -b devel -m "update to x.x.x" /path/to/srpm
>> common/cvs-import.sh -b F-9 -m "update to x.x.x" /path/to/srpm
>
> Jeroen, please don't do that. We had this discussion back in Feb 2007
> on the maintainers list, please search for the thread named "Discourage
> cvs-import (was: Re: Plan for tomorrows (20070222) FESCO meeting)".

Is using cvs-import for updating a package really discouraged?

It is *really* handy, compared to the series of single steps that are
to be done manually otherwise. Also, it does show a diff between old
and new spec and auxiliary files and gives you the possibility to
abort the import nowadays, so the main concern mentioned in that old
thread doesn't seem to be valid anymore.

Regards,
Thomas

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 06-16-2008, 09:12 AM
Jeroen van Meeuwen
 
Default automating updates

Thomas Moschny wrote:

2008/6/16 Christoph Wickert <christoph.wickert@googlemail.com>:

Am Sonntag, den 15.06.2008, 23:04 +0200 schrieb Jeroen van Meeuwen:

Hmm... although I'm not much of a packager nor a frequent user of the
CVS system:

common/cvs-import.sh -b devel -m "update to x.x.x" /path/to/srpm
common/cvs-import.sh -b F-9 -m "update to x.x.x" /path/to/srpm

Jeroen, please don't do that. We had this discussion back in Feb 2007
on the maintainers list, please search for the thread named "Discourage
cvs-import (was: Re: Plan for tomorrows (20070222) FESCO meeting)".


Is using cvs-import for updating a package really discouraged?



From the discussion I was pointed to it seems it has to do with having
the maintainer(s) look at the diffs before they commit anything, and
cvs-import.sh possibly nuking changes other people made... Someone with
more knowledge on the topic might be able to tell us a little more or
step in if I'm wrong;


Afaics, cvs-import.sh forces me to look at a diff, so I'm not sure if
this concern is still valid/current.


-Jeroen

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 

Thread Tools




All times are GMT. The time now is 11:54 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org