apt_all doesn't grok Ubuntu

[Soren Hansen]

Binary package hint: munin

apt_all tries to figure out how many packages are going to be installed from stabe, testing, and unstable. That's rather useless on Ubuntu.

What we probably want to do is to have it look for the same type of numbers for ${RELEASE}, ${RELEASE}-backports, ${RELEASE}-proposed, ${RELEASE}-updates, and ${RELEASE}-security. These numbers can be grabbed by doing something like "apt-get -s dist-upgrade | grep -c "^Inst.*/${pocket})$".

kthxbye

[Nicolas Valcarcel (nvalcarcel)]

We can also use: "lsb_release -a 2> /dev/null | grep Codename | cut -f2" to find the ${RELEASE}" to find out the ${RELEASE}

[Launchpad Janitor (janitor)]

This bug was fixed in the package munin - 1.2.6-1ubuntu2

---------------
munin (1.2.6-1ubuntu2) intrepid; urgency=low

  * debian/patches/220-honor-pid-file.patch:
    - Dropped no longer needed.
  * debian/patches/221-apt-ubuntu-changes.patch:
    - Make apt_all.in Ubuntu specific (LP: #245031)

 -- Chuck Short <email address hidden> Thu, 03 Jul 2008 13:05:52 +0000

[Martin Jackson (mhjacks)]

I believe this bug has re-surfaced. Looking at /usr/share/munin/plugins/apt_all on both 12.04 and Quantal, it appears that @releases is back to being "stable", "testing", "unstable" which unfortunately errors out on Ubuntu systems.

[Kenyon Ralph (kralph)]

On 2012-08-17T04:09:06-0000, Martin Jackson <email address hidden> wrote:
> I believe this bug has re-surfaced. Looking at
> /usr/share/munin/plugins/apt_all on both 12.04 and Quantal, it appears
> that @releases is back to being "stable", "testing", "unstable" which
> unfortunately errors out on Ubuntu systems.

You should open a new bug report and refer to this one, otherwise the
Ubuntu package maintainer may not notice your comment.

--
Kenyon Ralph

[Daniel Hahler (blueyed)]

The patch that has been used appears to be:
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/karmic/munin/karmic/revision/15/debian/patches/221-apt-ubuntu-changes.patch

The new bug being reported about this is bug 1038044.