On 2018-01-11 14:17, Raphael Hertzog wrote:
> On Thu, 11 Jan 2018, Aurelien Jarno wrote:
> > > 10:32 So libc6-dev-amd64:i386 should Conflicts:
> > > libc6-dev-i386:amd64
> > > 10:32 and vice versa
> > >
> > > So it's probably time to revisit this.
> >
> > Does it also now support
On Thu, 11 Jan 2018, Aurelien Jarno wrote:
> > 10:32 So libc6-dev-amd64:i386 should Conflicts:
> > libc6-dev-i386:amd64
> > 10:32 and vice versa
> >
> > So it's probably time to revisit this.
>
> Does it also now support cross-architecture "self"-conflicts? (see
> bug#747261 for more
On 2018-01-11 11:19, Raphael Hertzog wrote:
> Control: forcemerge 702962 -1
> Control: severity 702962 important
>
> On Wed, 27 Apr 2016, Aurelien Jarno wrote:
>
> [ ... file conflicts between various libc6-dev-$ARCH ... ]
>
> > This has already been reported multiple time, for example in
Control: forcemerge 702962 -1
Control: severity 702962 important
On Wed, 27 Apr 2016, Aurelien Jarno wrote:
[ ... file conflicts between various libc6-dev-$ARCH ... ]
> This has already been reported multiple time, for example in #702962.
> Anyway apt-get simply do not support
Processing control commands:
> forcemerge 702962 -1
Bug #702962 [src:glibc] file conflicts in libc6-dev-i386 and libc6-dev-mips64
Unable to merge bugs because:
package of #820826 is 'libc6-dev-amd64' not 'src:glibc'
Failed to forcibly merge 702962: Did not alter merged bugs.
> severity 702962
On 2016-04-12 21:04, Sean wrote:
> Package: libc6-dev-amd64
> Version: 2.19-18+deb8u4
> Severity: normal
>
> Dear Maintainer,
>
> I'm not an expert in the cross-compilation toolchain or its Debian repository
> configuration, but the libc6-dev-* packages appear to be set up with
> architecture
Package: libc6-dev-amd64
Version: 2.19-18+deb8u4
Severity: normal
Dear Maintainer,
I'm not an expert in the cross-compilation toolchain or its Debian repository
configuration, but the libc6-dev-* packages appear to be set up with
architecture qualifiers so that only one will ever be installed;
7 matches
Mail list logo
