COPR rawhide repo links

[Michal Novotny]

Dear rawhide users,

if you have enabled a COPR repo in the last three months (since the
beginning of December last year till yesterday), then it points to
fedora-$releasever-$basearch. You can reenable it by using `dnf copr enable
<project>` to get .repo file pointing to actual fedora-rawhide chroot in
the given project.

Sorry for this
clime

[Vít Ondruch]

I don't understand what are you doing again and again with the
repository settings. Looking at my doublecmd repository [1], I am
missing F25 versions there and neither it works for my rawhide:


~~~

Failed to synchronize cache for repo 'vondruch-doublecmd', disabling.

~~~


I don't want to update my project just because there was some branching.
I don't need to care about it in Fedora, so why it does not work in
Copr? Or was this change to keep it working from now forewer?


Vít


[1] https://copr.fedorainfracloud.org/coprs/vondruch/doublecmd/


Dne 4.3.2017 v 10:00 Michal Novotny napsal(a):
>  Dear rawhide users,
>
>  if you have enabled a COPR repo in the last three months (since the
>  beginning of December last year till yesterday), then it points to
>  fedora-$releasever-$basearch. You can reenable it by using `dnf copr
>  enable <project>` to get .repo file pointing to actual fedora-rawhide
>  chroot in the given project.
>
>  Sorry for this
>  clime
>
>
>  _______________________________________________
>  copr-devel mailing list -- copr-devel(a)lists.fedorahosted.org
>  To unsubscribe send an email to copr-devel-leave(a)lists.fedorahosted.org

[Michal Novotny]

Hey Vit,

On Mon, Mar 6, 2017 at 1:20 PM, Vít Ondruch <vondruch(a)redhat.com&gt; wrote:

>  I don't understand what are you doing again and again with the
> repository
>  settings. Looking at my doublecmd repository [1], I am missing F25 versions
>  there and neither it works for my rawhide:
>  
Missing f25 chroot in your project means you probably haven't added it.


The package is not available in rawhide because it needs to be rebuilt for
the rawhide chroot now when the rawhide chroot was added back as a new
chroot.


I am very sorry for this inconvenience and if it is too much of a trouble,
let us know and perhaps we can figure out how to make it easier. We can
e.g. copy your builds from f26 to the rawhide chroot but such builds won't
be in our db nor in dist-git. That's why this wasn't done automatically.

>  ~~~
>
>  Failed to synchronize cache for repo 'vondruch-doublecmd', disabling.
>
>  ~~~
>
>
>  I don't want to update my project just because there was some branching. I
>  don't need to care about it in Fedora, so why it does not work in Copr? Or
>  was this change to keep it working from now forewer?
>  
 The last change - returning rawhide - was to keep it working like this
from now. There was not any other change in this regard. The email was just
a follow-up info. I am very sorry for the trouble and we will make sure we
do our best to alleviate any issues, whether related to this or not, and
bring the best possible features from now on. We will make sure we provide
means you will not need to care about branching next time.

For COPR team
clime

>  Vít
>
>
>  [1] https://copr.fedorainfracloud.org/coprs/vo is ndruch/doublecmd/
>  <https://copr.fedorainfracloud.org/coprs/vondruch/doublecmd/>
>
>  Dne 4.3.2017 v 10:00 Michal Novotny napsal(a):
>
>  Dear rawhide users,
>
>  if you have enabled a COPR repo in the last three months (since the
>  beginning of December last year till yesterday), then it points to
>  fedora-$releasever-$basearch. You can reenable it by using `dnf copr enable
>  <project>` to get .repo file pointing to actual fedora-rawhide chroot in
>  the given project.
>
>  Sorry for this
>  clime
>
>
>  _______________________________________________
>  copr-devel mailing list -- copr-devel(a)lists.fedorahosted.org
>  To unsubscribe send an email to copr-devel-leave(a)lists.fedorahosted.org
>
>
>
>  _______________________________________________
>  copr-devel mailing list -- copr-devel(a)lists.fedorahosted.org
>  To unsubscribe send an email to copr-devel-leave(a)lists.fedorahosted.org
>
>

[Vít Ondruch]

Dne 6.3.2017 v 14:54 Michal Novotny napsal(a):
>  Hey Vit,
>
>  On Mon, Mar 6, 2017 at 1:20 PM, Vít Ondruch <vondruch(a)redhat.com
>  <mailto:[e-mail]>> wrote:
>
>      I don't understand what are you doing again and again with the
>      repository settings. Looking at my doublecmd repository [1], I am
>      missing F25 versions there and neither it works for my rawhide:
>
>
>  Missing f25 chroot in your project means you probably haven't added it.
>
>
>  The package is not available in rawhide because it needs to be rebuilt
>  for the rawhide chroot now when the rawhide chroot was added back as a
>  new chroot.
>   
>
>  I am very sorry for this inconvenience and if it is too much of a
>  trouble, let us know and perhaps we can figure out how to make it
>  easier. We can e.g. copy your builds from f26 to the rawhide chroot
>  but such builds won't be in our db nor in dist-git. That's why this
>  wasn't done automatically. 
Well, Rawhide should be always rawhide. If there is new branch (e.g.
F26), you should branch the dist-git and copy/clone/symlink/hardlink the
content of Rawhide into the branch. This is how Fedora works, so I would
appreciate if Copr can follow that pattern.

The case with the F25 is apparently of similar issue :/


>      ~~~
>
>      Failed to synchronize cache for repo 'vondruch-doublecmd', disabling.
>
>      ~~~
>
>
>      I don't want to update my project just because there was some
>      branching. I don't need to care about it in Fedora, so why it does
>      not work in Copr? Or was this change to keep it working from now
>      forewer?
>
>   The last change - returning rawhide - was to keep it working like
>  this from now. There was not any other change in this regard. 
The $releasever and rawhide should be equivalent IMO, no matter what is
written in the config file. Both should work.

Also, if you check the "fedora.repo" on Rawhide, it contains $releasever
variable and it allows me to specify --releasever parameter for DNF and
use older repository in case I need it. I use it to get stable kernels
for Rawhide for example, but in this case, this would actually allowed
me to workaround the missing Rawhide build ....

>  The email was just a follow-up info. I am very sorry for the trouble
>  and we will make sure we do our best to alleviate any issues, whether
>  related to this or not, and bring the best possible features from now
>  on. We will make sure we provide means you will not need to care about
>  branching next time. 
Thx. I appreciate that.


Vít

[Vít Ondruch]

Dne 6.3.2017 v 15:24 Vít Ondruch napsal(a):
>  Dne 6.3.2017 v 14:54 Michal Novotny napsal(a):
> > Hey Vit,
> >
> > On Mon, Mar 6, 2017 at 1:20 PM, Vít Ondruch <vondruch(a)redhat.com
> > <mailto:[e-mail]>> wrote:
> >
> >     I don't understand what are you doing again and again with the
> >     repository settings. Looking at my doublecmd repository [1], I am
> >     missing F25 versions there and neither it works for my rawhide:
> >
> >
> > Missing f25 chroot in your project means you probably haven't added it.
> >
> >
> > The package is not available in rawhide because it needs to be
> > rebuilt for the rawhide chroot now when the rawhide chroot was added
> > back as a new chroot.
> >  
> >
> > I am very sorry for this inconvenience and if it is too much of a
> > trouble, let us know and perhaps we can figure out how to make it
> > easier. We can e.g. copy your builds from f26 to the rawhide chroot
> > but such builds won't be in our db nor in dist-git. That's why this
> > wasn't done automatically.
>
>  Well, Rawhide should be always rawhide. If there is new branch (e.g.
>  F26), you should branch the dist-git and copy/clone/symlink/hardlink
>  the content of Rawhide into the branch. This is how Fedora works, so I
>  would appreciate if Copr can follow that pattern.
>
>  The case with the F25 is apparently of similar issue :/
>
>
> >     ~~~
> >
> >     Failed to synchronize cache for repo 'vondruch-doublecmd', disabling.
> >
> >     ~~~
> >
> >
> >     I don't want to update my project just because there was some
> >     branching. I don't need to care about it in Fedora, so why it
> >     does not work in Copr? Or was this change to keep it working from
> >     now forewer?
> >
> >  The last change - returning rawhide - was to keep it working like
> > this from now. There was not any other change in this regard.
>
>  The $releasever and rawhide should be equivalent IMO, no matter what
>  is written in the config file. Both should work.
>
>  Also, if you check the "fedora.repo" on Rawhide, it contains
>  $releasever variable and it allows me to specify --releasever
>  parameter for DNF and use older repository in case I need it. I use it
>  to get stable kernels for Rawhide for example, but in this case, this
>  would actually allowed me to workaround the missing Rawhide build .... 
Actually, this was not precise, because fedora-rawhide.repo does not use
the $releasever variable. But there is still fedora.repo installed,
which I can enable ....


Vít


> > The email was just a follow-up info. I am very sorry for the trouble
> > and we will make sure we do our best to alleviate any issues, whether
> > related to this or not, and bring the best possible features from now
> > on. We will make sure we provide means you will not need to care
> > about branching next time.
>
>  Thx. I appreciate that.
>
>
>  Vít
>
>
>
>  _______________________________________________
>  copr-devel mailing list -- copr-devel(a)lists.fedorahosted.org
>  To unsubscribe send an email to copr-devel-leave(a)lists.fedorahosted.org