= Proposed Self Contained Change: Fontconfig cache directory change =
https://fedoraproject.org/wiki/Changes/FontconfigCacheDirChange
Change owner(s):
* Akira TAGOH
The fontconfig cache files are placed onto /var/cache/fontconfig now.
this seems incompatible with the ostree model. so this is a p
On Tue, 2016-12-20 at 23:30 +, Pádraig Brady wrote:
> On 20/12/16 22:28, Christopher wrote:
> >
> > What's with the new sources format?
> > The old format, I could do `md5sum -c sources`
> > Why not make the new format with SHA512 follow the same pattern, so
> > I could do: `shasum -c sources`
From 70951f39a237c52d9d236ed0b6875009289efb16 Mon Sep 17 00:00:00 2001
From: Jitka Plesnikova
Date: Wed, 21 Dec 2016 09:33:26 +0100
Subject: 3.02 bump
---
.gitignore | 1 +
perl-CPAN-Perl-Releases.spec | 5 -
sources | 2 +-
3 files changed, 6 insertion
On 12/21/2016 09:22 AM, Jan Kurik wrote:
= Proposed Self Contained Change: Fontconfig cache directory change =
https://fedoraproject.org/wiki/Changes/FontconfigCacheDirChange
Change owner(s):
* Akira TAGOH
The fontconfig cache files are placed onto /var/cache/fontconfig now.
this seems incompa
> The fontconfig cache files are placed onto /var/cache/fontconfig now.
> this seems incompatible with the ostree model. so this is a proposal
> to move it to /usr/lib/fontconfig/cache.
Is OStree calling for the entire /var/cache to disappear, or is there
something special about the Fontconfig cac
On Wed, Dec 21, 2016 at 01:35:56AM +, Peter Robinson wrote:
> > ...and actual QA, from the professionals and volunteers on the QA team,
> > who are very good at finding bugs pre-release but currently do zero QA
> > on our updates because it's an unmanageable rolling stream of a
> > bazillion se
Hey everyone -- clearly there's a bit of a miscommunication here.
Working it out through further discussion is good, but in the future,
it's probably better to briefly take that off list and come back when
both sides are satisfied that understanding has been reached.
Otherwise, it adds a lot of noi
OLD: Fedora-Rawhide-20161219.n.0
NEW: Fedora-Rawhide-20161221.n.0
= SUMMARY =
Added images:2
Dropped images: 0
Added packages: 15
Dropped packages:0
Upgraded packages: 144
Downgraded packages: 1
Size of added packages: 43.37 MiB
Size of dropped packages
Missing expected images:
Workstation live i386
Xfce raw-xz armhfp
Workstation live x86_64
Failed openQA tests: 14/91 (x86_64), 3/16 (i386), 1/2 (arm)
ID: 51754 Test: x86_64 Server-dvd-iso install_repository_nfs_graphical
URL: https://openqa.fedoraproject.org/tests/51754
ID: 51755 Tes
On Mon, 19 Dec 2016 09:25:19 -0500
Greg Hellings wrote:
> Marian,
>
> Alas, no luck with that. Nor with using a new browser nor a private
> mode window. The error seems to legitimately be coming from the
> server side.
Just FYI as far as I can see, this got sorted out on IRC.
Turns out to be
On Tue, 20 Dec 2016 16:03:49 +0100
Pavel Raiskup wrote:
> Hi all,
>
> where is documented what system/hw is used on (primary) Koji builders?
> I'm interested in memory, storage, filesystem, host operating system,
> guest operating system (if those are VMs), etc.
>
> The only thing I was able to
https://bugzilla.redhat.com/show_bug.cgi?id=1406581
--- Comment #4 from Fedora Update System ---
perl-CPAN-Perl-Releases-3.02-1.fc25 has been pushed to the Fedora 25 testing
repository. If problems still persist, please make note of it in this bug
report.
See https://fedoraproject.org/wiki/QA:U
On Tue, 20 Dec 2016 14:27:33 -0600
Dennis Gilmore wrote:
> On Mon, 2016-12-19 at 12:45 +0100, Nikos Mavrogiannopoulos wrote:
> > On Sun, 2016-12-11 at 18:34 -0600, Dennis Gilmore wrote:
> > > Greetings.
> > >
> > > As previously announced, releng has made a number of changes as
> > > part
> >
On Tue, 20 Dec 2016 16:03:49 +0100
Pavel Raiskup wrote:
> Hi all,
>
> where is documented what system/hw is used on (primary) Koji builders?
> I'm interested in memory, storage, filesystem, host operating system,
> guest operating system (if those are VMs), etc.
>
> The only thing I was able to
from: Task info: http://koji.fedoraproject.org/koji/taskinfo?taskID=17017344
https://kojipkgs.fedoraproject.org//work/tasks/7345/17017345/root.log
" Error: nothing provides libpython3.6m.so.1.0 needed by
gdb-headless-7.12-31.fc26.i686"
any ideas?
regards
.g
_
On Wed, 21 Dec 2016 17:06:03 +0100
gil wrote:
> from: Task info:
> http://koji.fedoraproject.org/koji/taskinfo?taskID=17017344
>
> https://kojipkgs.fedoraproject.org//work/tasks/7345/17017345/root.log
>
> " Error: nothing provides libpython3.6m.so.1.0 needed by
> gdb-headless-7.12-31.fc26.i686
On Wed, 2016-12-21 at 09:42 +0100, Ralf Corsepius wrote:
> > The fontconfig cache files are placed onto /var/cache/fontconfig
> > now.
> > this seems incompatible with the ostree model. so this is a
> > proposal
> > to move it to /usr/lib/fontconfig/cache.
>
> This proposal likely is incompatible
On Wed, Dec 21, 2016 at 11:18:54AM -0500, Randy Barlow wrote:
> > > to move it to /usr/lib/fontconfig/cache.
> > This proposal likely is incompatible to the FHS.
> >
> > Files in directories below /usr/lib are supposed to static and not
> > to be dynamically created.
> I agree - let's not violate
On 12/20/2016 11:14 PM, Sérgio Basto wrote:
On Ter, 2016-12-20 at 11:20 -0500, Matthew Miller wrote:
2. I really want releases to come at a known time every year, +/- two
weeks. Keeping to this with six month targets means that if
(when!)
we slip, the next release may only have five or fou
On Wed, 2016-12-21 at 09:12 -0700, Kevin Fenzi wrote:
> On Wed, 21 Dec 2016 17:06:03 +0100
> gil wrote:
>
> > from: Task info:
> > http://koji.fedoraproject.org/koji/taskinfo?taskID=17017344
> >
> > https://kojipkgs.fedoraproject.org//work/tasks/7345/17017345/root.log
> >
> > " Error: nothing p
Dne 21.12.2016 v 18:08 Matthew Miller napsal(a):
> On Wed, Dec 21, 2016 at 11:18:54AM -0500, Randy Barlow wrote:
to move it to /usr/lib/fontconfig/cache.
>>> This proposal likely is incompatible to the FHS.
>>>
>>> Files in directories below /usr/lib are supposed to static and not
>>> to be
Dne 21.12.2016 v 18:26 Vít Ondruch napsal(a):
>
> Dne 21.12.2016 v 18:08 Matthew Miller napsal(a):
>> On Wed, Dec 21, 2016 at 11:18:54AM -0500, Randy Barlow wrote:
> to move it to /usr/lib/fontconfig/cache.
This proposal likely is incompatible to the FHS.
Files in directories b
> I agree — it's ideal to avoid these kind of things. However, there are a
> *lot* of moving parts, and we just plain don't have coverage for every use
> case.
I don't think the base.xml file is that incomprehensible. If you remove layouts
from it, you can be pretty sure that they will be remov
On Wed, 2016-12-21 at 12:08 -0500, Matthew Miller wrote:
> I see that the fc-cache data is arch-specific, but is it really
> host-specific? What if we just pre-generated it at *build* time and
> put
> it into /usr/share or /usr/lib? I guess that'd end up making font
> files
> archful, but that's no
On Wed, Dec 21, 2016 at 06:26:48PM +0100, Vít Ondruch wrote:
> > I see that the fc-cache data is arch-specific, but is it really
> > host-specific? What if we just pre-generated it at *build* time and put
> > it into /usr/share or /usr/lib? I guess that'd end up making font files
> > archful, but t
On Wed, 2016-12-21 at 09:26 -0800, Adam Williamson wrote:
> On Wed, 2016-12-21 at 09:12 -0700, Kevin Fenzi wrote:
> > On Wed, 21 Dec 2016 17:06:03 +0100
> > gil wrote:
> >
> > > from: Task info:
> > > http://koji.fedoraproject.org/koji/taskinfo?taskID=17017344
> > >
> > > https://kojipkgs.fedora
It's the first time I'm trying to use 'fedpkg chain-build' feature, but
I'm receiving an error that I don't understand.
I want to chain-build 'kpmcore' and then 'kde-partitionmanager' in
master. So, if I understood correctly, under kde-partitionmanager master
branch I enter 'fedpkg chain-build k
On Wed, 2016-12-21 at 20:16 +0100, Mattia Verga wrote:
> Second question: I've uploaded new sources by using the new kinit
> method, but I see that the sources are actually double uploaded
> (upload
> reaches 100% and then restart again a second time). Is that normal?
I also noticed this change,
> "SM" == Sandro Mani writes:
SM> Hi I filed the request to unretire eigen2, but I accidentally
SM> specified only the rhbz ticket number instead of the full URL so it
SM> got denied with "Invalid review BZ". I now tried filing a new
SM> unretirement request with the full ticket url, but now
On Wed, Dec 21, 2016, at 07:19 AM, Björn Persson wrote:
> > The fontconfig cache files are placed onto /var/cache/fontconfig now.
> > this seems incompatible with the ostree model. so this is a proposal
> > to move it to /usr/lib/fontconfig/cache.
>
> Is OStree calling for the entire /var/cache
On Wednesday, 21 December 2016 at 18:33, Iiro Laiho wrote:
> > I agree — it's ideal to avoid these kind of things. However,
> > there are a *lot* of moving parts, and we just plain don't
> > have coverage for every use case.
[...]
> > Quality control exists
>
> But what it does actually mean? I wo
On Wed, Dec 21, 2016 at 02:02:03PM -0600, Jason L Tibbitts III wrote:
> This is the kind of thing that should probably be in an infrastructure
> ticket instead of the mailing list, but I happened to see your message.
> As far as I can tell, you're correct in your assessment and I'd
> certainly cal
On 21.12.2016 23:28, Till Maas wrote:
On Wed, Dec 21, 2016 at 02:02:03PM -0600, Jason L Tibbitts III wrote:
This is the kind of thing that should probably be in an infrastructure
ticket instead of the mailing list, but I happened to see your message.
As far as I can tell, you're correct in yo
FYI, I am taking over authd now.
CAI Qian
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
On Wed, Dec 21, 2016 at 11:34:16PM +0100, Sandro Mani wrote:
> Side-note: the new package request allows either full url or just BZ ticket
> number. Perhaps the unretirement form could be made to also accept both
> inputs.
Yes, a fix is already queued for the next release of the admin tool that
p
On 21.12.2016 23:52, Till Maas wrote:
On Wed, Dec 21, 2016 at 11:34:16PM +0100, Sandro Mani wrote:
Side-note: the new package request allows either full url or just BZ ticket
number. Perhaps the unretirement form could be made to also accept both
inputs.
Yes, a fix is already queued for the
FYI, I'll pick it up now.
CAI Qian
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> You've just offended three people without knowing anything about them.
No. I am just describing the current QA procedure. The +1 comments from three
people are seen as some kind of proof of stability of the update, and those
commenters don't go through any screening of any manner. "Works for m
If you didn't mean insult by your comments (which came across as rather
aggressive to me, too), it sufficient to say "Oh, sorry, I didn't mean
it that way." I know it's natural and easy to get defensive, but
Dominik is totally in right with the code of conduct reminder.
--
Matthew Miller
Fedora
Liro the QA team do the best they can to test updates before they go to
stable, but you hit a diferent issue, there is not enough people testing
packages before going to stable.
My keyboard layout is spanish, most QA people have a English keyboard
layout, I can update and I do not note the missing
I have two packages for review. These should be very
simple reviews.
python-pathlib2: https://bugzilla.redhat.com/show_bug.cgi?id=1406962
python-ipykernel: https://bugzilla.redhat.com/show_bug.cgi?id=1406958
Thanks,
Paulo
___
devel mailing list -- dev
Iiro Laiho wrote:
> No. I am just describing the current QA procedure. The +1 comments from
> three people are seen as some kind of proof of stability of the update,
> and those commenters don't go through any screening of any manner. "Works
> for me" really is a common expression in those comments
On Thu, Dec 22, 2016 at 01:27:34AM +0100, Kevin Kofler wrote:
> * automatically summing up unrelated +1 and -1 comments with no human
> looking at the contents does not work – 4 "+1 works for me" and 1 "-1
> destroys all my data" disastrously sum up to "+3".
I think simply blocking autokarma o
On Wed, 2016-12-21 at 23:36 +, Iiro Laiho wrote:
> > You've just offended three people without knowing anything about them.
>
> No. I am just describing the current QA procedure. The +1 comments
> from three people are seen as some kind of proof of stability of the
> update,
No they aren't. Y
On Wed, Dec 21, 2016 at 4:36 PM, Iiro Laiho wrote:
>> You've just offended three people without knowing anything about them.
>
> No. I am just describing the current QA procedure. The +1 comments from three
> people are seen as some kind of proof of stability of the update, and those
> commenter
On Wed, 2016-12-21 at 18:34 -0700, Chris Murphy wrote:
> Well it seems to me if a packaging change means some files are going
> to be removed upon updating that package with the new (and changed)
> package, that it's reasonable something somewhere is going to break,
> and that this should cause the
Hi Laiho, your bug was fixed less than five hours from the report. Keep in mind
that is a bit hard to find an issue in a specific Language, so please do not
blame testers/QA guys. Feel free to always report these situations and keep
contribuing with tests/patches.
Cheers, Filipe R.
Hi,
I occasionally get this strange failure in koji. Sometimes this happens
with a good package build, and I can just re-submit it without changing
anything, and it works fine. Is this a known issue?
For example, from
https://kojipkgs.fedoraproject.org//work/tasks/1330/17021330/build.log:
sh: /u
Hi,
I occasionally get this strange failure in koji. Sometimes this happens
with a good package build, and I can just re-submit it without changing
anything, and it works fine. Is this a known issue?
For example, from
https://kojipkgs.fedoraproject.org//work/tasks/1330/17021330/build.log:
sh: /u
On Thu, 22 Dec 2016 03:03:56 +
Christopher wrote:
> Hi,
>
> I occasionally get this strange failure in koji. Sometimes this
> happens with a good package build, and I can just re-submit it
> without changing anything, and it works fine. Is this a known issue?
>
> For example, from
> https:/
Mattia Verga wrote:
> It's the first time I'm trying to use 'fedpkg chain-build' feature, but
> I'm receiving an error that I don't understand.
> I want to chain-build 'kpmcore' and then 'kde-partitionmanager' in
> master. So, if I understood correctly, under kde-partitionmanager master
> branch I
On Wed, Dec 21, 2016 at 6:42 PM, Adam Williamson
wrote:
> On Wed, 2016-12-21 at 18:34 -0700, Chris Murphy wrote:
>> Well it seems to me if a packaging change means some files are going
>> to be removed upon updating that package with the new (and changed)
>> package, that it's reasonable something
On Wed, Dec 21, 2016 at 10:14 PM Kevin Fenzi wrote:
> On Thu, 22 Dec 2016 03:03:56 +
> Christopher wrote:
>
> > Hi,
> >
> > I occasionally get this strange failure in koji. Sometimes this
> > happens with a good package build, and I can just re-submit it
> > without changing anything, and it
Hi All,
Just a heads up that xapian 1.4 is headed to rawhide.
Peter
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
On 12/21/2016 11:12 PM, Peter Robinson wrote:
Hi All,
Just a heads up that xapian 1.4 is headed to rawhide.
Peter
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
I tried to
>> Hi All,
>>
>> Just a heads up that xapian 1.4 is headed to rawhide.
>>
>> Peter
>> ___
>> devel mailing list -- devel@lists.fedoraproject.org
>> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>>
>
> I tried to rebuild doxygen - fix
56 matches
Mail list logo
