I'v just been bitten by nasm-2.09
(https://bugzilla.redhat.com/show_bug.cgi?id=678818) that changed
a derivation of __OUTPUT__FORMAT__ macro derivation from `-f FORMAT'
If your package uses nasm and conditionalizes some assembly code by
statement, resulting binary will not be what you would expect.
Backward nasm and yasm compatible solution is to change the `elf' value
to `elf32' or `elf64' (depending on target architecture) in the macro
test _and_ at the `-f elf' nasm option.
nasm-2.09 has been introduced in Fedora 14 while beeing rawhide.
Following listing of F14 SRPM shows some victims:
$ repoquery --repoid=fedora-source --repoid=updates-source \
--repoid=updates-testing-source --arch=src --whatrequires 'nasm'
As you can see SDL is missing there for unknown reason. Maybe
because the nasm BuildRequires is conditionalized by architecture.
I just made a couple changes to the first table of this page:
The chkconfig frozbozz --levels 345 on line listed systemctl enable
frozbozz.service as the main equivalent. From running that command on
rawhide, that doesn't seem to be correct. enable made the service active in
the targets that were listed in the services unit file (in the WantedBy=
line). It didn't have anything to do with the runlevels that the system
administrator was specifying (345).
The second change is that the "manual" method specified there was using
ln -s ../frobozz.service /lib/systemd/system/runlevel3.target.wants/
This seems to be incorrect since it's touching /lib instead of /etc. /etc
would both be the proper FHS place to do this (/lib and /etc could be on
separate partitions with different read-write permissions in FHS and /etc
might be backed up while /lib would not by a sysadmin that thinks the system
adheres to the FHS) and it seems to be where the systemctl enable command
puts the symlinks as well.
If someone who's more familiar with systemd could take a look and verify
that the updated equivalents are correct, that would be great.
Se você não conhece Emilio Fernandes, ignore esta mensagem de email.
Se você não pode clicar nos links, clique em « Mostrar conteúdo » e tente novamente.
Finalmente, um sistema inteligente e simples para gerenciar seus contatos!
Com UNYK, eu reuni todos os meus contatos num mesmo caderno de endereços, que se atualiza automaticamente. Um dos meus contatos modifica os dados dele(a) no site UNYK.com: meu caderno se atualiza. Eu modifico um dado no site UNYK.com: o caderno dos meus contatos se atualiza. É simples e facilita a vida!
Posso lhe acrescentar aos meus contatos? Para aceitar, clique aqui!
Você poderá também criar seu caderno de endereços inteligente.
UNYK : MQA 133
Não responda diretamente a esta mensagem. Caso você tenha perguntas ou dúvidas, por favor, entre em contato conosco: http://unyk.com/pt/Entre-em-contato-conosco
UNYK Inc., 1010 de Serigny, bureau 820, Longueuil, QC, J4K 5G7, Canada.
Não quero mais receber nenhum convite para utilizar UNYK da parte de Emilio Fernandes: cancelar minha inscrição
Não quero mais receber nenhum convite para utilizar UNYK: cancelar minha inscrição
UNYK, o primeiro caderno de endereços inteligente que se atualiza sozinho!
Sorry for the mostly off-topic post, but google hasn't been my friend
lately and I don't know where to turn.
We've had a few machines (mostly non-Fedora machines) which seem to have
a kind of rootkit installed on them, and write data to a file called
/var/run/.defunct among other non-niceties. Of course, we're going to
wipe the machines in question but googling doesn't seem to provide us
with any info and we'd like to make sure that whatever exploit got the
system cracked in the first place is patched up this time around. Any
"299792458 m/s. It's not just a good idea, It's the law."
Department of Physics and Astronomy
University of Pennsylvania
FESCo has added an additional path to becoming a co-maintainer of an
existing package in the Fedora package collection for folks who are not
currently in the packager group.
Traditionally, you would gain sponsorship by submitting a new package
you create and demonstrating your understanding of the guidelines and
processes from the review process.
This new path requires you to convince an existing maintainer
to mentor you in the processes and guidelines of package maintenance,
and would allow you to be sponsored by FESCo or an existing sponsor to
co-maintain those package(s) with your mentor guiding you.
For the full description and process for this path to becoming a package
devel-announce mailing list