calls
in packages where it's actually an issue (which is surely a small
minority, unless Colin has got evidence to the contrary).
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
. Auto nagmail to proventesters
might be of some value, but not to the package maintainer.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
know I've got packages that were built several weeks ago
and are still waiting in testing. When exactly was the busted rpm
version present in the buildroots?
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman
to think
about inventing non-connection-based protocols for testing database
server status, but I doubt that either one will be receptive.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Adam Williamson awill...@redhat.com writes:
On Tue, 2011-08-23 at 17:28 -0400, Tom Lane wrote:
Yeah. Another way in which socket activation is not transparent is that
code might try to determine whether the service is running by seeing
whether a connection attempt succeeds. In such a case
.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
you want to have happen
after a routine yum update.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
would be prepared to push 9.1 into f16 on
Monday if there were enough people willing to test and up-karma it
before the freeze ... any volunteers out there?
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman
=?ISO-8859-2?Q?Micha=B3_Piotrowski?= mkkp...@gmail.com writes:
2011/9/11 Tom Lane t...@redhat.com:
Yeah. I have done test packaging of 9.1rc1 already, so it's pretty much
ready to go on my end. I would be prepared to push 9.1 into f16 on
Monday if there were enough people willing to test
Bruno Wolff III br...@wolff.to writes:
Tom Lane t...@redhat.com wrote:
Yeah. I have done test packaging of 9.1rc1 already, so it's pretty much
ready to go on my end. I would be prepared to push 9.1 into f16 on
Monday if there were enough people willing to test and up-karma it
before
Bruno Wolff III br...@wolff.to writes:
On Mon, Sep 12, 2011 at 03:16:47 -0400,
Tom Lane t...@redhat.com wrote:
OK, it's built and filed at
https://admin.fedoraproject.org/updates/postgresql-9.1.0-1.fc16
One thing I noticed is that service postgresql initdb and
service postgresql help
=?ISO-8859-2?Q?Micha=B3_Piotrowski?= mkkp...@gmail.com writes:
2011/9/13 Tom Lane t...@redhat.com:
(This isn't new with 9.1, btw --- the last version or so of 9.0
for F16 was the same, since we switched over to native systemd
files.)
I used this service file on F15 and it starts slower
=?ISO-8859-2?Q?Micha=B3_Piotrowski?= mkkp...@gmail.com writes:
2011/9/14 Tom Lane t...@redhat.com:
Certainly postgresql.init was never exactly lean-and-mean, so it
seems like it ought to have been doing more work than the unit file
requires. Are you sure you were comparing apples to apples
on me (as a package maintainer) in the service
of an unproven piece of software that may yet go down the tubes.
Take a look back at the list archives over the past few months, and
ask yourself how happy people actually are with this experiment.
regards, tom lane
--
devel
it remarkable that the
systemd advocates seem to have managed not to read them, let alone admit
that they suggest something's seriously wrong.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
egregiously wrong with systemd's performance on
this test.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
with people getting branched by
default at branch time.
I don't really care which is the default; whichever it is, the need is
to make it reasonably simple to choose the other. But locking rawhide
down in pursuit of such a goal is the Wrong Thing.
regards, tom lane
did we get into such a situation, and what should
I do about it? Neither specfile appears to have any provision for
bootstrapping.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Petr Pisar ppi...@redhat.com writes:
On 2011-10-05, Tom Lane t...@redhat.com wrote:
For example, cairo BuildRequires: librsvg2-devel, and librsvg2
BuildRequires: cairo-devel, so there is no order in which I can rebuild
them. How the heck did we get into such a situation, and what should
I do
to be rebuilt.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
than rawhide where they belong. Surely, this
is a matter to discuss with the Fedora maintainer(s) of glibc and nobody
else.
And yes, I think it's about time for FESCo to step in and lay down the
law.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
, and instead have the triggerun script check to see whether the
mysql sysv initscript file is present. I wonder whether anyone else has
dealt with this and has working scriptlets?
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org
maintenance seriously.)
What I want is a packaging guideline that doesn't simply blow off
the problem of upgrading packages in pre-systemd branches. It's not
an acceptable restriction, and I'm astonished that anybody ever thought
it would be.
regards, tom lane
--
devel mailing
Honza Horak hho...@redhat.com writes:
On 10/24/2011 05:52 AM, Tom Lane wrote:
The idea I have at the moment is to ignore the advice to check package
version, and instead have the triggerun script check to see whether the
mysql sysv initscript file is present. I wonder whether anyone else has
Kevin Kofler kevin.kof...@chello.at writes:
Tom Lane wrote:
FWIW, I'm totally on board with the idea of not switching to systemd in
F15 --- and even if I wanted to do that, it's pure luck that the problem
doesn't apply to F14-F15 upgrades as well, where such an option is
certainly
speaking it is better for end users to use
#!/usr/bin/env php/python/whatever in scripts.
Why?
This whole thing seems like make-work for packagers, and big
compatibility problems for users, for negligible benefit to either.
regards, tom lane
--
devel mailing list
devel
away from Fedora and into
distributions that have more respect for their users' time.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
variants of that. I assume this is another manifestation of
the same bug being discussed here ... or have the glibc guys managed to
break the world in two different ways in the same release?
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https
Matthias Clasen mcla...@redhat.com writes:
On Wed, 2011-10-26 at 16:12 +0200, Jakub Jelinek wrote:
On Wed, Oct 26, 2011 at 10:06:31AM -0400, Tom Lane wrote:
/usr/include/glib-2.0/glib/gmacros.h:32:2: error: #error Only glib.h can
be included directly.
You are confusing glibc with glib here
be possible to rebuild a package that has source-level
dependencies on 1.2.x until those are fixed. I think this is enough
to avoid needing a special build tag for staging the rebuilds.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https
compiler warnings? I know I can't
claim to spend any time on that, except with my upstream hat on.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Chris Adams cmad...@hiwaay.net writes:
Once upon a time, Tom Lane t...@redhat.com said:
Any opinions on which way to jump?
How hard is it to fix source that accesses the fields directly? Do all
the fields that were previously exposed have direct accessor functions?
AFAIK, they all do
that, I will proceed forward with 1.5, unless somebody thinks
of a very good reason not to.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
to find patches.
(Sorry for not being more verbose, but I've got to leave shortly.
If you need help, ask me off-list.)
regards, tom lane
(orphan) amide
(orphan) assogiate
(orphan) emerald
(orphan) gconf-cleaner
(orphan) geda-gattrib
(orphan) geda-gnetlist
(orphan) geda
to
have to deal with.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
... actually I did it on an F-14 box. My notes say I did repoquery
--repoid=fedora-rawhide --whatrequires ... but I've had problems before
with repoquery not doing what I thought it would. Can anyone elucidate
on the proper incantation for this?
regards, tom lane
--
devel
Nils Philippsen n...@redhat.com writes:
On Fri, 2011-11-04 at 13:12 -0400, Tom Lane wrote:
I plan to provide the 1.2.x libpng shared library (and only the library,
not its devel support files) in a libpng-compat subpackage for the time
being.
Any reason why the compat package ships
exactly the same results? Can anyone
suggest how I might reproduce the failure someplace where I can debug it?
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Jesse Keating jkeat...@redhat.com writes:
On Nov 9, 2011, at 9:18 AM, Tom Lane wrote:
postgresql is currently failing to rebuild in rawhide:
http://koji.fedoraproject.org/koji/taskinfo?taskID=3499379
This seems quite repeatable, in koji, but the package builds fine on my
workstation under
Honza Horak hho...@redhat.com writes:
On 11/09/2011 11:54 PM, Tom Lane wrote:
That was the first thing I thought of, but the failure originally
occurred yesterday in koji, and I still can't reproduce it today in
mock.
I don't know what has changed from yesterday (instead that I've upgraded
the timing even weirder, because AFAICS gcc was last built
for rawhide on 2011-10-31. If the bug was injected then, how did it not
propagate to mock's view of rawhide until today? Something is rotten in
the state of Denmark.
regards, tom lane
--
devel mailing list
devel
Dennis Gilmore den...@ausil.us writes:
Tom Lane t...@redhat.com escribió:
postgresql is currently failing to rebuild in rawhide:
http://koji.fedoraproject.org/koji/taskinfo?taskID=3499379
so the builders are all rhel6 and the buildroots all have dns
resolution disabled. we are all running
-aliasing might be
your friend.
-fwrapv is another good tool for keeping the compiler from breaking
traditional understandings of C semantics.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
the buildroots.
Well, I don't have any objection to doing it that way, but exactly what
about this confuses the buildroots?
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
this
dependency go away again. I have routine occasion to shuffle mysql
packages in and out, and I don't want entirely-unnecessary dependencies
getting in the way.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo
Toshio Kuratomi a.bad...@gmail.com writes:
On Tue, Nov 22, 2011 at 01:16:01AM -0500, Tom Lane wrote:
I was rather surprised to find a routine yum update on my F14 system
suddenly wanting to pull in a lot of mysql stuff that I'd not had
installed at the moment.
Are you able to upgrade
upstream project produces
something we want to integrate, but not now, IMO.
Any comments, or other ideas about what to do?
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Toshio Kuratomi a.bad...@gmail.com writes:
Sounds like this is just going to occur for RawHide, right? With that in
mind
Right, no intention of changing unixODBC in released branches.
On Fri, Dec 02, 2011 at 04:22:55PM -0500, Tom Lane wrote:
There are a couple of ways I could go about
seems like a good plan.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Jun 13 2008 Tom Lane t...@redhat.com 2.2.12-8
- Install icons in /usr/share/pixmaps, not /usr/share/icons as this package
has historically done; the former is considered correct.
Digging further, the reason I changed it is because Red Hat's rpmdiff
tool whinged about the previous placement
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 lane
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
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.
regards, tom
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
Rex Dieter rdie...@math.unl.edu writes:
Tom Lane wrote:
Toshio Kuratomi a.bad...@gmail.com 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.
... um
I'm going to need.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/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
.
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 mailing list
devel
--- see
http://www.postgresql.org/download/linux
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
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.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https
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
is that mysql is now open source in name only.
/opinion
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
package, we'd be telling the maintainer to hold off
till F19. The rest of us don't get to be doing major feature
development post-beta-freeze.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
as
possible. There is not a third option. (Brooks' _Mythical_Man-Month_
has useful things to say about this sort of scheduling trap --- anybody
who hasn't read it should.)
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org
per release cycle
across the whole distro. Any significant extra burden is going to be
insupportable.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
development cycle so feature owners and
others working in the community are dealing with active and actively
maintained packages.
How exactly are you going to force maintainers who go missing to do so
at a prescheduled time? Real life is seldom that convenient.
regards, tom
=?UTF-8?B?IkrDs2hhbm4gQi4gR3XDsG11bmRzc29uIg==?= johan...@gmail.com writes:
On 11/02/2012 04:25 PM, Tom Lane wrote:
How exactly are you going to force maintainers who go missing to do so
at a prescheduled time? Real life is seldom that convenient.
bash script + a cron job should suffice
or the day after. (Anyone up for porting fedpkg
to Ubuntu?)
I've seen a whole lot of user demand for *more* stable versions of
Fedora. I've seen none whatever for less stable versions.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https
Adam Williamson awill...@redhat.com writes:
On Fri, 2012-11-02 at 17:53 -0400, Tom Lane wrote:
I've seen a whole lot of user demand for *more* stable versions of
Fedora. I've seen none whatever for less stable versions.
Perhaps I ought to be more clear. I think we can maintain the level
you right back to the series-of-releases approach
that we have now.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
creating a nasty feedback loop that further helps to drive away people
whose main interest is not in helping to debug the system. Eventually
the short-lived releases would just be rawhide-with-a-different-name.
regards, tom lane
--
devel mailing list
devel
dangerous.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Juan Rodriguez nus...@fedoraproject.org writes:
I did it on a live system, too. The only thing that failed during that time
was postgres (Which managed to stay borked after it was done and f18
booted, the pg_upgrade method didn't work properly)
BZ?
regards, tom lane
-turbo-devel provide
libjpeg-devel and not libjpeg-turbo-compat-devel?
Only if jpeg8 is a drop-in (source code compatible) replacement.
Otherwise you're only moving the point at which failures will occur.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
: mysql-devel, and no source changes are needed in other
packages.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
. Personally I'd like to dump mysql in
time for F19, but we need validation that switching to maria doesn't
break anything for anyone.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
.
regards, tom lane
once organizer, Independent JPEG Group
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
expecting would be that the mysql database package group would
actually give you mariadb, as would the anaconda checkbox.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
dropped?
We could leave 'em as is, couldn't we?
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Bill Nottingham nott...@redhat.com writes:
Tom Lane (t...@redhat.com) said:
(If the compatibility testing goes *really* smoothly, maybe we could
just drop the requirement for original mysql to still be available,
in which case it reduces to the standard package-replacement problem.
But I'm
short-term benefit. mariadb really
wants to plop down exactly where mysql was sitting: take over the
executable names, the library sonames, the data directory, etc.
Anything else will greatly complicate packaging and open the door
to added bugs.
regards, tom lane
--
devel
more work to do
... but it's work you'd have had to face up to soon anyway.)
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
the biggest issue involved with Oracle's
handling of mysql vis-a-vis downstream packagers. But if there were
to be an attempt to deal with the docs licensing problem in particular,
that would be a good solution from my standpoint.
regards, tom lane
--
devel mailing list
devel
list all the libraries that *they*
depend on, instead of being sloppy.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
to 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
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 lane
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
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 list
devel@lists.fedoraproject.org
Luke Macken lmac...@redhat.com 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 list
devel
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
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman
Kevin Kofler kevin.kof...@chello.at 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
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
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
Clyde E. Kunkel clydekunkel7...@cox.net 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 narrowing the policy to a small number
inefficient use of
their time.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
is not a useful approach to security.
regards, tom lane
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
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 one alone?)
regards, tom lane
--
devel
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
1 - 100 of 278 matches
Mail list logo
