Starting Tuesday I will be away for 4 weeks, and hence won't have much
time dealing with packing stuff.
So if there is any fallout from the mass rebuild or any other urgent
bugs feel free to push/build tested changes.
I would like to make available to f17 and f16 a package I currently
own and maintain (currently only available for f18, EL5 and EL6); What
would be right procedure?
// Before all else, be armed!
what should I do with the spec file of a package (ftp) with no upstream and no upstream source?
I mean the URL and Source0 lines. Should I just let them there, put a note in a comment or
just remove them?
I haven't found anything about such case in the guidelines.
Software Engineer, BaseOS team Brno, Red Hat
First I had a problem posting to the list, but that was my fault sorry,
forgot to confirm the subscription :)
I am one of the two maintainers of GNOME:Ayatana. Xiao-Lonng Chen did most
of Fedora spec files writing, but recently I switched to Fedora too.
Chen is now on vacation for a few days. Unity could work basically without
too much patches but with limited functionality.
utouch- packages don't need any vendor patches
nux doesn't need any vendor patches
indicator's don't need vendor specific patches
With compiz 0.9.8, Ubuntu has restructured the Compiz packages a bit:
Everything is now part of the compiz package:
- compiz-plugins (obsoleted compiz-plugins-main)
- compiz-plugins-extra (obsoleted compiz-plugins-extra)
so we would need here only one packacke (maybe compiz-unity/ubuntu/ayatan)
we use gcc46 now because unity and nux still need to be build with it.
gcc47 fails for that
At the moment for unity to build/run we need patched:
libXfixes (requires a patch coming from debian)
xorg-x11-proto (see above patch)
xorg-x11-server (else autohide feature from unity launcher does not work)
gtk2,3 for the menu export
gnome-disk-utility - must build libdu which was removed from upstream in 3.2
The other packages enhance functinoality like
gnome-control-center (e.g in appearance be able to change theme)
pulseaudio needs ubuntu patches, but pulse 2.0 will obsolete them)
gnome-session for a gnome-session file (in theory we could get that in the
bluetooth and NetworkManager to show these indicators in unity
What I would propose is to get 1st all indicator and the requires of them
into Fedora since they only require few patches
indicator-appmenu needs pachted gtk2,3
indicator-time needs patched gnome-control-center
but we could start finding a way to get the gtk2,3 with patches and after
that dbusmenu etc.
Has there been any trouble booting the 3.4.4-5 kernel?
I updated one of my F17 machines today and it brought in a new kernel, 3.4.4-5.
When I rebooted the box after all the updates completed it refused to boot.
It just hangs with a non-blinking cursor in the upper left hand corner of a totally blank screen.
The drive light will continue to blink for about 30 seconds and then no further drive activity.
Have to power cycle the box to recover and boot into the previous kernel.
If prelink chews on a binary that's currently running, its /proc/self/exe
essentially goes away. Which can be undesirable, for a persistent daemon
It took me a while to figure out why my daemon kept breaking all the time,
when it couldn't stat its /proc/self/exe any more.
I suppose I could blacklist it, in prelink.conf. But that seems wrong.
prelink should either avoid touching binaries that are currently loaded, or
there should be a way prelink can coordinate its activity with binaries.