Am 23.02.23 um 20:05 schrieb Kevin Fenzi:
On Thu, Feb 23, 2023 at 11:11:49AM +0100, Florian Weimer wrote:
* Giuseppe Scrivano:
Florian Weimer writes:
It could be an old kernel bug:
Task exit is signaled before task resource deallocation, leading to
bogus EAGAIN errors
Am 21.02.23 um 07:41 schrieb Florian Weimer:
* Kevin Fenzi:
Greetings.
We are running into some anoying limits on koji builds of chromium.
First, since a long time ago, the koji.service file we are using has:
TasksMax=infinity
But yet, chromium was failing, seemingly hitting a task limit.
it is the standard mock build (centos-stream+epel-9-x86_64) which
includes centos-stream-9 and epel-9 repo.
Thanks,
Than
Am 03.01.23 um 14:47 schrieb Florian Weimer:
* Than Ngo:
our current build system for epel9 contains old version (14.0.6) of
llvm/clang while mock build has the new
Hi,
our current build system for epel9 contains old version (14.0.6) of
llvm/clang while mock build has the new version of clang/llvm (15.0.1).
there is bug in llvm 14.0.6 that causes linking error when building
chromium. The bug was fixed in llvm-15.x.
Is it possible to get new version of
Weitergeleitete Nachricht
Betreff:Re: fedpkg upload broken
Datum: Mon, 21 Nov 2022 10:38:23 +0100
Von:Than Ngo
An: Ondrej Nosek
Am 21.11.22 um 10:29 schrieb Ondrej Nosek:
Hi,
I checked the functionality and for me, it worked.
Could you, please, run
Hi,
i cannot upload new tarball chromium-107.0.5304.110-clean.tar.xz (1.6GB)
for chromium:
fedpkg upload chromium-107.0.5304.110-clean.tar.xz
Uploading: chromium-107.0.5304.110-clean.tar.xz
100.0%
Could not execute
Am Freitag, 21. Juni 2013, 17:16:09 schrieben Sie:
2013-05-06 11:13, Peter Robinson skrev:
On Mon, May 6, 2013 at 8:35 AM, Bastien Nocera bnoc...@redhat.com wrote:
Heya,
In Fedora 20, we'll be using BlueZ 5.x to manage Bluetooth devices.
Bluez5 uses a D-Bus API that's not compatible
One package wouldn't rebuild because latex doesn't work. I get the error:
cd doc/res/latex \
latex doc.tex \
latex doc.tex \
dvips doc.dvi -o doc.ps
This is pdfTeX, Version 3.1415926-2.5-1.40.14 (TeX Live 2013)
restricted \write18 enabled.
kpathsea: Running
, Than Ngo t...@redhat.com[1] wrote:
the buildrequirement is not correct, please replace your BR with these:
BuildRequires: ghostscriptBuildRequires: texlive-collection-latexrecommended
texlive-preprint
can you please check this bug?
https://bugzilla.redhat.com/show_bug.cgi?id=994883[2
the buildrequirement is not correct, please enable manual creation again and
replace all your BuildRequires on texlive* with these:
BuildRequires: texlive-collection-latexrecommended
BuildRequires: texlive-framed
BuildRequires: texlive-moreverb
it should fix the build failure.
could you please open a bug in bugzilla?
i will take a look at this.
thanks,
Than
Dear all,I'm trying to fix gdcm FTBFS and it seems that there is something
broken
with texlive in rawhide:
http://kojipkgs.fedoraproject.org//work/tasks/691/5780691/root.log[1]
For now I built without it but
the bug is fixed in new texlive, it will be available soon in rawhide.
big thanks to niels philipp for the fix!
Than
- Original Message -
could you please open a bug in bugzilla?
i will take a look at this.
Than,
Jan referenced this FTBFS
we have now arm in F20 and it seems latex2html is broken on arm in F20. It's
why
it's built fine in F19 for you but not in f20.
why is arm plattform used by default to build noarch packages in F20?
Than
On 5 August 2013 12:14, Simone Caronni negativ...@gmail.com[1] wrote:
I have a
have you built it localy or in koji? could you please give me the url if it
fails in koji?
which package is it?
thanks
than
One package wouldn't rebuild because latex doesn't work. I get the error:
cd doc/res/latex \
latex doc.tex \
latex doc.tex \
dvips doc.dvi -o doc.ps
This build has the pdf file with a different timestamp in the i686 and
x86_64 build.
http://koji.fedoraproject.org/koji/taskinfo?taskID=4189461
The pdf file is /usr/share/doc/libbluray-devel-0.2.2/libbluray.pdf from
libbluray-devel-0.2.2-2.fc18
it's a bug in pdftex (part of texlive
I think I got this fixed in
doxygen-1.8.1.1-2.fc18 :
http://koji.fedoraproject.org/koji/buildinfo?buildID=325050
I'll talk to than about getting a fixed build for f17 too
-- rex
Thanks for all the answers and thanks for the fixed doxygen. I'll try to
build the package I have
you can use xgamma or xrandr to adjust gamma.
Than
I have problems with bug 722745
(https://bugzilla.redhat.com/show_bug.cgi?id=722745), but I have heard
that there are other ways to control the screen brightness settings.
Are there any special commands you can do in addition to the gnome
17 matches
Mail list logo
