This bug was fixed in the package lcov - 2.0-1ubuntu0.2
---
lcov (2.0-1ubuntu0.2) mantic; urgency=medium
[ Sudip Mukherjee ]
* Remove patches supporting old gcc. (LP: #2029924)
- These patches modified geninfo which are now affecting gcc-13 in Mantic.
[ Dave Jones ]
*
I can confirm that the lcov package in mantic-proposed has fixed the bug
for me.
Test done:
1. Install lcov on a Mantic image
2. Execute "lcov -h" and confirmed the issue is still seen
3. Add mantic-proposed to apt sources.list
4. Install lcov from mantic-proposed
5. Execute "lcov -h" again to
Hello Danilo, or anyone else affected,
Accepted lcov into mantic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/lcov/2.0-1ubuntu0.2 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Aha! After a little more investigation it appears we're just missing
libtimedate-perl as a runtime dependency (it already has libdatetime-
perl, but libtimedate-perl is required for Date/Parse.pm ... and those
two names aren't *horribly* confusing!). Anyway, that's a trivial change
so I'll patch
I'd generally agree with Sudip that fixing the version issue shouldn't
be a blocker for an SRU fix that moves the package from "completely
broken" to "at least mostly working" (querying the version is certainly
useful functionality, but it's not the core function of the package or
vital to it's
You have manually overriden the pin for lcov in proposed to 400 using a
package-specific pin in /etc/apt/preferences so that takes precedence
over the -t option (which is pinning the Packages line to 990).
Not sure why you do this but in any case you can install by specifying
lcov/mantic-proposed
Hi Sudip,
Still trying to get lcov working on and off :).
You asked for the output of apt cache:
bp@bas-hp:~ % apt-cache policy lcov
lcov:
Installed: (none)
Candidate: 2.0-1
Version table:
2.0-1ubuntu0.1 400
100 http://nl.archive.ubuntu.com/ubuntu
** Description changed:
[ Impact ]
lcov is completely unusable as it will always give the following error
when lcov is executed.
$ lcov --help
Can't locate lcovutil.pm in @INC (you may need to install the lcovutil
module) (@INC contains: /usr/local/lib/lcov /etc/perl
iiuc, "get_version.sh" is not needed for proper functioning of the
package, its only a cosmetic change which will print the proper version
information in the "LCOV version" part of the report. And, I believe
fixing only a warning about "get_version.sh" should not be SRU. But,
please correct me if
This was in the sponsors queue, so I took a look as part of today's
shift.
I can confirm the behavior observed in this comment:
https://bugs.launchpad.net/ubuntu/+source/lcov/+bug/2029924/comments/15
There is a reference to a get_version.sh that is not present in this (or
any) binary package.
Hi Bas,
1. Have you enabled proposed for universe or only main ?
2. What is the output from the follwing command:
apt-cache policy lcov
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2029924
Title:
Arghh... I wrote you name wrong and I can't edit my comment :(.
Apologies again...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2029924
Title:
[SRU] "Can't locate lcovutil.pm" after updating to
Hi Supid, I am really sorry but I don't know how to install the fix. Not that
familiar with linux as I should be I guess.
- I again added the proposed repos
- sudo apt remove lcov
- sudo apt-get install lcov -t mantic-proposed (I am pretty sure this installed
the wrong version again, the 2.0.1)
13 matches
Mail list logo
