[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#930812: marked as done (unblock: cargo/0.35.0-2)

Your message dated Sun, 23 Jun 2019 11:55:57 +0200
with message-id <0a4c6b26-44c5-1e96-56af-37b6cf71130f@debian.org>
and subject line Re: Bug#930812: unblock: cargo/0.35.0-2
has caused the Debian Bug report #930812,
regarding unblock: cargo/0.35.0-2
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 owner@bugs.debian.org
immediately.)


-- 
930812: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930812
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock

Please unblock package cargo

rustc 1.34.2 was unblocked in bug #930661 but the bug requestor forgot to file
the corresponding unblock request for cargo version 0.35.0-1. This is the
recommended version of cargo that goes with that rust version.

unblock cargo/0.35.0-2

-- System Information:
Debian Release: 10.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable'), (300, 'unstable'), (100, 'experimental'), (1, 'experimental-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

--- End Message ---
--- Begin Message --- 
Hi Ximin,

On 22-06-2019 23:03, Moritz Muehlenhoff wrote:
> On Sat, Jun 22, 2019 at 07:52:40PM +0200, Paul Gevers wrote:
>> Hi Ximin,
>>
>> On 22-06-2019 11:57, Ximin Luo wrote:
>>> Paul Gevers:
>>>> On 21-06-2019 07:38, Ximin Luo wrote:
>>>>> rustc 1.34.2 was unblocked in bug #930661 but the bug requestor forgot to file
>>>>> the corresponding unblock request for cargo version 0.35.0-1. This is the
>>>>> recommended version of cargo that goes with that rust version.
>>>>
>>>> How strong is this recommendation? It is too late in the freeze to take
>>>> new upstream releases that aren't targeted fixes for important or higher
>>>> bugs.
>>>>
>>>
>>> Strong in that upstream does not officially support any other
>>> combination and doesn't even talk about it as being possible. It's
>>> only a quirk of the Debian packaging situation that sometimes the
>>> versions are mismatched in unstable, because we de-synchronise rustc
>>> vs cargo releases. Upstream always releases them in sync. I don't
>>> think we should desync them for a stable release.

One other thing. If this is your point of view, I think it makes a lot
of sense if this is visible in the depends/recommends of rustc and
cargo. Such that this is also visible to the outside world, even if the
way is not clear from those relations alone (but that could/should be
documented in the d/changelog).

>> And is the security team aware of this (in CC)? We are doing this to
>> support Firefox security builds.
> 
> Rust 1.34 is needed for Firefox ESR68 and if Cargo 0.35 should complement that,
> then let's do that.

Unblocked, thanks.

Paul

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
Reply to: