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

Bug#766708: marked as done (Coordinate plan and requirements for cross toolchain packages in Debian)

Your message dated Sat, 04 Jun 2016 11:03:50 +0200
with message-id <87lh2ll409.fsf@whist.hands.com>
and subject line Re: Bug#766708: Coordinating a plan and requirements for cross toolchain packages in Debian
has caused the Debian Bug report #766708,
regarding Coordinate plan and requirements for cross toolchain packages in Debian
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.)


-- 
766708: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766708
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: gcc-4.9
Version: 4.9.1-19
Severity: serious
Justification: do not migrate to jessie
User: helmutg@debian.org
Usertags: rebootstrap

Hi Matthias,

I notice that starting with -19 gcc emits unsatisfiable dependencies in
multiarch cross builds regressing from -18. This makes all rebootstrap
builds fail to install gcc. You can find a failed attempt to install at
https://jenkins.debian.net/job/rebootstrap_m68k_gcc49/100/console.

It seems that gcc now emits dependencies on libc-*-$arch-cross, but
glibc doesn't build those.

I'll look into the matter and try to provide a patch.

Helmut

--- End Message ---
--- Begin Message --- 
As agreed at the most recent meeting of the Technical Committee, this
bug is being closed.

It has not been resolved, as such, but parts of it have been rendered
moot by the release of Jessie, and other parts have been rendered less
relevant by the passage of time.

This is not a particularly satisfying outcome, but at least it clears
the way for bugs in related areas, which people might otherwise hesitate
to submit as long as this bug remains open.

Please be assured, the members of the Technical Committee are still very
much interested in assisting in whatever way we can with progress in
this area (either as individuals or as a group, in either informal
mediation or via bugs submitted to the committee).

We also intend to learn the lessons of this bug:

  Some issues clearly have an expiry date, and in such cases any
  decision is generally better than none.

  In order to make such quick decisions possible, we intend to
  encourage good behaviour by giving the most sympathetic hearing to
  those participants that provide clear justifications of their position
  and respond to questions in a timely manner.

Philip Hands
(on behalf of the Technical Committee)

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: