sr/lib64/glib-2.0/include/glibconfig.h
-rw-r--r-- /usr/lib64/pkgconfig/glib-2.0.pc
-rw-r--r-- /usr/lib/glib-2.0/include/glibconfig.h
-rw-r--r-- /usr/lib/pkgconfig/glib-2.0.pc
$ pkg-config --cflags glib-2.0
-I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include
Björn Persson
signature.as
iteria are no
better than flipping a coin.
Björn Persson
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
y
> desirable.
The requirement to build from source is already explicit:
https://fedoraproject.org/wiki/Packaging:Guidelines#No_inclusion_of_pre-built_binaries_or_libraries
Björn Persson
signature.asc
Description: PGP signature
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
only to some users, or if it
pulls in lots of additional stuff, then it should be suggested and get
installed only on the user's explicit request. This minimizes bloat.
Björn Persson
signature.asc
Description: PGP signature
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
s.
In batch operations like Kickstart and Mock I'm thinking recommendations
and suggestions would be ignored and only required packages would be
pulled in. I don't know how Kickstart handles Comps groups but "default"
sounds to me like it would be installed even in batch operations.
Björn Persson
signature.asc
Description: PGP signature
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
the client, while the client might only suggest the server.
A third example is graphical administration tools for some daemon that
are in a separate package so that the daemon can be installed without
pulling in half a desktop environment. In this case the daemon should
suggest the tools, but perha
ls,
so doing it with libraries can't be too difficult. There must be a
better way to handle soname bumps like the one in LibPNG that is being
discussed right now.
If automatic cleanup of dependencies gets implemented, then an old
version of a library should be removed when no installed packages
r
quot;net", ATTR{address}=="00:1e:8c:cf:cd:e5",
NAME:="gigabit"
ACTION=="add", SUBSYSTEM=="net", ATTR{address}=="00:16:6f:a9:95:34",
NAME:="wifi"
As a bonus I got human-readable interface names, making it much easier
to remember which interface is which, but my primary motivation was to
make it possible to configure stuff.
Björn Persson
signature.asc
Description: PGP signature
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
hat users would notice *before* they start typing.
Björn Persson
signature.asc
Description: PGP signature
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
t; The admin won't know about this misfeature until he looks up
from the keyboard and sees the password being displayed in the clear,
right?
Always close the door and the blinds when installing operating systems?
That's easier said than done in an open plan office.
Björn P
Richard W.M. Jones wrote:
> On Thu, Apr 18, 2013 at 01:14:33AM +0200, Björn Persson wrote:
> [...]
> > > Passing pointers to objects from one language to another is likely
> > > *not* possible however.
> >
> > Ada imports and exports C pointers just fine, inc
another is likely
> *not* possible however.
Ada imports and exports C pointers just fine, including pointers to
functions and records. Strings typically need to be converted though,
as strings aren't null-terminated in Ada.
Of course Ada can't prevent the C code from corrupting
t; objects.
Of course there is always some overhead. Do you mean that they have a
significantly larger overhead than garbage collectors have?
Björn Persson
signature.asc
Description: PGP signature
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
e than other
languages. Of course an infallible superhuman could write good code in
any language, and a fool can write bad code in any language, but a
normal human programmer will write better code in a well-designed
language than in an ill-designed language.
Björn Persson
signature.asc
Description: P
at's not
a problem with the language itself but a result of low popularity, and
would change with time if more programmers would start using Ada. Help
with packaging the libraries that do exist would be welcome.
A free compiler? Yes, we have one in Fedora.
Björn Persson
s
estarts itself between each connection or at
> least on a regular basis (ie. it's a forking or pre-forking server, or
> the server is started on each connection by inetd/systemd)?
Or it crashes and gets restarted every time the attacker fails to guess
the addresses.
Björn Persson
s
Paul Wouters wrote:
> Why does the _hardened_build macro for the spec file use "-z,relro" and not
> "-z,relro,-z,now" ?
Huh? As far as I can see _hardened_build adds -z now, not relro.
-Wl,-z,relro is supposed to be included in LDFLAGS. Or has this change
Juerg Haefliger wrote:
> BuildArch: noarch
>
> %if 0%{?rhel}
> # Only build on x86_64 for EPEL because qemu-img only exists for that arch
> ExclusiveArch: x86_64
> %endif
[...]
> error: Architecture is not included: noarch
Try "ExclusiveArch: noarch x86_64".
e FESCo maintains a list, I suppose anyone can propose specific
programs to be added to the list, but it seems pointless to explicitly
list programs that are already covered by the first three criteria.
Björn Persson
signature.asc
Description: PGP signature
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Kevin Fenzi wrote:
> On Tue, 19 Mar 2013 21:24:22 +0100
> Björn Persson wrote:
>
> > Is there a date in the release schedule when the new release key shall
> > be added to <https://fedoraproject.org/keys>? It seems logical to me
> > to publish the key as soo
owing up on the mirrors, and on
the keyservers there is a key that claims to be the Fedora 19 release
key, generated on the first of December, but since the key isn't signed
and isn't on the web page I have no way of verifying it.
Björn Persson
signature.asc
Description: PGP signature
-
nges left and right.
As I understand it Fedora has release names because people like to see
them displayed in various places. That means they are user-visible
content.
Björn Persson
signature.asc
Description: PGP signature
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedo
Przemek Klosowski wrote:
> On 03/11/2013 05:03 PM, Björn Persson wrote:
>
> >> Your TV (which likely has embedded Linux)? Your car?
> >> Windows? OS X?
> >
> > I don't have any of those, and I doubt I'll ever buy a car when I want
> > a genera
he disk encryption passphrase."
Are there other messages that Plymouth may need to display? I would
guess there aren't so many that the scalability of this approach would
be a problem.
Björn Persson
signature.asc
Description: PGP signature
--
devel mailing list
devel@lists.fedoraproject.
be a significant problem. Could
you explain why you think people are likely to press random keys by
mistake during the boot? I don't think that has ever happened to me.
Björn Persson
signature.asc
Description: PGP signature
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
it?
Could there at least be some instructions displayed *after* I
accidentally succeed the first time, so I'll know how to do it next
time?
Björn Persson
signature.asc
Description: PGP signature
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
e boot loader because the OS fails
to boot.
Björn Persson
signature.asc
Description: PGP signature
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Lennart Poettering wrote:
> On Mon, 11.03.13 21:20, Björn Persson (bjorn@rombobjörn.se) wrote:
>
> > Peter Robinson wrote:
> > > It use to only be displayed if there was more than one OS configured
> > > or if the CTRL was held down. Having to press a particular key
whether and how I'll be able to revert if
anything goes wrong.
> Your TV (which likely has embedded Linux)? Your car?
> Windows? OS X?
I don't have any of those, and I doubt I'll ever buy a car when I want
a general-purpose computer.
Björn Persson
signature.asc
Description:
add some kernel
parameter to get the system up enough to solve some boot problem?
Detecting that the previous boot failed is nice and all, but that
mechanism needs to be totally infallible if it's going to be the only
way the Grub menu can be accessed.
Björn Persson
signature.asc
Description:
that way. As I already wrote, if the Grub menu is simply displayed,
then five seconds is enough. Much better. And if you want to save those
five seconds you just need to press Enter.
Björn Persson
signature.asc
Description: PGP signature
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
t before the BIOS
> disappears.
But how are users supposed to discover it?
Björn Persson
signature.asc
Description: PGP signature
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
is made the harder it will be to
understand. I estimate that at least 15 seconds would be needed. Adding
"Press Enter to save a few seconds." would make it even more text to
read and understand.
Björn Persson
signature.asc
Description: PGP signature
--
devel mailing
Ryan Lerch wrote:
> Does the bootup screen require any keyboard other input at all other
> than escape to bring up the details?
It must be possible to enter a disk encryption password.
Björn Persson
signature.asc
Description: PGP signature
--
devel mailing list
devel@lists.fedoraproje
ding the graphical screen will be a win in terms of reduced visual noise.
What would there be instead? A text-mode boot menu? Or nothing at all
displayed unless the user happens to know to press some key at the
right moment?
Björn Persson
signature.asc
Description: PGP signature
--
devel
ript uses CSV generated from Bugzilla in one time but
> as the script runs nearly for a day, conflicts can happen...
I seem to recall that I've seen Bugzilla detect and warn about
conflicting concurrent changes. It would seem like a good idea to have
the script use that mech
d do that, and retry the scratch build once a day, then it
would eventually work its way through dependency chains.
Björn Persson
signature.asc
Description: PGP signature
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
in the
cryptographic language I'm used to.
Ah, according to this:
http://software.intel.com/en-us/blogs/2012/11/17/the-difference-between-rdrand-and-rdseed
RDRAND doesn't output random numbers, only pseudorandom numbers. I
suppose that's what you meant.
Björn Persson
signatu
plot.
Wow, that's a weird compiler bug.
Your test program works for me if I change the conversion to
Integer(Long_Long_Integer(R1)). Perhaps you could patch PLplot with
that workaround while we wait for a fix to GCC?
Björn Persson
signature.asc
Description: PGP signature
--
devel mailing lis
florist-2011-8.fc18.i686 requires libgnarl-4.7.so
> > florist-2011-8.fc18.x86_64 requires libgnat-4.7.so()(64bit)
> > florist-2011-8.fc18.x86_64 requires libgnarl-4.7.so()(64bit)
Same thing as with zeromq-ada: "BuildRequires: gcc-gnat" is missing.
Björn Per
s that upgrading by Yum
isn't supported, as Fedora is said to be community-supported and the
community seems to be supporting Yum upgrades about as well as any
other aspect of Fedora.
Björn Persson
signature.asc
Description: PGP signature
--
devel mailing list
devel@lists.fedoraproject
e to have. Then maybe "yum upgrade"
> could require (or at least recommend) switching to that mode first.
Isn't that essentially what Fedup does?
Björn Persson
signature.asc
Description: PGP signature
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
le it should be possible to do the rebuild entirely
automatically, if we allow automated processes to push to Git. Even a
client-side tool to do rebuilds in dependency order would help, but I
haven't yet figured out how to write one.
Björn Persson
signature.asc
Description: PGP signature
--
o be manually started and
monitored it will always take some time. I imagine that quite a few
people would be annoyed if GCC would be delayed while we rebuild the
Ada packages.
Björn Persson
signature.asc
Description: PGP signature
--
devel mailing list
devel@lists.fedoraproject.org
http
ronous name resolution without involvement of threads and
> suchlike then your only option is to make NSS asynchronous in itself,
> and you cannot do that without reworking glibc substantially.
Thank you for presenting a valid argument instead of just ranting
sarcastically.
Björn Persson
signat
u make them a
separate, portable library, then they can be installed on all Unix-like
systems, and maybe other operating systems too, and programs that use
them will also be portable. Wouldn't that be better?
Björn Persson
signature.asc
Description: PGP signature
--
dev
Stephen John Smoogen wrote:
> On 10 January 2013 14:17, Björn Persson wrote:
> > Adam Jackson wrote:
> >> On Thu, 2013-01-10 at 17:56 +0100, Till Maas wrote:
> >> > But why should anaconda not verify packages if secure boot is disabled?
> >>
> >> F
k.
Anaconda shouldn't proceed unless you tell it that you have checked the
boot image manually and found it to be genuine. This could be done with
a button that you have to clik on, labeled "Yes I checked the boot
image." Or the fact that you booted the boot image could be taken
Peter Jones wrote:
> On Tue, Jan 08, 2013 at 05:46:04PM +0100, Björn Persson wrote:
> > In my opinion, if Anaconda finds that it was booted without Secure
> > Boot, then it should assume that the user has verified the checksum on
> > the installation image and that the keys
ys to verify any packages it downloads.
It's enough to verify downloaded packages in that case. Packages
included on the boot medium don't need to be checked if the boot medium
is trusted, but of course it doesn't hurt to verify those too if it's
easier to program that way.
Adam Williamson wrote:
> On Tue, 2012-12-18 at 02:05 +0100, Björn Persson wrote:
> > Adam Williamson wrote:
> > > anyhow, the tricky thing here lies in somehow making it safe for
> > > fedup to *automatically* import the correct key for the next
> > >
k pair, and
Fedup needs to verify that signature. Naturally the signature must be
verified before the kernel/ramdisk pair is booted.
Björn Persson
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
. As long as people are being
discouraged from upgrading by Yum because it's "unsupported", removing
the only "supported" and secure upgrade method is definitely a
regression, and quite irresponsible.
Björn Persson
--
devel mailing list
devel@lists.fedoraproject.o
kages depend on each other? What "Provides" and
"Requires" fields are there in their spec files? What do you get if you
run "rpm --query --provides" and "rpm --query --requires" on each
package?
Björn Persson
--
devel mailing list
devel@lists.fedoraproje
maintainers in other distributions.
Björn Persson
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
e SSID and
the channel, if that's what you mean.
You don't seem to think the problem is in my ifcfg file, so I filed a bug
report:
https://bugzilla.redhat.com/show_bug.cgi?id=876786
Björn Persson
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
0m0.001s
user0m0.000s
sys 0m0.000s
Björn Persson
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
t_edit_wars
Also, mistakes on Wikipedia are unlikely to cause widespread breakage of
users' work environments or insert backdoors into lots of computers all
over the world.
Björn Persson
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Dan Williams wrote:
> On Tue, 2012-11-06 at 21:47 +0100, Björn Persson wrote:
> > I have a Wifi card that is supposed to be managed by the "network"
> > service. The interface's IP addresses, prefixes, routes and all that
> > get assigned correctly on boot
ore I file a bug report I wanted to ask: Does
anyone see anything wrong with the ifcfg file below?
Björn Persson
DEVICE=wifi
NAME="Wifi"
HWADDR=00:16:6f:a9:95:34
NM_CONTROLLED=no
BOOTPROTO=none
ONBOOT=yes
TYPE=Wireless
IPADDR0=192.168.96.1
PREFIX0=24
DEFROUTE=no
IPV4_FAILURE_FATAL=yes
IPV6
"/", and proceeds to look for files in
/share, which doesn't exist and never has.
We really need to get /bin and /sbin removed from PATH, or at least
moved behind /usr/bin and /usr/sbin.
Björn Persson
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
t perhaps "ctl" is short for "cutler" and alludes to Journalctl's
ability to slice up logs in several different ways? In that case the name
would be easier to remember if "cutler" were spelled out.
Björn Persson
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Daniel P. Berrange wrote:
> On Wed, Oct 10, 2012 at 12:00:41PM +0200, Björn Persson wrote:
> > So if my Fedora box won't boot, and I take the disk out and mount it
> > in a CentOS box, I might not be able to read the log because
> > journalctl in CentOS might be too
to read any previous version of the
> binary file format.
So if my Fedora box won't boot, and I take the disk out and mount it in
a CentOS box, I might not be able to read the log because journalctl in
CentOS might be too old? Not fun.
Björn Persson
--
devel mailing
l -D
So the rescue system (which might not always be Fedora) must have
journalctl installed. Is the file format stable, or can it break if the
rescue system has a different version of journalctl? Is the format
perchance even documented so that other tools for reading logs could be
written?
Björn
t the terms "alpha" and "beta"? Fedora 18 has been declared alpha.
Before that it was pre-alpha. After some more testing and fixing it will
reach beta status. Right?
Björn Persson
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Richard W.M. Jones wrote:
> If I give negative karma, that's because I tested the update and
> found it didn't work.
Why would you do that instead of retracting the update?
Björn Persson
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
is. I'm just pointing out a logical consequence that
officially allowing proxy karma would have.
Björn Persson
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
kept waiting for everyone
else, so here we are now with an Internet that has been split into an IPv4-
only part and an IPv6-only part.
Björn Persson
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
mebody's idea of "good". As we found out in another branch
of this thread, people can disagree on which rendering method makes a font
look good.
Björn Persson
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Are you not even allowed to install Putty and log in by SSH from the laptop to
your home PC?
A Git implementation for Windows would probably make your work easier. A quick
search indicates that such programs exist.
Björn Persson
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.
unfortunate, but they are an inevitable effect of
limited screen resolution. I'll choose the thickness jumps over the blurry
letters without hesitation.
Should we hold a vote to determine how the majority of users like their fonts?
Björn Persson
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Changing a programming language under the programmers' feet it almost never a
good idea. Shall I start setting all Bash options explicitly in every single
shell script just so that I'll know how the language works even if someone
changes the defaults on me?
Björn Persson
signature
cases fall under "unsupported".
That's no excuse for not doing the right thing (provided that there is an
objectively right thing to do).
Björn Persson
signature.asc
Description: This is a digitally signed message part.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Michael Schwendt wrote:
> On Sat, 7 Jul 2012 19:50:41 +0200, Björn Persson wrote:
> > When fedpkg chain-build fails with the message "Unsuccessfully waited
> > 120:09 for GtkAda-2.24.2-1.fc18 to appear in the f18-build repo", how
> > can I check later whether the pac
When fedpkg chain-build fails with the message "Unsuccessfully waited 120:09
for GtkAda-2.24.2-1.fc18 to appear in the f18-build repo", how can I check
later whether the package has appeared yet so that I can build the next
package in the dependency chain?
Björn Persson
sig
have to translate
"xterm-256color" to "xterm", "screen-256color" to "screen" et cetera. Simply
setting TERM=xterm in all SSH sessions is probably not sufficient.
Björn Persson
signature.asc
Description: This is a digitally signed message part.
--
de
Paul Wouters wrote:
> Let me know how dnssec-trigger 0.11 works, with the additional
> hotspot port 80 manglign detection.
I'm afraid my laptop isn't all that usable right now –
https://bugzilla.redhat.com/show_bug.cgi?id=832723 – but I'll see what I can
do.
Björn Pe
would like to see on
> Fedora.
Hi Julian, and welcome! We can certainly need another Ada packager. It will be
great to have GPS in Fedora, but it's brave of you to do that as your first
Fedora package. I haven't dared to tackle GPS myself yet.
Björn Persson
signature.asc
Descript
cludes that the installation
prefix is /, and looks for its data in /share instead of /usr/share, which of
course fails because there is no /share. Working around this required a
Fedora-specific patch to make GPRbuild resolve the symbolic link.
Björn Persson
signature.asc
Description: This
cache when even HTTPS is blocked.
Perhaps dual-view setups like mine should simply use a short TTL to minimize
the problem.
Björn Persson
signature.asc
Description: This is a digitally signed message part.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
sure that the new library is in place.
Björn Persson
signature.asc
Description: This is a digitally signed message part.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
bar
grows and shrinks, but the brightness is not affected.
> Does `xbacklight` work?
All xbacklight commands I try (except for "xbacklight -help") cause the screen
to flash once and return zero. Even "xbacklight -get" causes a flash, prints
nothing, and returns zero.
Bjö
brightness back up.
Which package should I report this against? Linux? X? Plymouth? Or something
else?
Björn Persson
signature.asc
Description: This is a digitally signed message part.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Adam Williamson wrote:
> On Sun, 2012-06-03 at 19:56 +0200, Björn Persson wrote:
> > I also won't install anything that I haven't checked the PGP signature
> > on. That excludes netinst.iso and Preupgrade, and if I use Anaconda I
> > have to be careful to not let
just Sweden.
Note 2: Yes there are reusable optical media, so user's don't need to buy new
discs every time they upgrade Fedora. None the less, the more people use
optical media, the more optical media will be sold in total, and the more
money will flow to the copyright lobby.
Björn Pe
Josh Boyer wrote:
> On Sun, Jun 3, 2012 at 4:32 PM, Björn Persson
> wrote:
> > Tomasz Torcz wrote:
> >> You can write .iso image to USB key¹ and boot from it, you know.
> >
> > Even the installation DVD images? What I've heard is that that only works
&g
started doing that.)
Björn Persson
signature.asc
Description: This is a digitally signed message part.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
ing that I haven't checked the PGP signature on.
That excludes netinst.iso and Preupgrade, and if I use Anaconda I have to be
careful to not let it download anything.
Therefore I usually upgrade by Yum. That's also a laborious process, but I
usually get a mostly working system in the
SSH server, then
I'd suspect the firewall. Many firewalls have a bad habit of mangling data and
violating protocols. Is it possible for you to see what it looks like from the
server side? For example, does the SSH server crash or does it also receive an
RST packet?
Björn Persson
signatur
e build has completed, then the right solution is to change
the user interface of Bodhi to allow that. An even better solution might be a
combined interface where you could start a set of builds and submit the update
information as a single operation.
Björn Persson
signature.asc
Description: Th
atch
> Will it allow me then build package?
Yes.
Björn Persson
signature.asc
Description: This is a digitally signed message part.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
link to the one on the upstream
website.
To link to a patch you can use a URL similar to this:
http://pkgs.fedoraproject.org/gitweb/?p=erlang.git;a=blob_plain;f=otp-0002-
Remove-rpath.patch;hb=5d2c8835ef0223b3939eb372189625c2a88692b4
Björn Persson
signature.asc
Description: This is a digitall
Ankur Sinha wrote:
> The package is required for Fedora videos[1] :)
>
> [1] http://fedoraproject.org/wiki/Video
How does a keylogger help you upload videos to the Internet Archive?
Björn Persson
signature.asc
Description: This is a digitally signed message part.
--
devel mailing l
ballz marked as executable after the %install
step? I have found that RPMbuild doesn't pick up dependencies from shared
libraries if they don't have the execute privilege bits set. Presumably that
goes for executables too. It would be strange though if GCC doesn't mark the
executabl
ug 998 remains unfixed I hope it will at least be possible to make
a fresh install from an ISO image, using only what is included in the image.
Otherwise I don't see how Fedora could be installed securely. Upgrading
securely is still possible with Yum, but installation requires Anaconda as f
ew Fedora
release.
Björn Persson
signature.asc
Description: This is a digitally signed message part.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
c/).
If that's not enough to justify a separate package, but it's undesirable to
include these files even on a minimal server, then perhaps they could be added
to some X package that all graphical programs depend on anyway? Just a
thought.
Björn Persson
signature.asc
Description: This is a
o build then yes: there is no choice but to remove it.
Or if it has a security bug that nobody is trying to fix. And how will the
project become aware of newly discovered security bugs in orphan packages?
Björn Persson
signature.asc
Description: This is a digitally signed message part.
--
d
> I'll try to get a macros.gnat-srpm into redhat-rpm- config.
I have filed this request:
https://bugzilla.redhat.com/show_bug.cgi?id=772012
Björn Persson
signature.asc
Description: This is a digitally signed message part.
--
devel mailing list
devel@lists.fedoraproject.o
501 - 600 of 698 matches
Mail list logo
