Orphaned python-alsa
Not required by any package other than alsa-tools. Cheers Robin -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
rawhide report: 20110515 changes
Compose started at Sun May 15 08:15:02 UTC 2011 Broken deps for x86_64 -- acheck-0.5.1-4.fc15.noarch requires perl(Text::Aspell) almanah-0.7.3-10.fc15.x86_64 requires libcamel-1.2.so.23()(64bit) 1:anerley-0.2.14-5.fc15.i686 requires libcamel-1.2.so.23 1:anerley-0.2.14-5.fc15.x86_64 requires libcamel-1.2.so.23()(64bit) beldi-0.9.25-3.fc15.x86_64 requires libhal-storage.so.1()(64bit) beldi-0.9.25-3.fc15.x86_64 requires libhal.so.1()(64bit) beldi-0.9.25-3.fc15.x86_64 requires hal callweaver-javascript-1.2.1-8.fc16.x86_64 requires libjs.so.1()(64bit) camcardsync-0.1.1-4.fc15.x86_64 requires libhal.so.1()(64bit) cegui-ogre-renderer-0.7.5-6.fc16.x86_64 requires libOgreMain.so.1.7.2()(64bit) chess-1.0-36.fc16.x86_64 requires libOgreMain.so.1.7.2()(64bit) couchdb-1.0.2-2.fc16.x86_64 requires libjs.so.1()(64bit) cyphesis-0.5.24-3.fc15.x86_64 requires libskstream-0.3.so.4()(64bit) db4o-7.4-2.fc13.x86_64 requires mono(Mono.GetOptions) = 0:2.0.0.0 deskbar-applet-2.32.0-4.fc15.x86_64 requires libcamel-1.2.so.23()(64bit) dh-make-0.55-3.fc15.noarch requires debhelper ekiga-3.3.0-8.fc16.x86_64 requires libcamel-1.2.so.23()(64bit) ember-0.6.0-6.fc16.x86_64 requires libOgreMain.so.1.7.2()(64bit) ember-0.6.0-6.fc16.x86_64 requires libskstream-0.3.so.4()(64bit) evolution-3.1.1-2.fc16.i686 requires libevolution-mail-settings.so.0 evolution-3.1.1-2.fc16.x86_64 requires libevolution-mail-settings.so.0()(64bit) evolution-couchdb-0.5.3-1.fc16.x86_64 requires libcamel-provider-1.2.so.23()(64bit) evolution-couchdb-0.5.3-1.fc16.x86_64 requires libcamel-1.2.so.23()(64bit) evolution-rss-0.2.90-19.20110307git.fc16.x86_64 requires libcamel-provider-1.2.so.23()(64bit) evolution-rss-0.2.90-19.20110307git.fc16.x86_64 requires libcamel-1.2.so.23()(64bit) evolution-sharp-0.21.1-12.fc15.x86_64 requires libcamel-1.2.so.23()(64bit) exaile-0.3.2.1-1.fc16.noarch requires hal fawkes-guis-0.4.2-4.fc16.i686 requires libgraph.so.4 fawkes-guis-0.4.2-4.fc16.i686 requires libcdt.so.4 fawkes-guis-0.4.2-4.fc16.i686 requires libgvc.so.5 fawkes-guis-0.4.2-4.fc16.x86_64 requires libgraph.so.4()(64bit) fawkes-guis-0.4.2-4.fc16.x86_64 requires libcdt.so.4()(64bit) fawkes-guis-0.4.2-4.fc16.x86_64 requires libgvc.so.5()(64bit) ffgtk-plugin-evolution-0.7.8-4.fc16.x86_64 requires libcamel-1.2.so.23()(64bit) file-browser-applet-0.6.6-1.fc15.x86_64 requires libpanel-applet-2.so.0()(64bit) gedit-valencia-0.3.0-4.fc14.x86_64 requires libvala-0.10.so.0()(64bit) giggle-0.5-4.fc15.i686 requires libcamel-1.2.so.23 giggle-0.5-4.fc15.x86_64 requires libcamel-1.2.so.23()(64bit) glabels-2.2.8-4.fc15.x86_64 requires libcamel-1.2.so.23()(64bit) glunarclock-0.34.1-1.fc14.x86_64 requires libpanel-applet-2.so.0()(64bit) gnome-applet-bubblemon-2.0.15-1.fc13.x86_64 requires libpanel-applet-2.so.0()(64bit) gnome-applet-cpufire-1.6-3.fc14.x86_64 requires libpanel-applet-2.so.0()(64bit) gnome-applet-globalmenu-0.7.9-1.fc15.x86_64 requires libpanel-applet-2.so.0()(64bit) gnome-applet-grandr-0.4.1-2.fc12.x86_64 requires libpanel-applet-2.so.0()(64bit) gnome-applet-music-2.5.1-5.fc15.x86_64 requires libpanel-applet-2.so.0()(64bit) gnome-applet-sensors-2.2.7-4.fc15.i686 requires libpanel-applet-2.so.0 gnome-applet-sensors-2.2.7-4.fc15.x86_64 requires libpanel-applet-2.so.0()(64bit) gnome-applet-sshmenu-3.18-3.fc15.noarch requires ruby(panelapplet2) gnome-applet-window-picker-0.5.8-2.fc14.x86_64 requires libpanel-applet-2.so.0()(64bit) gnome-device-manager-0.2-6.fc15.x86_64 requires libhal.so.1()(64bit) gnome-device-manager-devel-0.2-6.fc15.i686 requires hal-devel = 0:0.5.10 gnome-device-manager-devel-0.2-6.fc15.i686 requires pkgconfig(hal) gnome-device-manager-devel-0.2-6.fc15.x86_64 requires hal-devel = 0:0.5.10 gnome-device-manager-devel-0.2-6.fc15.x86_64 requires pkgconfig(hal) gnome-device-manager-libs-0.2-6.fc15.i686 requires libhal.so.1 gnome-device-manager-libs-0.2-6.fc15.i686 requires hal = 0:0.5.10 gnome-device-manager-libs-0.2-6.fc15.x86_64 requires libhal.so.1()(64bit) gnome-device-manager-libs-0.2-6.fc15.x86_64 requires hal = 0:0.5.10 gnome-launch-box-0.4-20.fc15.x86_64 requires libcamel-1.2.so.23()(64bit) gnome-netstatus-2.28.2-1.fc15.x86_64 requires libpanel-applet-2.so.0()(64bit) gnome-phone-manager-0.66-1.fc16.x86_64 requires libcamel-1.2.so.23()(64bit) gnome-phone-manager-telepathy-0.66-1.fc16.x86_64 requires libcamel-1.2.so.23()(64bit) gnome-pilot-conduits-2.32.1-2.fc15.x86_64 requires
Re: Systemd questions following 15B upgrade
On Fri, 13.05.11 23:57, Philip Prindeville (philipp_s...@redfish-solutions.com) wrote: I installed F15B, but now I'm seeing: May 13 23:01:01 mail /usr/sbin/crond[5243]: pam_systemd(crond:session): Moving new user session for root into control group /user/root/18. May 13 23:01:01 mail /USR/SBIN/CROND[5243]: pam_systemd(crond:session): Moving remaining processes of user session 18 of root into control group /user/root/master. every hour. How do I squelch this message? We can probably lower this log messages to DEBUG for the future. Also, now that we don't use upstart, what's the equivalent of: chkconfig service on You may continue to use that. It will work just fine. The native systemd replacement is his: systemctl enable name.service for turning services on? Is there a FAQ/Release Note for users to make sure the migration to F15 included all services being correctly configured under systemd? https://fedoraproject.org/wiki/SysVinit_to_Systemd_Cheatsheet Lennart -- Lennart Poettering - Red Hat, Inc. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: And logging issues following F15B upgrade
On Sat, 14.05.11 12:01, Philip A. Prindeville (philipp_s...@redfish-solutions.com) wrote: May 13 11:08:02 mail kernel: [ 133.097131] sendmail[2179]: p4DH6ui4002179: Milter delete (noop): header: X-Spam-Score May 13 11:08:02 mail kernel: [ 133.105238] sendmail[2179]: p4DH6ui4002179: Milter add: header: X-Scanned-By: MIMEDefang 2.72 on 192.168.1.3 May 13 11:08:02 mail kernel: [ 133.115242] lmtpunix[2176]: accepted connection May 13 11:08:02 mail kernel: [ 133.119932] lmtpunix[2176]: lmtp connection preauth'd as postman May 13 11:08:02 mail kernel: [ 133.884189] lmtpunix[2176]: skiplist: checkpointed /var/lib/imap/user/p/philipp.seen (387 records, 116172 bytes) in 0 seconds May 13 11:08:02 mail kernel: [ 133.895967] lmtpunix[2176]: seen_db: user philipp opened /var/lib/imap/user/p/philipp.seen May 13 11:08:02 mail kernel: [ 188.010336] master[1892]: process 2170 exited, status 0 May 13 11:08:02 mail kernel: [ 188.016042] master[2204]: about to exec /usr/lib/cyrus-imapd/lmtpd May 13 11:08:02 mail kernel: [ 188.022558] lmtpunix[2204]: executed so it looks like mail messages are being relogged as kernel messages What's going on? systemd provides logging from beginning of userspace on. As long as syslog isn't up this will go to kmsg. As soon as rsyslog is up the kernel log buffer will be fliushed to disk and all following messages go directly to disk with no involvement of kmsg. In F16 and later you'll be able to use dmesg -k to get the usual dmesg output but with all non-kernel messages removed. Note that dmesg never has been about kernel messages only. Low-level userspace system components logged to kmsg already. All we added is that during early boot /dev/log logging ends up in kmsg. Lennart -- Lennart Poettering - Red Hat, Inc. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Orphaning gbirthday and linbox
On Sat, 14 May 2011 21:14:20 -0600 Jerry James wrote: On Thu, May 12, 2011 at 6:46 AM, Thomas Spura toms...@fedoraproject.org wrote: * linbox: Required for SAGE [1], but FTBFS since a while and the new version now requires another package, not yet in fedora. This is hard to maintain, because of many multilib problems/hacks etc. (CC'ing givaro maintainer, so he doesn't need to wait for an upgrade for linbox.) What other package, not yet in Fedora, does the new version require? I've been collecting SAGE-related packages lately, so I might be willing to take this one, too. The latest version 1.2.0 is now complaining with: ERROR: Fflas-Ffpack not found! and I gave up, because linbox is quite hacky. Maybe it would be better to use the sage sourcepackage of linbox and not packaging it from the upstream webpage... Greetings, Thomas -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [Test-Announce] Fedora 15 Final Release Candidate 3 (RC3) Available Now!
I did an install from the RC3 live CD (on USB) and it went well. However F15 remains very unstable, I don't think I will be able to use it. The main problem is that it will lock up spontaneously (then heats up if left as if in a tight CPU consuming loop). Apart from that any kind of session ending - logout, reboot, and other things like suspend, hibernate, turning wireless on and off - things that use systemd maybe? - will lock up the machine in the same way. This machine was perfectly usable on F14 and never locked up. I have a bug: 697157 on the kernel which seems to be getting little or no attention; at the same time I don't have any idea how to diagnose this given that the logs contain no clues. It will be back to F14 or I might have to try Ubuntu again for this hardware if it doesn't improve. Sorry if the tone of this message is a bit negative. I would love to use F15 and will continue to test any updates as I find time. I'll be keen to work with any developers that are interested in debugging the issues. -Cam On Fri, May 13, 2011 at 9:33 PM, Andre Robatino robat...@fedoraproject.org wrote: As per the Fedora 15 schedule [1], Fedora 15 Final Release Candidate 3 (RC3) is now available for testing. Please see the following pages for download links and testing instructions. In general, official live images arrive a few hours after the install images: see the links below for updates. When they appear, the download directory should be the same as that for install images, except with the trailing /Fedora/ replaced by /Live/. Installation: https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test Desktop: https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test Ideally, all Alpha, Beta, and Final priority test cases for installation [2] and desktop [3] should pass in order to meet the Final Release Criteria [4]. Help is available on #fedora-qa on irc.freenode.net [5], or on the test list [6]. Create Final Release Candidate (RC): Install CD/DVD (installation media): https://fedorahosted.org/rel-eng/ticket/4697 Create Final Release Candidate (RC): Official Live Images: https://fedorahosted.org/rel-eng/ticket/4699 F15 Final Blocker tracker bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=617261 F15 Final Nice-To-Have tracker bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=657621 [1] http://rbergero.fedorapeople.org/schedules/f-15/f-15-quality-tasks.html [2] https://fedoraproject.org/wiki/QA:Installation_validation_testing [3] https://fedoraproject.org/wiki/QA:Desktop_validation_testing [4] https://fedoraproject.org/wiki/Fedora_15_Final_Release_Criteria [5] irc://irc.freenode.net/fedora-qa [6] https://admin.fedoraproject.org/mailman/listinfo/test ___ test-announce mailing list test-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/test-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [Test-Announce] Fedora 15 Final Release Candidate 3 (RC3) Available Now!
On 05/15/2011 06:59 PM, Camilo Mesias wrote: I did an install from the RC3 live CD (on USB) and it went well. However F15 remains very unstable, Very weird, I've been using F15 since around alpha full time and never have any stability problem. I suspect it should be a bug related to your specific configuration (hardware?) and worth exploring/troubleshooting. I had issues with Flash (gnome-shell freezing) but those stops once I removed it. Using GNASH now and it works about ok most of the time, though I wouldn't consider myself as someone browsing flash sites... (I watch youtube under HTML5, though it sometimes goes to gnash and seems to work as well most of the time too). I hope my message gives you hope your issues are fixable. Fred -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [Test-Announce] Fedora 15 Final Release Candidate 3 (RC3) Available Now!
Thanks, I agree it's a hardware thing although ION / Atom combination isn't that rare and also used to work fine under F14. I have an older, larger laptop with Radeon graphics that works OK with F15. Other machines in the house use F15 and Intel graphics without problems. That said I really don't want to have a miscellany of different OSs in the house and the machine that doesn't work is my main one! -Cam -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: systemd questions
On Thu, 12.05.11 15:28, Michal Hlavinka (mhlav...@redhat.com) wrote: Hi, Heya, I'm working with nut upstream to test sysv-systemd changes, but I found some problems and they've came up with a few questions too. 1) does systemd support alternative to service sthd configtest or other special actions? Additional SysV verbs continue to work with the systemd SysV compatibility. However, in the long run we'd like people to use service-specific tools for service-specific operations. 2) does systemd have support for conditions in service files? It seem it's not supported right now. Is there any plan for this? I am not entirely sure what you understand by condition, but if you do understand the same thing as we do, then we support a pretty flexible set of condition checks: ConditionPathExists= ConditionPathIsDirectory= ConditionDirectoryNotEmpty= ConditionKernelCommandLine= ConditionVirtualization= ConditionSecurity= The latter two are for checking whether we are run in a virtualized environment (kvm, vmware, ...), resp with a specific secureity framework enabled (selinux, ...). See systemd.unit(5) for details. 3) in which cases I should ommit [Install] section in service file? [Install] is used for systemctl enable and systemctl disable. If you have no such sections these commands will become NOPs. Which is desirable in two cases: a) you always expect the user to manually create .wants/ symlinks with ln -s or b) your package hard-enables the service file in question, because it is such a core component of the system that there is no point in ever disabling it. One example for such a service is udev, but of course most services do not qualify as this, and should hence include [Install]. 4) Is there any difference between a) A.service: After=B.service and b) B.service: Before=A.service or both a) and b) are required? a) implies b) and b) implies a). One of those lines is sufficient, specifying both doesn't hurt. It's probably a good idea to place the order line in the small service, relative to the big service, and leave out the other direction, to simplify things. We have service A and service B. Service B requires service A, but it can require service A from different host (depends on configuration). So we've added After=A in service B and also Before=B in service A, but it did not help. Expected result was B is started and if A is configured to start too, it should be started before B. Actual result is that B is started before A if both of them should start (when using systemctl start B.service A.service). As you already filed a bug about currently systemctl start A.service B.service starts those services in the order you specify them on the cmdline, in two separate transaction. We should probably fix this to start them in a single transaction. 5) in old initscripts, there was /etc/init.d/halt with section for ups shutdown. With that script gone, was that functionality ported to systemd somehow? Well, any such code is just inherently broken. It *cannot* work. A number of kernel subsystems hook into the shutdown code of the kernel. For example storage code syncs meta data to disk after the reboot() syscall is invoked. If you however turn off power before reaching reboot(), then this step is omitted which might trigger data loss. UPS code like that needs to sit in the kernel itself to properly work. Adding userspace kludges which invokes this from userspace is a recipe for desaster. The point of UPS is to prevent data loss after all, and if you turn off the power before the kernel dealt with reboot() you invite data loss. (And no, just adding random sleeps, is not a fix, it just delays the problem.) (That all said you may drop binaries into /lib/systemd/system-shutdown which are executed right before invoking reboot(). But if you package anything that drops binaries into that dir for UPS uses, then I will personally track you down and tell you mom how bad you are!) Lennart -- Lennart Poettering - Red Hat, Inc. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: systemd questions
On Thu, 12.05.11 17:04, Jóhann B. Guðmundsson (johan...@gmail.com) wrote: You can run ExecStartPre= before starting a service for syntax checking before starting the service like we do for .. ExecStartPre=/usr/sbin/radiusd -C ExecStartPre=/usr/sbin/named-checkconf /etc/named.conf ExecStartPre=/usr/sbin/cupsd -t Humm, I really wonder what the benefit of placing these lines here is. What does it buy you? A sane daemon should do a syntax check anyway when starting (and exit if it fails), so why do you do another one before? Unless there's a really good reason for it this just complicates things, makes things slower, and duplicates everything. Lennart -- Lennart Poettering - Red Hat, Inc. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: systemd questions
On 05/15/2011 01:59 PM, Lennart Poettering wrote: On Thu, 12.05.11 17:04, Jóhann B. Guðmundsson (johan...@gmail.com) wrote: You can run ExecStartPre= before starting a service for syntax checking before starting the service like we do for .. ExecStartPre=/usr/sbin/radiusd -C ExecStartPre=/usr/sbin/named-checkconf /etc/named.conf ExecStartPre=/usr/sbin/cupsd -t Humm, I really wonder what the benefit of placing these lines here is. What does it buy you? A sane daemon should do a syntax check anyway when starting (and exit if it fails), so why do you do another one before? Unless there's a really good reason for it this just complicates things, makes things slower, and duplicates everything. For example if you are doing autogenerated updates on config files you might want to test the config before restarting/reloading the daemon which is commonly done in enterprise environments running Freeradius and Bind atleast those environments I'm familiar with ( cups not so much )... Also the previous behaviour when starting a service used to throw out which config file and which line the syntac error occoured to the console however that's no longer the case see https://bugzilla.redhat.com/show_bug.cgi?id=684152. As I have mentioned to you previously systemd lacks certain administrative features ( yet ) like fine grained failour handling ( like ExecStartPreFail= etc. ) and more and it comes as a no surprice since you seem to have a limited sysadmin perspective/experience on things ( after all you are a developer not sysadmin ) as your blog post indicates which are targeted more at the above average end user running something @ home than real sysadmins in real enterprise environments from my pov. JBG -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: systemd questions
On Sun, 15.05.11 15:55, Jóhann B. Guðmundsson (johan...@gmail.com) wrote: On 05/15/2011 01:59 PM, Lennart Poettering wrote: On Thu, 12.05.11 17:04, Jóhann B. Guðmundsson (johan...@gmail.com) wrote: You can run ExecStartPre= before starting a service for syntax checking before starting the service like we do for .. ExecStartPre=/usr/sbin/radiusd -C ExecStartPre=/usr/sbin/named-checkconf /etc/named.conf ExecStartPre=/usr/sbin/cupsd -t Humm, I really wonder what the benefit of placing these lines here is. What does it buy you? A sane daemon should do a syntax check anyway when starting (and exit if it fails), so why do you do another one before? Unless there's a really good reason for it this just complicates things, makes things slower, and duplicates everything. For example if you are doing autogenerated updates on config files you might want to test the config before restarting/reloading the daemon which is commonly done in enterprise environments running Freeradius and Bind atleast those environments I'm familiar with ( cups not so much )... Well, but ExecStartPre= doesn't help you with this. As it is run only after the service is already stopped. It has been suggested that we add ExecRestartPre=, i.e. something we run before stopping a service for a restart. It has been on the TODO list for a while, but is currently not available. ExecStartPre= doesn't appear useful for this stuff at all to me. Also the previous behaviour when starting a service used to throw out which config file and which line the syntac error occoured to the console however that's no longer the case see https://bugzilla.redhat.com/show_bug.cgi?id=684152. In F16 it is our plan to make all service STDOUT/STDERR to go to syslog by default. As soon as we have that and also can relate syslog output to systemd services we can make this kind of output more accessible. As I have mentioned to you previously systemd lacks certain administrative features ( yet ) like fine grained failour handling ( like ExecStartPreFail= etc. ) and more and it comes as a no surprice since you seem to have a limited sysadmin perspective/experience on things ( after all you are a developer not sysadmin ) as your blog post indicates which are targeted more at the above average end user running something @ home than real sysadmins in real enterprise environments from my pov. Sorry, I still haven't found the time to reply to your long mail about this. It's not forgotten. ;-) From a quick browse through it I think this is mostly a misunderstanding however, and you can already do what you want to do with the current code. Lennart -- Lennart Poettering - Red Hat, Inc. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Access to some of Alexey Torkhov's packages
Alexey hasn't been doing a lot of Fedora related stuff recently. I was able to reach him indirectly a few months ago to get access to some of his packages that depend on ogre. But more recently I have been trying to get access to some of his other game related packages in advance of issues, so that I could work on them in a more timely fashion. However there was no response to my email messages noting the I requested access in the package database system. For a few other packages I was able to have another co-maintainer give me access but for the following packages Alexey is the only one that can approve access by the normal means: boswars-addons, btanks, gnubik and kcheckers. gnubik currently needs to be fixed in rawhide for the guile update and there is a new upstream version available. The others I wasn't in a special hurry to touch write now. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: systemd questions
On Sun, May 15, 2011 at 3:56 PM, Lennart Poettering mzerq...@0pointer.de wrote: 5) in old initscripts, there was /etc/init.d/halt with section for ups shutdown. With that script gone, was that functionality ported to systemd somehow? Well, any such code is just inherently broken. It *cannot* work. Such code has worked fine for more than ten years, and Fedora has shipped it for a long time as well. Did we ship code that could not ever have worked? snip The point of UPS is to prevent data loss after all, and if you turn off the power before the kernel dealt with reboot() you invite data loss. At that point, all non-root filesystems are unmounted; / has been remounted read-only, which means the kernel has synced all dirty data, and waited for the writeback to finish. So reboot() only needs to write very little to the disks, if anything at all. The UPS shutdown command doesn't turn off the power immediately, the UPS shuts down after a delay, usually 30 seconds. 30 seconds was plenty to shut down the system properly even 10 years ago, and AFAIK it is still plenty today. Mirek -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
[bucardo/f14] - new version 4.4.4
Summary of changes: 8ae56a4... - new version 4.4.4 (*) (*) This commit already existed in another branch; no separate mail sent -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
Re: systemd questions
On 05/15/2011 04:08 PM, Lennart Poettering wrote: Well, but ExecStartPre= doesn't help you with this. As it is run only after the service is already stopped. It has been suggested that we add ExecRestartPre=, i.e. something we run before stopping a service for a restart. It has been on the TODO list for a while, but is currently not available. ExecStartPre= doesn't appear useful for this stuff at all to me. Would not ExecStopPre= suffice for this ? JBG -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: systemd questions
On 05/15/2011 05:05 PM, Jóhann B. Guðmundsson wrote: On 05/15/2011 04:08 PM, Lennart Poettering wrote: Well, but ExecStartPre= doesn't help you with this. As it is run only after the service is already stopped. It has been suggested that we add ExecRestartPre=, i.e. something we run before stopping a service for a restart. It has been on the TODO list for a while, but is currently not available. ExecStartPre= doesn't appear useful for this stuff at all to me. Would not ExecStopPre= suffice for this ? As in having ExecStopPre= instead lof ExecRestartPre=? JBG -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: systemd questions
On Sun, 15.05.11 17:05, Jóhann B. Guðmundsson (johan...@gmail.com) wrote: On 05/15/2011 04:08 PM, Lennart Poettering wrote: Well, but ExecStartPre= doesn't help you with this. As it is run only after the service is already stopped. It has been suggested that we add ExecRestartPre=, i.e. something we run before stopping a service for a restart. It has been on the TODO list for a while, but is currently not available. ExecStartPre= doesn't appear useful for this stuff at all to me. Would not ExecStopPre= suffice for this ? No, ExecStopPre= cannot be used for making shutdown of a service conditional. Even if one of the pre lines fails we will go on with shutting down the service, however we will store the exit code and the service will be in failed state once fully shut down. Lennart -- Lennart Poettering - Red Hat, Inc. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: systemd questions
On Sun, May 15, 2011 at 6:57 PM, Lennart Poettering mzerq...@0pointer.de wrote: Well, adding 30s-sleep()s here and there and everywhere is a hack, not a clean fix. But if you have a lot of sync to disk, and/or a slow disk, then 30s might not be enough and you are fucked. I can't see where would that a lot of sync to disk come from: the filesystems are synced, RAID has been marked clean. What else needs to be written back? We always did it this way is not a fix for a problem. The race is real, and should be fixed properly. Sure, when/if somebody feels this is important enough to rewrite all of the UPS drivers. In the mean time, future Fedoras should work at least as well as F14 does. Mirek -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: And logging issues following F15B upgrade
On 5/15/11 4:33 AM, Lennart Poettering wrote: On Sat, 14.05.11 12:01, Philip A. Prindeville (philipp_s...@redfish-solutions.com) wrote: May 13 11:08:02 mail kernel: [ 133.097131] sendmail[2179]: p4DH6ui4002179: Milter delete (noop): header: X-Spam-Score May 13 11:08:02 mail kernel: [ 133.105238] sendmail[2179]: p4DH6ui4002179: Milter add: header: X-Scanned-By: MIMEDefang 2.72 on 192.168.1.3 May 13 11:08:02 mail kernel: [ 133.115242] lmtpunix[2176]: accepted connection May 13 11:08:02 mail kernel: [ 133.119932] lmtpunix[2176]: lmtp connection preauth'd as postman May 13 11:08:02 mail kernel: [ 133.884189] lmtpunix[2176]: skiplist: checkpointed /var/lib/imap/user/p/philipp.seen (387 records, 116172 bytes) in 0 seconds May 13 11:08:02 mail kernel: [ 133.895967] lmtpunix[2176]: seen_db: user philipp opened /var/lib/imap/user/p/philipp.seen May 13 11:08:02 mail kernel: [ 188.010336] master[1892]: process 2170 exited, status 0 May 13 11:08:02 mail kernel: [ 188.016042] master[2204]: about to exec /usr/lib/cyrus-imapd/lmtpd May 13 11:08:02 mail kernel: [ 188.022558] lmtpunix[2204]: executed so it looks like mail messages are being relogged as kernel messages What's going on? systemd provides logging from beginning of userspace on. As long as syslog isn't up this will go to kmsg. As soon as rsyslog is up the kernel log buffer will be fliushed to disk and all following messages go directly to disk with no involvement of kmsg. In F16 and later you'll be able to use dmesg -k to get the usual dmesg output but with all non-kernel messages removed. Note that dmesg never has been about kernel messages only. Low-level userspace system components logged to kmsg already. All we added is that during early boot /dev/log logging ends up in kmsg. Lennart Ok, then I'm unclear. Should rsyslog be running? Because chkconfig rsyslog --list doesn't show any information, and it doesn't seem to be running after reboot. Doing: # chkconfig rsyslog --add # chkconfig rsyslog on doesn't seem to do anything. Shouldn't it be on by default? -Philip -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: And logging issues following F15B upgrade
On Sun, 15.05.11 13:08, Philip Prindeville (philipp_s...@redfish-solutions.com) wrote: Lennart Ok, then I'm unclear. Should rsyslog be running? Because chkconfig rsyslog --list doesn't show any information, and it doesn't seem to be running after reboot. The output this command generates should point you to the fact that the --list command is not supported on systemd: snip Note: This output shows SysV services only and does not include native systemd services. SysV configuration data might be overridden by native systemd configuration. /snip # chkconfig rsyslog --add # chkconfig rsyslog on doesn't seem to do anything. Shouldn't it be on by default? Yes, it should be on by default. systemctl enable rsyslog.service or chkconfig rsyslog on should ensure that. When upgrading at the wrong time the conversion from sysv to systemd might not work properly and the service is not enabled after the upgrade. This should not be a problem however in the final release of F15. Lennart -- Lennart Poettering - Red Hat, Inc. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Orphaned python-alsa
Without doing any research (since it's Sunday and I'm tired) does this mean it is no longer needed, or that you won't be maintaining it and someone else probably should if they're so inclined? -J On 05/15/2011 02:33 AM, Robin 'cheese' Lee wrote: Not required by any package other than alsa-tools. Cheers Robin -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
F-15 Branched report: 20110515 changes
Compose started at Sun May 15 13:15:23 UTC 2011 Broken deps for x86_64 -- db4o-7.4-2.fc13.x86_64 requires mono(Mono.GetOptions) = 0:2.0.0.0 dh-make-0.55-3.fc15.noarch requires debhelper file-browser-applet-0.6.6-1.fc15.x86_64 requires libpanel-applet-2.so.0()(64bit) glunarclock-0.34.1-1.fc14.x86_64 requires libpanel-applet-2.so.0()(64bit) gnome-applet-bubblemon-2.0.15-1.fc13.x86_64 requires libpanel-applet-2.so.0()(64bit) gnome-applet-cpufire-1.6-3.fc14.x86_64 requires libpanel-applet-2.so.0()(64bit) gnome-applet-globalmenu-0.7.9-1.fc15.x86_64 requires libpanel-applet-2.so.0()(64bit) gnome-applet-grandr-0.4.1-2.fc12.x86_64 requires libpanel-applet-2.so.0()(64bit) gnome-applet-music-2.5.1-5.fc15.x86_64 requires libpanel-applet-2.so.0()(64bit) gnome-applet-sensors-2.2.7-4.fc15.i686 requires libpanel-applet-2.so.0 gnome-applet-sensors-2.2.7-4.fc15.x86_64 requires libpanel-applet-2.so.0()(64bit) gnome-applet-sshmenu-3.18-3.fc15.noarch requires ruby(panelapplet2) gnome-applet-window-picker-0.5.8-2.fc14.x86_64 requires libpanel-applet-2.so.0()(64bit) 1:gnome-applets-2.32.0-3.fc15.x86_64 requires libpanel-applet-3.so.0()(64bit) 1:gnome-applets-2.32.0-3.fc15.x86_64 requires libpanel-applet-2.so.0()(64bit) 1:gnome-applets-2.32.0-3.fc15.x86_64 requires libgweather.so.1()(64bit) gnome-netstatus-2.28.2-1.fc15.x86_64 requires libpanel-applet-2.so.0()(64bit) gnome-pilot-conduits-2.32.1-2.fc15.x86_64 requires libgpilotd.so.5()(64bit) gnome-pilot-conduits-2.32.1-2.fc15.x86_64 requires libgpilotdcm.so.4()(64bit) gnome-pilot-conduits-2.32.1-2.fc15.x86_64 requires libgpilotdconduit.so.3()(64bit) gnome-python2-applet-2.32.0-1.fc14.x86_64 requires libpanel-applet-2.so.0()(64bit) gnome-python2-brasero-2.32.0-1.fc14.x86_64 requires libbrasero-media.so.1()(64bit) gnome-python2-brasero-2.32.0-1.fc14.x86_64 requires libbrasero-burn.so.1()(64bit) gnome-python2-evince-2.32.0-1.fc14.x86_64 requires libevview.so.3()(64bit) gnome-python2-evince-2.32.0-1.fc14.x86_64 requires libevdocument.so.3()(64bit) gnome-python2-evolution-2.32.0-1.fc14.x86_64 requires libcamel-1.2.so.19()(64bit) gnome-python2-gdl-2.25.3-22.fc15.x86_64 requires libgdl-1.so.3()(64bit) gnome-python2-totem-2.32.0-1.fc14.x86_64 requires libgnome-media-profiles.so.0()(64bit) gnome-rdp-0.2.3-6.fc12.x86_64 requires mono(Mono.Data.SqliteClient) = 0:2.0.0.0 gnotime-2.3.0-8.fc15.x86_64 requires libgtkhtml-3.15.so.19()(64bit) gnubiff-2.2.13-4.fc15.x86_64 requires libpanel-applet-2.so.0()(64bit) gnustep-back-0.18.0-4.fc14.x86_64 requires libobjc.so.2()(64bit) gnustep-back-0.18.0-4.fc14.x86_64 requires libgnustep-base.so.1.20()(64bit) gnustep-examples-1.3.0-4.fc15.x86_64 requires libgnustep-base.so.1.20()(64bit) gnustep-examples-1.3.0-4.fc15.x86_64 requires libobjc.so.2()(64bit) gnustep-gui-0.18.0-2.fc14.x86_64 requires libgnustep-base.so.1.20()(64bit) gnustep-gui-0.18.0-2.fc14.x86_64 requires libobjc.so.2()(64bit) gnustep-gui-libs-0.18.0-2.fc14.i686 requires libobjc.so.2 gnustep-gui-libs-0.18.0-2.fc14.i686 requires libgnustep-base.so.1.20 gnustep-gui-libs-0.18.0-2.fc14.x86_64 requires libgnustep-base.so.1.20()(64bit) gnustep-gui-libs-0.18.0-2.fc14.x86_64 requires libobjc.so.2()(64bit) gold-2.1.12.2-5.fc15.noarch requires perl(Data::Properties) gorm-1.2.12-2.fc15.i686 requires libobjc.so.2 gorm-1.2.12-2.fc15.i686 requires libgnustep-base.so.1.20 gorm-1.2.12-2.fc15.x86_64 requires libgnustep-base.so.1.20()(64bit) gorm-1.2.12-2.fc15.x86_64 requires libobjc.so.2()(64bit) gpx-viewer-0.2.0-3.fc14.x86_64 requires libchamplain-0.6.so.0()(64bit) gpx-viewer-0.2.0-3.fc14.x86_64 requires libchamplain-gtk-0.6.so.0()(64bit) gpx-viewer-0.2.0-3.fc14.x86_64 requires libgdl-1.so.3()(64bit) gyachi-plugin-libnotify-1.2.10-3.fc14.x86_64 requires libnotify.so.1()(64bit) honeyd-1.5c-13.fc15.x86_64 requires libevent-1.4.so.2()(64bit) intellij-idea-9.0.1.94.399-12.fc15.x86_64 requires commons-collections libopenvrml-0.18.6-4.fc14.1.i686 requires libboost_thread-mt.so.1.44.0 libopenvrml-0.18.6-4.fc14.1.i686 requires libboost_filesystem-mt.so.1.44.0 libopenvrml-0.18.6-4.fc14.1.x86_64 requires libboost_filesystem-mt.so.1.44.0()(64bit) libopenvrml-0.18.6-4.fc14.1.x86_64 requires libboost_thread-mt.so.1.44.0()(64bit) libopenvrml-gl-0.18.6-4.fc14.1.i686 requires libboost_thread-mt.so.1.44.0 libopenvrml-gl-0.18.6-4.fc14.1.i686 requires libboost_filesystem-mt.so.1.44.0 libopenvrml-gl-0.18.6-4.fc14.1.x86_64 requires libboost_filesystem-mt.so.1.44.0()(64bit)
How to build noarch package on only certain architectures?
I'm trying to build Clapham for EPEL6. Clapham is a noarch package, but it depends on Batik, which is ExclusiveArch: i686 x86_64. When I submitted a build with koji, it failed to build for ppc and ppc64 due to the missing dependency. I tried adding the same ExclusiveArch to Clapham. That causes errors from rpm and koji. Now I've tried adding ExcludeArch: ppc ppc64 s390 s390x. Koji still tries to build it for ppc64, and it still fails due to the missing dependency. Is there some other way to add a noarch package that doesn't build on some architectures? Thanks, Eric -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Review Request/Review Swaps Request for writetype, pyttsx, python-timelib
Hi! Currently, more then 3 of my packages are under review request. And 4+ packages are already packaged but not submitted for review since the dependency packages are not reviewed till now (or some other issues). My packages under review: 1. python-timelib [1] - This package is one the dependency package of python-mwlib-0.12.14 2. pyttsx [2] - This package is a dependency package of writetype 3. writetype [3] - [1]. https://bugzilla.redhat.com/show_bug.cgi?id=704445 [2]. https://bugzilla.redhat.com/show_bug.cgi?id=702998 [3]. https://bugzilla.redhat.com/show_bug.cgi?id=698362 -- by Prabin Kumar Datta prabinda...@fedoraproject.org prabinda...@vgvsngo.org IRC: prabindatta gtalk: prabindatta GPG key: pub 2048R/1E0CFA36 2010-11-06 uid PRABIN KUMAR DATTA linux.n@gmail.com sub 2048R/AF311EF8 2010-11-06 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Orphaned python-alsa
I just means anybody who would like to take this package should recognize that it is such a minor package that few people would ever install it. Robin On Mon, May 16, 2011 at 5:14 AM, Jon Ciesla l...@jcomserv.net wrote: Without doing any research (since it's Sunday and I'm tired) does this mean it is no longer needed, or that you won't be maintaining it and someone else probably should if they're so inclined? -J On 05/15/2011 02:33 AM, Robin 'cheese' Lee wrote: Not required by any package other than alsa-tools. Cheers Robin -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
File Bucardo-4.4.4.tar.gz uploaded to lookaside cache by itamarjp
A file has been added to the lookaside cache for bucardo: 41493ace4e81ae4587250ff59dc4e911 Bucardo-4.4.4.tar.gz -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[bucardo] - new version 4.4.4
commit 8ae56a4d5789908c173db91d5bce4e61a9f8585f
Author: Itamar Reis Peixoto ita...@ispbrasil.com.br
Date: Sun May 15 13:15:16 2011 -0300
- new version 4.4.4
.gitignore |1 +
bucardo.spec |5 -
sources |2 +-
3 files changed, 6 insertions(+), 2 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 0836210..6097f4a 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,2 +1,3 @@
Bucardo-4.4.0.tar.gz
/Bucardo-4.4.3.tar.gz
+/Bucardo-4.4.4.tar.gz
diff --git a/bucardo.spec b/bucardo.spec
index 681af40..58ab6f1 100644
--- a/bucardo.spec
+++ b/bucardo.spec
@@ -1,6 +1,6 @@
%define realname Bucardo
Name: bucardo
-Version:4.4.3
+Version:4.4.4
Release:1%{?dist}
Summary:Postgres replication system for both multi-master and
multi-slave operations
@@ -92,6 +92,9 @@ rm -rf $RPM_BUILD_ROOT
%dir %{_localstatedir}/run/bucardo
%changelog
+* Sun May 15 2011 Itamar Reis Peixoto ita...@ispbrasil.com.br - 4.4.4-1
+- New version 4.4.4 fix backslash bug
+
* Thu Apr 21 2011 Itamar Reis Peixoto ita...@ispbrasil.com.br - 4.4.3-1
- New version 4.4.3
diff --git a/sources b/sources
index 13aa2c4..b993030 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-bd15d99de987ccb0b9fa5050e208e061 Bucardo-4.4.3.tar.gz
+41493ace4e81ae4587250ff59dc4e911 Bucardo-4.4.4.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[bucardo/f15] - new version 4.4.4
Summary of changes: 8ae56a4... - new version 4.4.4 (*) (*) This commit already existed in another branch; no separate mail sent -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[bucardo/f13] (2 commits) ...Merge branch 'master' into f13
Summary of changes: 8ae56a4... - new version 4.4.4 (*) 19bda46... Merge branch 'master' into f13 (*) This commit already existed in another branch; no separate mail sent -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[bucardo/f13: 2/2] Merge branch 'master' into f13
commit 19bda469f861fcfabf739ac25d76d288395a29d0 Merge: 722709b 8ae56a4 Author: Itamar Reis Peixoto ita...@ispbrasil.com.br Date: Sun May 15 13:41:42 2011 -0300 Merge branch 'master' into f13 Conflicts: .gitignore .gitignore |3 +++ bucardo.spec |5 - sources |2 +- 3 files changed, 8 insertions(+), 2 deletions(-) --- -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[bucardo/el6] (2 commits) ...Merge branch 'master' into el6
Summary of changes: 8ae56a4... - new version 4.4.4 (*) 4a5577a... Merge branch 'master' into el6 (*) This commit already existed in another branch; no separate mail sent -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[bucardo/el6: 2/2] Merge branch 'master' into el6
commit 4a5577a564a0f427a4562607c7273eeb08c29dcd Merge: 19ec8f6 8ae56a4 Author: Itamar Reis Peixoto ita...@ispbrasil.com.br Date: Sun May 15 13:49:22 2011 -0300 Merge branch 'master' into el6 .gitignore |1 + bucardo.spec |5 - sources |2 +- 3 files changed, 6 insertions(+), 2 deletions(-) --- -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
File File-Slurp-9999.18.tar.gz uploaded to lookaside cache by corsepiu
A file has been added to the lookaside cache for perl-File-Slurp: 400983e739aea5677c3a7e8cb2c23de0 File-Slurp-.18.tar.gz -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-File-Slurp] Upstream update.
commit b6300f1e842fd2813e1602d747db57de7ae6
Author: Ralf Corsépius corse...@fedoraproject.org
Date: Mon May 16 05:48:33 2011 +0200
Upstream update.
.gitignore |1 +
perl-File-Slurp.spec |5 -
sources |2 +-
3 files changed, 6 insertions(+), 2 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index 36785b6..f7e1924 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,3 +1,4 @@
File-Slurp-.13.tar.gz
/File-Slurp-.15.tar.gz
/File-Slurp-.16.tar.gz
+/File-Slurp-.18.tar.gz
diff --git a/perl-File-Slurp.spec b/perl-File-Slurp.spec
index 178340f..52d4ff0 100644
--- a/perl-File-Slurp.spec
+++ b/perl-File-Slurp.spec
@@ -1,5 +1,5 @@
Name: perl-File-Slurp
-Version: .16
+Version: .18
Release: 1%{?dist}
Summary: Efficient Reading/Writing of Complete Files
License: GPL+ or Artistic
@@ -54,6 +54,9 @@ make test
%{_mandir}/man3/*
%changelog
+* Sun May 15 2011 Ralf Corsépius corse...@fedoraproject.org - .18-1
+- Upstream update.
+
* Thu Apr 28 2011 Ralf Corsépius corse...@fedoraproject.org - .16-1
- Upstream update.
diff --git a/sources b/sources
index 143a0a9..785bafa 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-1df4c6ecae308cf41bf1eb91657d87f7 File-Slurp-.16.tar.gz
+400983e739aea5677c3a7e8cb2c23de0 File-Slurp-.18.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-File-Slurp/f15] Upstream update.
Summary of changes: b6300f1... Upstream update. (*) (*) This commit already existed in another branch; no separate mail sent -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-File-Slurp/f14] (2 commits) ...Merge remote-tracking branch 'origin/master' into f14
Summary of changes: b6300f1... Upstream update. (*) 2f5b9d4... Merge remote-tracking branch 'origin/master' into f14 (*) This commit already existed in another branch; no separate mail sent -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-File-Slurp/f14: 2/2] Merge remote-tracking branch 'origin/master' into f14
commit 2f5b9d42b7eb78b4cd182fa6a9f2e730dd830210 Merge: 3bf6ef6 b6300f1 Author: Ralf Corsépius corse...@fedoraproject.org Date: Mon May 16 06:38:33 2011 +0200 Merge remote-tracking branch 'origin/master' into f14 .gitignore |1 + perl-File-Slurp.spec |5 - sources |2 +- 3 files changed, 6 insertions(+), 2 deletions(-) --- -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-File-Slurp/f13] (2 commits) ...Merge remote-tracking branch 'origin/master' into f13
Summary of changes: b6300f1... Upstream update. (*) 8a2786a... Merge remote-tracking branch 'origin/master' into f13 (*) This commit already existed in another branch; no separate mail sent -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[perl-File-Slurp/f13: 2/2] Merge remote-tracking branch 'origin/master' into f13
commit 8a2786abadafd99d09e3f0541c7f7376664386f6 Merge: 751485d b6300f1 Author: Ralf Corsépius corse...@fedoraproject.org Date: Mon May 16 06:58:55 2011 +0200 Merge remote-tracking branch 'origin/master' into f13 .gitignore |1 + perl-File-Slurp.spec |5 - sources |2 +- 3 files changed, 6 insertions(+), 2 deletions(-) --- -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/perl-devel
