Fwd: bridging for system-config-network
by Dragos Tatulea
Hi,
It seems that there is little support for bridging in
system-config-network and maybe even NetworkManager. I'd like to help adding
them. I don't know if this is the right place to ask but are there any
ongoing plans for this? Do you find it useful? Maybe it has beed done before
and I missed it.
I use bridging a lot for virtualisation and every time I want to start
using virtual machines some script invocation is needed. It would be nicer
to have it integrated and make NetworkManager cope nicely with this
situation. What do you think?
--Dragos
15 years, 5 months
help required regarding Bugzilla
by Rakesh Pandit
I was writing a script for generating weekly report from bugzilla
using python-bugzilla. Everything seems to work for old bugs but for
new bugs I get "Bug <no> does not exist. Most probably the there has
been an upgrade in bugzilla and I am not using correct url to connect.
Suggestions or help ?
Here is an example python session. 469811 is latest bug and 445027 is
an old bug.
>>> from bugzilla import Bugzilla
>>> bZilla = Bugzilla(url='https://partner-bugzilla.redhat.com/xmlrpc.cgi', username='<bugzilla_username>', password='<bugzilla_password>')
>>> history_bug1 = bugzilla._proxy.Bug.get_history({'ids':[469811]})
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
NameError: name 'bugzilla' is not defined
>>> history_bug1 = bZilla._proxy.Bug.get_history({'ids':[469811]})
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/usr/lib/python2.5/xmlrpclib.py", line 1150, in __call__
return self.__send(self.__name, args)
File "/usr/lib/python2.5/xmlrpclib.py", line 1440, in __request
verbose=self.__verbose
File "/usr/lib/python2.5/site-packages/bugzilla.py", line 713, in request
return self._parse_response(h.getfile(), sock)
File "/usr/lib/python2.5/xmlrpclib.py", line 1343, in _parse_response
return u.close()
File "/usr/lib/python2.5/xmlrpclib.py", line 790, in close
raise Fault(**self._stack[0])
xmlrpclib.Fault: <Fault 101: 'Bug #469811 does not exist.'>
>>>
>>>
>>> history_bug1 = bZilla._proxy.Bug.get_history({'ids':[445027]})
>>>
Thanks,
--
rakesh
15 years, 5 months
rawhide report: 20081109 changes
by Fedora compose checker
Compose started at Sun Nov 9 06:01:09 UTC 2008
Summary:
Added Packages: 0
Removed Packages: 0
Modified Packages: 0
Broken deps for ppc64
----------------------------------------------------------
livecd-tools-019-1.fc10.ppc64 requires yaboot
15 years, 5 months
Rubygems >= 1.3.0 for Merb
by Jesse Hutton
Merb 1.0 was just released yesterday and it requires Rubygems >= 3.0.
I have very little experience messing with spec files, but I tried modifying
rubygems-1.2.0-2.fc10.src.rpm to build the 1.3.1 tgz. I adapted the noarch
patch to rubygems-1.3.1, but ran into some difficulty building the rpm. The
patch applied fine, but the install files seemed to be in different
directories than what was expected in the spec file (the gem binary was in
/bin and ubygems.rb, rubygems.rb, rubygems, and rubyconfig also were in
paths without a '/usr' prefix). After adjusting rubygems.spec to find the
files in the right directories, it built and installed. But, perhaps
unsurprisingly, stuff was in the wrong directory, eg gem was in /bin, etc.
I am running Rawhide (up to date as of today, 11/8) on x86_64, so the noarch
patch does affect where gems end up on my system. Does anyone know how to
build rubygems-1.3.1 correctly into an rpm? Or will 1.3.1 be making it's way
into F10 in the near future?
Jesse
15 years, 5 months
CVS access for first-time packager?
by Chris Adams
I submitted a package, got it reviewed, got sponsored, and submitted the
CVS request. I got mail back that CVS was done, but I can't seem to log
in:
kosh:72:~/cvs$ fedora-cvs ufiformat
Checking out ufiformat from fedora cvs:
Error: Permission denied (publickey).
cvs [checkout aborted]: end of file from server (consult above messages if any)
I double-checked my SSH key in the account system, so I don't think that
is the problem.
This all went through right before the CVS outage Thursday night - could
something have fallen through the cracks with respect to setting up my
account? Or did I miss a step somewhere?
--
Chris Adams <cmadams(a)hiwaay.net>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.
15 years, 6 months
Concerns about 'provenpackager' and why I didn't mass ACL open
by Michael DeHaan
Jesse Keating mentioned I should probably start a thread about why I
didn't include a few packages of mine in the mass-ACL opening with the
idea of starting a discussion about why some packages should or
shouldn't be included. I generally think in most cases people will do
the right thing with such access, but I choose to err on the side of
paranoid security when it comes to systems management software.
I'll explain -- For starters, I agree that it's important for people to
be able to fix packaging problems when needed (when the project owner is
not around especially), though my concern with the provenpackager system
is I am not sure of the levels of controls in place for what allows
someone to become a provenpackager -- or what would happen if a
provenpackager's machine+passwords get comprimised. With the number
of people being able to access a package being reasonably low, the risk
is low, but as we increase the number of people with commit access to
/anything/ so the risk also increases.
As I understand it, in general, provenpackager status requires packaging
a certain number of packages (N). In my opinion, this is insufficient
and potentially dangerous and package access should be given under an
"as needed" basis. This is for the same reason commit access to
repositories needs to be vetted (do any of us allow /everyone/ to
commit?) -- though in this case it's more important -- while git allows
backing off on a version, deleting history, and other things, this
system seems to allow for potentially releasing bits -- which is much
more powerful. It seems to allow deployed code to be changed without
the descretion of the people running the project. The risk is
unlikely but possible.
There are two events when it is dangerous -- (A) provenpackager decides
to correct what he thinks is an rpmlint error and thus unintentially
breaks the security of the packaged application, (B) credentials of
provenpackager are compromised allowing $evil to replace the contents of
a said package. In either case, the change could either be making a
new release of an application (which contains an exploit and/or
unwitting bug), or updating the specfile in a way that breaks file
permissions in a way that may not be immediately obvious (whether
intentional or not).
Now for some things, like desktop libraries, that could be used to
install a botnet type application -- through you still have to
comprimise N machines. What if you had a tool that allowed you to
comprimise an entire organization? That's something I want to make
sure never happens. Our security track record does not only stem from
things like SELinux, Unix permissions, and the like -- it also stems
from a culture of vigilance.
Now the two packages I've left off from the mass ACL opening now are
cobbler, koan, func, and certmaster.
The reason being for this is that these, if comprised, are tools that
/do/ allow reprogramming of an entire datacenter in very easy steps.
Cobbler could reinstall an entire set of managed machines in 1
command. Func should be more obvious. We pay very close attention to
these programs and while we are very accepting of any contributions and
ideas, we /do/ watch the commits very carefully. I know there are many
programs with similar capability that /have/ been opened up, but perhaps
because we didn't talk about consequences.
While it's true that any comprimised package would be a problem,
something as simple as making an unintended change to package
permissions (without first discussing it on the project lists), could
expose not the one system with packages installed but the entire set of
/managed/ systems.
I am not really comfortable with opening that up.
So, anyway, that's my logic ... if anyone can persuade me that releasing
new code is /not/ possible through the provenpackager system, I think I
could be persuaded to flip things, but right now, I can't see an
advantage in doing so.
(If a change is needed, people can still bring up the change on the
project lists and it can be made)
--Michael
15 years, 6 months
rawhide report: 20081108 changes
by Fedora compose checker
Compose started at Sat Nov 8 06:01:34 UTC 2008
Removed package gstreamer-plugins-pulse
Updated Packages:
anaconda-11.4.1.56-1
--------------------
* Thu Nov 6 17:00:00 2008 David Cantrell <dcantrell(a)redhat.com> - 11.4.1.56-1
- Don't have the key icon take up so much space on the LUKS dialog
(#470338). (clumens)
- Avoid getting linux-base in the kernel list (katzj)
- Deselect groups when we reset things also (#469854) (katzj)
- make iscsi login code wait for udev to create the devices (#466661,
- Set the correct path when using the directory chooser. (clumens)
- We always need a wait window, not just when the repo has a name. (clumens)
- Set initial state of IP configuration fields in text mode (#469933)
(dcantrell)
- Prevent traceback when there are no network devices (#469339) (dcantrell)
- Indentation fix. (pjones)
- Let users edit net settings on network failure in stage 1 (#465887)
(dcantrell)
- Move startNewt later to avoid printing extra messages on the screen
(#469687). (clumens)
control-center-2.24.0.1-9.fc10
------------------------------
* Thu Nov 6 17:00:00 2008 Matthias Clasen <mclasen(a)redhat.com> - 2.24.0.1-9
- Remove a nonworking help button (#470375)
desktop-backgrounds-9.0.0-5
---------------------------
* Tue Nov 4 17:00:00 2008 Ray Strode <rstrode(a)redhat.com> 9.0.0-5
- Fix compat links after solar-backgrounds restructuring
(bug 469789)
e2fsprogs-1.41.3-2.fc10
-----------------------
* Fri Nov 7 17:00:00 2008 Eric Sandeen <sandeen(a)redhat.com> 1.41.3-2
- Bump to revision 2, f10 was behind f9, oops.
gdm-2.24.0-12.fc10
------------------
* Fri Nov 7 17:00:00 2008 Matthias Clasen <mclasen(a)redhat.com> - 1:2.24.0-12
- Make logout auditing work (#470269)
gnome-desktop-2.24.1-5.fc10
---------------------------
* Thu Nov 6 17:00:00 2008 Matthias Clasen <mclasen(a)redhat.com> - 2.24.1-5
- Require gnome-python2-gnome (#469938)
qt-4.4.3-2.fc10
---------------
* Thu Nov 6 17:00:00 2008 Than Ngo <than(a)redhat.com> 4.4.3-2
- bz#468814, immodule selection behavior is unpredictable without QT_IM_MODULE,
patch from Peng Wu
- backport fix from 4.5
Summary:
Added Packages: 0
Removed Packages: 1
Modified Packages: 7
Broken deps for ppc64
----------------------------------------------------------
livecd-tools-019-1.fc10.ppc64 requires yaboot
15 years, 6 months
Building for rawhide
by Paul F. Johnson
Hi,
When I try to build for rawhide on koji, all I get is the dist-f10 is
locked error. What should I be using for building in rawhide?
TTFN
Paul
--
Sie können mich aufreizen und wirklich heiß machen!
15 years, 6 months
Mass ACL open complete
by Casey Dahlin
The mass ACL open has at last been completed. If you did not opt out of
this change in pkgdb, your package is now open to all of the
uber^H^Hprovenpackager group. The checkbox to opt in or out may still be
present, but is no longer useful and should go away very shortly.
--CJD
_______________________________________________
Fedora-devel-announce mailing list
Fedora-devel-announce(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-announce
15 years, 6 months