yum or dnf in the Fedora 22 Docker base image?

[M. Edward (Ed) Borasky]

Right now, the fedora:rawhide image on Docker Hub uses yum instead of
dnf, as does the Fedora 21 release. Is there any plan to switch this
release over to dnf?

I'm in the process of refactoring my remix - big pieces of it are
going into Docker images. I'm wondering if it's worth porting the main
workstation to dnf if the Docker pieces will still be on yum.

-- 
OSJourno: Robust Power Tools for Digital Journalists
http://www.znmeb.mobi/stories/osjourno-robust-power-tools-for-digital-jou...

Remember, if you're traveling to Bactria, Hump Day is Tuesday and Thursday.

[Jan Zelený]

On 14. 2. 2015 at 22:28:53, M. Edward  Borasky wrote:
>  Right now, the fedora:rawhide image on Docker Hub uses yum instead
> of
>  dnf, as does the Fedora 21 release. Is there any plan to switch this
>  release over to dnf? 
Not likely. Porting of the system components is being done in F22+. Even if 
all the system components were ported, dnf as default is a Change proposed for 
F22. Doing this in F21 would not be safe for countless reasons.

>  I'm in the process of refactoring my remix - big pieces of it
> are
>  going into Docker images. I'm wondering if it's worth porting the main
>  workstation to dnf if the Docker pieces will still be on yum. 
You will need to deal with such situation anyway, unless you migrate your 
containers to F22 (all at once) at some point in the future.

Thanks
Jan

[Daniel J Walsh]

On 02/16/2015 02:32 AM, Jan Zelený wrote:
>  On 14. 2. 2015 at 22:28:53, M. Edward  Borasky wrote:
> > Right now, the fedora:rawhide image on Docker Hub uses yum instead of
> > dnf, as does the Fedora 21 release. Is there any plan to switch this
> > release over to dnf?
>  Not likely. Porting of the system components is being done in F22+. Even if 
>  all the system components were ported, dnf as default is a Change proposed for 
>  F22. Doing this in F21 would not be safe for countless reasons. 
I think the F22 and
Rawhide (Is it F23 at this point), should both use dnf
not yum.  We need to get more testing on dnf in containers.
> > I'm in the process of refactoring my remix - big pieces of it
> are
> > going into Docker images. I'm wondering if it's worth porting the main
> > workstation to dnf if the Docker pieces will still be on yum.
>  You will need to deal with such situation anyway, unless you migrate your 
>  containers to F22 (all at once) at some point in the future.
>
>  Thanks
>  Jan

[M. Edward (Ed) Borasky]

On Mon, Feb 16, 2015 at 5:19 AM, Daniel J Walsh <dwalsh(a)redhat.com&gt; wrote:

>  I think the F22 and Rawhide (Is it F23 at this point), should both
> use dnf
>  not yum.  We need to get more testing on dnf in containers. 
I'm ready to start testing F22 containers either way and would prefer
dnf. What's the best process to get this rolling? Who owns the image -
release engineering or Project Atomic? The reason I ask is that
Project Atomic has their own mailing list and uses Trac, not the Red
Hat Bugzilla, for issue tracking.

Either way, my main upstream component (RStudio Server) may end up
stuck with F21 - it doesn't link with the latest Boost right now and
they only support CentOS and Debian/Ubuntu.
-- 
OSJourno: Robust Power Tools for Digital Journalists
http://www.znmeb.mobi/stories/osjourno-robust-power-tools-for-digital-jou...

Remember, if you're traveling to Bactria, Hump Day is Tuesday and Thursday.

[Daniel J Walsh]

On 02/16/2015 12:31 PM, M. Edward (Ed) Borasky wrote:
>  On Mon, Feb 16, 2015 at 5:19 AM, Daniel J Walsh
> <dwalsh(a)redhat.com&gt; wrote:
>
> > I think the F22 and Rawhide (Is it F23 at this point), should both use dnf
> > not yum.  We need to get more testing on dnf in containers.
>  I'm ready to start testing F22 containers either way and would prefer
>  dnf. What's the best process to get this rolling? Who owns the image -
>  release engineering or Project Atomic? The reason I ask is that
>  Project Atomic has their own mailing list and uses Trac, not the Red
>  Hat Bugzilla, for issue tracking.
>
>  Either way, my main upstream component (RStudio Server) may end up
>  stuck with F21 - it doesn't link with the latest Boost right now and
>  they only support CentOS and Debian/Ubuntu. 
Vaclav is handling this right now.  I
don't see this as owned by
ProjectAtomic.

[M. Edward (Ed) Borasky]

Thanks! Are there tracking bugs in Bugzilla I can subscribe to?

On Mon, Feb 16, 2015 at 9:42 AM, Daniel J Walsh <dwalsh(a)redhat.com&gt; wrote:
>  On 02/16/2015 12:31 PM, M. Edward (Ed) Borasky wrote:
> > On Mon, Feb 16, 2015 at 5:19 AM, Daniel J Walsh <dwalsh(a)redhat.com&gt; wrote:
> >
> >> I think the F22 and Rawhide (Is it F23 at this point), should both use dnf
> >> not yum.  We need to get more testing on dnf in containers.
> > I'm ready to start testing F22 containers either way and would prefer
> > dnf. What's the best process to get this rolling? Who owns the image -
> > release engineering or Project Atomic? The reason I ask is that
> > Project Atomic has their own mailing list and uses Trac, not the Red
> > Hat Bugzilla, for issue tracking.
> >
> > Either way, my main upstream component (RStudio Server) may end up
> > stuck with F21 - it doesn't link with the latest Boost right now and
> > they only support CentOS and Debian/Ubuntu.
>  Vaclav is handling this right now.  I don't see this as owned by
>  ProjectAtomic.
>  --
>  devel mailing list
>  devel(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/devel
>  Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct 


-- 
OSJourno: Robust Power Tools for Digital Journalists
http://www.znmeb.mobi/stories/osjourno-robust-power-tools-for-digital-jou...

Remember, if you're traveling to Bactria, Hump Day is Tuesday and Thursday.

[Daniel J Walsh]

Not that I know of.
On 02/16/2015 09:50 AM, M. Edward (Ed) Borasky wrote:
>  Thanks! Are there tracking bugs in Bugzilla I can subscribe to?
>
>  On Mon, Feb 16, 2015 at 9:42 AM, Daniel J Walsh <dwalsh(a)redhat.com&gt; wrote:
> > On 02/16/2015 12:31 PM, M. Edward (Ed) Borasky wrote:
> >> On Mon, Feb 16, 2015 at 5:19 AM, Daniel J Walsh <dwalsh(a)redhat.com&gt; wrote:
> >>
> >>> I think the F22 and Rawhide (Is it F23 at this point), should both use dnf
> >>> not yum.  We need to get more testing on dnf in containers.
> >> I'm ready to start testing F22 containers either way and would prefer
> >> dnf. What's the best process to get this rolling? Who owns the image -
> >> release engineering or Project Atomic? The reason I ask is that
> >> Project Atomic has their own mailing list and uses Trac, not the Red
> >> Hat Bugzilla, for issue tracking.
> >>
> >> Either way, my main upstream component (RStudio Server) may end up
> >> stuck with F21 - it doesn't link with the latest Boost right now and
> >> they only support CentOS and Debian/Ubuntu.
> > Vaclav is handling this right now.  I don't see this as owned by
> > ProjectAtomic.
> > --
> > devel mailing list
> > devel(a)lists.fedoraproject.org
> > https://admin.fedoraproject.org/mailman/listinfo/devel
> > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
>
>

[Václav Pavlín]

On 17.2.2015 12:33, Daniel J Walsh wrote:
>  Not that I know of.
>  On 02/16/2015 09:50 AM, M. Edward (Ed) Borasky wrote:
> > Thanks! Are there tracking bugs in Bugzilla I can subscribe to? 
I don't
think there are any - feel free to file it.
> >
> > On Mon, Feb 16, 2015 at 9:42 AM, Daniel J Walsh <dwalsh(a)redhat.com&gt; wrote:
> >> On 02/16/2015 12:31 PM, M. Edward (Ed) Borasky wrote:
> >>> On Mon, Feb 16, 2015 at 5:19 AM, Daniel J Walsh <dwalsh(a)redhat.com&gt;
> wrote:
> >>>
> >>>> I think the F22 and Rawhide (Is it F23 at this point), should both use
> dnf
> >>>> not yum.  We need to get more testing on dnf in containers.
> >>> I'm ready to start testing F22 containers either way and would prefer
> >>> dnf. What's the best process to get this rolling? Who owns the image -
> >>> release engineering or Project Atomic? The reason I ask is that
> >>> Project Atomic has their own mailing list and uses Trac, not the Red
> >>> Hat Bugzilla, for issue tracking.
> >>>
> >>> Either way, my main upstream component (RStudio Server) may end up
> >>> stuck with F21 - it doesn't link with the latest Boost right now and
> >>> they only support CentOS and Debian/Ubuntu.
> >> Vaclav is handling this right now.  I don't see this as owned by
> >> ProjectAtomic. 
The problem currently is I am not able to build any Fedora
image due to 
some Anaconda problems. I'll get back to you as soon as I have something 
helpful.

Vašek
> >> --
> >> devel mailing list
> >> devel(a)lists.fedoraproject.org
> >> https://admin.fedoraproject.org/mailman/listinfo/devel
> >> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> > 
-- 

Lead Infrastructure Engineer
Developer Experience
Brno, Czech Republic

[M. Edward (Ed) Borasky]

I've got a build process that uses Live Media Creator instead of Image
Factory if it'll help - see
https://bitbucket.org/znmeb/osjourno/src/344cb38b042e352f6198e789ddeeb865...

On Wed, Feb 18, 2015 at 1:06 AM, Václav Pavlín <vpavlin(a)redhat.com&gt; wrote:
>  On 17.2.2015 12:33, Daniel J Walsh wrote:
> >
> > Not that I know of.
> > On 02/16/2015 09:50 AM, M. Edward (Ed) Borasky wrote:
> >>
> >> Thanks! Are there tracking bugs in Bugzilla I can subscribe to?
>
>  I don't think there are any - feel free to file it.
> >>
> >>
> >> On Mon, Feb 16, 2015 at 9:42 AM, Daniel J Walsh <dwalsh(a)redhat.com&gt;
> >> wrote:
> >>>
> >>> On 02/16/2015 12:31 PM, M. Edward (Ed) Borasky wrote:
> >>>>
> >>>> On Mon, Feb 16, 2015 at 5:19 AM, Daniel J Walsh
> <dwalsh(a)redhat.com&gt;
> >>>> wrote:
> >>>>
> >>>>> I think the F22 and Rawhide (Is it F23 at this point), should both
> use
> >>>>> dnf
> >>>>> not yum.  We need to get more testing on dnf in containers.
> >>>>
> >>>> I'm ready to start testing F22 containers either way and would
> prefer
> >>>> dnf. What's the best process to get this rolling? Who owns the image
> -
> >>>> release engineering or Project Atomic? The reason I ask is that
> >>>> Project Atomic has their own mailing list and uses Trac, not the Red
> >>>> Hat Bugzilla, for issue tracking.
> >>>>
> >>>> Either way, my main upstream component (RStudio Server) may end up
> >>>> stuck with F21 - it doesn't link with the latest Boost right now and
> >>>> they only support CentOS and Debian/Ubuntu.
> >>>
> >>> Vaclav is handling this right now.  I don't see this as owned by
> >>> ProjectAtomic.
>
>  The problem currently is I am not able to build any Fedora image due to some
>  Anaconda problems. I'll get back to you as soon as I have something helpful.
>
>  Vašek
> >>>
> >>> --
> >>> devel mailing list
> >>> devel(a)lists.fedoraproject.org
> >>> https://admin.fedoraproject.org/mailman/listinfo/devel
> >>> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> >>
> >>
>
>  --
>
>  Lead Infrastructure Engineer
>  Developer Experience
>  Brno, Czech Republic
>
>
>  --
>  devel mailing list
>  devel(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/devel
>  Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct 


-- 
OSJourno: Robust Power Tools for Digital Journalists
http://www.znmeb.mobi/stories/osjourno-robust-power-tools-for-digital-jou...

Remember, if you're traveling to Bactria, Hump Day is Tuesday and Thursday.