Dnia 19-09-2007, Śr o godzinie 22:22 +0200, Rafał Cygnarowski
napisał(a):
quotation
If an individual or organization is creating a Community Edition of Mozilla
Firefox or Thunderbird, it must use the names Firefox Community Edition
or Thunderbird Community Edition to identify this software.
I think Debian does allow it, but I don't even remember those package
names. BTW: iceweasel.spec contains obsolete version of package, with
well known security bugs.
Those Debian patches seems to simply replace logos and some texts in
source. After removing debian specific chunks from patches
Patrys asked me to up evolution spec to 1.12 (corresponding with GNOME
2.20) and I've spotted, that during the GNOME packages update all the
BR-s and R-s of gnome packages were upped to 2.20 line.
The question is -- Is this necessary? I mean I've looked into
evolution's configure.in and it seems
So is this some kind of policy, to require newest packages possible at
the time of upping spec?
It seems so. Its stupid IMO to bump version to highest possible ignoring
real requirements. For example many specs from HEAD are building
perfectly on Ac after dropping unecessary version
It's used to ensure that there are latest packages on the builders. That's
the
only reason I know.
I always thought its RM job to maintain builders. But what do I know... :)
M.
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
On Thursday 20 of September 2007, Marcin Król wrote:
It's used to ensure that there are latest packages on the builders.
That's the only reason I know.
I always thought its RM job to maintain builders. But what do I know... :)
Not only RM has rights to send packages to builders.
M.
--
Dnia czwartek, 20 września 2007, Cezary Krzyzanowski napisał:
Dnia 19-09-2007, Śr o godzinie 22:22 +0200, Rafał Cygnarowski
napisał(a):
quotation
If an individual or organization is creating a Community Edition of
Mozilla Firefox or Thunderbird, it must use the names Firefox Community
Dnia 20-09-2007, Cz o godzinie 08:57 +0200, Arkadiusz Miskiewicz
napisał(a):
On Thursday 20 of September 2007, Marcin Król wrote:
So is this some kind of policy, to require newest packages possible at
the time of upping spec?
It seems so. Its stupid IMO to bump version to highest
Not only RM has rights to send packages to builders.
I don't get it. If someone will send some package it will be
automagically upgraded on builders. If such upgrade will fail on deps
I'll usually know about it quite soon and will have to fix it manually
anyway. If someone will send something
On Thursday 20 of September 2007, Marcin Król wrote:
The only good thing from bumping version I see is that when upgrade on
builders will fail user will be unable to build dependant stuff till
I'll fix it.
It happens from time to time and this is exactly the problem I was referring
to. (and
The only good thing from bumping version I see is that when upgrade on
builders will fail user will be unable to build dependant stuff till
I'll fix it.
It happens from time to time and this is exactly the problem I was referring
to. (and user can fix the problem himself and resend)
On Thu, Sep 20, 2007 at 08:33:09AM +0200, Cezary Krzyzanowski wrote:
Patrys asked me to up evolution spec to 1.12 (corresponding with GNOME
2.20) and I've spotted, that during the GNOME packages update all the
BR-s and R-s of gnome packages were upped to 2.20 line.
The question is -- Is this
On Thursday 20 of September 2007, Marcin Król wrote:
The only good thing from bumping version I see is that when upgrade on
builders will fail user will be unable to build dependant stuff till
I'll fix it.
It happens from time to time and this is exactly the problem I was
referring to.
User sends request for: libcrap, few seconds later for appX appY. libcrap
installes fine on i386 but not i686. appX and appY on i386 rebuilds fine with
new libcrap and with old libcrap on i686. Whoops.
True, but only difference is that RM will have to delete appX and appY
for i686 and user
On Thu, 20 Sep 2007, Jakub Bogusz wrote:
On Thu, Sep 20, 2007 at 08:33:09AM +0200, Cezary Krzyzanowski wrote:
Patrys asked me to up evolution spec to 1.12 (corresponding with GNOME
2.20) and I've spotted, that during the GNOME packages update all the
BR-s and R-s of gnome packages were
On Thursday 20 of September 2007, Marcin Król wrote:
User sends request for: libcrap, few seconds later for appX appY. libcrap
installes fine on i386 but not i686. appX and appY on i386 rebuilds fine
with new libcrap and with old libcrap on i686. Whoops.
True, but only difference is that
On Thursday 20 September 2007 13:57:50 Arkadiusz Miskiewicz wrote:
On Thursday 20 of September 2007, Marcin Król wrote:
User sends request for: libcrap, few seconds later for appX appY.
libcrap installes fine on i386 but not i686. appX and appY on i386
rebuilds fine with new libcrap and
On Thu, 20 Sep 2007, Marcin Król wrote:
So is this some kind of policy, to require newest packages possible at
the time of upping spec?
It seems so.
no, it's not.
It was done sometimes for things like KDE, gnome, etc to force the updates
and ensure that libraries will be upgraded.
--
18 matches
Mail list logo
