[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Please rebuild your packages in the development tree of Fedora Extras



Hello Hans, Zoltan, everybody else. 

Am Freitag, den 17.02.2006, 22:32 +0100 schrieb Zoltan Kota:
> On Fri, 17 Feb 2006, Hans de Goede wrote:
> > It seems to check the wrong time/date though, its listing a few of my 
> > packages which have all been rebuild, take Glide3 as an example from the 
> > changelog:
> > * Mon Feb 13 2006 Hans de Goede <j w r degoede hhs nl> 20050815-3
> > - Bump release and rebuild for new gcc4.1 and glibc.
> > - add %%{?dist} for consistency with my other packages
> 
> Same for me (Feb 13). Packages: recode, python-bibtex, pybliographer.

Well, I had to define a point in time *somewhere*. I took the obvious
one: The time when I announced the mass rebuild. The exact one. I know
that the rawhide push with the results from the mass rebuild was done
some hours earlier, but it also takes some time until it hits the
buildsys afaik. Yes, that was Feb 13, but to be precise it was:
$ date --date='2006-02-13 18:22:00 CET' +%s
1139851320

Then I looked at the repoquery-output from

$ repoquery -a --repoid=buildcheck-extras-development-sources
--repoid=buildcheck-extras-development-buildsys  --qf='%{buildtime}
%{name}' *.src | sort
[...]
1139849567 ngrep
1139850811 syck
1139851916 ttywatch
1139851945 contact-lookup-applet
1139852218 dkms
[...]

So I took everything above ttywatch in this list as "needs rebuild".
Hans, Zoltan, sorry, but your packages were rebuild just before that
point of time: 

$ repoquery -a --repoid=buildcheck-extras-development-sources
--repoid=buildcheck-extras-development-buildsys  --qf='%{buildtime}
%{name}' *.src | sort | grep -e Glide3$ -e recode$ -e python-bibtex$ -e
pybliographer$
1139826189 recode
1139828260 python-bibtex
1139829715 pybliographer
1139845307 Glide3

Okay. We can revisit that point in time and can set i back some hours --
but where exactly? And wherever we put it, there will probably always be
someone who'll say "My package was rebuild just <insert something
between 1 and 1440> minutes earlier then <new point of time>, why does
it need a rebuild?" This could soon lead to and endless discussion that
might take a lot of more time then it takes to just rebuild the packages
in question... 

But Hans, Zoltan, if you come up with a new point of time that is
acceptable for everyone I'm willing to change the script to that one. 

CU
thl
-- 
Thorsten Leemhuis <fedora leemhuis info>


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]