On Mon, 2013-12-16 at 00:37 -0500, James Antill wrote:
> > The most complex bug is #1043231. yum tries to keep track of what
> > package groups were installed as a result of the installation of what
> > environment groups, but this seems to be completely broken: it winds up
> > believing that no p
On Mon, 2013-12-16 at 00:37 -0500, James Antill wrote:
> > Oh, and based on reports I've read, I'd strongly recommend against
> > running 'yum group mark convert', as yum apparently suggests to you at
> > times. What this is supposed to do, roughly, is "convert" a legacy
> > system to 'groups as o
On Sun, 2013-12-15 at 01:10 -0800, Adam Williamson wrote:
> Oh, and based on reports I've read, I'd strongly recommend against
> running 'yum group mark convert', as yum apparently suggests to you at
> times. What this is supposed to do, roughly, is "convert" a legacy
> system to 'groups as object
On Sun, 2013-12-15 at 01:10 -0800, Adam Williamson wrote:
> On Sat, 2013-12-14 at 16:29 -0800, Adam Williamson wrote:
>
> > OK, I think I got as far as I can with this. I was wrong about some
> > things, above - I was reading /var/lib/yum/groups/installed wrong. It's
> > actually rather simpler th
On Sat, 2013-12-14 at 16:29 -0800, Adam Williamson wrote:
> OK, I think I got as far as I can with this. I was wrong about some
> things, above - I was reading /var/lib/yum/groups/installed wrong. It's
> actually rather simpler than I thought.
It was so simple I spent the rest of the day looking
On Sat, 2013-12-14 at 14:26 -0800, Adam Williamson wrote:
> On Wed, 2013-12-11 at 22:35 -0600, Michael Cronenworth wrote:
> > On 12/08/2013 08:37 AM, Mateusz Marzantowicz wrote:
> > > Curious, why it blew up right now, just before F20 is released. It
> > > should have happened in alpha and not now.
On Sat, 2013-12-14 at 14:26 -0800, Adam Williamson wrote:
> I managed to identify the specific change to yum which made these
> messages appear, and I think I know the attributes of the groups for
> which it appears: non-environment groups that are listed as installed
> in /var/lib/yum/groups/inst
On Wed, 2013-12-11 at 22:35 -0600, Michael Cronenworth wrote:
> On 12/08/2013 08:37 AM, Mateusz Marzantowicz wrote:
> > Curious, why it blew up right now, just before F20 is released. It
> > should have happened in alpha and not now.
> >
> > Workaround is to yum group mark remove for every group
>
Adam Pribyl wrote:
What happens if yum downloads again the groups info? BTW: I only have two 4bytes
long file in this directory, and have the same problem.
The files in the directory are created by yum and are not downloaded from a
repository. Removing the files will stop yum from using the gr
On Thu, 12 Dec 2013, Michael Cronenworth wrote:
Adam Pribyl wrote:
There is much more problems with groups in bugzilla, it affects F19 too.
You can "fix" this by using "yum mark remove " on all groups you get
a
warning they are missing (you have to have the latest yum - so yum update
yum).
Adam Pribyl wrote:
There is much more problems with groups in bugzilla, it affects F19 too.
You can "fix" this by using "yum mark remove " on all groups you get a
warning they are missing (you have to have the latest yum - so yum update yum).
You don't need to bother with this. If you read the
On Wed, 11 Dec 2013, Michael Cronenworth wrote:
On 12/08/2013 08:37 AM, Mateusz Marzantowicz wrote:
Curious, why it blew up right now, just before F20 is released. It
should have happened in alpha and not now.
Workaround is to yum group mark remove for every group
on the list. What a waste of
On 12 December 2013 06:35, Michael Cronenworth wrote:
> On 12/08/2013 08:37 AM, Mateusz Marzantowicz wrote:
>>
>> Curious, why it blew up right now, just before F20 is released. It
>> should have happened in alpha and not now.
>>
>> Workaround is to yum group mark remove for every group
>> on the
On 12/08/2013 08:37 AM, Mateusz Marzantowicz wrote:
Curious, why it blew up right now, just before F20 is released. It
should have happened in alpha and not now.
Workaround is to yum group mark remove for every group
on the list. What a waste of time.
Whatever you do - do not run "yum group m
On Sun, Dec 8, 2013 at 8:07 PM, Mateusz Marzantowicz <
mmarzantow...@osdf.com.pl> wrote:
> Curious, why it blew up right now, just before F20 is released. It
> should have happened in alpha and not now.
>
> Workaround is to yum group mark remove for every group
> on the list. What a waste of time
On 08.12.2013 12:35, Joachim Backes wrote:
> On 12/08/2013 11:45 AM, piruthiviraj natarajan wrote:
>>
>> On Sun, Dec 8, 2013 at 2:12 PM, Joachim Backes
>> mailto:joachim.bac...@rhrk.uni-kl.de>>
>> wrote:
>>
>> Hi piruthiviraj,
>>
>> seeing this on my box too:
>>
>> Warning: Environment
On 12/08/2013 11:45 AM, piruthiviraj natarajan wrote:
>
> On Sun, Dec 8, 2013 at 2:12 PM, Joachim Backes
> mailto:joachim.bac...@rhrk.uni-kl.de>>
> wrote:
>
> Hi piruthiviraj,
>
> seeing this on my box too:
>
> Warning: Environment Group mate-desktop-environment does not exist.
>
On Sun, Dec 8, 2013 at 2:12 PM, Joachim Backes <
joachim.bac...@rhrk.uni-kl.de> wrote:
> Hi piruthiviraj,
>
> seeing this on my box too:
>
> Warning: Environment Group mate-desktop-environment does not exist.
> Warning: group core does not exist.
> Warning: group multimedia does not exist.
> Warni
On 12/07/2013 04:13 PM, piruthiviraj natarajan wrote:
> I tried updating today. Yum is working.
> But I get weird warning about the groups.
> yum update -y
> updates-testing/20/x86_64/metalink | 7.2 kB
> 00:00
> Warning: group core does not exist.
> Warning: group mult
I tried updating today. Yum is working.
But I get weird warning about the groups.
yum update -y
updates-testing/20/x86_64/metalink | 7.2 kB
00:00
Warning: group core does not exist.
Warning: group multimedia does not exist.
Warning: group input-methods does not exist.
Warning:
20 matches
Mail list logo
