On 12/06/2014 10:29 AM, valent.turko...@gmail.com wrote:
Any of these actions is simple uses error but results in permanently
disabling of priner (Stops printer) and users can't print even when they
resolve issue that was stopping them from accessing the printer.
Yes, I've run into this a lot.
On Sun, Dec 07, 2014 at 04:59:54AM +0100, Kevin Kofler wrote:
> > That is not part of the "tick-tock" proposal.
> > That is part of the "polish" release proposal.
> I don't care how you call it. The fact remains that doing a release without
> taking in new upstream releases is a complete no-go fro
Michael DePaulo wrote:
> That is not part of the "tick-tock" proposal.
> That is part of the "polish" release proposal.
I don't care how you call it. The fact remains that doing a release without
taking in new upstream releases is a complete no-go from the standpoint of
desktop environment maint
Hello,
Please see:
-> https://bugzilla.redhat.com/show_bug.cgi?id=1104041#c6
-> https://admin.fedoraproject.org/pkgdb/package/dcmtk/
Mr Mario, the current maintainer is looking for a co-maintainer for the 'dcmtk'
Fedora package. If you are interested, please apply for the co-maintainer
co
Hi,
currently default error policy for printers in Fedora is "Stop printer" on
any error which is a really bad default. I have run across this issue LOTS
of times with regular Fedora desktop users who don't get why has their
printer stopped working, there is no UI queue to warn users, there is no
e
On Sat, Dec 06, 2014 at 07:25:48 +0100,
Kevin Kofler wrote:
The updates-testing repository is only supposed to be used for packages that
will eventually hit the regular updates repository. It is NOT a dumping
ground for incompatible upgrades.
Part of the reason for this is that it creates pr
On Fri, Dec 05, 2014 at 22:57:50 -0800,
"M. Edward (Ed) Borasky" wrote:
I thought PostgreSQL fixed that a couple of years ago - "upgrade in
place" was the most-requested feature for a long time. But I can see
why DBAs wouldn't trust it after having mastered the
dump-upgrade-restore process.
On Sat, Dec 06, 2014 at 07:25:48 +0100,
Kevin Kofler wrote:
And unfortunately, a new PostgreSQL IS incompatible, because if you just run
"yum update", your databases will cease to work. You have to actually dump
them BEFORE doing the upgrade (or downgrade PostgreSQL for the dump, or
install th
On Fri, Dec 05, 2014 at 20:27:37 -0800,
"M. Edward (Ed) Borasky" wrote:
PostgreSQL is a good example - 9.4 is in the release candidate stage
right now and will probably be declared stable within a month. If it
doesn't at least make it into updates-testing before F22, I'll be
adding 9.4 from th
On 12/05/2014 03:01 PM, devel-requ...@lists.fedoraproject.org wrote:
Message: 3 Date: Fri, 05 Dec 2014 06:24:47 +0100 From: poma
To: Jeremy Newton
Cc: Development discussions related to Fedora
Subject: Re: Power Consumption
Message-ID: <5481419f.9030...@gmail.com> Content-Type: text/plain;
Compose started at Sat Dec 6 05:15:02 UTC 2014
Broken deps for i386
--
[3Depict]
3Depict-0.0.16-3.fc22.i686 requires libmgl.so.7.2.0
[Sprog]
Sprog-0.14-27.fc20.noarch requires perl(:MODULE_COMPAT_5.18.0)
[cab]
cab-0.1.
# Fedora Quality Assurance Meeting
# Date: 2014-12-08
# Time: 16:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting on irc.freenode.net
Greetings testers!
It's meeting time again on Monday! We're done with Fedora 21, so now's
the time to pat ourselves on t
12 matches
Mail list logo
