Your message dated Sat, 12 Jan 2019 21:43:11 +0530
with message-id <87bm4lhn1k....@bhairava.copyninja.info>
and subject line Re: Bug#919005: [cargo] 0.31.1 is actually 0.30
has caused the Debian Bug report #919005,
regarding [cargo] 0.31.1 is actually 0.30
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
919005: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919005
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cargo
Version: 0.31.1-1

The packages version of Cargo is actually v0.30.0, not 0.31.1 as the
package version number and changelog suggest

--- End Message ---
--- Begin Message ---
jnq...@gmail.com writes:

> Package: cargo
> Version: 0.31.1-1
>
> The packages version of Cargo is actually v0.30.0, not 0.31.1 as the
> package version number and changelog suggest

How are you saying this?. On my system see below output

 vasudev@bhairava  ~  /usr/bin/cargo -V                                       
                                                                     ✔  1408 
 21:09:12
cargo 1.30.0

 vasudev@bhairava  ~  apt-cache policy cargo                                  
                                                                     ✔  1409 
 21:09:22
cargo:
  Installed: 0.31.1-1
  Candidate: 0.31.1-1
  Version table:
     0.32.0-1~exp1 1
          1 http://deb.debian.org/debian experimental/main amd64 Packages
 *** 0.31.1-1 500
        500 http://deb.debian.org/debian sid/main amd64 Packages
        100 /var/lib/dpkg/status

So version printed by cargo is actually rust language version previously
cargo used to print a version different than rust and which is always
one point ahead to rust. But that version has become internal now so
package still maintains that version but cargo binary prints version
same as rust.

Hope I'm able to clarify. I'm closing this bug for now.

Best Regards,
Vasudev

Attachment: signature.asc
Description: PGP signature


--- End Message ---

Reply via email to