Fedora 19 updates-testing report

2013-07-03 Thread updates
The following Fedora 19 Security updates need testing:
 Age  URL
  78  
https://admin.fedoraproject.org/updates/FEDORA-2013-5801/mantis-1.2.15-1.fc19
  33  
https://admin.fedoraproject.org/updates/FEDORA-2013-9715/heat-jeos-9-1.fc19
  21  
https://admin.fedoraproject.org/updates/FEDORA-2013-10678/python-keystoneclient-0.2.3-4.fc19
   9  
https://admin.fedoraproject.org/updates/FEDORA-2013-10467/openstack-keystone-2013.1.2-3.fc19
   7  
https://admin.fedoraproject.org/updates/FEDORA-2013-11734/libXv-1.0.9-1.fc19
   6  
https://admin.fedoraproject.org/updates/FEDORA-2013-11682/ReviewBoard-1.7.11-1.fc19
   4  
https://admin.fedoraproject.org/updates/FEDORA-2013-11911/php-pecl-radius-1.2.7-1.fc19
   4  
https://admin.fedoraproject.org/updates/FEDORA-2013-11904/autotrace-0.31.1-34.fc19
   2  
https://admin.fedoraproject.org/updates/FEDORA-2013-12083/libXp-1.0.2-1.fc19
   2  
https://admin.fedoraproject.org/updates/FEDORA-2013-12115/gegl-0.2.0-11.fc19
   0  
https://admin.fedoraproject.org/updates/FEDORA-2013-12118/ruby-2.0.0.247-11.fc19
   0  
https://admin.fedoraproject.org/updates/FEDORA-2013-12199/dbus-glib-0.100-5.fc19
   0  
https://admin.fedoraproject.org/updates/FEDORA-2013-12178/lldpad-0.9.46-2.fc19


The following builds have been pushed to Fedora 19 updates-testing

audacious-3.4-1.fc19
audacious-plugins-3.4-1.fc19
crtools-0.6-2.fc19
devassistant-0.4.0-2.fc19
gappa-0.18.0-1.fc19
gappalib-coq-0.21.1-1.fc19
groonga-3.0.5-1.fc19
ibus-typing-booster-1.2.1-1.fc19
insight-7.4.50-9.20120403cvs.fc19
ledmon-0.78-1.fc19
lfcxml-1.1.4-1.fc19
libXi-1.7.2-1.fc19
libdrm-2.4.46-1.fc19
msktutil-0.5-1.fc19
pkgwat-0.8-1.fc19
pnp4nagios-0.6.21-2.fc19
procps-ng-3.3.8-8.fc19
python-django-flash-1.8-7.fc19
python-django-horizon-2013.1.2-2.fc19
spice-protocol-0.12.6-1.fc19
spice-vdagent-0.14.0-3.fc19
sugar-labyrinth-16-1.fc19
sugar-memorize-45-1.fc19
superkb-0.22-3.fc19
teeworlds-0.6.2-2.fc19
uucp-1.07-38.fc19
vcftools-0.1.11-1.fc19
virt-v2v-0.9.0-3.fc19

Details about builds:



 audacious-3.4-1.fc19 (FEDORA-2013-12259)
 Advanced audio player

Update Information:

Update from 3.4-beta2 to 3.4 final release for a very few more bug-fixes and 
translation updates.


ChangeLog:

* Sat Jun 29 2013 Michael Schwendt  - 3.4-1
- Update to 3.4 final (a few bug-fixes and translation updates).




 audacious-plugins-3.4-1.fc19 (FEDORA-2013-12259)
 Plugins for the Audacious audio player

Update Information:

Update from 3.4-beta2 to 3.4 final release for a very few more bug-fixes and 
translation updates.


ChangeLog:

* Sat Jun 29 2013 Michael Schwendt  - 3.4-1
- Update to 3.4 final (just the merged big-endian fix, and translation updates).




 crtools-0.6-2.fc19 (FEDORA-2013-12240)
 Tool for Checkpoint/Restore in User-space

Update Information:

updated to usptream release 0.6

ChangeLog:

* Wed Jul  3 2013 Andrew Vagin  - 0.6-2
- fix building on ARM
- fix null pointer dereference
* Tue Jul  2 2013 Adrian Reber  - 0.6-1
- updated to 0.6
- upstream moved binaries to sbin
- using upstream's make install
* Tue May 14 2013 Adrian Reber  - 0.5-1
- updated to 0.5




 devassistant-0.4.0-2.fc19 (FEDORA-2013-12283)
 Developer tool for setting up projects quickly

Update Information:

Fixes manpage typo, that caused the "build" argument to not be on its own line.
New minor release of devassistant that allows much greater usage of its 
facilities. Includes many new assistants (php, perl) and whole new concept of 
"preparer" assistants, that can be used to checkout and set existing project 
from scm.
Also incorporates major improvements in the devassistant yaml DSL as well as 
many bugfixes and other minor enhancements.

ChangeLog:

* Wed Jul  3 2013 Bohusla

Fedora 17 updates-testing report

2013-07-03 Thread updates
The following Fedora 17 Security updates need testing:
 Age  URL
 363  
https://admin.fedoraproject.org/updates/FEDORA-2012-10269/revelation-0.4.14-1.fc17
 175  
https://admin.fedoraproject.org/updates/FEDORA-2013-0455/fedora-business-cards-1-0.1.beta1.fc17
 103  
https://admin.fedoraproject.org/updates/FEDORA-2013-4234/stunnel-4.55-1.fc17
  98  
https://admin.fedoraproject.org/updates/FEDORA-2013-4501/libxslt-1.1.28-1.fc17
  95  
https://admin.fedoraproject.org/updates/FEDORA-2013-4581/libuser-0.57.6-2.fc17
  27  
https://admin.fedoraproject.org/updates/FEDORA-2013-10121/subversion-1.7.10-1.fc17
  17  
https://admin.fedoraproject.org/updates/FEDORA-2013-10940/tomcat6-6.0.37-1.fc17
  12  
https://admin.fedoraproject.org/updates/FEDORA-2013-11397/python-bugzilla-0.9.0-1.fc17
   9  
https://admin.fedoraproject.org/updates/FEDORA-2013-11568/curl-7.24.0-10.fc17
   6  https://admin.fedoraproject.org/updates/FEDORA-2013-11785/xen-4.1.5-8.fc17
   6  
https://admin.fedoraproject.org/updates/FEDORA-2013-11413/glpi-0.83.9.1-1.fc17
   5  https://admin.fedoraproject.org/updates/FEDORA-2013-11871/xen-4.1.5-9.fc17
   2  
https://admin.fedoraproject.org/updates/FEDORA-2013-11992/php-pecl-radius-1.2.7-1.fc17
   2  
https://admin.fedoraproject.org/updates/FEDORA-2013-12075/gegl-0.2.0-11.fc17
   2  
https://admin.fedoraproject.org/updates/FEDORA-2013-12062/ruby-1.9.3.448-31.fc17


The following Fedora 17 Critical Path updates have yet to be approved:
 Age URL
 315  
https://admin.fedoraproject.org/updates/FEDORA-2012-12509/PackageKit-0.7.6-1.fc17
 123  
https://admin.fedoraproject.org/updates/FEDORA-2013-3304/libvpx-1.2.0-1.fc17
  12  
https://admin.fedoraproject.org/updates/FEDORA-2013-11411/deltarpm-3.6-0.12.20110223git.fc17
  12  
https://admin.fedoraproject.org/updates/FEDORA-2013-11397/python-bugzilla-0.9.0-1.fc17
   9  
https://admin.fedoraproject.org/updates/FEDORA-2013-11568/curl-7.24.0-10.fc17
   0  
https://admin.fedoraproject.org/updates/FEDORA-2013-12153/xulrunner-22.0-4.fc17


The following builds have been pushed to Fedora 17 updates-testing

drupal7-domain-3.10-2.fc17
drupal7-domain_locale-1.0-0.2.beta3.fc17
drupal7-language_cookie-1.6-2.fc17
gfal2-2.3.0-0.fc17
ibus-typing-booster-1.2.1-1.fc17
insight-7.4.50-8.20120403cvs.fc17
kde-plasma-alsa-volume-0.43.5-1.fc17
libdivecomputer-0.4.1-1.fc17
mozilla-https-everywhere-3.2.3-1.fc17
qpid-cpp-0.22-2.fc17
simspark-0.2.4-2.fc17
subsurface-3.1.1-1.fc17
sugar-labyrinth-16-1.fc17
superkb-0.22-2.fc17
superkb-0.22-3.fc17

Details about builds:



 drupal7-domain-3.10-2.fc17 (FEDORA-2013-12265)
 A domain-based access control system

Update Information:

The Domain Access project is a suite of modules that provide tools for running
a group of affiliated sites from one Drupal installation and a single shared
database. The module allows you to share users, content, and configurations
across a group of sites such as:
* example.com
* one.example.com
* two.example.com
* my.example.com
* thisexample.com <-- can use any domain string
* example.com:3000 <-- treats non-standard ports as unique

By default, these sites share all tables in your Drupal installation.

This package provides the following Drupal modules:
* domain
* domain_alias
* domain_conf
* domain_content
* domain_nav
* domain_settings
* domain_source
* domain_strict
* domain_test
* domain_theme




 drupal7-domain_locale-1.0-0.2.beta3.fc17 (FEDORA-2013-12253)
 Adds language handling functionality per domain basis

Update Information:

Domain Locale allows to customize language sets per domain for Drupal installs
using Domain Access and core Locale module. This module also offers drush
integration.

You need this module if:
* you want a different default language on different domains
* you want a different language set for each different domain

This package provides the following Drupal module:
* domain_locale




 drupal7-language_cookie-1.6-2.fc17 (FEDORA-2013-12301)
 Allows usage of cookies to remember the user's last language

Update Information:

Adds an extra "Cookie" field to the Language Negotiation settings, allowing the
language to be set according to a cookie.

The cookie name, domain & expiration are configurable in the settings page.

This package provides the following Drupal module:
* language_cookie
---

Second draft of revised final criteria, proposed criterion for partition resizing

2013-07-03 Thread Adam Williamson
Hi folks! Taking into account the feedback on the first draft of the 
revised criteria, I've updated the draft page with a few changes:


https://fedoraproject.org/wiki/User:Adamwill/Draft_final_criteria_sandbox

I updated it to F20 status first of all. Then I re-worded the AVC/abrt 
criterion to cover live installation, as we want to cover that. It now 
reads:


"There must be no SELinux denial notifications or crash notifications on 
boot of or during installation from a release-blocking live image, or at 
first login after a default install of a release-blocking desktop."


For the 'single partition' issue with the Windows criterion I simply 
dropped the single partition reference entirely, that seemed like all 
that was necessary. The remaining 'caveats' should be strong enough to 
allow us not to block for crazy cases. 
https://fedoraproject.org/w/index.php?title=User:Adamwill/Draft_final_criteria_sandbox&diff=343806&oldid=343805


I considered the suggestion to make the "unless they require hardware 
that is not present" bit of the 'services must work' criterion a 
sub-section, but on balance I don't like it: the sub-sections are really 
meant to _explain_ the main criterion, not fundamentally alter its 
meaning. I did use it to list exceptions a few times, but this one just 
seems like too big of an exception: it really is a part of the main text 
of the criterion, I think, it doesn't belong as a sub-section. So I left 
that as it is.


I'd also like to consider adding a criterion that covers resizing, as 
discussed in the long thread about dual-booting. I think we can add a 
minimal criterion that's realistically enforceable if we word it right. 
Let's make that a proposal here on the list, rather than part of the 
'revision' draft, though. So, here's my proposal:




Any installer mechanism for resizing storage volumes must correctly 
attempt the requested operation.


Sub-section "What does that cover?":

This means that if the installer offers mechanisms for resizing storage 
volumes, then it must run the appropriate resizing tool with the 
appropriate parameters for the resize the user chooses. The reason it's 
worded this way is we specifically ''don't'' want to cover cases where 
the requested resize operation then fails for some reason - dirtily 
unmounted or over-fragmented partition, for instance - then fails. We 
only want to cover the case that the installer's resize code itself is 
badly broken.




Any comments on that criterion proposal or the revised Final criteria 
draft would be most welcome! Thanks folks. I'm aiming to have this 
rounded off fairly soon so I can move on to other F20 prep work.

--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: Self-introduction: Matt Kottre

2013-07-03 Thread Adam Williamson

On 2013-07-03 14:17, mkot...@lavabit.com wrote:

Hello,

My name is Matt Kottre. I'm 16, almost 17, years old and live in
Tillamook, Oregon. I know the basics of most major programming 
languages
as well as. I also know most of the basics of managing a Linux system. 
I'm

really looking forward to improving both while helping to make Fedora a
better distribution.

I've been a Linux user for years and I'm very excited to start getting
involved in the community. I've been distro hopping since I first 
started

using Linux in 2008. I used Fedora on several occasions over that time,
but a few months ago, I decided that I'm going to settle down on 
Fedora. I

really appreciate the quality of their work and their focus on
incorporating the latest technologies without sacrificing stability.

I plan on joining other Fedora projects later on as well, but I thought
that QA would be the best stepping stone and also help me get used to 
the

way that Fedora operates.


Hi Matt, and welcome! Please feel free to ping me on IRC or by mail with 
any questions. Thanks for volunteering to help out!

--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Self-introduction: Matt Kottre

2013-07-03 Thread mkottre
Hello,

My name is Matt Kottre. I'm 16, almost 17, years old and live in
Tillamook, Oregon. I know the basics of most major programming languages
as well as. I also know most of the basics of managing a Linux system. I'm
really looking forward to improving both while helping to make Fedora a
better distribution.

I've been a Linux user for years and I'm very excited to start getting
involved in the community. I've been distro hopping since I first started
using Linux in 2008. I used Fedora on several occasions over that time,
but a few months ago, I decided that I'm going to settle down on Fedora. I
really appreciate the quality of their work and their focus on
incorporating the latest technologies without sacrificing stability.

I plan on joining other Fedora projects later on as well, but I thought
that QA would be the best stepping stone and also help me get used to the
way that Fedora operates.

My IRC nickname is mkottre.
My email is mkot...@lavabit.com

Thanks


-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: F19 - networking problem & questions

2013-07-03 Thread Frank Murphy
On Wed, 03 Jul 2013 20:52:52 +0200
Mateusz Marzantowicz  wrote:

> Shouldn't be grub2-mkconfig -o /boot/grub2/grub.cfg?
> 

Yes, I need to go watch TV :(

-- 
Regards,
Frank  "When in doubt PANIC!"
 I check for new mail app. 20min
www.frankly3d.com
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: F19 - networking problem & questions

2013-07-03 Thread Mateusz Marzantowicz
On 03.07.2013 20:46, Frank Murphy wrote:
> On Wed, 03 Jul 2013 11:47:53 +0300
> Cristian Sava  wrote:
>
>
>> After updating aujour:
>>
>> The external network is not reachable anymore but the internal
>> network is ok if NM is enabled and working.
>> This setup does not work with network service anymore.
>> Any advice how to fix (not downgrade-ing?)?
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=980785
>>
>> C. Sava
>>
>
> http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
> try on the kernel line net.ifnames=0
> or add to /etc/default/grub 
> GRUB_CMDLINE_LINUX= "some other stuff net.ifnames=0"
> grub2-install /boot/grub2/grub.cfg
>

Shouldn't be grub2-mkconfig -o /boot/grub2/grub.cfg?


Mateusz Marzantowicz
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: F19 - networking problem & questions

2013-07-03 Thread Frank Murphy
On Wed, 03 Jul 2013 11:47:53 +0300
Cristian Sava  wrote:


> 
> After updating aujour:
> 
> The external network is not reachable anymore but the internal
> network is ok if NM is enabled and working.
> This setup does not work with network service anymore.
> Any advice how to fix (not downgrade-ing?)?
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=980785
> 
> C. Sava
> 


http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
try on the kernel line net.ifnames=0
or add to /etc/default/grub 
GRUB_CMDLINE_LINUX= "some other stuff net.ifnames=0"
grub2-install /boot/grub2/grub.cfg

-- 
Regards,
Frank  "When in doubt PANIC!"
 I check for new mail app. 20min
www.frankly3d.com
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: F19 - networking problem & questions

2013-07-03 Thread Adam Williamson

On 2013-07-03 1:47, Cristian Sava wrote:

I have a server with two NICs (on-board and attached).
HW: ASRock H67M-GE + I3-2120 + 8GB + 1TB (hdd, sata)



1) Why "route" shows iface=p4p1, p5p1 instead enp4s0, enp5s0 ?


This will likely be something to do with:

https://fedoraproject.org/wiki/Common_F19_bugs#biosdevname-vs-systemd

I'd say p4p1 is the biosdevname name for the interface, enp4s0 is the 
systemd name. I don't understand why some tools would show one and some 
tools the other, though. It sounds like we haven't quite figured out 
*all* the interactions between biosdevname and the systemd stuff here. 
Did you do your install with biosdevname=0 ? Was biosdevname in your 
package set at install time?

--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

rawhide report: 20130703 changes

2013-07-03 Thread Fedora Rawhide Report
Compose started at Wed Jul  3 08:15:02 UTC 2013

Broken deps for x86_64
--
[avgtime]
avgtime-0-0.6.git20130201.fc20.x86_64 requires 
libphobos-ldc.so.60()(64bit)
[contour]
contour-0.3-2.fc19.x86_64 requires libsolidcontrolifaces.so.4()(64bit)
contour-0.3-2.fc19.x86_64 requires libsolidcontrol.so.4()(64bit)
[derelict]
derelict-tcod-3-20.20130626gite70c293.fc20.i686 requires tcod
derelict-tcod-3-20.20130626gite70c293.fc20.x86_64 requires tcod
derelict-tcod-devel-3-20.20130626gite70c293.fc20.i686 requires tcod
derelict-tcod-devel-3-20.20130626gite70c293.fc20.x86_64 requires tcod
[ekiga]
ekiga-4.0.1-1.fc19.x86_64 requires libedata-book-1.2.so.17()(64bit)
[evolution-rss]
1:evolution-rss-0.3.93-3.fc20.x86_64 requires libeutil.so()(64bit)
1:evolution-rss-0.3.93-3.fc20.x86_64 requires libeshell.so()(64bit)
[gdb-heap]
gdb-heap-0.5-12.fc19.x86_64 requires glibc(x86-64) = 0:2.17
[gooddata-cl]
gooddata-cl-1.2.56-2.fc19.noarch requires gdata-java
[gtkd]
gtkd-2.0.0-29.20120815git9ae9181.fc18.i686 requires libphobos-ldc.so.60
gtkd-2.0.0-29.20120815git9ae9181.fc18.x86_64 requires 
libphobos-ldc.so.60()(64bit)
[jboss-as]
jboss-as-7.1.1-19.fc20.noarch requires cxf-common >= 0:2.6.3
[kawa]
1:kawa-1.11-5.fc19.x86_64 requires servlet25
[koji]
koji-vm-1.8.0-1.fc20.noarch requires python-virtinst
[kyua-cli]
kyua-cli-0.5-3.fc19.x86_64 requires liblutok.so.0()(64bit)
kyua-cli-tests-0.5-3.fc19.x86_64 requires liblutok.so.0()(64bit)
[lancet]
lancet-1.0.1-6.fc19.noarch requires ant-nodeps >= 0:1.7.1
[openbox]
gdm-control-3.5.0-11.20121001git782b28.fc19.x86_64 requires gnome-panel
gnome-panel-control-3.5.0-11.20121001git782b28.fc19.x86_64 requires 
gnome-panel
[openlierox]
openlierox-0.59-0.11.beta10.fc20.x86_64 requires libgd.so.2()(64bit)
[ovirt-engine]
ovirt-engine-notification-service-3.1.0-1.fc19.noarch requires 
classpathx-mail
[ovirt-guest-agent]
ovirt-guest-agent-gdm-plugin-1.0.6-6.fc19.x86_64 requires 
libgdmsimplegreeter.so.1()(64bit)
[oyranos]
oyranos-libs-0.4.0-7.fc19.i686 requires libraw.so.5
oyranos-libs-0.4.0-7.fc19.x86_64 requires libraw.so.5()(64bit)
[perl-Bio-ASN1-EntrezGene]
perl-Bio-ASN1-EntrezGene-1.091-17.fc19.noarch requires 
perl(Bio::Index::AbstractSeq)
[perl-Bio-SamTools]
perl-Bio-SamTools-1.35-2.fc19.x86_64 requires 
perl(Bio::SeqFeature::Lite)
perl-Bio-SamTools-1.35-2.fc19.x86_64 requires perl(Bio::PrimarySeq)
[perl-PDL]
perl-PDL-2.4.10-6.fc19.x86_64 requires libgd.so.2()(64bit)
[perl-qpid]
perl-qpid-0.22-2.fc20.x86_64 requires libqpidtypes.so.1.0.0()(64bit)
perl-qpid-0.22-2.fc20.x86_64 requires libqpidmessaging.so.2.0.0()(64bit)
[python-TraitsBackendQt]
python-TraitsBackendQt-3.5.0-5.fc19.noarch requires python-TraitsGUI
[rubygem-openshift-origin-common]
rubygem-openshift-origin-common-1.8.10-1.fc20.noarch requires 
rubygem(safe_yaml)
[rubygem-openshift-origin-node]
rubygem-openshift-origin-node-1.9.15-1.fc20.noarch requires 
rubygem(safe_yaml)
rubygem-openshift-origin-node-1.9.15-1.fc20.noarch requires 
openshift-origin-node-proxy
[rubygem-qpid]
rubygem-qpid-0.16.0-14.fc20.x86_64 requires 
libqpidmessaging.so.3()(64bit)
rubygem-qpid-0.16.0-14.fc20.x86_64 requires libqpidcommon.so.5()(64bit)
rubygem-qpid-0.16.0-14.fc20.x86_64 requires libqpidclient.so.5()(64bit)
[rubygem-qpid_messaging]
rubygem-qpid_messaging-0.22.0-1.fc20.x86_64 requires 
libqpidtypes.so.1.0.0()(64bit)
rubygem-qpid_messaging-0.22.0-1.fc20.x86_64 requires 
libqpidmessaging.so.2.0.0()(64bit)
rubygem-qpid_messaging-0.22.0-1.fc20.x86_64 requires 
libqpidcommon.so.2.0.0()(64bit)
rubygem-qpid_messaging-0.22.0-1.fc20.x86_64 requires 
libqpidclient.so.2.0.0()(64bit)
[sagemath]
sagemath-core-5.9-5.fc20.i686 requires libgd.so.2
sagemath-core-5.9-5.fc20.x86_64 requires libgd.so.2()(64bit)
[scala]
scala-2.9.2-2.fc19.noarch requires osgi(org.scala-ide.scala.library)
[spacewalk-web]
spacewalk-dobby-1.9.22-2.fc19.noarch requires perl(Spacewalk::Setup)
[spring]
spring-94.1-1.fc20.x86_64 requires libassimp.so.2()(64bit)
[sumwars]
sumwars-0.5.6-12.fc20.x86_64 requires libenet-1.3.7.so()(64bit)
[tango]
tango-2-12.20120821git7b92443.fc19.i686 requires libphobos-ldc.so.60
tango-2-12.20120821git7b92443.fc19.x86_64 requires 
libphobos-ldc.so.60()(64bit)
[vfrnav]
vfrnav-20130510-1.fc20.x86_64 requires libpolyclipping.so.8()(64bit)
vfrnav-utils-20130510-1.fc20.x86_64 requires 
libpolyclipping.so.8()(64bit)
[zarafa]
libmapi-7.0.13-1.fc19.i686 requires libicalss.so.0
libmapi-7.0.13-1.fc19.i686 requires libical.so.0
libmapi-7.0.13-1.fc19.x86_64 requires libicalss.

The heroes of Fedora 19 Final testing

2013-07-03 Thread Kamil Paral
Fedora 19 the Schrödinger’s Cat is out of the box, and alive! I have again 
gathered some interesting statistics about QA contributions, this time during 
the Final phase (between Beta and Final release).

Read the blog at:
https://kparal.wordpress.com/2013/07/03/the-heroes-of-fedora-19-final-testing/

Thanks everyone.
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: F19 - networking problem & questions

2013-07-03 Thread Cristian Sava
On Wed, 2013-07-03 at 11:47 +0300, Cristian Sava wrote:
> After updating aujour:
> 
> The external network is not reachable anymore but the internal network
> is ok if NM is enabled and working.
> This setup does not work with network service anymore.
> Any advice how to fix (not downgrade-ing?)?
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=980785

Mainly, this bug is due to kernel-3.9.8-300.fc19.x86_64 and downgrading
to kernel-3.9.5-301.fc19.x86_64 solve the networking accessibility. The
other points are still valid.

C. Sava


-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

F19 - networking problem & questions

2013-07-03 Thread Cristian Sava
I have a server with two NICs (on-board and attached).
HW: ASRock H67M-GE + I3-2120 + 8GB + 1TB (hdd, sata)

[root@physics network-scripts]# cat ifcfg-enp4s0
IPV6_PEERDNS="yes"
IPV6INIT="yes"
UUID="b43c0128-ec02-4793-98c9-f396fb9438d2"
IPADDR1="192.168.1.1"
IPADDR0="172.16.0.1"
PREFIX1="24"
PREFIX0="16"
DEFROUTE="yes"
IPV4_FAILURE_FATAL="yes"
HWADDR="64:70:02:14:43:EF"
BOOTPROTO="none"
IPV6_DEFROUTE="yes"
IPV6_AUTOCONF="yes"
IPV6_FAILURE_FATAL="no"
IPV6_PEERROUTES="yes"
TYPE="Ethernet"
ONBOOT="yes"
NAME="enp4s0"
[root@physics network-scripts]# cat ifcfg-enp5s0
TYPE=Ethernet
BOOTPROTO=none
DEFROUTE=yes
IPV4_FAILURE_FATAL=yes
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
NAME=enp5s0
UUID=fc903246-75fa-4680-86f8-b5132fc891c5
ONBOOT=yes
IPADDR0=193.x.y.130
PREFIX0=26
GATEWAY0=193.x.y.129
DNS1=193.x.y.254
DOMAIN=central.ucv.ro
IPADDR1=193.x.y.162
PREFIX1=26
IPADDR2=193.x.y.163
PREFIX2=26
HWADDR=00:25:22:F9:71:3D
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes

[root@physics ~]# route
Kernel IP routing table
Destination  Gateway Genmask  Flags Metric Ref Use Iface
default  g129.central.uc 0.0.0.0 UG  0  0   0 p5p1
link-local * 255.255.0.0 U   1002   0   0 p4p1
link-local * 255.255.0.0 U   1003   0   0 p5p1
172.16.0.0 * 255.255.0.0 U   1  0   0 p4p1
192.168.1.0* 255.255.255.0   U   0  0   0 p4p1
193.x.y.128* 255.255.255.192 U   1  0   0 p5p1

[root@s194 sysconfig]# cat iptables
# Custom file edited on 02-Jul-2013
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A INPUT -m conntrack --ctstate ESTABLISHED,RELATED -j ACCEPT
-A INPUT -p icmp -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -m conntrack --ctstate NEW -m tcp -p tcp --dport 22 -j ACCEPT
-A INPUT -j REJECT --reject-with icmp-host-prohibited
-A FORWARD -j ACCEPT
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
COMMIT
# Completed on 2013-07-02 11:48
*nat
:PREROUTING ACCEPT [0:0]
:POSTROUTING ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A PREROUTING --dst 193.x.y.162 -p tcp -j DNAT --to 192.168.1.73
-A OUTPUT --dst 193.x.y.162 -p tcp -j DNAT --to 192.168.1.73
-A PREROUTING --dst 193.x.y.163 -p tcp -j DNAT --to 192.168.1.200
-A OUTPUT --dst 193.x.y.163 -p tcp -j DNAT --to 192.168.1.200
-A POSTROUTING -s 192.168.1.0/24 -p tcp --dst 192.168.1.73 --dport 22 -j
SNAT --to 192.168.1.1
-A POSTROUTING -s 192.168.1.0/24 -o p5p1 -j SNAT --to-source 193.x.y.130
-A POSTROUTING -s 172.16.0.0/16 -o p5p1 -j SNAT --to-source 193.x.y.130
COMMIT

With F19 install (no updates) it is the same with NM or with network
service.

The problems:
1) Why "route" shows iface=p4p1, p5p1 instead enp4s0, enp5s0 ?
2) Why "ifconfig" does show only the IPADDR0 without aliases?
3) All is working as expected when 192.168.1.73 is on-line. If ...73 not
on-line, the address 193.x.y.162 is assigned to the the server, it
responds to "ping 193.x.y.162" but it should be unreachable (or
something equivalent) because 192.168.1.73 is off.
Similar for 193.x.y.163 .

After updating aujour:

The external network is not reachable anymore but the internal network
is ok if NM is enabled and working.
This setup does not work with network service anymore.
Any advice how to fix (not downgrade-ing?)?

https://bugzilla.redhat.com/show_bug.cgi?id=980785

C. Sava




-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

Re: critera proposal/discussion: FESCo blockers

2013-07-03 Thread Jaroslav Reznik
- Original Message -
> On 2013-06-21 10:41, Kevin Fenzi wrote:
> > On Fri, 21 Jun 2013 10:37:01 -0700
> > Adam Williamson  wrote:
> > 
> >> So, just a phrasing thing, the criteria are mostly written in the form
> >> 'XXX must be the case', not 'XXX is added to the blocker list'. So
> >> perhaps:
> >> 
> >> 'All bugs deemed by FESCo to block the milestone release must be
> >> fixed.'
> >> 
> >> Would be enough. My suggestion used the terms 'issues' and 'addressed'
> >> as weasel words we've found useful before - in the case where we work
> >> around a bug, rather than fixing it, we can call that 'addressing' it
> >> - but I don't really mind writing it that way and just using Common
> >> Sense (tm). I think specifying FESCo's current decision-making
> >> mechanism - majority vote - in the criterion is a mistake, as it's at
> >> least theoretically plausible that FESCo could change its
> >> decision-making mechanism in future, and then the criterion would
> >> need to be updated for no good reason. All that matters to the
> >> blocker process is that 'FESCo Hath Deemed It Thus'. The mechanism by
> >> which FESCo Deems things is out of scope.
> > 
> > Sure. Works for me.
> 
> As there were no objections, I'm adding this to the Alpha page as I
> create the F20 criteria pages. Thanks!

Late +1! It's good to have it documented and part of blocker process to
avoid surprises.

R.

> --
> Adam Williamson
> Fedora QA Community Monkey
> IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
> http://www.happyassassin.net
> --
> test mailing list
> test@lists.fedoraproject.org
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/test
-- 
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test