Delays in package processing
by Bryan O'Sullivan
I'm finding the manual package signing step that has to happen before a
package can go into testing to be a considerable drag.
There's a long lag between submitting a request and the event actually
occurring, and there's no real visibility into why a request is
languishing. For example, there are some packages in the F-8 pending
queue that have been there for six weeks. I usually end up going into
#fedora-devel and bugging people after four or five days, but I don't
actually like having to prod people who I assume are already busy doing
other worthy work.
The combination of delay and opacity makes my volunteer job as a
packager a lot less rewarding. I'd like to package more software,
rather than less, but as long as the delays and overhead of maintaining
just one or two packages are this high, that's a big barrier to me
working up any further enthusiasm.
I have a few meta-questions about this situation which might help to
defuse my discontent with the process. I can't imagine that I'm the
only one in this position, so maybe it will help others too.
Is the package signing step done by hand? That's been my understanding,
but maybe I'm missing something. It reminds me of Sigourney Weaver's
role in "Galaxy Quest": a seemingly needless insertion of people into
the process.
If so, why? Can we switch to an automated process?
If a long delay between submitting a request to bodhi and getting a
human to turn the crank is going to the norm, could we add some
functionality that lets us see why? Some graphs showing the rates of
request submission and clearance, and the amounts of time that packages
are spending in queues, might help people who aren't glued into the
faily process to understand what's going on.
Thanks!
<b
16 years, 4 months
Firefox 3 Beta On x86_64--Does it work?
by Janina Sajka
Does the x86 FF3 work for anyone? It doesn't for me--but then it never
did through the entire alpha cycle.
To get a working FF3 on my two gui boxes, I have to manually retrieve
i386 FF# and xul.
Janina
--
Janina Sajka, Phone: +1.202.595.7777; sip:janina@a11y.org
Partner, Capital Accessibility LLC http://CapitalAccessibility.Com
Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada
Learn more at http://ScreenlessPhone.Com
Chair, Open Accessibility janina(a)a11y.org
Linux Foundation http://a11y.org
16 years, 4 months
Scrollbars rendering bug in Firefox?
by Martin Sourada
Hi,
I am currently in the process of remaking scrollbars for nodoka theme
and I noticed strange issue when displayed in firefox. In F-8's firefox
the secondary steppers are not displayed even if set in gtkrc, and the
returned stepper ID is wrong - instead of stepper A it returns D and
instead of D it returns A. See the attachments for more info. In Firefox
3 mozilla's nightly build there are A and D steppers OK, but the
secondary ones are switched, so instead of B, C is rendered and
otherwise. See the attachments for more info.
In both firefox's the steppers are never disabled. See again attachments
for more info.
Is this a bug in firefox or somewhere else?
In the clearlooks-gtk.png screenshots it is how it looks in most gtk
applications, in the clearlooks-ephy.png sceenshots it is how it looks
in epiphany from F-8 and in the clearlooks-ff3.png screenshots it is how
it looks in firefox 3.
Thanks, Martin
16 years, 4 months
F8->Devel + SELinux unbootable.
by Gilboa Davara
Hello all,
I've create a VMWare guest with F8/x86_64 on it and immediately upgraded
it to -devel. (Minus some small gnome-panel multi-lib breakage)
However, once I reboot the machine (and init finished it course) I got
an "ld 'x' re-spawning too fast" and when I try to ssh into the machine
I get greeted by "/bin/bash: Permission denied".
If I disable SELinux things seem to work just fine.
Oh, I've relabeled the FS (fixfiles relabel, tried again
with .autorelabel) but it didn't solve the problem.
Any ideas?
- Gilboa
16 years, 4 months
x86_64/F8 -> rawhide breaks on missing (?) gnome-panel.i386 package.
by Gilboa Davara
--> Processing Dependency: libpanel-applet-2.so.0()(64bit) for package: gnome-panel
...
---> Package gnome-panel.x86_64 0:2.20.2-2.fc9 set to be updated
---> Package gnome-panel-libs.x86_64 0:2.20.2-2.fc9 set to be updated
...
gnome-panel x86_64 2.20.2-2.fc9 development 3.5 M
gnome-panel-libs x86_64 2.20.2-2.fc9 development 55 k
...
file /etc/gconf/schemas/pager.schemas from install of gnome-panel-2.20.2-2.fc9 conflicts with file from package gnome-panel-2.20.1-1.fc8
file /etc/gconf/schemas/panel-general.schemas from install of gnome-panel-2.20.2-2.fc9 conflicts with file from package gnome-panel-2.20.1-1.fc8
file /etc/gconf/schemas/panel-global.schemas from install of gnome-panel-2.20.2-2.fc9 conflicts with file from package gnome-panel-2.20.1-1.fc8
file /etc/gconf/schemas/panel-object.schemas from install of gnome-panel-2.20.2-2.fc9 conflicts with file from package gnome-panel-2.20.1-1.fc8
file /etc/gconf/schemas/panel-toplevel.schemas from install of gnome-panel-2.20.2-2.fc9 conflicts with file from package gnome-panel-2.20.1-1.fc8
file /etc/gconf/schemas/tasklist.schemas from install of gnome-panel-2.20.2-2.fc9 conflicts with file from package gnome-panel-2.20.1-1.fc8
file /etc/gconf/schemas/window-list.schemas from install of gnome-panel-2.20.2-2.fc9 conflicts with file from package gnome-panel-2.20.1-1.fc8
file /etc/gconf/schemas/workspace-switcher.schemas from install of gnome-panel-2.20.2-2.fc9 conflicts with file from package gnome-panel-2.20.1-1.fc8
file /usr/share/applications/gnome-panel.desktop from install of gnome-panel-2.20.2-2.fc9 conflicts with file from package gnome-panel-2.20.1-1.fc8
file /usr/share/locale/et/LC_MESSAGES/gnome-panel-2.0.mo from install of gnome-panel-2.20.2-2.fc9 conflicts with file from package gnome-panel-2.20.1-1.fc8
file /usr/share/locale/ga/LC_MESSAGES/gnome-panel-2.0.mo from install of gnome-panel-2.20.2-2.fc9 conflicts with file from package gnome-panel-2.20.1-1.fc8
file /usr/share/locale/he/LC_MESSAGES/gnome-panel-2.0.mo from install of gnome-panel-2.20.2-2.fc9 conflicts with file from package gnome-panel-2.20.1-1.fc8
file /usr/share/locale/pt_BR/LC_MESSAGES/gnome-panel-2.0.mo from install of gnome-panel-2.20.2-2.fc9 conflicts with file from package gnome-panel-2.20.1-1.fc8
file /usr/share/locale/sk/LC_MESSAGES/gnome-panel-2.0.mo from install of gnome-panel-2.20.2-2.fc9 conflicts with file from package gnome-panel-2.20.1-1.fc8
file /usr/share/locale/sl/LC_MESSAGES/gnome-panel-2.0.mo from install of gnome-panel-2.20.2-2.fc9 conflicts with file from package gnome-panel-2.20.1-1.fc8
- Gilboa
16 years, 4 months
where s my kernel
by subhodip biswas
hi !
i am currently using kernel 2.6.23.8-63.fc8.i686 , but i am unable to
find it in /usr/src/kernels.. though i have kernel-devel installed
....... what i have missed to solve the problem
--
Regards
Subhodip Biswas
GPG key : FAEA34AB
Server : pgp.mit.edu
http://subhodipbiswas.wordpress.com
http:/www.fedoraproject.org/wiki/SubhodipBiswas
16 years, 4 months
/usr/bin/xetex has executable stack
by Steve Grubb
Hi,
Running a test across the distribution and it looks like a new program has
popped up that needs an executable stack:
[root ~]# /usr/bin/eu-readelf -l /usr/bin/xetex | grep STACK
GNU_STACK 0x000000 0x0000000000000000 0x0000000000000000 0x000000
0x000000 RWE 0x8
Does this app really need its stack to be executable? This could be a security
risk.
-Steve
16 years, 4 months
License change for Tecnoballz
by Andrea Musuruane
Hi all,
tecnoballz 0.92 (I will submit soon an updated package) is now GPLv3+
(it was GPLv2+).
Bye,
Andrea.
16 years, 4 months
Yum broke in transaction, how to restore system?
by Linus Walleij
I had yum breaking in the middle of a transaction yesterday (kernel post
scriptlet failed) so now some packages were installed but no "clean up"
was done.
Is there some archaic way of resolving this and run just the cleanups
post-mortem? I never understood this quite, and yum manpage is not very
helpful to unexpected situations...
Actually this happening so seldom is an indication of how good yum
actually is, so me not knowing the answer already is a GoodThing(TM).
Linus
16 years, 4 months
kernel problem in todays rawhide update
by Richard Hally
While running yum update for todays rawhide update the following error
occured:
Updating : glib2-devel ####################### [34/75]
Updating : dvipng ####################### [35/75]
Installing: kernel ####################### [36/75]
/sbin/new-kernel-pkg: line 254: /sbin/depmod: Permission denied
nash received SIGSEGV! Backtrace (11):
/sbin/nash[0x805315a]
[0x110440]
/lib/libglib-2.0.so.0[0x2d91a3]
/usr/lib/libbdevid.so.6.0.24(bdevid_module_unload_all+0x31)[0x6cae37]
/usr/lib/libbdevid.so.6.0.24(bdevid_destroy+0x2d)[0x6ca57c]
/usr/lib/libnash.so.6.0.24[0x6a8198]
/usr/lib/libnash.so.6.0.24(nash_vitals_destroy_probes+0x3f)[0x6a8810]
/usr/lib/libnash.so.6.0.24(_nashFreeContext+0x1c)[0x698fd6]
/sbin/nash[0x80536f4]
/lib/libc.so.6(__libc_start_main+0xe0)[0x99d4a0]
/sbin/nash[0x804ae71]
-----------end-------------
And nothing further, not even a prompt.
After a ctrl-c, the following:
error: %post(kernel-2.6.24-0.118.rc5.git6.fc9.i686) scriptlet failed,
signal 2
[root@localhost ~]#
What up?
Richard
16 years, 4 months
