Hi doko,
Quoting Matthias Klose (2022-11-18 15:34:45)
> > my last NMU got cancelled because you uploaded a new version of
> > gcc-defaults while my NMU was still waiting in the delayed queue. On
> > September 1, you told me in #debian-devel that this bug is on your TODO
> > list but now more than
Hi doko,
Quoting Johannes Schauer Marin Rodrigues (2022-08-28 08:28:52)
> On Wed, 17 Aug 2022 18:20:36 +0200 Johannes Schauer Marin Rodrigues
> wrote:
> > On Wed, 16 Mar 2022 13:30:26 +0100 Johannes Schauer Marin Rodrigues
> > wrote:
> > > when creating chroots for
Control: severity -1 critical
On Sat, 22 Oct 2022 14:14:32 +0200 "Lukas F. Hartmann" wrote:
> Since an `apt upgrade` yesterday on Debian unstable on an aarch64 system
> (imx8mq based, cortex-a53), all wayland compositors and clients stopped
> working, including sway, wayfire and weston.
Since th
Hi,
On Wed, 17 Aug 2022 18:20:36 +0200 Johannes Schauer Marin Rodrigues
wrote:
> On Wed, 16 Mar 2022 13:30:26 +0100 Johannes Schauer Marin Rodrigues
> wrote:
> > when creating chroots for new architectures that are in the process of being
> > bootstrapped without yet having
(my last mail to d...@debian.org bounced with "retry timeout exceeded" so I'm
trying again with the ubuntu.com address as well)
Hi,
On Wed, 16 Mar 2022 13:30:26 +0100 Johannes Schauer Marin Rodrigues
wrote:
> when creating chroots for new architectures that are in th
Hi,
On Wed, 16 Mar 2022 13:30:26 +0100 Johannes Schauer Marin Rodrigues
wrote:
> when creating chroots for new architectures that are in the process of being
> bootstrapped without yet having emulation support from qemu, it is not
> possible to run maintainer scripts inside th
Source: gcc-defaults
Version: 1.194
Severity: normal
Tags: patch
User: debian-d...@lists.debian.org
Usertags: dpkg-root-support
X-Debbugs-Cc: jo...@debian.org
Hi,
when creating chroots for new architectures that are in the process of
being bootstrapped without yet having emulation support from qe
Source: gnat-4.9
Version: 4.9.2-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Hi,
gnat-4.9 currently FTBFS because of an unsatisfied dependency
gcc-4.9-source (<< 4.9.3). Currently, gcc-4.9-source in unstable is of
version 4.9.3-1.
https://qa.
Package: g++
Version: 4.9.2-2
Severity: normal
Hi,
I'm trying to solve the build failure of my package vcmi on ppc64el:
https://buildd.debian.org/status/fetch.php?pkg=vcmi&arch=ppc64el&ver=0.97%2Bdfsg-2&stamp=1416356066
The issue seems to only appear when compiling with c++. It does not
happen
Quoting Adam D. Barratt (2013-11-01 00:42:49)
> 4.8.1-3 is in unstable's Sources index, but as Extra-Source-Only: yes; I
> guess Johannes's tools need updating to handle that.
correct.
Sorry for the confusion.
cheers, josch
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with
Hi,
Quoting Matthias Klose (2013-10-30 20:27:20)
> Am 30.10.2013 16:55, schrieb Johannes Schauer:
> > I just wanted to mention that src:gcc-4.8 seems to be affected by the same
> > problem.
>
> I don't see that gcc-4.8 is affected.
the problem with this bug (gcc-
Hi,
I just wanted to mention that src:gcc-4.8 seems to be affected by the same
problem.
I stumbled over this one because all Debian architectures have not been
bootstrappable due to this bug. Since I have regular 4-day interval snapshots
of Debian unstable I can add that this dependency conflict
Package: gcc-4.7
Version: 4.7.2-4
Severity: wishlist
Tags: patch
User: j.scha...@email.de
Usertags: bootstrap-conflicts
Inter-package conflicts currently limit the ability of a CUDF solver to
optimize the dependency graph created during bootstrapping of Debian for
new architectures. Luckily there
13 matches
Mail list logo
