This MIR request has been abandoned a support point of view for C/B.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746598
Title:
[MIR] libnfs
To manage notifications about this bug go to:
This MIR request has been abandoned a support point of view.
** Changed in: libnfs (Ubuntu Bionic)
Assignee: Eric Desrochers (slashd) => (unassigned)
** Changed in: libnfs (Ubuntu Cosmic)
Assignee: Eric Desrochers (slashd) => (unassigned)
** Changed in: libnfs (Ubuntu Bionic)
** Changed in: libnfs (Ubuntu Bionic)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: libnfs (Ubuntu Cosmic)
Assignee: (unassigned) => Eric Desrochers (slashd)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: libnfs (Ubuntu Bionic)
Assignee: Eric Desrochers (slashd) => (unassigned)
** Changed in: libnfs (Ubuntu Cosmic)
Assignee: Eric Desrochers (slashd) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: libnfs (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: libnfs (Ubuntu Cosmic)
Importance: Undecided => High
** Changed in: libnfs (Ubuntu Bionic)
Status: New => In Progress
** Changed in: libnfs (Ubuntu Cosmic)
Status: New => In Progress
**
** Also affects: libnfs (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: libnfs (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I started to look how much effort the above fixes requirement will
implies.
Most fixes involved modifying 'lib/nfs3.c' and 'lib/nfs_v3.c' not yet
existing in current Bionic/Cosmic version (2.0.0) due to some 'code
moving' and 'code addition'.
I start to doubt that it will be a good idea to
Bellow is the review for 2.0.0 - cosmic and bionic. Pls feel free to add
your considerations :)
build dependencies:
- debhelper, dh-autoreconf, libnfs11
- No CVE history
- Security bugs found between 2.0.0...3.0.0:
commit 486b74f64717dfb8bef774fc795636fa4faf4071
sorry, didn't the next soname bump.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746598
Title:
[MIR] libnfs
To manage notifications about this bug go to:
@doko To be fair, the MIR team asked for 2.0, which is what's in bionic
and cosmic, not 3.0, which the security team is hoping for. That said,
I'm not against the backport-and-rebuild-rdeps solution, if that looks
to be the best way forward.
--
You received this bug notification because you are
@sil2100 ^
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746598
Title:
[MIR] libnfs
To manage notifications about this bug go to:
@sil200 Just properly reviewing what needs to be backported seems to be
more work than fixing the media players in older releases:
https://github.com/sahlberg/libnfs/compare/libnfs-2.0.0...sahlberg:libnfs-3.0.0
Most likely simple rebuilds of the rdeps would be enough.
--
You received this bug
On 19.03.19 16:20, Łukasz Zemczak wrote:
> Looking at this with my SRU hat on, I'd prefer if we could avoid
> backporting a completely new upstream version to bionic especially if
> there is a soname bump involved. It's not impossible of course, we do
> that for certain projects when there's need
Looking at this with my SRU hat on, I'd prefer if we could avoid
backporting a completely new upstream version to bionic especially if
there is a soname bump involved. It's not impossible of course, we do
that for certain projects when there's need for it, but I'd suppose we
would require a 'hard'
Leonidas, upgrading from 2.0.0 to 3.0.0 bumps the soname and would
require updates of kodi, mpd, and vlc. Normally, we don't do library
transitions in SRUs. (libnfs11 → libnfs12)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello!
It was asked us Sec Team to review this pkg for cosmic and bionic (both version
2.0.0).
>From the security team point of view it would be better if the version in
>these release was upgrade to version 3.0.0 as it is the same of disco and it
>was already MIRed/reviewed. So if it is
I'm removing the lines for other series and using bug #1637988 for the
SRU instead
** No longer affects: libnfs (Ubuntu Bionic)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746598
Title:
[MIR]
** No longer affects: libnfs (Ubuntu Xenial)
** No longer affects: libnfs (Ubuntu Cosmic)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746598
Title:
[MIR] libnfs
To manage notifications about
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746598
Title:
[MIR] libnfs
To manage notifications about this bug go to:
@cyphermox,
It was "Fix Released" for disco only[1], can we complete it for stable
releases ?
[1] - rmadison
libnfs | 1.2.0-3| precise/universe | source
libnfs | 1.3.0-2ubuntu1 | trusty/universe | source
libnfs | 1.9.8-1| xenial/universe | source
libnfs | 2.0.0-1~exp1 |
I'm not sure I understand the request. This is a paperwork bug that was
Fix Released, as libnfs was moved to the right location; it does not
really affect anything for supported releases.
If you need some changes made to packages, please file a separate new
bug with your specific request so that
Can this fix please be backported to Bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746598
Title:
[MIR] libnfs
To manage notifications about this bug go to:
Override component to main
libnfs12 3.0.0-2 in disco amd64: universe/libs/optional/100% -> main
libnfs12 3.0.0-2 in disco arm64: universe/libs/optional/100% -> main
libnfs12 3.0.0-2 in disco armhf: universe/libs/optional/100% -> main
libnfs12 3.0.0-2 in disco i386: universe/libs/optional/100% ->
Updating the status to fix committed thus, after doko's and Leonidas'
feedbacks.
** Changed in: libnfs (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
Availability
Built for all supported architectures. In sync with Debian.
Rationale
=
gvfs 1.24 added an NFS backend 3 years ago. It was enabled in Debian a year
ago, but we can't enable it in Ubuntu until libnfs is promoted to main.
I reviewed libnfs (3.0.0-1) from disco
- Build dependencies:
- debhelper, dh-autoreconf, libopt-dev
- Few issues on github
- NO CVE history
- no pre or postinst scritps
- no systemd unit files
- no system dbus services
- no setuid files
- Some binaries:
/usr/bin/nfs-cp:
Position
** Description changed:
Availability
Built for all supported architectures. In sync with Debian.
Rationale
=
gvfs 1.24 added an NFS backend 3 years ago. It was enabled in Debian a year
ago, but we can't enable it in Ubuntu until libnfs is promoted to main.
** Description changed:
Availability
Built for all supported architectures. In sync with Debian.
Rationale
=
gvfs 1.24 added an NFS backend 3 years ago. It was enabled in Debian a year
ago, but we can't enable it in Ubuntu until libnfs is promoted to main.
** Changed in: libnfs (Ubuntu)
Assignee: Ubuntu Security Team (ubuntu-security) => Leonidas S. Barbosa
(leosilvab)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746598
Title:
[MIR] libnfs
A lack of NFS support is a big issue for Enterprise deployments.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746598
Title:
[MIR] libnfs
To manage notifications about this bug go to:
Postponing this for 18.10 would be a problem, IMO. Please include it in
18.04.x (LTS). This missing package not only does not allow a Nautilus
browse, it also breaks deja dup nfs functionality as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libnfs (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/1746598
Title:
2.0 now in the release pocket. The packging looks ok, so assigning to
the security team for a review.
** Changed in: libnfs (Ubuntu)
Status: Incomplete => New
** Changed in: libnfs (Ubuntu)
Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)
--
You received this bug
The package ended up in unstable thus apparently FTP Masters agreed with
my opinion that license-wise the package is ok.
It can be synced to Ubuntu and we can run the small transition before
Bionic's release.
I'm a bit concerned about potential memory handling issues, since libnfs
had some in
I updated the package to 2.0 but it is held up in experimental/NEW due
to the SO bump. It needs a small transition in universe to have it in
Bionic but I think it would be fairly smooth - no big symbol changes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
chatting with the Debian libnfs maintainer, the recommendation is to
update to libnfs 2.x first. So maybe delay that for 18.10.
** Changed in: libnfs (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Description changed:
Availability
Built for all supported architectures. In sync with Debian.
Rationale
=
gvfs 1.24 added an NFS backend 3 years ago. It was enabled in Debian a year
ago, but we can't enable it in Ubuntu until libnfs is promoted to main.
37 matches
Mail list logo
