On Mon, Feb 08, 2010 at 07:39:45PM +0000, Adam D. Barratt wrote: > On Mon, 2010-02-08 at 19:04 +0100, Mike Hommey wrote: > > On Mon, Feb 08, 2010 at 06:57:20PM +0100, Mike Hommey wrote: > > > On Tue, Feb 02, 2010 at 09:39:17AM +0100, Mike Hommey wrote: > > > > nmu gluezilla_2.4.3-1 galeon_2.0.7-1.2 chmsee_1.0.7-1.2 > > > > gnome-python-extras_2.25.3-4.1 xiphos_3.1.2-1 . ALL . -m 'Rebuild with > > > > fixed dh_xulrunner, see #567746' > > > > dw gluezilla_2.4.3-1 galeon_2.0.7-1.2 chmsee_1.0.7-1.2 > > > > gnome-python-extras_2.25.3-4.1 xiphos_3.1.2-1 . ALL . -m 'xulrunner (>= > > > > 1.9.1.6-2)' > > > > > > I'm wondering... is the >= syntax properly handled ? 1.9.1.6-2 has been > > > available on (some) architectures for a few days, but none of the > > > packages above have apparently been attempted to be built. > > > > Cyril Brulebois enlighted me with the obvious: the dep-wait should be on > > xulrunner-dev (>= 1.9.1.6-2), not xulrunner. > > dep-waits fixed.
It seems the nmus haven't triggered on the architectures where xulrunner-dev >= 1.9.1.6-2 is available. Could you check what is happening ? Mike -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
