Re: F20 Installs Fail From Every Angle (Michael Schwendt)
by Brian Hanks
On Sat, 28 Dec 2013 23:56:30 +0100, Michael Schwendt wrote:
> What "dependency error" did it report?
> And how did you query the installed packages as well as the remote
> repos for what would be available_after_ the upgrade?
>
> Many users still misread such error messages and don't manage to work
> around them as a result. Often, the installed packages are okay, but
> during they upgrade they would get replaced and break dependencies.
The exact error message was "WARNING: problems were encountered during transaction test:
broken dependencies
kmod-VirtualBox-3.12.5-200.fc19.x86_64-4.3.6-1.fc19.1.x86_64 requires kernel-3.12.5-200.fc19.x86_64
Continue with upgrade at your own risk."
In response I removed kmod-VirtualBox, akmod-VirtualBox, and VirtualBox. Then I did a fedup --clean and reattempted fedup --network 20. This went well until the reboot. Following the reboot I select the Fedup option, but nothing really happened. I ended up back in my Fedora 19 system while running the new Fedora 20 kernel.
As an update on the other machine where I was having problems with the net install. I checked for any meaningful logs but found that none exist. The /var/log directory hasn't even been created. So, then I tried to run a grub2-mkconfig, grub2-install, dracut series to potentially fix the problem. The file sizes did change a bit, but the end result was the same.
Brian
10 years, 5 months
Re: F20 Installs Fail From Every Angle
by Brian Hanks
> On Sun, 29 Dec 2013 22:47:07 -0700, Chris Murphy wrote:
>
>
> You chose the fedup option in GRUB, but instead of getting text status of the progessing update, you got what appeared to be normal F19 boot?
>
> If /var is a separate partition/LV instead of on rootfs, this behavior occurs. Please post your fstab if unsure. Do you have any encrypted partitions or volumes? Please post the result of lsblk if yes.
>
I do not have any encrypted partitions, but /var is definitely separate:
/dev/sda3 /boot
/dev/sda5 /
/dev/sda6 /home
/dev/sda7 /var
Thanks,
Brian
10 years, 5 months
System mail (Fedora 20)
by Suvayu Ali
Hi,
I have a question.
On Tue, Dec 17, 2013 at 10:02:30AM -0500, Robyn Bergeron wrote:
>
> == No Default Sendmail, Syslog ==
>
> In the interests of paring down services that are generally not used
> on desktop systems, Fedora 20 removes and replaces some services that
> many users find unnecessary from the Live Desktop DVD. They will
> remain available as installable packages for users who might need
> them.
>
> The systemd journal now takes the place as the default logging
> solution for minimal and other selected installation methods, such as
> the Live Desktop DVD, having been tested and able to manage persistent
> logging in place of syslog.
>
> Also, Sendmail will no longer be installed by default, as most Fedora
> installs have no need of a Mail Transfer Agent (MTA).
Does this mean there won't be any system mail (e.g. mail from root, cron
jobs, etc)? I have never really used sendmail, but I always thought
system mail was handled by the default MTA; hence my question.
Thanks,
--
Suvayu
Open source is the future. It sets us free.
10 years, 5 months
Fedora features enquire and requirements
by Rahul Samaria
Hi Team,
As one of the best digital library software we want to implement Fedora for setting up digital library for our organization. However before starting I would like to know about a few features of Fedora which are essential parts of our requirements for setting up a library . Kindly clarify on below points.
- Repository of data having search functionality by title, keywords, meta tags and author
- Functionality to set roles of users with specified permission and set rules to access/edit/delete the content
- Storage and retrieval of long-term commitments content facilitate decision - making
- Data Storage of all data types (Documents, graphics, media, flash, source files, illustrator and vector files, etc.)
- Data can be accessed through internet and intranet
- Round the clock availability of information which accelerates any process
Please find our Annual Report for financial year 2012-13 : http://www.akshayapatra.org/annual-report-2013/index.html
Thanks & Regards,
Rahul Samaria
Web Administrator
The Akshaya Patra Foundation
Bangalore
080 30143400 Ext: 379
www.akshayapatra.org
Follows us @ [Description: youtube_icon_medium] <http://wwwyoutube.com/user/akshayapatra> [Description: facebook-icon] <http://www.facebook.com/TheAkshayapatraFoundation> [Description: twitter] <http://twitter.com/akshayapatra> [Description: googleplus-icon] <https://plus.google.com/u/0/103409264342204954520> [Description: 3icon_linkedin] <http://www.linkedin.com/company/the-akshaya-patra-foundation> [Description: Pinterest-Buttons-62-14-] <http://pinterest.com/akshayapatra/>
[Description: Description: signature_002]
No child in India will be deprived of education because of hunger
10 years, 5 months
Re: failed to ..
by Patrick Dupre
Thank for the recommendations.
Do not worry, I just set enforcing=0 1 time to get the relabelling
Then every thing is perfect.
>
> On 12/30/2013 07:01 AM, Chris Murphy wrote:
> >
> > On Dec 28, 2013, at 8:15 PM, Patrick Dupre <pdupre(a)gmx.com> wrote:
> >
> >> Hello,
> >>
> >> I tried to set relabel by using system-config-selinux,
> >> but nothing happens I have to keep selinux=0 to be able to boot!
> >
> > Try autorelabel=1, and in the future if you have selinux problems you don't want to troubeleshoot use enforcing=0. Disabling selinux is a hammer and eventually causes more problems.
> With all due respect, disabling SELinux *must not cause problems*.
>
> If it does, somebody is critically broken and needs to be fixed, ASAP.
>
> Ralf
>
> --
> users mailing list
> users(a)lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire de Physico-Chimie de l'Atmosphère | |
Université du Littoral-Côte d'Opale | |
Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44
189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===========================================================================
10 years, 5 months
I'm trying to install intel xdk
by William Biggs
I'm trying to install intel xdk software . Has any one got it to to
work ? If so how . it is asking for libudev.so.0 . I can not find it
10 years, 5 months
satellite - toshiba c55-a5286
by bruce
The system is unable to work with Centos 6.5 for connecting to the
network. Currently downloading FC20 to see if that makes a diffference
with the updated Kernel, or updated drivers.
Right now, when I do a centos install, the page that has the network
config is greyed out, so the install isn't seeing the card. As a
result, the NM/netowrk config from the System/Accessories menus
doesn't function.
So I suspect I need to resolve the issues after doing the initial
installation process.
The lspci gives:
01:00.0 Ethernet controller: Qualcomm Atheros AR8162 Fast Ethernet (rev 10)
Subsystem: Toshiba America Info Systems Device ff1e
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at c8500000 (64-bit, non-prefetchable) [size=256K]
I/O ports at 3000 [size=128]
Capabilities: [40] Power Management version 3
Capabilities: [58] Express Endpoint, MSI 00
Capabilities: [c0] MSI: Enable- Count=1/16 Maskable+ 64bit+
Capabilities: [d8] MSI-X: Enable- Count=16 Masked-
Capabilities: [100] Advanced Error Reporting
Capabilities: [180] Device Serial Number ff-6a-db-bd-00-8c-fa-ff
Kernel driver in use: alx
Kernel modules: alx
02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8188EE
Wireless Network Adapter (rev 01)
Subsystem: Realtek Semiconductor Co., Ltd. Device 0191
Flags: bus master, fast devsel, latency 0
I/O ports at 2000 [size=256]
Memory at c8400000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number 00-e0-4c-ff-fe-81-91-01
Capabilities: [150] Latency Tolerance Reporting
I'm unable to build on the system, as I can't access the netowrk to do
the yum, aside from whatever is already on the initial dvds for centos
6.5.
I've taken a look at the elrepos tree/site to see what might be
available for the solution.
I'm also looking to download/test other linux flavors to see
ifubuntu/mint/etc have the same issue with the wire/wireless
hardware/firmware.
Thoughts/Comments on how to resolve this would be helpful.
10 years, 5 months
fedup leaves half done 18 > 19
by sean darcy
I'm trying to upgrade FC18 to FC19. Ran fedup --network 19.
got this "non-fatal" error:
120.813] (II) fedup.yum:build_update_transaction()
systemd-sysv-201-2.fc18.9.x86_64 requires systemd = 201-2.fc18.9
120.815] (II) fedup.yum:build_update_transaction()
libgudev1-201-2.fc18.9.x86_64 requires systemd = 201-2.fc18.9
But seemed to work fine:
615.833] (II) fedup:<module>() /usr/bin/fedup exiting cleanly at Wed Dec
25 17:40:00 2013
Rebooted. Saw the start of the upgrade transaction. All seemed fine. Saw
first packages being installed.
Came back after a couple of hours. Screen blank.
Rebooted. No FC19. Booted into FC18.
Is there a log of what happened in the upgrade itself?
Now I have 1400 of fc19 packages installed.
rpm -qa | grep fc19 | wc -l
1406
but not the fc19 kernel.
All the fc18 packages are still there:
rpm -qa | grep fc18 | wc -l
1782
Tried to run fedup again, but no luck:
[ 190.819] (II) fedup.yum:build_update_transaction() buildTransaction
returned 1
[ 190.820] (II) fedup.yum:build_update_transaction() Depsolving
loop limit reached.
[ 190.821] (II) fedup.yum:build_update_transaction()
systemd-python-201-2.fc18.9.x86_64 requires systemd = 201-2.fc18.9
[ 190.822] (II) fedup.yum:build_update_transaction() avahi-ui-gtk3
conflicts with avahi-0.6.31-6.fc18.x86_64
[ 190.822] (II) fedup.yum:build_update_transaction()
libsss_sudo-1.9.6-1.fc18.x86_64 requires sssd = 1.9.6-1.fc18
[ 190.822] (II) fedup.yum:build_update_transaction()
systemd-sysv-201-2.fc18.9.x86_64 requires systemd = 201-2.fc18.9
[ 190.822] (II) fedup.yum:build_update_transaction()
libgudev1-201-2.fc18.9.x86_64 requires systemd = 201-2.fc18.9
[ 190.822] (II) fedup.yum:build_update_transaction() avahi-autoipd
conflicts with avahi-0.6.31-6.fc18.x86_64
[ 190.823] (II) fedup.yum:build_update_transaction()
PackageKit-0.8.9-1.fc18.x86_64 requires preupgrade
[ 190.823] (II) fedup.yum:build_update_transaction() avahi-libs
conflicts with avahi-0.6.31-6.fc18.x86_64
and then dies with a python error:
[ 240.965] (DD) fedup.yum:yum_plugin_for_exc() checking traceback
files: ['/usr/bin/fedup-cli', '/usr/bin/fedup-cli']
[ 240.965] (DD) fedup.yum:yum_plugin_for_exc() plugin path is
['/usr/share/yum-plugins', '/usr/lib/yum-plugins']
[ 240.965] (II) fedup:<module>() Exception:
Traceback (most recent call last):
File "/usr/bin/fedup-cli", line 236, in <module>
main(args)
File "/usr/bin/fedup-cli", line 216, in main
for line in s.format_details():
AttributeError: 'ProblemSummary' object has no attribute 'format_details'
[ 240.966] (II) fedup:<module>() /usr/bin/fedup-cli exiting with
unhandled exception at Thu Dec 26 10:45:19 2013
So I can't go forward with fedup. No clue what was the problem
upgrading. (there _really_ should be an upgrade log!)
Any help really appreciated.
sean
10 years, 5 months
Re: fedora update
by Patrick Dupre
Since I can access to all the rpm files on the DVD, I expected to find a tool to
verify the *.rpm files!
Does it not exist?
Something like rpm -Vp
>
> Patrick Dupre writes:
>
> > Hello,
> >
> > I burnt a DVD fedora 20 to update my distro.
>
> I do not believe that updating via the distro DVD images is implemented any
> more. You must use fedup to update.
>
> > However, it fails the test at 12.6%.
> > It there a risk to make an update using fedup?
>
> Yes.
>
> > I always have the option to download a package which may
> > be damaged.
>
> You are assuming that you will be able to boot at all, after skipping the
> damaged package.
>
> If the damaged package is glibc, or one of the critical gnome, systemd, or
> kernel packages, don't expect to be able to boot the resulting brick.
>
> Also, you do not know whether the remaining 88% of your DVD is any good at
> all.
>
> Besides, this is probably a moot point, since updating must be done via
> fedup.
>
> If you do happen to have a DVD image, you could skip downloading a bunch of
> stuff by using fedup --iso. But you don't need to actually burn the ISO
> image, for that, and, in fact, fedup does not support CD/DVD based updates
> (as I was amusingly informed on one of my machines by fedup, which was very
> convinced that my /home mount, with the DVD image, was a physical DVD drive).
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire de Physico-Chimie de l'Atmosphère | |
Université du Littoral-Côte d'Opale | |
Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44
189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===========================================================================
10 years, 5 months
