Nightly builds of DNF available

[Radek Holy]

Dear all,

I am glad to announce the launch of continuous integration job for DNF. Each change now
starts the bunch of DNF tests on top of upstream versions of hawkey, librepo and
libcomps.

It also means that from now nightly builds of DNF and its dependencies are available to
you. Download them at will from
http://jenkins.cloud.fedoraproject.org/job/DNF/lastSuccessfulBuild/artifact/. To check
presence of new builds please follow the RSS channel
http://jenkins.cloud.fedoraproject.org/job/DNF/rssAll.

Best regards
-- 
Radek Holý
Associate Software Engineer
Software Management Team
Red Hat Czech

[Richard Hughes]

On 29 January 2014 16:03, Radek Holy <rholy(a)redhat.com&gt; wrote:
>  I am glad to announce the launch of continuous integration job for
> DNF. Each change now starts the bunch of DNF tests on top of upstream versions of hawkey,
> librepo and libcomps. 
Great news, thanks for doing this. Is there any more documentation on
libcomps yet? i.e. is it stable enough to use now?

Richard

[Ales Kozumplik]

On 01/29/2014 05:05 PM, Richard Hughes wrote:
>  Great news, thanks for doing this. Is there any more documentation
> on
>  libcomps yet? i.e. is it stable enough to use now? 
There is at least: https://github.com/midnightercz/libcomps/wiki

But ask Jindrich.

Ales

[Mikolaj Izdebski]

On 01/29/2014 05:03 PM, Radek Holy wrote:
>  I am glad to announce the launch of continuous integration job for
> DNF. Each change now starts the bunch of DNF tests on top of upstream versions of hawkey,
> librepo and libcomps.
>  
>  It also means that from now nightly builds of DNF and its dependencies are available to
> you. Download them at will from
> http://jenkins.cloud.fedoraproject.org/job/DNF/lastSuccessfulBuild/artifact/. To check
> presence of new builds please follow the RSS channel
> http://jenkins.cloud.fedoraproject.org/job/DNF/rssAll. 
Wouldn't it make sense to create YUM metadata so that people can
automatically update DNF with itself?

XMvn project which uses Fedora Jenkins instance does that, see:
http://jenkins.cloud.fedoraproject.org/job/xmvn/ws/RPM/latest/

That works well for me.  In my yum.conf I have:

[jenkins-xmvn]
name=jenkins-xmvn
baseurl=http://jenkins.cloud.fedoraproject.org/job/xmvn/ws/RPM/latest
cost=3000

-- 
Mikolaj Izdebski
IRC: mizdebsk

[Radek Holy]

I have just added the metadata creation. Good point, thank you.
-- 
Radek Holý
Associate Software Engineer
Software Management Team
Red Hat Czech



----- Original Message -----
From: "Mikolaj Izdebski" <mizdebsk(a)redhat.com&gt;
To: devel(a)lists.fedoraproject.org
Sent: Wednesday, January 29, 2014 5:18:41 PM
Subject: Re: Nightly builds of DNF available

On 01/29/2014 05:03 PM, Radek Holy wrote:
>  I am glad to announce the launch of continuous integration job for
> DNF. Each change now starts the bunch of DNF tests on top of upstream versions of hawkey,
> librepo and libcomps.
>  
>  It also means that from now nightly builds of DNF and its dependencies are available to
> you. Download them at will from
> http://jenkins.cloud.fedoraproject.org/job/DNF/lastSuccessfulBuild/artifact/. To check
> presence of new builds please follow the RSS channel
> http://jenkins.cloud.fedoraproject.org/job/DNF/rssAll. 
Wouldn't it make sense to create YUM metadata so that people can
automatically update DNF with itself?

XMvn project which uses Fedora Jenkins instance does that, see:
http://jenkins.cloud.fedoraproject.org/job/xmvn/ws/RPM/latest/

That works well for me.  In my yum.conf I have:

[jenkins-xmvn]
name=jenkins-xmvn
baseurl=http://jenkins.cloud.fedoraproject.org/job/xmvn/ws/RPM/latest
cost=3000

-- 
Mikolaj Izdebski
IRC: mizdebsk
-- 
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

[Ankur Sinha]

On Wed, 2014-01-29 at 12:11 -0500, Radek Holy wrote:
>  I have just added the metadata creation. Good point, thank you.
Is it OK to file bugs at bugzilla for nightlies, or should we only file
bugs for the versions pushed to Fedora?

This repo file works for me:

[dnf-nightlies]
name=DNF nightlies for $releasever - $basearch
baseurl=http://jenkins.cloud.fedoraproject.org/job/DNF/lastSuccessfulBuil...
cost=3000
enabled=1
skip_if_unavailable=True
gpgcheck=0

It gives me:
Repo-id      : dnf-nightlies
Repo-name    : DNF nightlies for Fedora 20 - x86_64
Repo-revision: 1391031363
Repo-updated : Thu Jan 30 08:36:03 2014
Repo-pkgs    : 26
Repo-size    : 6.9 M
Repo-baseurl :
http://jenkins.cloud.fedoraproject.org/job/DNF/lastSuccessfulBuild/artifa...
Repo-expire  : 172,800 second(s) (last: Thu Jan 30 15:07:09 2014)
Repo-filename: ///etc/yum.repos.d/dnf-nightlies.repo

-- 
Thanks,
Warm regards,
Ankur (FranciscoD)

http://fedoraproject.org/wiki/User:Ankursinha

Join Fedora! Come talk to us!
http://fedoraproject.org/wiki/Fedora_Join_SIG

[Radek Holy]

On Thu, 2014-01-30 at 5:11:31 AM, Ankur Sinha wrote:
>  Is it OK to file bugs at bugzilla for nightlies, or should we only
> file
>  bugs for the versions pushed to Fedora? 
Yes, it is, sure.

Best regards
-- 
Radek Holý
Associate Software Engineer
Software Management Team
Red Hat Czech

[Stanislav Ochotnicky]

Radek Holy <rholy(a)redhat.com&gt; writes:

>  I have just added the metadata creation. Good point, thank you.
Another thing worth mentioning: The release tags of those rpms are
incorrect.

Instead of:
dnf-0.4.12-1.git3584018.fc20
It should be:
dnf-0.4.12-0.1.git3584018.fc20

That way when 0.4.12 is actually released the dnf-0.4.12-1 will be
higher than those older nightlies. By that time the nightlies should
have higher version so no problems there either.

--
Stanislav Ochotnicky <sochotnicky(a)redhat.com&gt;
Software Engineer - Developer Experience

PGP: 7B087241
Red Hat Inc.                               http://cz.redhat.com

[Mikolaj Izdebski]

On 01/30/2014 10:38 AM, Stanislav Ochotnicky wrote:
>  Radek Holy <rholy(a)redhat.com&gt; writes:
>  
> > I have just added the metadata creation. Good point, thank you.
>  
>  Another thing worth mentioning: The release tags of those rpms are
>  incorrect.
>  
>  Instead of:
>  dnf-0.4.12-1.git3584018.fc20
>  It should be:
>  dnf-0.4.12-0.1.git3584018.fc20
>  
>  That way when 0.4.12 is actually released the dnf-0.4.12-1 will be
>  higher than those older nightlies. By that time the nightlies should
>  have higher version so no problems there either. 
In order to have proper versioning release tag should also be increased
in consecutive builds.

One way to achieve this is:

RELEASE=$(git describe --match="[^(jenkins)].*" --tags | sed
's/[^-]*-/0./;s/-/./;s/g/git/')
sed -i "s/^Release:\s\+[0-9.]*%{?dist}$/Release: ${RELEASE}/" *.spec

-- 
Mikolaj Izdebski
IRC: mizdebsk

[Ankur Sinha]

On Thu, 2014-01-30 at 11:19 +0100, Mikolaj Izdebski wrote:
>  In order to have proper versioning release tag should also be
>  increased
>  in consecutive builds. 
Hi Radek,

Can you please check if the repodata is being generated properly? I can
see dnf-0.4.12-1.git8c69fa2.fc20.noarch.rpm in my web browser[1], but a
dnf check-update doesn't list it as an update. Here's the relevant
output from dnf --disablerepo=* --enablerepo=dnf-nightlies list:

>  Available Packages
>  dnf.src                                                           
> 0.4.12-1.git8c69fa2.fc20                                                               
> dnf-nightlies
>  dnf-plugins-core.src                                              
> 0.0.2-1.gitda58e66.fc20                                                                
> dnf-nightlies
>  hawkey.src                                                        
> 0.4.9-1.git1d1a1e4.fc20                                                                
> dnf-nightlies
>  hawkey-debuginfo.x86_64                                           
> 0.4.9-1.git1d1a1e4.fc20                                                                
> dnf-nightlies
>  hawkey-devel.x86_64                                               
> 0.4.9-1.git1d1a1e4.fc20                                                                
> dnf-nightlies
>  libcomps.src                                                      
> 0.1.6-2.gitc107105013b521bf236e96e525dfb89b40855431.fc20                               
> dnf-nightlies
>  libcomps-debuginfo.x86_64                                         
> 0.1.6-2.gitc107105013b521bf236e96e525dfb89b40855431.fc20                               
> dnf-nightlies
>  libcomps-devel.x86_64                                             
> 0.1.6-2.gitc107105013b521bf236e96e525dfb89b40855431.fc20                               
> dnf-nightlies
>  libcomps-doc.noarch                                               
> 0.1.6-2.gitc107105013b521bf236e96e525dfb89b40855431.fc20                               
> dnf-nightlies
>  librepo.src                                                       
> 1.5.2-2.gitb9bafb7.fc20                                                                
> dnf-nightlies
>  librepo-debuginfo.x86_64                                          
> 1.5.2-2.gitb9bafb7.fc20                                                                
> dnf-nightlies
>  librepo-devel.x86_64                                              
> 1.5.2-2.gitb9bafb7.fc20                                                                
> dnf-nightlies
>  python-libcomps-doc.noarch                                        
> 0.1.6-2.gitc107105013b521bf236e96e525dfb89b40855431.fc20                               
> dnf-nightlies
>  python3-dnf.noarch                                                
> 0.4.12-1.git8c69fa2.fc20                                                               
> dnf-nightlies
>  python3-dnf-plugins-core.noarch                                   
> 0.0.2-1.gitda58e66.fc20                                                                
> dnf-nightlies
>  python3-hawkey.x86_64                                             
> 0.4.9-1.git1d1a1e4.fc20                                                                
> dnf-nightlies
>  python3-libcomps.x86_64                                           
> 0.1.6-2.gitc107105013b521bf236e96e525dfb89b40855431.fc20                               
> dnf-nightlies
>  python3-librepo.x86_64                                            
> 1.5.2-2.gitb9bafb7.fc20                                                                
> dnf-nightlies
>  [asinha@ankur-laptop  ~]$ dnf --version
>  0.4.12
>    Installed: dnf-0:0.4.12-1.git3584018.fc20.noarch at 2014-01-30 04:09
>    Built    :  at 2014-01-29 21:29
>  
>    Installed: rpm-0:4.11.1-7.fc20.x86_64 at 2014-01-17 00:22
>    Built    : Fedora Project at 2013-09-09 12:13
>  [asinha@ankur-laptop  ~]$  
There isn't a dnf package in the "available packages" for some reason.
I've checked with yum too, and a dnf update isn't available according to
the repodata.

Could you please correct/bump the release tag too? git commit tags don't
have to be incremental and this might also end up breaking the upgrade
path in the future.

[1]
http://jenkins.cloud.fedoraproject.org/job/DNF/lastSuccessfulBuild/artifa...

-- 
Thanks,
Warm regards,
Ankur (FranciscoD)

http://fedoraproject.org/wiki/User:Ankursinha

Join Fedora! Come talk to us!
http://fedoraproject.org/wiki/Fedora_Join_SIG

[Radek Holy]

Hello Ankur,

On Mon, 2014-02-03 at 6:33:02 AM, Ankur Sinha wrote:
>  Can you please check if the repodata is being generated properly? I
> can
>  see dnf-0.4.12-1.git8c69fa2.fc20.noarch.rpm in my web browser[1], but a
>  dnf check-update doesn't list it as an update. Here's the relevant
>  output from dnf --disablerepo=* --enablerepo=dnf-nightlies list: 
it's wierd, I'm not able to reproduce it here. The command ``dnf --disablerepo=*
--enablerepo=dnf-nightlies list`` outputs::

    Available Packages
    dnf.noarch                                          0.4.12-1.git8c69fa2.fc20          
                                    dnf-nightlies
    dnf.src                                             0.4.12-1.git8c69fa2.fc20          
                                    dnf-nightlies
    dnf-plugins-core.noarch                             0.0.2-1.gitda58e66.fc20           
                                    dnf-nightlies
    dnf-plugins-core.src                                0.0.2-1.gitda58e66.fc20           
                                    dnf-nightlies
    hawkey.src                                          0.4.9-1.git1d1a1e4.fc20           
                                    dnf-nightlies
    hawkey.x86_64                                       0.4.9-1.git1d1a1e4.fc20           
                                    dnf-nightlies
    hawkey-debuginfo.x86_64                             0.4.9-1.git1d1a1e4.fc20           
                                    dnf-nightlies
    hawkey-devel.x86_64                                 0.4.9-1.git1d1a1e4.fc20           
                                    dnf-nightlies
    libcomps.src                                       
0.1.6-2.gitc107105013b521bf236e96e525dfb89b40855431.fc20               dnf-nightlies
    libcomps.x86_64                                    
0.1.6-2.gitc107105013b521bf236e96e525dfb89b40855431.fc20               dnf-nightlies
    libcomps-debuginfo.x86_64                          
0.1.6-2.gitc107105013b521bf236e96e525dfb89b40855431.fc20               dnf-nightlies
    libcomps-devel.x86_64                              
0.1.6-2.gitc107105013b521bf236e96e525dfb89b40855431.fc20               dnf-nightlies
    libcomps-doc.noarch                                
0.1.6-2.gitc107105013b521bf236e96e525dfb89b40855431.fc20               dnf-nightlies
    librepo.src                                         1.5.2-2.gitb9bafb7.fc20           
                                    dnf-nightlies
    librepo.x86_64                                      1.5.2-2.gitb9bafb7.fc20           
                                    dnf-nightlies
    librepo-debuginfo.x86_64                            1.5.2-2.gitb9bafb7.fc20           
                                    dnf-nightlies
    librepo-devel.x86_64                                1.5.2-2.gitb9bafb7.fc20           
                                    dnf-nightlies
    python-hawkey.x86_64                                0.4.9-1.git1d1a1e4.fc20           
                                    dnf-nightlies
    python-libcomps.x86_64                             
0.1.6-2.gitc107105013b521bf236e96e525dfb89b40855431.fc20               dnf-nightlies
    python-libcomps-doc.noarch                         
0.1.6-2.gitc107105013b521bf236e96e525dfb89b40855431.fc20               dnf-nightlies
    python-librepo.x86_64                               1.5.2-2.gitb9bafb7.fc20           
                                    dnf-nightlies
    python3-dnf.noarch                                  0.4.12-1.git8c69fa2.fc20          
                                    dnf-nightlies
    python3-dnf-plugins-core.noarch                     0.0.2-1.gitda58e66.fc20           
                                    dnf-nightlies
    python3-hawkey.x86_64                               0.4.9-1.git1d1a1e4.fc20           
                                    dnf-nightlies
    python3-libcomps.x86_64                            
0.1.6-2.gitc107105013b521bf236e96e525dfb89b40855431.fc20               dnf-nightlies
    python3-librepo.x86_64                              1.5.2-2.gitb9bafb7.fc20           
                                    dnf-nightlies

The ``createrepo`` command did not give any error. Also manually looking into the metadata
[1]_ it seems OK.

Please try running ``dnf clean all --enablerepo=dnf-nightlies``.

.. [1]
http://jenkins.cloud.fedoraproject.org/job/DNF/lastSuccessfulBuild/artifa...

Best regards
-- 
Radek Holý
Associate Software Engineer
Software Management Team
Red Hat Czech

[Ankur Sinha]

Hi Radek,

On Mon, 2014-02-03 at 04:24 -0500, Radek Holy wrote:
>  
>  it's wierd, I'm not able to reproduce it here. The command ``dnf
>  --disablerepo=* --enablerepo=dnf-nightlies list`` outputs:: 
Looks like it was a result of the versioning scheme that you're using.

I had dnf-0.4.12-1.git3584018.fc20.noarch installed and the latest build
as of today is dnf-0.4.12-1.git01649a8.fc20.noarch.rpm. Since
0.4.12-1.git3584018 > 0.4.12-1.git01649a8, neither yum, nor dnf saw the
newest package as an update. I'm not sure why neither of them listed the
package, though. Can you please use a correct version scheme as required
by the package guidelines, or bump the release to 1 1.1 1.2 etc? Git
commit hashes are not incremental and therefore the upgrade path will
not always be correct if packages continue with this version scheme.

https://fedoraproject.org/wiki/Packaging:NamingGuidelines#Pre-Release_pac...

The current versions are:
Build #453: 	dnf-0.4.12-1.git7613c16.fc20.noarch.rpm
Build #454:	dnf-0.4.12-1.git8c69fa2.fc20.noarch.rpm
Build #455:	dnf-0.4.12-1.git01649a8.fc20.noarch.rpm

As you see, they're not incremental and as a result, folks won't receive
updates if the installed version is > the latest build version.

Rather funnily, *downgrading* the package gave me the *latest* build
here:

>  [asinha@ankur-laptop  ~]$ sudo dnf downgrade dnf
>  [sudo] password for asinha:
>  Resolving dependencies
>  --> Starting dependency resolution
>  ---> Package dnf.noarch 0.4.12-1.git3584018.fc20 will be downgraded
>  ---> Package dnf.noarch 0.4.12-1.git01649a8.fc20 will be a downgrade
>  --> Finished dependency resolution
>  Depsolve time: 0.072
>  Dependencies resolved.
>  
>
> ========================================================================================================================================================================
>   Package                        Arch                              Version                
>                                Repository                                Size
>
> ========================================================================================================================================================================
>  Downgrading:
>   dnf                            noarch                           
> 0.4.12-1.git01649a8.fc20                               dnf-nightlies                      
>      433 k
>  
>  Transaction Summary
>
> ========================================================================================================================================================================
>  Downgrade  1 Package
>  
>  Total download size: 433 k
>  Is this ok [y/N]: y
>  Downloading Packages:
>  dnf-0.4.12-1.git01649a8.fc20.noarch.rpm                                                  
>                                               160 kB/s | 433 kB     00:02
>  populate_rpm_ts: downgrade:
> dnf-0.4.12-1.git01649a8.fc20.noarch/dnf-0.4.12-1.git3584018.fc20.noarch
>  Running transaction check
>  Transaction check succeeded.
>  Transaction check time: 0.110
>  Running transaction test
>  Transaction test succeeded.
>  Transaction test time: 1.066
>  Running transaction
>  runTransaction: rpm transaction start.
>    Downgrading : dnf-0.4.12-1.git01649a8.fc20.noarch                                      
>                                                                           1/2
>    Erasing     : dnf-0.4.12-1.git3584018.fc20.noarch                                      
>                                                                           2/2
>  runTransaction: rpm transaction over.
>    Verifying   : dnf-0.4.12-1.git01649a8.fc20.noarch                                      
>                                                                           1/2
>    Verifying   : dnf-0.4.12-1.git3584018.fc20.noarch                                      
>                                                                           2/2
>  VerifyTransaction time: 0.837
>  Transaction time: 3.651
>  
>  Downgraded:
>    dnf.noarch 0.4.12-1.git01649a8.fc20
>  
>  Completion plugin: Generating completion cache...
>  Complete!
>  [asinha@ankur-laptop  ~]$ 
-- 
Thanks,
Warm regards,
Ankur (FranciscoD)

http://fedoraproject.org/wiki/User:Ankursinha

Join Fedora! Come talk to us!
http://fedoraproject.org/wiki/Fedora_Join_SIG

[Alec Leamas]

Another solution is to incorporate the jenkins variable BUILD_NR in
the release - although not entirely kosher it handles multiple builds
on same date.

--alec

On 2/3/14, Ankur Sinha <sanjay.ankur(a)gmail.com&gt; wrote:
>  Hi Radek,
>
>  On Mon, 2014-02-03 at 04:24 -0500, Radek Holy wrote:
> >
> > it's wierd, I'm not able to reproduce it here. The command ``dnf
> > --disablerepo=* --enablerepo=dnf-nightlies list`` outputs::
>
>  Looks like it was a result of the versioning scheme that you're using.
>
>  I had dnf-0.4.12-1.git3584018.fc20.noarch installed and the latest build
>  as of today is dnf-0.4.12-1.git01649a8.fc20.noarch.rpm. Since
>  0.4.12-1.git3584018 > 0.4.12-1.git01649a8, neither yum, nor dnf saw the
>  newest package as an update. I'm not sure why neither of them listed the
>  package, though. Can you please use a correct version scheme as required
>  by the package guidelines, or bump the release to 1 1.1 1.2 etc? Git
>  commit hashes are not incremental and therefore the upgrade path will
>  not always be correct if packages continue with this version scheme.
>
>  https://fedoraproject.org/wiki/Packaging:NamingGuidelines#Pre-Release_pac...
>
>  The current versions are:
>  Build #453: 	dnf-0.4.12-1.git7613c16.fc20.noarch.rpm
>  Build #454:	dnf-0.4.12-1.git8c69fa2.fc20.noarch.rpm
>  Build #455:	dnf-0.4.12-1.git01649a8.fc20.noarch.rpm
>
>  As you see, they're not incremental and as a result, folks won't receive
>  updates if the installed version is > the latest build version.
>
>  Rather funnily, *downgrading* the package gave me the *latest* build
>  here:
>
> > [asinha@ankur-laptop  ~]$ sudo dnf downgrade dnf
> > [sudo] password for asinha:
> > Resolving dependencies
> > --> Starting dependency resolution
> > ---> Package dnf.noarch 0.4.12-1.git3584018.fc20 will be downgraded
> > ---> Package dnf.noarch 0.4.12-1.git01649a8.fc20 will be a downgrade
> > --> Finished dependency resolution
> > Depsolve time: 0.072
> > Dependencies resolved.
> >
> >
> ========================================================================================================================================================================
> >  Package                        Arch                              Version
> >                                               Repository
> >              Size
> >
> ========================================================================================================================================================================
> > Downgrading:
> >  dnf                            noarch
> > 0.4.12-1.git01649a8.fc20                               dnf-nightlies
> >                      433 k
> >
> > Transaction Summary
> >
> ========================================================================================================================================================================
> > Downgrade  1 Package
> >
> > Total download size: 433 k
> > Is this ok [y/N]: y
> > Downloading Packages:
> > dnf-0.4.12-1.git01649a8.fc20.noarch.rpm
> >                                                              160 kB/s |
> > 433 kB     00:02
> > populate_rpm_ts: downgrade:
> > dnf-0.4.12-1.git01649a8.fc20.noarch/dnf-0.4.12-1.git3584018.fc20.noarch
> > Running transaction check
> > Transaction check succeeded.
> > Transaction check time: 0.110
> > Running transaction test
> > Transaction test succeeded.
> > Transaction test time: 1.066
> > Running transaction
> > runTransaction: rpm transaction start.
> >   Downgrading : dnf-0.4.12-1.git01649a8.fc20.noarch
> >
> >               1/2
> >   Erasing     : dnf-0.4.12-1.git3584018.fc20.noarch
> >
> >               2/2
> > runTransaction: rpm transaction over.
> >   Verifying   : dnf-0.4.12-1.git01649a8.fc20.noarch
> >
> >               1/2
> >   Verifying   : dnf-0.4.12-1.git3584018.fc20.noarch
> >
> >               2/2
> > VerifyTransaction time: 0.837
> > Transaction time: 3.651
> >
> > Downgraded:
> >   dnf.noarch 0.4.12-1.git01649a8.fc20
> >
> > Completion plugin: Generating completion cache...
> > Complete!
> > [asinha@ankur-laptop  ~]$
>
>  --
>  Thanks,
>  Warm regards,
>  Ankur (FranciscoD)
>
>  http://fedoraproject.org/wiki/User:Ankursinha
>
>  Join Fedora! Come talk to us!
>  http://fedoraproject.org/wiki/Fedora_Join_SIG
>
>

[Vít Ondruch]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dne 3.2.2014 11:17, Ankur Sinha napsal(a):
>  Hi Radek,
>
>  On Mon, 2014-02-03 at 04:24 -0500, Radek Holy wrote:
> >
> > it's wierd, I'm not able to reproduce it here. The command ``dnf
> > --disablerepo=* --enablerepo=dnf-nightlies list`` outputs::
>
>  Looks like it was a result of the versioning scheme that you're using.
>
>  I had dnf-0.4.12-1.git3584018.fc20.noarch installed and the latest build
>  as of today is dnf-0.4.12-1.git01649a8.fc20.noarch.rpm. Since
>  0.4.12-1.git3584018 > 0.4.12-1.git01649a8, neither yum, nor dnf saw the
>  newest package as an update. I'm not sure why neither of them listed the
>  package, though. Can you please use a correct version scheme as required
>  by the package guidelines, or bump the release to 1 1.1 1.2 etc? Git
>  commit hashes are not incremental and therefore the upgrade path will
>  not always be correct if packages continue with this version scheme.
>
>  
https://fedoraproject.org/wiki/Packaging:NamingGuidelines#Pre-Release_pac...

This is better link:
https://fedoraproject.org/wiki/Packaging:NamingGuidelines#Snapshot_packages


There should be always included the snapshot date.


Vít


>  The current versions are:
>  Build #453:     dnf-0.4.12-1.git7613c16.fc20.noarch.rpm
>  Build #454:    dnf-0.4.12-1.git8c69fa2.fc20.noarch.rpm
>  Build #455:    dnf-0.4.12-1.git01649a8.fc20.noarch.rpm
>
>  As you see, they're not incremental and as a result, folks won't receive
>  updates if the installed version is > the latest build version.
>
>  Rather funnily, *downgrading* the package gave me the *latest* build
>  here:
>
> > [asinha@ankur-laptop  ~]$ sudo dnf downgrade dnf
> > [sudo] password for asinha:
> > Resolving dependencies
> > --> Starting dependency resolution
> > ---> Package dnf.noarch 0.4.12-1.git3584018.fc20 will be downgraded
> > ---> Package dnf.noarch 0.4.12-1.git01649a8.fc20 will be a downgrade
> > --> Finished dependency resolution
> > Depsolve time: 0.072
> > Dependencies resolved.
> >
> >
========================================================================================================================================================================
> >  Package                        Arch                             
Version                                               
Repository                                Size
> >
========================================================================================================================================================================
> > Downgrading:
> >  dnf                            noarch                           
0.4.12-1.git01649a8.fc20                              
dnf-nightlies                            433 k
> > 
>> Transaction Summary
> >
========================================================================================================================================================================
>> Downgrade  1 Package
> > 
>> Total download size: 433 k
>> Is this ok [y/N]: y
>> Downloading Packages:
> > 
dnf-0.4.12-1.git01649a8.fc20.noarch.rpm                    
                                                                           
160 kB/s | 433 kB     00:02
> > populate_rpm_ts: downgrade:
dnf-0.4.12-1.git01649a8.fc20.noarch/dnf-0.4.12-1.git3584018.fc20.noarch
> > Running transaction check
> > Transaction check succeeded.
> > Transaction check time: 0.110
> > Running transaction test
> > Transaction test succeeded.
> > Transaction test time: 1.066
> > Running transaction
> > runTransaction: rpm transaction start.
> >   Downgrading : 
dnf-0.4.12-1.git01649a8.fc20.noarch                            
                                                                                   
1/2
> >   Erasing     : 
dnf-0.4.12-1.git3584018.fc20.noarch        
                                                                                          
            
2/2
> > runTransaction: rpm transaction over.
> >   Verifying   : 
dnf-0.4.12-1.git01649a8.fc20.noarch                            
                                                                                   
1/2
> >   Verifying   : 
dnf-0.4.12-1.git3584018.fc20.noarch        
                                                                                          
            
2/2
>> VerifyTransaction time: 0.837
>> Transaction time: 3.651
> > 
>> Downgraded:
>>   dnf.noarch 0.4.12-1.git01649a8.fc20
> > 
>> Completion plugin: Generating completion cache...
>> Complete!
>> [asinha@ankur-laptop  ~]$
>
>
>

> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQIcBAEBAgAGBQJS73nVAAoJEAzgnueZF7h8YXUQAJhCc2SVx3Mq7XcAcyTCNueC
> ztWXw28YmI5W4d1slgcj3qzg2BW/wwMr8iitd066Uvqgfn25U0aN2XagIoUJM0yq
> aCHFpfPEME5Cs1/CSgma1RHMBbbkPYd5tpbIcuG6VVISllnZkFoyPSK+kB+0mtsG
> oVTideMEFgoRA1G6Z1b5PK2AZH27hqU+vdyUeFLZjykTIe5U7BRway1ctPnCRtQm
> Iot8jgHGT6TVyXrMldHONTZVDfxJ0xDfByXkBsRrtGuzDLks0q6LycLh7Ra/SFkV
> nRD3Ks6I5PePUIe9d9UkA2UUwIOI8qmt2Ppa781D1Z8hVlt0YfYFGAXJQy6tmTOk
> 2MVRluT0X7kLDcuq8lJbvvKNBK3vUWCMU8y67gy3SMGRbyLXgyOsuf0gwOtMou7H
> C1cR8PpJScKWoBdAZecQ53GlHmcXmWSqQojlMuIIhSrCl7gugNC53VPKQ9z6g+Wc
> +B8ZjueYE6zVxNW4GARYab78zm2fOWQ9PkLQPgwG47cqO3UEgxyCzJsDPJCXWcB2
> DisD/NQhNbjtofigegudnaZhwt7eaAY+txrwUoUn1XCTaUDFT6i+SFykZ36qLDqC
> typtfObh65a49NzLvCpzEWJue+ZH06Tkb+/AEyJslboMkJjfCdOtP7UvqM+UlFwI
> nMVgMRTqlJA0AigJjq2/
> =w3NI
> -----END PGP SIGNATURE-----

[Radek Holy]

----- Original Message -----
>  From: "Vít Ondruch" <vondruch(a)redhat.com&gt;
>  To: devel(a)lists.fedoraproject.org
>  Sent: Monday, February 3, 2014 12:13:44 PM
>  Subject: Re: Nightly builds of DNF available
>  
>  
>  Dne 3.2.2014 11:17, Ankur Sinha napsal(a):
>  > https://fedoraproject.org/wiki/Packaging:NamingGuidelines#Pre-Release_pac...
>  
>  This is better link:
>  https://fedoraproject.org/wiki/Packaging:NamingGuidelines#Snapshot_packages
>  
>  
>  There should be always included the snapshot date. 
Ankur, Alec, Vít, thank you for your help.

Please let me know if the changed versioning scheme does not work for you.

Best regards
-- 
Radek Holý
Associate Software Engineer
Software Management Team
Red Hat Czech

[Radek Holy]

I have just changed the versioning scheme. Thank you for pointing it out.

Best regards
-- 
Radek Holý
Associate Software Engineer
Software Management Team
Red Hat Czech



----- Original Message -----
From: "Stanislav Ochotnicky" <sochotnicky(a)redhat.com&gt;
To: "Radek Holy" <rholy(a)redhat.com&gt;, "Development discussions related
to Fedora" <devel(a)lists.fedoraproject.org&gt;
Sent: Thursday, January 30, 2014 10:38:28 AM
Subject: Re: Nightly builds of DNF available

Radek Holy <rholy(a)redhat.com&gt; writes:

>  I have just added the metadata creation. Good point, thank you.
Another thing worth mentioning: The release tags of those rpms are
incorrect.

Instead of:
dnf-0.4.12-1.git3584018.fc20
It should be:
dnf-0.4.12-0.1.git3584018.fc20

That way when 0.4.12 is actually released the dnf-0.4.12-1 will be
higher than those older nightlies. By that time the nightlies should
have higher version so no problems there either.

--
Stanislav Ochotnicky <sochotnicky(a)redhat.com&gt;
Software Engineer - Developer Experience

PGP: 7B087241
Red Hat Inc.                               http://cz.redhat.com