This bug was fixed in the package ebtables - 2.0.10.4-3.4ubuntu2.16.04.2
---
ebtables (2.0.10.4-3.4ubuntu2.16.04.2) xenial; urgency=medium
[ Dan Streetman ]
* Never return failure during ebtables.init stop(), it can cause
errors during package upgrade (LP: #1774120)
* Add
This bug was fixed in the package ebtables - 2.0.10.4-3.5ubuntu2.17.10.3
---
ebtables (2.0.10.4-3.5ubuntu2.17.10.3) artful; urgency=medium
* Update versions to fix in prerm to Artful's ebtables versions
ebtables (2.0.10.4-3.5ubuntu2.17.10.2) artful; urgency=medium
[ Dan
This bug was fixed in the package ebtables - 2.0.10.4-3.5ubuntu2.18.04.3
---
ebtables (2.0.10.4-3.5ubuntu2.18.04.3) bionic; urgency=medium
* Update versions to fix in prerm to Bionic's ebtables versions
ebtables (2.0.10.4-3.5ubuntu2.18.04.2) bionic; urgency=medium
[ Dan
Tested version on Artful: 2.0.10.4-3.5ubuntu2.17.10.3
Log:
...
ubuntu@rbalint11:~$ sudo apt install --reinstall
ebtables=2.0.10.4-3.5ubuntu2.17.10.3
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and
Tested version on Xenial: 2.0.10.4-3.4ubuntu2.16.04.2
Log:
...
ubuntu@rbalint11:~$ sudo apt install --reinstall
ebtables=2.0.10.4-3.4ubuntu2.16.04.2
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following package was automatically installed and is
I'll be releasing this since the test case obviously only requires the
package to be installable, but for the future please be more verbose
with testing (i.e. xenial and artful). Even for simple test cases like
these please include what operations have been performed as part of
testing, noting
** Tags removed: verification-needed verification-needed-artful
verification-needed-xenial
** Tags added: verification-done verification-done-artful
verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774120
Title:
ebtables cannot be upgraded from 2.0.10.4-3.5ubuntu2
@rbalint
I can confirm working in bionic-proposed on WSL.
https://gist.github.com/sirredbeard/6c5f4a6501233c7887234e3b7ca64bc8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774120
Title:
@recalcitrantowl Thanks looking into verification. It usually takes a
little time to get the packages on the mirrors, it should be fine now
for all the releases.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks @rbalint, I just got back from vac.
** Changed in: ebtables (Ubuntu Trusty)
Assignee: Dan Streetman (ddstreet) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774120
I did some testing with bionic-proposed, it must not have come through
yet.
https://gist.github.com/sirredbeard/7afc9a95cb040a7d0886301cb26ccaae
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774120
Ok, actually I accepted the artful package too early. The artful and
xenial packages need a re-upload since the dpkg --compare-versions has
the version from bionic. Those need to be fixed to use version numbers
for their respective series.
So please re-upload xenial and artful. I'll reject xenial
Hello Hayden, or anyone else affected,
Accepted ebtables into artful-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/ebtables/2.0.10.4-3.5ubuntu2.17.10.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new
Hello Hayden, or anyone else affected,
Accepted ebtables into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/ebtables/2.0.10.4-3.5ubuntu2.18.04.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new
** Changed in: ebtables (Ubuntu Xenial)
Assignee: Dan Streetman (ddstreet) => Balint Reczey (rbalint)
** Changed in: ebtables (Ubuntu Artful)
Assignee: Dan Streetman (ddstreet) => Balint Reczey (rbalint)
** Changed in: ebtables (Ubuntu Bionic)
Assignee: Dan Streetman (ddstreet) =>
Thank you Balint.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774120
Title:
ebtables cannot be upgraded from 2.0.10.4-3.5ubuntu2 to
2.0.10.4-3.5ubuntu2.18.04.1 on WSL
To manage notifications
I also marked Trusty as wontfix since Trusty is not provided for WSL.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774120
Title:
ebtables cannot be upgraded from 2.0.10.4-3.5ubuntu2 to
@ddstreet I uploaded a backported patch to Bionic to make it to the .1
point release.
** Changed in: ebtables (Ubuntu Trusty)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On Wed, Jun 20, 2018 at 2:11 PM Dimitri John Ledkov
wrote:
>
> IMHO this is a class of issues on WSL. Given that systemd is not
> services should be attempted to be stopped, nor started.
I had the same idea for a little, but IMO trying to address the class
of potentially broken init scripts by
IMHO this is a class of issues on WSL. Given that systemd is not
services should be attempted to be stopped, nor started.
systectl calls are guarded and check for presense of
/run/systemd/system, I'm confused as to why the lsb-hook on ubuntu
doesn't have the same guard as well. Given that on
@ddstreet I think this is what @sil2100 suggested, indeed. @sil2100?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774120
Title:
ebtables cannot be upgraded from 2.0.10.4-3.5ubuntu2 to
@sil2100 @rbalint, if the above cosmic debdiff looks like what you're
suggesting, please upload it to cosmic, and I'll re-upload to the SRU
releases once cosmic is in place. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp1774120-cosmic-v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ebtables/+bug/1774120/+attachment/5151443/+files/lp1774120-cosmic-v2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@ddstreen I think @sil2100 is suggesting ignoring failed-upgrade from
known-bad versions in .prerm. It is an established practice and would
not shadow future different breakages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
> Why is the importance set to low here?
I set it to low because this bug will only happen AFAICT on WSL. It
will always happen there, but on WSL there is no use for ebtables (since
it doesn't work there, IIUC). So the major impact is 'apt upgrade'
fails, but users can easily work around that
I am wondering a bit about the debian/ebtables.prerm change you have
proposed in your upload. Your unconditional check for "failed-upgrade"
is a bit worrying. It makes sense for the case of upgrade from the
previous version, but what if a user has a much older version of the
package and the
Why is the importance set to low here? Is it because ebtables is dead
upstream? Since an upgrade issue for packages that are installed on end-
user systems (looks like it's seeded?) seems more serious to me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Tags added: id-5b0ff20a61c73d97a81ca9e0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774120
Title:
ebtables cannot be upgraded from 2.0.10.4-3.5ubuntu2 to
2.0.10.4-3.5ubuntu2.18.04.1 on WSL
This bug was fixed in the package ebtables - 2.0.10.4-3.5ubuntu4
---
ebtables (2.0.10.4-3.5ubuntu4) cosmic; urgency=medium
* Never return failure during ebtables.init stop(), it can cause
errors during package upgrade (LP: #1774120)
-- Dan Streetman Thu, 31 May 2018
Balint,
I have opened a bug report upstream with netfilter team, who inherited
ebtables, regarding this.
https://bugzilla.netfilter.org/show_bug.cgi?id=1259
Hayden
** Bug watch added: bugzilla.netfilter.org/ #1259
http://bugzilla.netfilter.org/show_bug.cgi?id=1259
--
You received this bug
Please note that WSL properly returns EPROTONOSUPPORT to socket() call
and ebtables binary translates this to a possible permission issue thus
WSL does not have to be fixed because it is not broken.
https://lists.ubuntu.com/archives/ubuntu-devel-
discuss/2018-May/018072.html
The ebtables.init
** Description changed:
+ [impact]
+
+ ebtables cannot be upgraded on Ubuntu 18.04 for WSL.
+
+ [test case]
+
+ on a WSL installation that already has ebtables installed (most
+ installations do), try to upgrade the package with apt or dpkg; its
+ prerm script will fail, and prevent the
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774120
Title:
ebtables cannot be upgraded from 2.0.10.4-3.5ubuntu2 to
2.0.10.4-3.5ubuntu2.18.04.1 on WSL
To manage
Dan and Eric,
Thank you for addressing this bug, I sincerely appreciate it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774120
Title:
ebtables cannot be upgraded from 2.0.10.4-3.5ubuntu2 to
Dan, I sponsored the change in devel release (cosmic).
You can go ahead with the SRU upload as soon as ebtables goes into
-releases.
Thanks !
** Changed in: ebtables (Ubuntu Cosmic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of
I can confirm the fix works on WSL
Preparing to unpack
.../ebtables_2.0.10.4-3.5ubuntu2.18.04.1+hf1774120v20180531b3_amd64.deb ...
invoke-rc.d: could not determine current runlevel
* Error: insufficient privileges to access the ebtables rulesets.
invoke-rc.d: initscript ebtables, action "stop"
** Patch added: "lp1774120-cosmic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ebtables/+bug/1774120/+attachment/5147057/+files/lp1774120-cosmic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The problem is that on WSL, it appears creating a raw socket is failing:
sockfd = socket(AF_INET, SOCK_RAW, PF_INET);
if (sockfd < 0) {
ebt_print_error("Problem getting a socket, "
"you probably don't
*I get the same result as @Hayden
(https://launchpad.net/~recalcitrantowl):*
m*o@M*Z:~$ sudo apt update
Get:1 http://security.ubuntu.com/ubuntu bionic-security InRelease [83.2 kB]
Hit:2 http://archive.ubuntu.com/ubuntu bionic InRelease
Get:3 http://archive.ubuntu.com/ubuntu bionic-updates
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ebtables (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774120
Title:
According to https://github.com/marchom:
"The problem comes from the install/remove scripts trying to do service
ebtables stop and failing. You can see this by trying to stop ebtables
manually."
https://github.com/Microsoft/WSL/issues/1761#issuecomment-392575807
The temporary workaround is an
42 matches
Mail list logo
