devel November 2008

devel@lists.fedoraproject.org

288 participants
293 discussions

upgrading RH 9 system->Fedora with iso files and apt only
by Didier Casse 17 Jan '22

17 Jan '22

I have the yarrow's iso files on my HD in a RH9 system. Let's say I want to upgrade selected packages using an "apt-get install" pointing to my iso-mounted files, how do I do it? i.e I mount the iso into some /mnt/yarrow1, /mnt/yarrow 2 etc.. Then what is the complete procedure to make my apt look into my own HD to upgrade packages. Can anybody redirect me to the correct resource or some literature hanging on the web? Thanks. Assume also that I do not wish to burn CDs! I do not want to use apt-cdrom. Thanks. With kind regards, Didier. --- PhD student Singapore Synchrotron Light Source (SSLS) 5 Research Link, Singapore 117603 Email: slsbdfc at nus dot edu dot sg \or\ didierbe at sps dot nus dot edu dot sg Website: http://ssls.nus.edu.sg

6 9

kernel/accounting question ...
by William W. Austin 16 Dec '09

16 Dec '09

(I know that this question might be more reasonable on a kernel list, but a while back I posted the question twice and got no answers.) The acct struct is defined in /usr/include/sys/acct.h includes both ac_io and ac_rw for bytes transferred and blocks read or written, respectively. Fair and good - works (on paper) similarly to unix, solaris, hp-ux, etc. However, in the kernel code [kernel/acct.c], ac_io (char) and ac_rw (blocks) are always set to 0 by these two lines: ac.ac_io = encode_comp_t(0 /* current->io_usage */); ac.ac_rw = encode_comp_t(ac.ac_io / 1024); For most purposes, this probably wouldn't be an issue, but I also do extensive performance analysis on several platforms and have written a fairly compresive accounting package (as a wraparound for psacct or as a standalone) including both an improved acctcom and a built-in reporter for it. Does anyone know wby the kernel zero's out the bytes transferred data? (Overhead comes to mind.) Not that it makes a huge differnce for my purposes (I had to write some wraparound code to make a "best-guestimate" about the data I'm missing), but curiosity is bugging me now. When I compile my program on other OS's I get useful data for char and block i/o and I'd like to find out whether there is something obvious that I'm just totally missing here...). Thanks -- william w. austin waustin(a)speakeasy.net "life is just another phase i'm going through. this time, anyway ..."

4 3

acctcom for linux
by William W. Austin 16 Dec '09

16 Dec '09

I recently made several updates to a Linux version of of acctcom (actually another accounting add-on package) which I've been using for several years, and one of the people testing it asked a question which I cannot answer. I'm hoping that someone on this list can give me some info. I have previously (over a year ago) asked on both this and a couple of kernel lists (several times there) about this issue, but nobody has ever answered. So if you have any info about this, I'd really appreciate it. As in many (all?) previous Linux kernels, the struct acct (defined in /usr/include/sys/acct.h) has members ac_io and ac_rw which are presumably counts of characters transferred and blocks read/written respectively. However, in the kernel code, the ac_io is set to 0 and the ac_rw gets set to (ac_io/512) or some such - it is set to 0 as well (and thus these are always reported as 0 in process accounting records. not good if you're trying to measure them...). Does anybody know why this is done that way? A long time ago (IIRC late 2.2 and an early 2.4 kernel) I looked into "fixing" this in the kernel code but was not successful (I finally produced a bootable kernel, but it was unstable. Then I changed jobs, got swamped at work, and eventually gave up). As I said above, I have previously asked about this issue without success, and I have essentially given up changing or "fixing" it. But if anyone knows __WHY__ it is this way (I'm hypothesizing that it's just too much work for too little added value), I'd really appreciate knowing the reason. Curiosity and the cat and all that ... Thanks - Bill -- william w. austin waustin(a)speakeasy.net "life is just another phase i'm going through. this time, anyway ..."

3 2

Packages looking for new owners
by Trond Danielsen 07 Dec '09

07 Dec '09

Hi everyone, it is becoming clear to me that I can no longer provide the collection of packages I maintain the love and care that they deserve. If only there were more hours in a day, but the current situation does no leave much room for volunteer work on free software :-(. Hopefully I will find time in the future to return to Fedora related work The list if packages I maintain is available here: https://admin.fedoraproject.org/pkgdb/users/packages/trondd?acls=owner I don't mind keeping libopenraw, avrdude and uisp unless anyone _really_ want to maintain these packages. Best regards, -- Trond Danielsen

8 12

ctrlproxy-3.0.6
by Bernie Innocenti 09 Jun '09

09 Jun '09

Ciao, I updated ctrlproxy to 3.0.6, and the resulting packages are here: http://www.codewiz.org/pub/fedora/pkgs/ Patch follows. Can I commit it to CVS? diff -u -p -r1.15 ctrlproxy.spec --- ctrlproxy.spec 19 Feb 2008 07:31:45 -0000 1.15 +++ ctrlproxy.spec 25 May 2008 14:25:14 -0000 @@ -1,12 +1,18 @@ +%define ctrlproxy_homedir %{_var}/lib/ctrlproxy +%define ctrlproxy_logdir %{_var}/log/irc +%define ctrlproxy_service ctrlproxy +%define ctrlproxy_user ctrlproxy + Summary: ctrlproxy Name: ctrlproxy -Version: 3.0.5 -Release: 2%{?dist} +Version: 3.0.6 +Release: 1%{?dist} License: GPLv2+ Group: Applications/Internet Source: http://jelmer.vernstok.nl/releases/ctrlproxy-%{version}.tar.gz Url: http://jelmer.vernstok.nl/ctrlproxy/ -Patch0: ctrlproxy-fix-ansi-build.patch +Source100: ctrlproxy.init +Source101: ctrlproxy.config BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n) BuildRequires: glib2-devel, popt, gnutls-devel @@ -31,7 +37,6 @@ ctrlproxy development headers %prep %setup -q -%patch0 -p1 %build %configure @@ -45,6 +50,23 @@ mkdir $RPM_BUILD_ROOT make DESTDIR=$RPM_BUILD_ROOT install make DESTDIR=$RPM_BUILD_ROOT -C doc install chmod 0644 ${RPM_BUILD_ROOT}%{_datadir}/ctrlproxy/motd +install -D -m 0755 %{SOURCE100} $RPM_BUILD_ROOT/%{_sysconfdir}/init.d/ctrlproxy +install -D -m 0640 %{SOURCE101} $RPM_BUILD_ROOT/%{ctrlproxy_homedir}/config +install -D -d -m 0750 $RPM_BUILD_ROOT/%{ctrlproxy_logdir} + + +%pre +/usr/sbin/useradd -s /sbin/nologin -M -r -d %{ctrlproxy_homedir} \ + -c "ctrlproxy IRC daemon" %{ctrlproxy_user} &>/dev/null || : + +%post +/sbin/chkconfig --add %{ctrlproxy_service} + +%preun +if [ $1 = 0 ]; then + /sbin/service %{ctrlproxy_service} stop > /dev/null 2>&1 || : + /sbin/chkconfig --del %{ctrlproxy_service} +fi %clean [ -d "$RPM_BUILD_ROOT" -a "$RPM_BUILD_ROOT" != "/" ] && rm -rf $RPM_BUILD_ROOT @@ -59,12 +81,24 @@ chmod 0644 ${RPM_BUILD_ROOT}%{_datadir}/ %dir %{_docdir}/ctrlproxy %{_docdir}/ctrlproxy/* +%{_sysconfdir}/init.d/ctrlproxy +%attr(0750, ctrlproxy, ctrlproxy) %dir %{ctrlproxy_logdir} +%attr(0750, ctrlproxy, ctrlproxy) %dir %{ctrlproxy_homedir} +%attr(0750, ctrlproxy, ctrlproxy) %config(noreplace) %{ctrlproxy_homedir}/config + + %files devel %defattr(-,root,root) %{_includedir}/ctrlproxy-3.0/* %{_libdir}/pkgconfig/ctrlproxy.pc %changelog +* Sun May 25 2008 Bernardo Innocenti <bernie(a)codewiz.org> 3.0.6-1 +- Update to latest upstream +- Drop ctrlproxy-fix-irssi-log.patch +- Add initscript +- Create a ctrlproxy user to run ctrlproxy as a daemon + * Tue Feb 19 2008 Fedora Release Engineering <rel-eng(a)fedoraproject.org> - 3.0.5-2 - Autorebuild for GCC 4.3 -- \___/ _| X | Bernie Innocenti - http://www.codewiz.org/ \|_O_| "It's an education project, not a laptop project!"

3 3

Maintainer Responsibility Policy
by Brian Pepple 03 Jun '09

03 Jun '09

Hi all, I'm looking for some feedback on what I've got so far for the Maintainer Responsibility Policy. http://fedoraproject.org/wiki/Extras/Schedule/MaintainerResponsibilityPolicy -- == Maintainer Responsibility Policy == === How long to maintain? === 13 months from initial release. === Belong to the appropriate low-traffic mailing list === * Package maintainers will receive important announcements through the moderated fedora-devel-announce mailing list. Maintainers will be automatically subscribed to this list. Everyone that is a primary maintainer of a package in Fedora is also strongly encouraged to subscribe to the fedora-devel list, though this is not mandatory. * http://www.redhat.com/mailman/listinfo/fedora-devel-announce * http://www.redhat.com/mailman/listinfo/fedora-devel-list === Manage security issues === * Package maintainer should handle security issues quickly, and if they need help they should contact the Security Response Team. * http://fedoraproject.org/wiki/Security/ResponseTeam === Deal with reported bugs in a timely manner ==== * 'Nuff said. === Maintain stability for users === * Package maintainers should limit updates within a single Fedora release to those which do not require special user action. Many users update automatically, and if their applications stop working from no action of their own then they will be upset. This goes doubly for services which may break overnight. === Track dependency issues in a timely manner === * In the development tree, and to a small degree in the release trees as well, updates to packages may cause other packages to have broken dependencies. Maintainers will be alerted when this happens, and should work to rebuild their packages with all due haste. Broken dependencies may leave end user systems in a state where no updates will be applied. In order to keep the distribution in a reasonable state, someone will step in and rebuild packages that have had dependency issues for some time, but package maintainers should not rely on these rebuilds. === Notify others of changes that may affect their packages === * Some packages are depended upon by others; in this case, changes to one package may cause issues for others. Maintainers should be aware of the effects that changes to their packages may have, and should alert to the fedora-devel-announce mailing list of updates which contain ABI or API changes which may cause dependency problems for other packages. The announcement should occur a week before the packages update, so all maintainers affected are notified. The announcement should include the following information: * Nature of the change. * Branches (devel, F9, etc.) which will be affected by the change. * Expected date of the change. * List of packages which are affected by the change. Generally, this is merely the list of packages which depend directly on the package which is being updated, and can be found with "repoquery --whatrequires package" where "package" is the package being updated. * If your package upgrade breaks other packages in Rawhide, you should try to help fix the packages affected. For example, when Python-2.5 was integrated into Rawhide, Jeremy Katz at least fixed the important packages and queued a rebuild for all the other packages affected. === Miscellaneous Items === * Maintainers need to maintain an upgrade path for their packages. * F(current-1) -> F(current) -> Rawhide * Packages should be pushed to the Rawhide branch first. If it builds and works fine for a few days, then it can be pushed to F(current). If there is a good reason to push it to F(current-1), it should be done after a few days of being in F(current). --- Thanks, /B -- Brian Pepple <bpepple(a)fedoraproject.org> http://fedoraproject.org/wiki/BrianPepple gpg --keyserver pgp.mit.edu --recv-keys 810CC15E BD5E 6F9E 8688 E668 8F5B CBDE 326A E936 810C C15E

13 21

preupgrade F9 -> rawhide?
by Camilo Mesias 19 Mar '09

19 Mar '09

Is preupgrade from F9 to rawhide supposed to work at the moment, and where can I report problems? I've tried to run it and got a few depsolving problems for packages from livna... but when it gets to the boot images stage there are problems: Traceback (most recent call last): File "/usr/share/preupgrade/preupgrade-gtk.py", line 198, in on_assistant_apply self._do_main() File "/usr/share/preupgrade/preupgrade-gtk.py", line 206, in _do_main self.main_preupgrade() File "/usr/share/preupgrade/preupgrade-gtk.py", line 349, in main_preupgrade self.pu.retrieve_treeinfo() File "/usr/lib/python2.5/site-packages/preupgrade/__init__.py", line 395, in retrieve_treeinfo self.instimage = cp.get('stage2', 'instimage') File "/usr/lib/python2.5/ConfigParser.py", line 520, in get raise NoOptionError(option, section) ConfigParser.NoOptionError: No option 'instimage' in section: 'stage2' Any ideas? -Cam

4 12

Fedora User Certificates
by Dennis Gilmore 09 Mar '09

09 Mar '09

Effective immediately we have replaced the CA that is in use for cvs.fedoraproject.org and koji.fedoraproject.org This effects uploading to lookaside cache and building packages. There are some manual steps that everyone needs to do to be able to use the systems again. they are login to https://admin.fedoraproject.org/accounts/ and click on the "Download a client-side certificate" link at the bottom of the home page. save the output to ~/.fedora.cert rm ~/.fedora-server-ca.cert ~/.fedora-upload-ca.cert fedora-packager-setup then open your browser got to Edit -> Preferences -> Advanced -> Encryption -> View Certificates -> Your Certificates Select your existing Certificate and remove it then import the new one from ~/fedora-browser-cert.p12 you will be able to log in to koji * Please note that you can only have one client side certificate at a time. when you download a new one your old one is revoked. Please also only click on the "Download a client-side certificate" link once as it makes multiple requests and revokes all the transient certs. the CRL is at https://admin.fedoraproject.org/ca/crl.pem Thanks for your understanding and patience. Dennis _______________________________________________ Fedora-devel-announce mailing list Fedora-devel-announce(a)redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-announce

20 39

Orphaning: MochiKit
by Konstantin Ryabitsev 11 Feb '09

11 Feb '09

Hi, all: I no longer use MochiKit, so I am not a good maintainer. There is a new release, which is quite different from the old one, so it's best if someone can thoroughly test it before updating packages. If you use MochiKit in your projects, please feel free to pick it up. Cheers, -- Konstantin Ryabitsev Montréal, Québec

5 8

F10 Live CD possible bug
by Nathanael D. Noblet 11 Feb '09

11 Feb '09

Hello, I downloaded the live cd of F10 beta. Booted and added the live_ram option to the boot params. After copying the image to RAM I get the following error on two machines, (Apple Mac Book, and Acer 3680). Done copying live image to RAM. eject: did not find a device /dev/root in /sys/block Bug in initramfs /init detected. Dropping to a shell. Good luck! sbin/real-init: line 7: plymouth: command not found I know I used that param for F9. Is it depreciated or is this a bug needing filling? -- Nathanael d. Noblet

6 9

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

devel November 2008