On 08/10/2017 06:46 PM, Ravindra Kumar wrote:
> I forgot to mention that Bodhi web interface did not offer any
> suggestions when I typed 'open-vm-tools' package name. This was bit
> surprising and I could not use Bodhi web interface as a workaround.
This is a known issue and is planned to be fixe
3:44 PM
To: Development discussions related to Fedora
Subject: Re: Unable to push update
> Oh wait, this is actually a bug:
> https://bugzilla.redhat.com/show_bug.cgi?id=1445294
> You need to ensure you are updated to
> bodhi >= 2.6.2
> python-fedora >= 0.9.0-3.fc25
Than
> Oh wait, this is actually a bug:
> https://bugzilla.redhat.com/show_bug.cgi?id=1445294
> You need to ensure you are updated to
> bodhi >= 2.6.2
> python-fedora >= 0.9.0-3.fc25
Thanks Rich. Looks like there is no bodhi package, but updating python-fedora
package fixed it.
Thanks,
Ravindra
Oh wait, this is actually a bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1445294
You need to ensure you are updated to
bodhi >= 2.6.2
python-fedora >= 0.9.0-3.fc25
Try ‘dnf update’ and then run the update command again.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://
On Thu, Aug 10, 2017 at 10:19:04PM +, Ravindra Kumar wrote:
> Hi,
>
>
> I have a new build for my package -
> https://koji.fedoraproject.org/koji/buildinfo?buildID=953883.
>
>
> However, when I try 'fedpkg update' for the new build, command fails
> with following error:
>
> https://gist.git
Hi,
I have a new build for my package -
https://koji.fedoraproject.org/koji/buildinfo?buildID=953883.
However, when I try 'fedpkg update' for the new build, command fails with
following error:
https://gist.github.com/ravindravmw/5bbbedff0785980e5b8e3f93ef2417d6
I have tried it multiple tim
On 13/02/13 07:38 PM, Kevin Kofler wrote:
Jochen Schmitt wrote:
He explained me, that he also unable to push the package to the
stable repository and told me, that this package is in crithpath
and may improvement of an proventester.
Why the heck is Emacs in the critical path in the first place
Jochen Schmitt wrote:
> He explained me, that he also unable to push the package to the
> stable repository and told me, that this package is in crithpath
> and may improvement of an proventester.
Why the heck is Emacs in the critical path in the first place???
Kevin Kofler
--
devel mai
> Wait 4 more days or get 2 more karma. IIRC, critpath updates have to
> wait for 2 weeks before they can be pushed if they do not have sufficient
> karma.
More testing is preferable, of course. I'd help except I don't know my way
around emacs.
--
Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁
On Wed, 13 Feb 2013 16:24:07 +0100, Jochen Schmitt wrote:
> Hello,
>
> as an provenpackage I have introduced an upstream patch to Emacs
> and have create an update in bodhi. After ten days I have to recognize,
> that I'm unable to push this update to the stable repository because there
> is no 'm
On Wed, Feb 13, 2013 at 10:24 AM, Jochen Schmitt wrote:
> Hello,
>
> as an provenpackage I have introduced an upstream patch to Emacs
> and have create an update in bodhi. After ten days I have to recognize,
> that I'm unable to push this update to the stable repository because there
> is no 'mark
Hello,
as an provenpackage I have introduced an upstream patch to Emacs
and have create an update in bodhi. After ten days I have to recognize,
that I'm unable to push this update to the stable repository because there
is no 'mark as stable' link on the UI. So I have ask the owner of the
package f
12 matches
Mail list logo
