> libtiff also had the same issue and it has been updated today). This has
> already been reported in
> https://bugzilla.redhat.com/show_bug.cgi?id=678635
> How can I find out when this new libtiff update will be added to Fedora
> 14.
https://admin.fedoraproject.org/updates/libtif
s like somebody acted
on the testing request without knowing about the bundled-update plans
:-(.
I think I can revoke the update request but I'm not sure whether that
will make the mess even worse. Comments?
regards, tom lane
--
devel mailing list
devel@lists.fedora
the ticket for
updates.
(Rawhide builds work for me, though.)
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
"Nathanael D. Noblet" writes:
> On 03/22/2011 09:24 AM, Tom Lane wrote:
>> OK, I built mysql 5.5.10 in F-15, but I'm not too clear on the process
>> for getting dependent packages rebuilt in that branch. Any advice what
>> to do next?
> So I just got a b
kages rebuilt in that branch. Any advice what
to do next?
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Adam Williamson writes:
> On Mon, 2011-03-21 at 12:30 -0500, Chris Adams wrote:
>> Once upon a time, Tom Lane said:
>>> Now I have no problem with pushing such a change into rawhide, but what
>>> shall I do about Fedora 15? It doesn't seem very nice to force a
Chris Adams writes:
> Once upon a time, Tom Lane said:
>> Now I have no problem with pushing such a change into rawhide, but what
>> shall I do about Fedora 15? It doesn't seem very nice to force a soname
>> bump after alpha. On the other hand, the alternatives se
=?ISO-8859-2?Q?Micha=B3_Piotrowski?= writes:
> 2011/3/21 Tom Lane :
>> Now I have no problem with pushing such a change into rawhide, but what
>> shall I do about Fedora 15? It doesn't seem very nice to force a soname
>> bump after alpha. On the other hand, t
patch the releases to continue using the .16 version number
* revert F15 to 5.1.x release series
I don't much like any of these choices, but I don't have a time machine.
Any opinions about what to do?
regards, tom lane
--
devel mailing list
devel@lists.fed
ure the answer you'll get is "yes".
You could possibly split the manual into a documentation subpackage
with its own License: tag if you wanted to keep the license tags clear.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://ad
he way they are
doing it, AFAICS, and it's not obvious what file format you will get
from their URLs. ("zipball" seems a particularly poor choice here
--- personally I'd have thought it meant a .zip archive ...)
regards, tom lane
--
devel mailing
Jesse Keating writes:
> On 2/10/11 7:42 PM, Tom Lane wrote:
>> ... so, given that I've used "fedpkg co -B" to create a working tree
>> with a subdirectory per branch, what's the incantation to get an f15/
>> subdirectory added to that tree? I hope there
er than
"rm -rf and re-clone".
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Paul Howarth writes:
> Tom Lane wrote:
>> For the last week or so I've been getting broken-dependencies nagmail
>> about
>> mysql-test-5.5.8-6.fc15.x86_64 requires perl(mtr_misc.pl)
> RPM 4.9 has made changes in the provides/requires extraction code that
> are n
though. Should I file this
as an rpm bug, or is there some other likely explanation?
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
on
today.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
f...@redhat.com (Frank Ch. Eigler) writes:
> Tom Lane writes:
>> Hmm ... so what should I do with mysql? Since approximately forever,
>> upstream has recommended using -fno-exceptions (and also
>> -felide-constructors -fno-rtti) in CXXFLAGS. [...]
>> ...
>> Se
that don't play nice with
, such a complaint is unlikely to impress authors of plain C
apps.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
e chary of
what they expose into application namespace, or this same scenario is
going to be played out again and again.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
to remove -fexceptions.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
d
its pidfile, which it ought to do only as the last externally visible
step in its shutdown.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
homebrew
implementation; so I don't think this is violating any packaging
guidelines.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Jon Ciesla writes:
> So should simply patching to call mysql_thread_end instead should do the
> trick?
Right.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Orcan Ogetbil writes:
> On Wed, Dec 22, 2010 at 5:28 PM, Tom Lane wrote:
>> For now I'll include a symlink libmysqlclient_r.so -> libmysqlclient.so,
>> so that a simple rebuild with no source-code changes should be
>> sufficient. Â Eventually we'll probably wan
Jon Ciesla writes:
> Tom Lane wrote:
>> I got tired of the amount of visible churn in exported-symbols-you're-
>> not-supposed-to-use. The new release will use a linker --version-script
>> to hide everything except the documented API functions. This might
>> br
ade scripts off to somewhere else. But I
don't currently know enough about systemd to tackle that.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Bruno Wolff III writes:
> On Tue, Dec 28, 2010 at 19:36:35 -0500,
> Tom Lane wrote:
>> I have pushed PostgreSQL 9.0.2 into rawhide, replacing the 8.4.x release
>> series.
>>
>> Please let me know of either successful or unsuccessful upgrades.
> I tried i
itional-form backup would be
a good thing to make first.
Please let me know of either successful or unsuccessful upgrades.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Remi Collet writes:
> Le 22/12/2010 23:28, Tom Lane a écrit :
>> mysql++
> I've just committed some minor changes to this one (not related to the
> MySQL 5.5 update, but on my TODO for a while)
> Just need to launch the build (I could do it as soon as -2 will hit rawhide
=?ISO-8859-2?Q?Micha=B3_Piotrowski?= writes:
> 2010/12/22 Tom Lane :
>> 1. libmysqlclient.so, which is linked into all manner of stuff, is
>> supposed to be ABI-compatible with the previous releases. However,
>> I got tired of the amount of visible churn in exported-s
to get repoquery to not filter by arch?
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
> nuauth-log-mysql-0:2.4.3-1.fc15.i686
That seems to more nearly match the rawhide report, but I'm still
baffled as to why I don't get that from repoquery here. Also, unless
you truncated that output before reaching qt-mysql, yours is incomplete
also.
rega
here are a couple of dozen dependencies instead
of four, maybe it was a bad idea.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
from-previous-series.html
I'm not sure to what extent these may affect Fedora applications,
but it seems like the easiest way to find out is to try them.
Any objections? Anything people think should be tested before pushing?
regards, tom lane
--
devel maili
ovm
qt-mysql
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
ovides
items? I hope there's a better way than #ifarch'ing for all the known
64-bit arches ...
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
= 5.5.8-1.fc13
I thought for a bit that RPM was ignoring symlinks for this purpose, but
even copying instead of symlinking the library didn't get me a second
set of provides items. What drives those decisions?
If there isn't any good hack to fix this, how bad would it be to just
drop libmys
Devrim =?ISO-8859-1?Q?G=DCND=DCZ?= writes:
> On Sun, 2010-12-19 at 17:30 -0500, Tom Lane wrote:
>> Yes.
> What about multiple version support in PG?
I'm hoping to support in-place upgrade from 8.4. I'm not planning to
open the concurrently-installed-versions can of wor
Yes.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
ewall by default is an
incredibly stupid idea. What we need to do is fix the UI problems,
not bypass them by dramatically reducing security.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
t
getting dropped on the initscripts at all. It works perfectly well to
set up these dirs once via RPM --- why shouldn't we make the tmpfs
creation process responsible for cloning the directory structure from
disk?
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
7;d be great if that actually did happen. But it's just not going to
happen, most of the time for most packages.
(And yeah, if we allow +1 autopush, we should definitely expect -1 is
sufficient to unpush. Maybe bodhi should restrict the combination of
those two settings, rather than either o
ale.
Absolutism is not a useful approach to security.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
dividual ad-hoc test managers is an incredibly inefficient use of
their time.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
oes not result in more
manpower becoming available ... more likely the opposite.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
"Clyde E. Kunkel" writes:
> On 11/12/2010 02:32 PM, Tom Lane wrote:
>> It's absolutely crystal clear to me that we don't have enough tester
>> manpower to make the current policy workable; it's past time to stop
>> denying that. I'd suggest na
critical packages, for which there might be some hope of it actually
working as designed.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
rovide a list of the packages you are intending to rebuild?
Or at least the exact dates where the bad gcc was in use?
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
ce because of
patents. Resurrecting it from the dead now is just an exercise in
misplaced priorities.
But having said that, it's not my decision to make; it's the
libjpeg-turbo authors' decision whether to expend effort in that
direction.
s soon as F-14 is stable --- see
http://www.postgresql.org/download/linux
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
nst the policy isn't a helpful way to
proceed.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
off that future day is atm.
There was some discussion last week about teaching the broken-dependencies
nagbot to also nag about NVR sequence discrepancies. Is that feasible
or a reasonable response? Or is that subsumed under your mention of
autoqa?
regards, tom lane
--
devel
, and even the "N days ago" annotations in the
shortlog view seem wonky, as if the server clock were stuck in early
August.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
en
I forget a package I'm going to need.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Rex Dieter writes:
> Tom Lane wrote:
>> Toshio Kuratomi writes:
>>> When you do an update in F-14 and rely on inheritance to get the package
>>> into rawhide, there is a problem. That package will not go to rawhide
>>> until it hits stable in F-14.
>>
awhide should inherit the
latest completed build. It's rawhide, after all.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
allel, and
one of the back branches happens to execute first?
What I think would be useful would be to extend the broken-dependency
nagbot so that it also nags if you have a back-branch that's NVR-newer
than any later branch.
IOW: nag good, preventing people from doing their work bad.
t I like that
idea a lot better than "branch" files, and especially better than some
complicated rule with multiple places to look for the information.
> Magic inspection of the branch relationships is not a substitute for
> real configuration.
Amen to that.
not doing the right thing.
As Matt said, this sort of difference shouldn't hurt the ability to
merge or cherrypick diffs from one branch to another.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Just in case you thought we weren't having enough infrastructure fun
already ...
My web browser is complaining that admin.fedoraproject.org is presenting
an invalid SSL certificate: it expired July 31, 2010 8:17:52 AM ET,
ie about three hours ago.
regards, tom
es. I'm sending a
> list of possibly affected ones.
Were there any ABI breaks? ie should we just be forcing rebuilds?
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
than anybody else in Fedora.
I think it's counterproductive to downgrade that responsibility,
or even worse pretend that it doesn't matter --- and Kevin's lead
statement in this thread is damn close to pretending that. Sorry
Kevin, we are not interchangeable parts.
Jesse Keating writes:
> On 6/30/10 12:29 PM, Tom Lane wrote:
>> I mentioned libtiff in my first comment in this thread. The other one
>> is libpng. But in any case, are maintainers supposed to have to scare
>> up testers on their own? Especially for packages that are
Will Woods writes:
> On Wed, 2010-06-30 at 15:04 -0400, Tom Lane wrote:
>> Yes I can. I have two critpath packages that are in testing with
>> security bugs, both pretty small and easy to test, and both still have
>> karma zero. That seems to me to be adequate proof
tional
system is hard to imagine.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
to
have two maintainers who each sign up as proventesters and then bump
the karma on their own packages? Surely that's not the way to get
more eyeballs on the problem.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/
Adam Williamson writes:
> On Wed, 2010-06-30 at 11:35 -0400, Tom Lane wrote:
>> The proposed policy might be workable if we had a surplus of
>> proventester manpower available, but we obviously have not got that.
> See above, you cannot judge this on current experience.
Yes
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
something else next year
init scripts. I'll just stick with the tested sysv ones, thanks.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
er under the bridge now. If the libjpeg-turbo
group is doing active development and is taking care not to break things
unnecessarily, I'm happy to see them become the forefront of libjpeg
development. Especially if it means I don't have to do the work ;-)
regards
first, you'd need a separate build farm for every
branch, and second, fedora N-1 is still a moving target for much of the
life of fedora N.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
e
a recompile of everything that depends on it ...
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
age names at all?
The rpm-config package is certainly pretty specific to RHEL/Fedora.
Can't speak to the other two of my own knowledge ... but if they weren't
renamed the first time around, it's probably because people thought they
were distro-specific. s/redhat/fedora/ seems
ing roadblocks in the way of people who prefer ntpd is nonexistent.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Jesse Keating writes:
> On Tue, 2010-05-04 at 12:49 -0400, Tom Lane wrote:
>> Anybody else getting server error 500 when attempting to submit new
>> updates in bodhi?
> If the update had bugs listed in it, it could be failing due to the
> bugzilla outage. Now that the outag
Anybody else getting server error 500 when attempting to submit new
updates in bodhi?
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Jakub Jelinek writes:
> On Mon, May 03, 2010 at 03:35:44PM -0400, Tom Lane wrote:
>> BTW, it's now two hours later and gcc 4.4.4 is still in the buildroot.
>> There is no newrepo task running for F-13, and no evidence that one has
>> been launched recently. Perhaps an
ldroot.
There is no newrepo task running for F-13, and no evidence that one has
been launched recently. Perhaps an untag event fails to force a repo
rebuild? If so seems like a bug.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fe
ed builds see the override, or just prevent unrelated
builds from happening during the window? This is surely not going to
be the last undesired failure if things stay like this.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedorapr
why
weren't there loud bleats from broken-dependencies checking?
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
esn't apply so much to Fedora, where I usually push the
"official" update about as quickly, but for sure it's an issue on
RHEL and CentOS.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Bruno Wolff III writes:
> On Sun, Apr 25, 2010 at 12:03:28 -0400,
> Tom Lane wrote:
>> Wouldn't it be sensible to approach the Mozilla folk about getting them
>> to relax their requirements so that sane packaging is possible? ISTM
>> that this must be a proble
;t it be sensible to approach the Mozilla folk about getting them
to relax their requirements so that sane packaging is possible? ISTM
that this must be a problem for other distros too.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.
I'm getting
500 Internal error
The server encountered an unexpected condition which prevented it from
fulfilling the request.
Powered by CherryPy 2.3.0
while trying to submit new package updates in bodhi.
regards, tom lane
--
devel ma
or
packages that are purely internal to the database, but I'm not finding
that to be a compelling idea. I think "name it after the upstream
project" is a good enough rule.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
ed postgresql-tcl and postgresql-python to
better match their upstream project names, so I guess that's precedent
for Devrim's position.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
developer, I can hardly think of a quicker way to piss me
off than if every distro were to start sending me such nagmail. I would
not want such a thing turned on on *any* of my packages.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.
xact route to get to the end goal.
You also need the resources to make it happen. A mandate from FESCO
is not worth diddly-squat unless FESCO is prepared to do the work.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Kevin Kofler writes:
> Some situations where I and others have used direct stable pushes in the
> past and where I think they're really warranted and should be used:
You forgot security fixes. The proposed policy is insane.
regards, tom lane
--
devel m
et out),
> so this particular version bump should no longer be a source of trouble.
I guess I am wondering why such a change is being made in a "stable"
branch in the first place. Why isn't this sort of thing strictly
rawhide material?
regards, tom lane
--
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Luke Macken writes:
> A large number of updates currently suffer from duplicate IDs, and I
> need to figure out a clever way to fix it.
Would it be prudent to not push new updates until you've fixed it?
regards, tom lane
--
devel mailing
I just got about half a dozen "broken dependencies in devel" emails that
seem to be completely wacko, as neither the dependent nor the dependee
have changed lately. Something messed up in the repo maybe?
regards, tom lane
--
devel mailing
Martin Langhoff writes:
> On Fri, Jan 22, 2010 at 8:03 PM, Tom Lane wrote:
>> The separate /lib directory tree seems the way to go, to me. That way
> /usr/share instead of /lib seems more appropriate -
Hardly. Checksums on executables are going to be platform-specific.
Puttin
ctive, since someone who could modify the file could
change the checksum too. (I'm assuming it's just a checksum and not
any sort of digital signature.)
The separate /lib directory tree seems the way to go, to me. That way
the checksum files could be named the same as what they check,
ther monstrous attachment load that dumps
would put on bugzilla, I think we can safely dismiss the idea.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
y I think: if you get multiple
reports of the same backtrace then you start to think that it's a real
bug rather than bad RAM. This still does nothing for the basic problem,
though, which is that a backtrace alone isn't very useful for fixing
the bug.
regards, tom
e thing just stays in NEEDINFO state.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
to use xmlMemSetup() ... basically, you can't replace
libxml's memory management, you just have to live with whatever it
chooses to leak.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
fix? There's
certainly nothing in their documentation suggesting that there's
such a requirement.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
201 - 300 of 302 matches
Mail list logo
