Hi,
On Thu, 7 Mar 2019 11:39:02 +0100 Helmut Grohne
wrote:
> An autopkgtest in python-selenium could have easily caught this issue. Please
> add one.
https://salsa.debian.org/sagiru-guest/python-selenium/-/merge_requests/2
the code exists. Now you just need to merge it.
Thanks!
cheers,
Control: tags 923929 - upstream
After splitting selenium bug #923929, I forgot to remove the upstream
tag.
On Thu, Mar 07, 2019 at 11:38:59AM +0100, Helmut Grohne wrote:
> $ chromium --remote-debugging-port=0
Given that -dbgsym packages are not published, I locally rebuilt
chromium. The output
Control: affects -1 + python3-selenium
Control: tags -1 - pending
Control: clone -1 -2
Control: reassign -2 src:python-selenium
Control: severity -2 wishlist
Control: retitle -2 python-selenium should have an autopkgtest that tries to
run chromium
Hi,
On Thu, Feb 28, 2019 at 12:16:33PM +0100,
On Wed, 20 Feb 2019 19:39:39 + Anton Avramov wrote:
Package: chromium
Version: 72.0.3626.96-1~deb9u1
Severity: normal
Tags: upstream
Dear Maintainer,
We have many installation where chromium is started with
--remote-debugging-port= so we can easy debug remotely. After an
debian
On Wed, 20 Feb 2019 19:39:39 + Anton Avramov wrote:
Package: chromium
Version: 72.0.3626.96-1~deb9u1
Severity: normal
Tags: upstream
Dear Maintainer,
We have many installation where chromium is started with
--remote-debugging-port= so we can easy debug remotely. After an
debian
Package: chromium
Version: 72.0.3626.96-1~deb9u1
Severity: normal
Tags: upstream
Dear Maintainer,
We have many installation where chromium is started with
--remote-debugging-port= so we can easy debug remotely. After an
debian package upgrade from stable 70.xxx to 72.xxx chromium cannot
6 matches
Mail list logo
