Re: libxcb-backports only for amd64
On Tue, Oct 14, 2014 at 1:47 AM, Alexander Wirt <formorer@formorer.de> wrote:
> On Tue, 14 Oct 2014, Vincent Cheng wrote:
>
>> On Tue, Oct 14, 2014 at 1:19 AM, Cyril Brulebois <kibi@debian.org> wrote:
>> > Christoph Mühlmann <christoph@nagnag.de> (2014-10-14):
>> >> Hello,
>> >>
>> >> actually it seems the libxcb-backports are only available for amd64, not
>> >> for i386?
>> >> Updating in a multiarch-installation removes many installed libraries
>> >> from the i386-architecture and some (third party) packages, see below...
>> >
>> > See build status:
>> > https://buildd.debian.org/status/package.php?p=libxcb&suite=wheezy-backports
>> >
>> > libxcb build-depends on missing:
>> > - xcb-proto (>= 1.10)
>> >
>> > Looks like the uploader (cc'd) forgot some bits? :)
>>
>> xcb-proto is already in the backports NEW queue.
>>
>> It's probably worth pointing out that a dist-upgrade with
>> wheezy-backports specified as the target release isn't how backports
>> is meant to work. Christoph, you should be selectively installing
>> packages from wheezy-backports based on what you actually need, rather
>> than upgrading all packages on your system to their wheezy-backports
>> version (which is not tested and not guaranteed to work at all).
> And rejected. It would help everybody if you get uploads right on the first
> time and if you would wait with upload until all dependencys are available in
> bpo.
I'm not sure how a reject helps in this case? libxcb has already been
accepted into backports and is currently non-build-able because of a
missing build-dep, xcb-proto, which you apparently just rejected.
Which means that libxcb is still non-build-able in wheezy-backports.
Regards,
Vincent
Reply to: