Re: [Cooker] New gmime-2.1.17-1mdk.src.rpm send in ftp.mandriva.com/incoming

[Michael Scherer]

Le Lundi 09 Janvier 2006 13:22, Moreno a écrit :
> Hi
>
> On 1/9/06, Michael Scherer <misc@mandriva.org> wrote:
> > Le Lundi 09 Janvier 2006 11:03, Moreno a écrit:
> > > Hi
> > >
> > > On 1/9/06, Götz Waschk <goetz.waschk@gmail.com> wrote:
> > > > 2006/1/8, Moreno <moreno.mg@gmail.com>:
> > > > > I have updated a new package in ftp.mandriva.com/incoming.
> > > > > The new package is gmime-2.1.17-1mdk.src.rpm, the previous version
> > > > > is 2.1.16 released in Oct 06 2005.
> > > >
> > > > Hi,
> > > >
> > > > there's no need to upload this package to incoming. I already
> > > > maintain it and I can update to a new version by myself. But if you
> > > > have any suggestions or patches, you can mail them to me.
> > > >
> > > > Regards,
> > > >
> > > > Götz
> > > > --
> > > > Terminate Schwarzenegger
> > >
> > > I'm sorry.
> > > I do not understand exactly how work ftp.mandriva.com/incoming.
> > >
> > > I have found a lot of package very old without update (your is one of
> > > the most recently updated).
> >
> > Well, in fact, while i do not want to say your work is nothing, we have a
> > script that take care of updating srpm ( called rpmbuildupdate,
> > documented on the wiki : 
> > http://qa.mandriva.com/twiki/bin/view/Main/RpmBuildUpdate).
> >
> > So, if you just update package, you are mostly doing a job that could be
> > automated. Now, if you change more than updating, this would be
> > interesting to know ( ie, include a diff in the mail ).
> >
> >
> > ( of course, rpmbuildupdate do not work with all packages, either because
> > of bugs that i would be happy to fix, or because the pec do not include
> > enough information, and that should also be fixed ).
> >
> > I will try to update antiword and whois this week, as at least, i know
> > how to use them :)
> >
> > > I have updated some of this package for give my contribute to the
> > > community.
> > >
> > > How i can know if a package is abandoned ??
> > > How i can adopt this poor packages ??
> >
> > discuss with the maintener ( rpmmon, or use the changelog ).
> >
> > --
> > Michael Scherer
>
> It's not important antiword or whois, this are secondary packages
> which i have selected because are very old, not dangerous but useful
> for gain experience.
>
> A different situation is sarg.
> In the incoming folder there are 3 sarg packages
> sarg-2.0.9-2mdk.src.rpm, sarg-2.0.9-3mdk.src.rpm and my
> sarg-2.1-1mdk.src.rpm but if we read the changelog
>
> %changelog
> * Sun Jan 01 2006 Mandriva Linux Team <http://www.mandrivaexpert.com/>
> 1.4.1-4mdk
> - Rebuild
>
> * Wed Aug 04 2004 Florin <florin@mandrakesoft.com> 1.4.1-3mdk
> - rebuild for cooker
>
> * Mon Jun 21 2004 Florin <florin@mandrakesoft.com> 1.4.1-2mdk
> - add patch (thx to  Randy Welch)
> - change url
> - add sort patch
>
> * Fri Aug 29 2003 Florin <florin@mandrakesoft.com> 1.4.1-1mdk
> - changing name (thx to D. Walser)
>
> * Thu Aug 28 2003 Florin <florin@mandrakesoft.com> 1.4-1.1mdk
> - 1.4.1
>
> * Fri Apr 04 2003 Florin <florin@mandrakesoft.com> 1.4-1mdk
> - 1.4
> - use MANDIR in make install
> - fix a typo
>
>
> Nobody have take care of this package only two stupid rebuild at
> 04/08/2004 and 01/01/2006 Why???
> The first rebuild is correct because the sarg2.0 come at Sep/29/2004
> but after ??

i guess florin left, so see with the new maintener :
~ $ rpmmon -p sarg
sbellabes@mandriva.com

if this is important, fill a bug report.

> Sarg is only an example of a lot of package simply rebuilded without
> check if a update exist.
> Where is the automated upgrade process ??

I didn't mean the upgrade was automated ( but to me, it should ), i said the 
upgrade could be automated, but you still need to run the script manualy.

And for the moment, you still need a human to give the new version to the 
script ( even if we could use youri to get this part ).
-- 
Michael Scherer