no repository available for repo extras-devel??

yum update for extras-devel:

[extras-development]
name=Fedora Extras - Development Tree
mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=extras-devel&arch=$basearch

and indeed:

http://mirrors.fedoraproject.org/mirrorlist?repo=extras-devel&arch=x86_64

gives:

# no repository available for repo extras-devel

yet

  http://mirrors.fedoraproject.org/

shows:

http://mirrors.fedoraproject.org/extras-devel-US-x86_64.txt

which contains a number of mirrors.

??

sean

--

-- 
fedora-devel-list mailing list

Re: Join the Devel Team

On 11/1/06, Jovan Spasojevic <support <at> fedora-club.de> wrote:
> Hi,
>
> i would be like to involved in the devel team too. i don't know if i had
> join the devel-group.
> what's the stepps?
>
>

There are a variety of tasks that need help here:
http://fedoraproject.org/wiki/HelpWanted

John

--

-- 
fedora-devel-list mailing list
fedora-devel-list <at> redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

rawhide report: 20061101 changes

Updated Packages:

curl-7.16.0-2.fc7
-----------------
* Tue Oct 31 2006 Jindrich Novy <jnovy <at> redhat.com> - 7.16.0-2
- fix BuildRoot
- add Requires: pkgconfig for curl-devel
- move LDFLAGS and LIBS to Libs.private in libcurl.pc.in (#213278)

dhcpv6-0.10-33.fc7
------------------
* Tue Oct 31 2006 David Cantrell <dcantrell <at> redhat.com> - 0.10-33
- spec file cleanup (remove NODEBUGINFO, useless code, etc)
- Patch rollup since a lot of the later patches overwrote previous patches
- Put typedef for dhcp_state_e before it's used in libdhcp_control.h (#212612)
- Include <sys/queue.h> rather than the old BSD queue.h in the source

eclipse-1:3.2.1-10.fc7
----------------------
* Tue Oct 31 2006 Ben Konrath <bkonrath <at> redhat.com> 3.2.1-10
- Add 3.2.1 splash screen.
- Sort the java source files before building (#209249).
- Remove Fedora ifdefs.
- Resolves: #209249.

* Tue Oct 31 2006 Ben Konrath <bkonrath <at> redhat.com> 3.2.1-9
- Re-enable building of the icu4j plugins.

fetchmail-6.3.5-1

vncserver in future dists

Hi all,

I'm going to port x11vnc
(http://www.karlrunge.com/x11vnc/) project as default vncserver in
future dists. Current vncserver has self xorg-server and this is
argument for x11vnc. When main xorg-x11-server package is patched,
patches must be ported to vnc now. vncserver might be only "layer" on
xorg-x11-server and have dependency for it. Maintaining of vnc could be really easy.. What do you think
about it?? Is this bad idea??

--

-- 
fedora-devel-list mailing list
fedora-devel-list <at> redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: vncserver in future dists

On Wed, Nov 01, 2006 at 01:51:50PM +0100, Adam Tkac wrote:

> Hi all,
> 
> I'm going to port x11vnc
> (http://www.karlrunge.com/x11vnc/) project as default vncserver in
> future dists. Current vncserver has self xorg-server and this is
> argument for x11vnc. When main xorg-x11-server package is patched,
> patches must be ported to vnc now. vncserver might be only "layer" on
> xorg-x11-server and have dependency for it. Maintaining of vnc could be really easy.. What do you think
> about it?? Is this bad idea??

>From what I can tell x11vnc requires a running X server which makes it
useless for headless servers. None of my users uses vnc in this setup
(or will want to). I thought that KDE (and Gnome I suspect) offer this
already anyway.

Kostas Georgiou 

--

-- 
fedora-devel-list mailing list
fedora-devel-list <at> redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: vncserver in future dists

On Wed, Nov 01, 2006 at 01:51:50PM +0100, Adam Tkac wrote:
> Hi all,
> 
> I'm going to port x11vnc
> (http://www.karlrunge.com/x11vnc/) project as default vncserver in
> future dists. Current vncserver has self xorg-server and this is
> argument for x11vnc. When main xorg-x11-server package is patched,
> patches must be ported to vnc now. vncserver might be only "layer" on
> xorg-x11-server and have dependency for it. Maintaining of vnc could be really easy.. What do you think
> about it?? Is this bad idea??

I think that it is a good idea, however it seems to be a rather different
software that the current vnc-server. And to have the client you have to
build the vnc-server since they come from the same source. So it is not a 
replacement for the vnc server package, but rather a usefull complementary
package (if I'm not wrong it replaces more or less x0vncserver from the
vncserver package).

Now you may use x11vnc for the distro specific bits, like in anaconda
(but I don't know enough to comment that), or the 
/etc/rc.d/init.d/vncserver.

Anyway you could allready submit x11vnc to extras, there are packages in 
rpmforge, you may want to coordinate with them.

--
Pat

--

-- 
fedora-devel-list mailing list

Re: vncserver in future dists

Adam Tkac schrieb:
> I'm going to port x11vnc
> (http://www.karlrunge.com/x11vnc/) project as default vncserver in
> future dists. Current vncserver has self xorg-server and this is
> argument for x11vnc. When main xorg-x11-server package is patched,
> patches must be ported to vnc now. vncserver might be only "layer" on
> xorg-x11-server and have dependency for it. Maintaining of vnc could be really easy.. What do you think
> about it?? Is this bad idea??

Does it require special support in the X drivers? It might be a bit
problematic to use with proprietary drivers if the answer to that
question is "yes" (*1)

Cu
thl

(*1) -- I remember I once used the stuff documented at
http://www.realvnc.com/products/free/4.1/x0.html for testing purposes on
Fedora and noticed that it did not work together with the proprietary
fglrx drivers from ati. :-/ Proprietary drivers really suck...

--

-- 
fedora-devel-list mailing list
fedora-devel-list <at> redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: vncserver in future dists

Kostas Georgiou wrote:
> On Wed, Nov 01, 2006 at 01:51:50PM +0100, Adam Tkac wrote:
> 
>> Hi all,
>>
>> I'm going to port x11vnc
>> (http://www.karlrunge.com/x11vnc/) project as default vncserver in
>> future dists. Current vncserver has self xorg-server and this is
>> argument for x11vnc. When main xorg-x11-server package is patched,
>> patches must be ported to vnc now. vncserver might be only "layer" on
>> xorg-x11-server and have dependency for it. Maintaining of vnc could be really easy.. What do you think
>> about it?? Is this bad idea??
> 
>>From what I can tell x11vnc requires a running X server which makes it
> useless for headless servers. None of my users uses vnc in this setup
> (or will want to). I thought that KDE (and Gnome I suspect) offer this
> already anyway.

The Xorg server is perfectly capable of running headless, just configure 
it to use the dummy driver.

- ajax

--

-- 
fedora-devel-list mailing list
fedora-devel-list <at> redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: vncserver in future dists

On Wed, 2006-11-01 at 10:25 -0500, Adam Jackson wrote:
> The Xorg server is perfectly capable of running headless, just configure 
> it to use the dummy driver.

I think the point is that VNC users are used to having a single 'Xvnc'
binary they can run, which is a bit like Xvfb but you can connect a VNC
viewer to it.

As far as I can tell, this isn't trivial with x11vnc (but maybe I'm
reading the FAQ incorrectly).

Tim.
*/

--

-- 
fedora-devel-list mailing list
fedora-devel-list <at> redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

Re: vncserver in future dists

Tim Waugh wrote:
> On Wed, 2006-11-01 at 10:25 -0500, Adam Jackson wrote:
>> The Xorg server is perfectly capable of running headless, just configure 
>> it to use the dummy driver.
> 
> I think the point is that VNC users are used to having a single 'Xvnc'
> binary they can run, which is a bit like Xvfb but you can connect a VNC
> viewer to it.
> 
> As far as I can tell, this isn't trivial with x11vnc (but maybe I'm
> reading the FAQ incorrectly).

Nothing a small shell script couldn't fix though.  Something like:

# cat > /usr/bin/Xvnc <<EOF
#!/bin/sh
DISPLAY="$1"
shift
/usr/bin/Xorg "$1" -config /etc/X11/xvnc.conf -ac -nolisten tcp "$ <at> " &
/usr/bin/x11vnc -display "$1" &
EOF

With the xvnc.conf file appropriately configured to use void and dummy 
drivers, and maybe some additional magic for X authority file generation 
and error checking.  I mean, yeah, X connection authentication is gross, 
but it's not some deep unsolveable voodoo.

- ajax

--

--