Re: Help with systemd/cgroup task limits in koji
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 <https://bugzilla.kernel.org/show_bug.cgi?id=154011> There have been recent namespace optimizations which introduce a similar pattern there. While they improve throughput in many cases, continuous allocation and deallocation can now fail, even though the program logic ensures that resources are never exceeded. Guiseppe, any suggestions how to debug this? the only optimization I am aware of that could cause a similar issue is the delayed IPC namespace cleanup. That would cause the IPC namespace creation to fail though, not posix_spawn. If you believe the failure can be related to reaching the pids limit for the cgroup, could you please check the actual limit inside the container? You could check the value of /sys/fs/cgroup/pids.max inside the container (assuming cgroupv2 and a cgroup namespace for the container). Please let me know if that helps. (replying for the benefit of the list) Than: could you try some chromium builds with a cat of that value at various points? (ie, prep, build, etc?) Hi Kevin i tried chromium build with a cat of that value. The value of /sys/fs/cgroup/pids.max is *max* at %prep, %setup and %build The chromium build failed again with errors: Error: spawn /usr/bin/node-19 EAGAIN at Process.ChildProcess._handle.onexit (node:internal/child_process:285:19) at onErrorNT (node:internal/child_process:483:16) at processTicksAndRejections (node:internal/process/task_queues:82:21) [!] Error: unfinished hook action(s) on exit https://kojipkgs.fedoraproject.org//work/tasks/2362/97912362/build.log Than ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Help with systemd/cgroup task limits in koji
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. "ninja: fatal: posix_spawn: Resource temporarily unavailable" in the build and: "kernel: cgroup: fork rejected by pids controller in /machine.slice/machine-7d12b2e6dcfb4230b04d2c2c0b499171.scope/payload" on the builder. Investigation and some help from folks in the #devel room (many thanks glb!) Showed that the systemd-nspawn container mock started has: systemctl show systemd-nspawn@0b3f01a2a8e345a389b30c477812c471 TasksMax=16384 So, I put in place a: /etc/systemd/system/systemd-nspawn@.service.d/override.conf with: [Service] TasksMax=infinity and that seemed to be used for the mock systemd-nspawn containers. However, the builds with lots of cpus is now failing later with: Error: spawn /usr/bin/node-18 EAGAIN at Process.ChildProcess._handle.onexit (node:internal/child_process:283:19) at onErrorNT (node:internal/child_process:476:16) at processTicksAndRejections (node:internal/process/task_queues:82:21) [!] Error: unfinished hook action(s) on exit: Is there yet another layer here that has another limit? Is there anything here I can set that says "infinity all the way down' ? Assistance welcome. I can file a systemd bug, but I am not sure this is a bug more than a lack of documentation. It could be an old kernel bug: Task exit is signaled before task resource deallocation, leading to bogus EAGAIN errors <https://bugzilla.kernel.org/show_bug.cgi?id=154011> There have been recent namespace optimizations which introduce a similar pattern there. While they improve throughput in many cases, continuous allocation and deallocation can now fail, even though the program logic ensures that resources are never exceeded. i am not sure if it's an old kernel bug, because kernel-6.1.7-200.fc37.aarch64 is running on koji builds of chromium. Than ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: old llvm/clang (14.0.6) in current epel9 build system while mock build has new version of clang/llvm (15.0.1)
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 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 llvm/clang (15.0.1) in build system for epel9? What “mock build” are you refering to? Is it about the c9s buildroot? That's only compatible with epel-next, not epel, as far as I understand it. Thanks, Florian ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
old llvm/clang (14.0.6) in current epel9 build system while mock build has new version of clang/llvm (15.0.1)
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 llvm/clang (15.0.1) in build system for epel9? Than ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Fwd: fedpkg upload broken
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 it with "-v" debug argument?
fedpkg -v upload ...
fedpkg -v upload chromium-107.0.5304.110-clean.tar.xz
Creating repo object from /home/than/repos/GIT/fedora/chromium
Uploading: chromium-107.0.5304.110-clean.tar.xz
100.0%
Could not execute upload: Fail to upload files. Server returns status 502
Traceback (most recent call last):
File "/usr/bin/fedpkg", line 33, in
sys.exit(load_entry_point('fedpkg==1.43', 'console_scripts',
'fedpkg')())
^^^
File "/usr/lib/python3.11/site-packages/fedpkg/__main__.py", line 89,
in main
sys.exit(client.args.command())
^
File "/usr/lib/python3.11/site-packages/pyrpkg/cli.py", line 2738, in
upload
self.new_sources()
File "/usr/lib/python3.11/site-packages/pyrpkg/cli.py", line 2727, in
new_sources
self.cmd.upload(
File "/usr/lib/python3.11/site-packages/pyrpkg/__init__.py", line
3118, in upload
self.lookasidecache.upload(
File "/usr/lib/python3.11/site-packages/pyrpkg/lookaside.py", line
353, in upload
self.raise_upload_error(status)
File "/usr/lib/python3.11/site-packages/pyrpkg/lookaside.py", line
128, in raise_upload_error
raise UploadError(message, http_status=http_status)
pyrpkg.errors.UploadError: Fail to upload files. Server returns status 502
And what are lookaside (and gitbase) addresses in the config
/etc/rpkg/fedpkg.conf ?
The config should not contain any http, but https protocols in URLs.
lookaside= https://src.fedoraproject.org/repo/pkgs
lookasidehash = sha512
lookaside_cgi = https://src.fedoraproject.org/repo/pkgs/upload.cgi
lookaside_namespaced = True
gitbaseurl = ssh://%(user)s...@pkgs.fedoraproject.org/%(repo)s
On Mon, Nov 21, 2022 at 10:22 AM Than Ngo wrote:
Hi Ondřej,
i have tried to upload new tarball
chromium-107.0.5304.110-clean.tar.xz (1.6GB) for chromium and got
the error:
fedpkg upload chromium-107.0.5304.110-clean.tar.xz
Uploading: chromium-107.0.5304.110-clean.tar.xz
100.0%
Could not execute upload: Fail to upload files. Server returns
status 502
--
rpm -q fedora-packager fedpkg curl python3-pycurl libcurl
fedora-packager-0.6.0.7-1.fc37.noarch
fedpkg-1.43-2.fc37.noarch
curl-7.85.0-2.fc37.x86_64
python3-pycurl-7.45.1-4.fc37.x86_64
libcurl-7.85.0-2.fc37.x86_64
libcurl-7.85.0-2.fc37.i686
--
Any ideas about what is going on here?
Thanks!
Than
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
fedpkg upload broken?
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 upload: Fail to upload files. Server returns status 502 -- rpm -q fedora-packager fedpkg curl python3-pycurl libcurl fedora-packager-0.6.0.7-1.fc37.noarch fedpkg-1.43-2.fc37.noarch curl-7.85.0-2.fc37.x86_64 python3-pycurl-7.45.1-4.fc37.x86_64 libcurl-7.85.0-2.fc37.x86_64 libcurl-7.85.0-2.fc37.i686 -- Any ideas about what is going on here? Than ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Orphaning packages
kde sig is orphaning following packages: - smokeqt - smokekde - qyoto - kimono - ruby-qt - ruby-korundum because of no upstream support and that they currently FTBFS on rawhide. Than ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: F23 System Wide Change: Mono 4
Hello Timotheus, the mono crashes during build process on ppc64. For more details please take a look at: https://bugzilla.redhat.com/show_bug.cgi?id=1225035 Than Am 18.05.2015 um 13:50 schrieb Timotheus Pokorra: Hello Dan, first update srpm builds fine on f22/s390x mono segfaults when running monolite on f22/ppc64 build runs well on f22/ppc64le (new arch) after adding ppc64le to the ExclusiveArch list Thanks for trying it! I have added ppc64le in the spec file to the ExclusiveArch list. I wonder how we should go about the segfault. Can you fpaste the details please? Is the segfault reproducible? How can I reproduce this? Thanks, Timotheus -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: FYI: F20 Feature: Migrate to Bluez5
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 with Bluez4[1] and as such, management applications and a number of libraries and daemons will need to be ported. For GNOME 3.10 (due September 2013), Gustavo Padovan and I are going to be porting gnome-bluetooth, NetworkManager and PulseAudio to BlueZ5. Packages for BlueZ5 will be available as soon as we figure out how to integrate a few downstream features that were in the Fedora packages. Bluez4 and Bluez5 are not parallel-installable, and incompatible, so other applications relying on Bluez4 will need to be ported by their respective maintainers. Any analysis to what packages are affected, how many are yet to support the new API and how hard it will be for them to be ported over. I took a look to see what the impact would be. I am not a BlueZ expert, so Bastien, please correct me if I am wrong somewhere. BlueZ ships a daemon and provides two main interfaces for applications to use it: 1) libbluetooth shared library 2) org.bluez DBus API The TL;DL version is that in my findings, the only package that still needs porting to bluez 5 is blueman. Others should either just continue working, or need new versions packaged up. Applications that use the libbluetooth shared library - The library ABI hasn't changed and the soname in 5.x is still the same as was in 4.x: libbluetooth.so.3, so the impact should be minimal. Everything should be able to continue working without needing even a simple rebuild. Affected packages: $ repoquery -q --whatrequires bluez-libs -s | sort | uniq amora-1.1-10.fc19.src.rpm anyremote-6.3.1-1.fc20.src.rpm asterisk-11.4.0-2.fc20.src.rpm bluecove-2.1.1-0.5.20101024snap63.fc19.src.rpm blueman-1.23-6.fc19.src.rpm bluemodem-0.7-9.fc19.src.rpm bluez-4.101-6.fc19.src.rpm bluez-hcidump-2.5-2.fc19.src.rpm btkbdd-1.3-2.fc19.src.rpm cwiid-0.6.00-21.20100505gitfadf11e.fc19.src.rpm dolphin-emu-3.0-12.fc19.src.rpm fawkes-0.5.0-7.fc20.src.rpm foxtrotgps-1.1.1-5.fc19.src.rpm gammu-1.26.1-10.fc19.src.rpm gnokii-0.6.31-6.fc20.src.rpm gnome-phone-manager-0.68-10.fc19.src.rpm gpsd-3.9-1.fc20.src.rpm gvfs-1.17.2-1.fc20.src.rpm gypsy-0.9-1.fc20.src.rpm kismet-0.0.2013.03.R1-1.fc20.src.rpm libbtctl-0.11.1-13.fc20.src.rpm libopensync-plugin-irmc-0.22-6.fc19.src.rpm nxtrc-2.3-7.fc19.src.rpm obexd-0.46-5.fc20.src.rpm obex-data-server-0.4.6-5.fc19.src.rpm obexfs-0.12-6.fc19.src.rpm obexftp-0.23-13.fc20.src.rpm openobex-1.5-8.fc19.src.rpm pilot-link-0.12.5-16.fc20.src.rpm pulseaudio-4.0-1.fc20.src.rpm pybluez-0.18-6.fc19.src.rpm qemu-1.5.0-9.fc20.src.rpm syncevolution-1.3.99.3-2.fc20.src.rpm vfrnav-20130510-1.fc20.src.rpm-- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: latex not working in F20: I can't find the format file `latex.fmt'!
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 mktexfmt latex.fmt I can't find the format file `latex.fmt'! I'm BuildRequiring the following: BuildRequires: texlive-texconfig, texlive-latex-bin-bin, texlive-dvips-bin BuildRequires: texlive-metafont-bin, texlive-cm, texlive-ec BuildRequires: texlive-preprint, texlive-cm-super, ghostscript BuildRequires: texlive-pdftex-bin which works in Fedora 19, doesn't work in Fedora 20. The missing file is /var/lib/texmf/web2c/pdftex/latex.fmt, but I've no idea how this file gets created, nor why it doesn't get created on Fedora 20. 'latex.fmt' is not mentioned in any RPM script that I have installed on F19. Ideas where to look? the buildrequirement is not correct, please replace your BR with these: BuildRequires: ghostscript BuildRequires: texlive-collection-latexrecommended texlive-preprint It should fix the build failure. The ocaml-res scratch build was done in f20 without any problem. http://koji.fedoraproject.org/koji/taskinfo?taskID=5794049 Than -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: latex not working in F20: I can't find the format file `latex.fmt'!
it built fine with same texlive version on my local machine (x86_64). This build failed on arm plattform, It seems textlive oder perl doesn't work correct on arm. How can developer access to arm machine with f20 in order to debug the issue? thanks than Hello Than, On 8 August 2013 14:47, 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] I don't know if it's related or not. My builds go timeout in Koji after 15 hours. Thanks, --Simone You cannot discover new oceans unless you have the courage to lose sight of the shore (R. W. Emerson). http://xkcd.com/229/[3] http://negativo17.org/[4] [1] mailto:t...@redhat.com [2] https://bugzilla.redhat.com/show_bug.cgi?id=994883 [3] http://xkcd.com/229/ [4] http://negativo17.org/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: latex not working in F20: I can't find the format file `latex.fmt'!
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. glassfish-jax-rs-api scratch build was done without any problem! http://koji.fedoraproject.org/koji/taskinfo?taskID=5794610 Than This is pdfTeX, Version 3.1415926-2.5-1.40.14 (TeX Live 2013) restricted \write18 enabled. kpathsea: Running mktexfmt pdflatex.fmt I can't find the format file `pdflatex.fmt'! make: *** [spec.pdf] Error 1 related to http://pkgs.fedoraproject.org/cgit/glassfish-jax-rs-api.git/tree/glassfish-jax-rs-api.spec[1] [1] http://pkgs.fedoraproject.org/cgit/glassfish-jax-rs-api.git/tree/glassfish-jax-rs-api.spec -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: gdcm FTBFS: texlive broken in rawhide?
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 that means no pdf doc and no vtk support so I would like to fix that. Thanks for any help you might provide, With best regards, Mario [1] http://kojipkgs.fedoraproject.org//work/tasks/691/5780691/root.log -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: gdcm FTBFS: texlive broken in rawhide?
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 https://bugzilla.redhat.com/show_bug.cgi?id=992788 Jaroslav 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 -- -- vtk-devel-6.0.0-7.fc20.x86_64 Error: Package: 3:texlive-dvips-bin-svn30088.0-0.3.20130608_r30832.fc20.1.x86_64 (build) Requires: texlive-kpathsea-lib = 3:2013-0.3.20130608_r30832.fc20 Installing: 3:texlive-kpathsea-lib-2013-0.3.20130608_r30832.fc20.1.x86_64 (build) --- For now I built without it but that means no pdf doc and no vtk support so I would like to fix that. Thanks for any help you might provide, With best regards, Mario -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Problem with mass rebuild / latex2html errors
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 problem on the bacula-docs package in Fedora 20. Build was stuck for 15 hours and then killed by Koji: http://koji.fedoraproject.org/koji/taskinfo?taskID=5698742[2]/[3] Would like to point out that previous Fedora 20 build from April was successful: http://koji.fedoraproject.org/koji/buildinfo?buildID=413039[4] Regards, --Simone You cannot discover new oceans unless you have the courage to lose sight of the shore (R. W. Emerson). http://xkcd.com/229/[5] http://negativo17.org/[3] [1] mailto:negativ...@gmail.com [2] http://koji.fedoraproject.org/koji/taskinfo?taskID=5698742 [3] http://negativo17.org/ [4] http://koji.fedoraproject.org/koji/buildinfo?buildID=413039 [5] http://xkcd.com/229/ -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: latex not working in F20: I can't find the format file `latex.fmt'!
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 is pdfTeX, Version 3.1415926-2.5-1.40.14 (TeX Live 2013) restricted \write18 enabled. kpathsea: Running mktexfmt latex.fmt I can't find the format file `latex.fmt'! I'm BuildRequiring the following: BuildRequires: texlive-texconfig, texlive-latex-bin-bin, texlive-dvips-bin BuildRequires: texlive-metafont-bin, texlive-cm, texlive-ec BuildRequires: texlive-preprint, texlive-cm-super, ghostscript BuildRequires: texlive-pdftex-bin which works in Fedora 19, doesn't work in Fedora 20. The missing file is /var/lib/texmf/web2c/pdftex/latex.fmt, but I've no idea how this file gets created, nor why it doesn't get created on Fedora 20. 'latex.fmt' is not mentioned in any RPM script that I have installed on F19. Ideas where to look? And, just generally asking, WTF is going on with texlive? 'texlive-latex-bin-bin' seriously? Rich. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: multilib conflict with doxygen generated pdf
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 package) which is used to create pdf
files. pdftex writes the timestamps CreationDate (%s) and ModDate (%s)
into PDF files.
extract from texk/web2c/pdftexdir/utils.c
---
void printcreationdate()
{
initstarttime();
pdf_printf(/CreationDate (%s)\n, start_time_str);
}
void printmoddate()
{
initstarttime();
pdf_printf(/ModDate (%s)\n, start_time_str);
}
---
Than
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: multilib conflict with doxygen generated pdf
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 issue with for F18 asap. it doesn't effect doxygen-1.8.0 in f17 and i don't plan to update new version in f17 yet So the newer doxygen doesn't help with the pdf file. I think the issue is the default header and footer when no LATEX_HEADER and LATEX_FOOTER are provided in the doxygen-config contain the timestamp. Should that be considered as a doxygen bug ? could you please provide a reproduce for this issue? Thanks Than -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Screen brightness settings, are there any commands?
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 screen brightness settings? That would probably help regarding that bug. /Andreas -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
