manpages for interfaces(5) uses two different source packages across releases

Bug #1677435 reported by Ryan Harper
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu Manpage Repository
New
Undecided
Unassigned

Bug Description

Looking at manpages.ubuntu.com for interfaces(5) and there are two different source packages that get referenced:

12.04 -> 15.10 we see ifupdown_0.X as the source

http://manpages.ubuntu.com/manpages/trusty/en/man5/interfaces.5.html

16.04 and newer point to ifupdown2 which is in universe, not main.

http://manpages.ubuntu.com/manpages/xenial/en/man5/interfaces.5.html

I don't think we should be pointing to ifupdown2 which it's not in main

% rmadison ifupdown
 ifupdown | 0.7~beta2ubuntu8 | precise | source, amd64, armel, armhf, i386, powerpc
 ifupdown | 0.7~beta2ubuntu11.1 | precise-updates | source, amd64, armel, armhf, i386, powerpc
 ifupdown | 0.7.47.2ubuntu4 | trusty | source, amd64, arm64, armhf, i386, powerpc, ppc64el
 ifupdown | 0.7.47.2ubuntu4.4 | trusty-updates | source, amd64, arm64, armhf, i386, powerpc, ppc64el
 ifupdown | 0.7.48.1ubuntu10 | vivid | source, amd64, arm64, armhf, i386, powerpc, ppc64el
 ifupdown | 0.8.10ubuntu1 | xenial | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x
 ifupdown | 0.8.10ubuntu1.2 | xenial-updates | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x
 ifupdown | 0.8.13ubuntu2 | yakkety | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x
 ifupdown | 0.8.13ubuntu3 | yakkety-updates | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x
 ifupdown | 0.8.16ubuntu1 | zesty | source, amd64, arm64, armhf, i386, ppc64el, s390x

% rmadison ifupdown2
 ifupdown2 | 1.0~git20151029-1 | xenial/universe | source, all
 ifupdown2 | 1.0~git20160525-1 | yakkety/universe | source, all
 ifupdown2 | 1.0~git20170114-1 | zesty/universe | source, all

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.