I'm re-testing fedup f20-f21 this morning. I get:
sudo fedup --network 21 --product=nonproduct
...
getting boot images...
.treeinfo.signed
| 1.8 kB 00:00:00
Downloading failed: invalid data in .treeinfo: File contains
I'm re-testing fedup f20-f21 this morning. I get:
sudo fedup --network 21 --product=nonproduct
...
getting boot images...
.treeinfo.signed
| 1.8 kB 00:00:00
Downloading failed: invalid data in .treeinfo: File contains no section
headers.
file: /var/cache/system-upgrade/.treeinfo,
On 12/8/2014 5:52 AM, Kamil Paral wrote:
I'm re-testing fedup f20-f21 this morning. I get:
sudo fedup --network 21 --product=nonproduct
...
getting boot images...
.treeinfo.signed
| 1.8 kB 00:00:00
Downloading failed: invalid data in .treeinfo: File contains no section
headers.
file:
On Tue, 2014-12-09 at 06:12 -0800, Thomas Gilliard wrote:
On 12/8/2014 5:52 AM, Kamil Paral wrote:
I'm re-testing fedup f20-f21 this morning. I get:
sudo fedup --network 21 --product=nonproduct
...
getting boot images...
.treeinfo.signed
| 1.8 kB 00:00:00
Downloading failed:
On 11/07/2014 05:34 PM, Adam Williamson wrote:
On Fri, 2014-11-07 at 16:48 -0800, Per Bothner wrote:
I wanted to try to updating to what will soon be Fedora 21.
I tried using fedup, but failed miserably. Did I use the correct incantation?
Well. Not according to the release information,
On Sat, 2014-11-08 at 00:13 -0800, Per Bothner wrote:
Then when I tried:
fedup --network 21 -v --product=workstation
--debuglog=/var/log/fedupdebug4.log
it worked. I'm using Fedora 21/rawhide now.
These are not the same thing. Rawhide is now F22. See
On 11/08/2014 12:46 AM, Adam Williamson wrote:
Can you run 'rpm -qa | grep fc22' and verify you have no Fedora 22
packages installed? You should not. Thanks!
Just one:
$ sudo rpm -qa | grep fc22
shim-unsigned-0.8-1.fc22.x86_64
I'm afraid I don't know what that is.
--
--Per Bothner
On Sat, 2014-11-08 at 10:06 -0800, Per Bothner wrote:
On 11/08/2014 12:46 AM, Adam Williamson wrote:
Can you run 'rpm -qa | grep fc22' and verify you have no Fedora 22
packages installed? You should not. Thanks!
Just one:
$ sudo rpm -qa | grep fc22
shim-unsigned-0.8-1.fc22.x86_64
On 11/08/2014 11:14 AM, Adam Williamson wrote:
Ah, that's actually fine. As a special case, the fc22 build of shim was
sent to all supported releases as it cuts down on the Secure Boot
signing/verification work - we don't have to verify four
actually-the-same builds of shim. So, looks fine.
I wanted to try to updating to what will soon be Fedora 21.
I tried using fedup, but failed miserably. Did I use the correct incantation?
All the references to fc22 are ... surprising.
# fedup --network 21 --product=workstation --debuglog=/var/log/fedupdebug.log
setting up repos...
On Fri, 2014-11-07 at 16:48 -0800, Per Bothner wrote:
I wanted to try to updating to what will soon be Fedora 21.
I tried using fedup, but failed miserably. Did I use the correct incantation?
Well. Not according to the release information, which we've been waving
all over the place lately:
On 04/25/2014 04:30 PM, Rick Stevens issued this missive:
On 04/25/2014 02:54 PM, Adam Williamson issued this missive:
On Fri, 2014-04-25 at 11:49 -0700, Samuel Sieb wrote:
On 04/25/2014 11:42 AM, Rick Stevens wrote:
Yup, I have yum-plugin-local installed. I'll kill it off and remove the
On Mon, 2014-04-28 at 15:42 -0700, Rick Stevens wrote:
Thanks again for the help. I may be back for more. I hope not, but the
way my luck goes...
Well, as suspected, it crapped out again. I get this at the end of
the fedup command:
Traceback (most recent call last):
On 04/28/2014 03:49 PM, Adam Williamson issued this missive:
On Mon, 2014-04-28 at 15:42 -0700, Rick Stevens wrote:
Thanks again for the help. I may be back for more. I hope not, but the
way my luck goes...
Well, as suspected, it crapped out again. I get this at the end of
the fedup
On 04/28/2014 03:42 PM, Rick Stevens wrote:
Prior to that, I get a ridiculous amount of package conflict errors,
most invoving perl:
perl-Params-Classify-0.013-7.fc19.x86_64 requires
perl-4:5.16.3-266.fc19.x86_64
That looks more like part of a broken dependency chain. For example
maybe
On 04/28/2014 04:15 PM, Samuel Sieb issued this missive:
On 04/28/2014 03:42 PM, Rick Stevens wrote:
Prior to that, I get a ridiculous amount of package conflict errors,
most invoving perl:
perl-Params-Classify-0.013-7.fc19.x86_64 requires
perl-4:5.16.3-266.fc19.x86_64
That looks more
On Mon, 2014-04-28 at 16:11 -0700, Rick Stevens wrote:
On 04/28/2014 03:49 PM, Adam Williamson issued this missive:
On Mon, 2014-04-28 at 15:42 -0700, Rick Stevens wrote:
Thanks again for the help. I may be back for more. I hope not, but the
way my luck goes...
Well, as
On Mon, 2014-04-28 at 16:41 -0700, Rick Stevens wrote:
On 04/28/2014 04:15 PM, Samuel Sieb issued this missive:
On 04/28/2014 03:42 PM, Rick Stevens wrote:
Prior to that, I get a ridiculous amount of package conflict errors,
most invoving perl:
Hi, gang.
I ran into a nasty trying to upgrade one of my machines from F19 to F20.
Two other machines upgraded without issues, but this one is rather
nasty.
I did an initial fedup --network 20 on the F19 box and ran into the
famous google-chrome repo issue, so I reran it with a
On 04/25/2014 10:25 AM, Samuel Sieb issued this missive:
On 04/25/2014 10:12 AM, Rick Stevens wrote:
I'm afraid this machine is now in a very sick state and I'm petrified
that, should I lose power or something else happens that will cause it
to reboot, it's going to be dead.
If all you've
On 04/25/2014 10:44 AM, Rick Stevens wrote:
I did a yum clean which completed with no errors. There is no
/var/tmp/system-upgrade directory that I can find (a lot of old systemd
stuff though, so I purged that).
/var/tmp/fedora-upgrade maybe? Are you sure you have the latest fedup?
Maybe
On 04/25/2014 10:59 AM, Samuel Sieb issued this missive:
On 04/25/2014 10:44 AM, Rick Stevens wrote:
I did a yum clean which completed with no errors. There is no
/var/tmp/system-upgrade directory that I can find (a lot of old systemd
stuff though, so I purged that).
/var/tmp/fedora-upgrade
On 04/25/2014 11:42 AM, Rick Stevens wrote:
Yup, I have yum-plugin-local installed. I'll kill it off and remove the
/var/lib/yum/plugins/local RPMs.
Now, assuming I clean all that cruft up (getting rid of the plugin-local
stuff, getting rid of the RPMs), how do I proceed with the upgrade?
It
On Fri, 2014-04-25 at 11:49 -0700, Samuel Sieb wrote:
On 04/25/2014 11:42 AM, Rick Stevens wrote:
Yup, I have yum-plugin-local installed. I'll kill it off and remove the
/var/lib/yum/plugins/local RPMs.
Now, assuming I clean all that cruft up (getting rid of the plugin-local
stuff,
On 04/25/2014 02:54 PM, Adam Williamson issued this missive:
On Fri, 2014-04-25 at 11:49 -0700, Samuel Sieb wrote:
On 04/25/2014 11:42 AM, Rick Stevens wrote:
Yup, I have yum-plugin-local installed. I'll kill it off and remove the
/var/lib/yum/plugins/local RPMs.
Now, assuming I clean all
Hi Gang:
I just tried a fedup 20 and got the following after it showed some upgrade
files:
testing upgrade transaction
Traceback (most recent call last):
File /bin/fedup-cli, line 181, in module
main(args)
File /bin/fedup-cli, line 128, in main
transaction_test(pkgs)
File
On 08.12.2013 18:42, Richard Vickery wrote:
Hi Gang:
I just tried a fedup 20 and got the following after it showed some
upgrade files:
testing upgrade transaction
Traceback (most recent call last):
File /bin/fedup-cli, line 181, in module
main(args)
File /bin/fedup-cli, line
On Sun, Dec 8, 2013 at 11:48 AM, Mateusz Marzantowicz
mmarzantow...@osdf.com.pl wrote:
On 08.12.2013 18:42, Richard Vickery wrote:
Hi Gang:
I just tried a fedup 20 and got the following after it showed some
upgrade files:
testing upgrade transaction
Traceback (most recent call
28 matches
Mail list logo
