[Pkg-chromium-maint] Bug#746330: Bug#746034: chromium 34.0.1847.116-1~deb7u1 depends on libudev0 which is no longer in the testing archive

Andreas Cadhalpun andreas.cadhalpun at googlemail.com
Tue Apr 29 12:15:42 UTC 2014

Control: tags -1 + sid
Control: forcemerge -1 746330


On 29.04.2014 13:51, Justin B Rye wrote:
> Andreas Cadhalpun wrote:
>> On 27.04.2014 11:26, shirish शिरीष wrote:
>>> I cannot install the update 34.0.1847.116-1~deb7u1 because
>>> it depends on libudev0 and libudev0 is no longer in the Debian testing
>>> archive. I have marked the bug as grave as almost everybody who has
>>> removed libudev0 would not be able to install this package.
>> I'm also affected by this. It seems the version currently in testing
>> was build for stable.
>> Luckily, the version from sid can be installed just fine, so I'm
>> closing this bug with that version and tag it as only affecting
>> jessie.
> Unluckily, this isn't true for everybody.  If you look at
>   https://packages.debian.org/sid/chromium or
>   http://ftp.debian.org/debian/pool/main/c/chromium-browser/
> you'll see that 34.0.1847.116-2 is only available for amd64.  On the
> i386 architecture, that version failed to build:
>   https://buildd.debian.org/status/package.php?p=chromium-browser
> so the latest available version of chromium is the misbegotten
> 34.0.1847.116-1~deb7u1.

I know this. :-\
The FTBFS on i386 is tracked in #745794.

> So maybe this bug needs to be marked as "still found on i386", though
> I don't see any mechanism for doing that.

This bug is still open in testing and unstable, see e.g. the graphic in 
the upper right corner on [1]. But I'm tagging it as affecting sid as 
well now.

Fixing the FTBFS on i386 is all that needs to be done.

>  Meanwhile I see Dan
> Jacobson's just opened a duplicate of this bug as #746330...

I'm merging the duplicate.

Best regards,

1: https://bugs.debian.org/746034

More information about the Pkg-chromium-maint mailing list