squid3 FTBFS due to missing --name arg to pod2man
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | Squid |
Unknown
|
Unknown
|
||
| | squid3 (Ubuntu) |
High
|
Unassigned | ||
Bug Description
squid3 fails with:
dh_install -psquid3 --sourcedir=
cp: cannot stat '/«PKGBUILDDIR»
dh_install: cp --reflink=auto -a /«PKGBUILDDIR»
make: *** [binary-
/usr/share/
caused by helpers/
The error in config.test is caused by a missing --name argument to pod2man:
IO::File=
POD document had syntax errors at /usr/bin/pod2man line 71.
This also affects helpers/
Cause
=====
Since Perl 5.20.2-4 pod2man behavior changed for pipes and now the --name parameter must be included (or --errors set to 'pod', 'stderr', or 'none'). As per Debian [1] and pod2man change log page [2]:
"[Pod::Man] Attempt to detect if the input came from a pipe and therefore has a completely unhelpful (and nonreproducible) source file name, and diagnose this as an error. Document that the name option (--name to pod2man) is required when processing POD source from standard input. (Debian Bug#777405)"
[1] https:/
[2] http://
Related branches
| tags: | added: ftbfs |
| description: | updated |
| Daniel Holbach (dholbach) wrote : | #3 |
It fails to build for me on amd64 wily:
libtool: link: g++ -I/usr/
| Tiago Stürmer Daitx (tdaitx) wrote : | #4 |
Daniel, thanks for sponsoring this.
I apologize, the main discussion for Squid FTBFS was being done in LP: #1496223 and I forgot to add here the piece that this patch actually requires libecap2 gcc5 transition for it to work. I also missed the fact that the bot subscribed ubuntu-sponsors, which was not my intention - at least until we decide to either keep the current squid3 version or merge a newer from Debian.
What is the appropriate action: should I remove the patch from here or just drop the patch flag+patch checkbox? If the latter then someone will have to unsubscribe ubuntu-sponsors.
| Tiago Stürmer Daitx (tdaitx) wrote : | #5 |
libecap3 was been deleted. I have created LP: #1504200 to handle the gcc5 transition. After it gets sponsored it should be ok to apply this fix.
| Launchpad Janitor (janitor) wrote : | #6 |
This bug was fixed in the package squid3 - 3.3.8-1ubuntu16
---------------
squid3 (3.3.8-1ubuntu16) wily; urgency=medium
[ Tiago Stürmer Daitx ]
* d/patches/
logical-
* d/patches/
(LP: #1496223)
* d/patches/
pod2man (LP: #1501566)
* roll back build-dependency to libecap2-dev, this version of squid3 is not
compatible with libecap3 and libecap3 transition has been rolled back for
wily.
-- Steve Langasek <email address hidden> Fri, 09 Oct 2015 00:29:47 +0000
| Changed in squid3 (Ubuntu): | |
| status: | New → Fix Released |
| Changed in squid3 (Ubuntu): | |
| importance: | Undecided → High |


The attachment "patch with fixes for this bug as well as LP: #1496223 and LP: #1496924" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.]