Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apt (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1185159
Title:
Failing to fetch https sources with apt-get update
Status in “apt” package in Ubuntu:
Confirmed
Bug description:
Raring packages fail to build in PPAs that use https:// sources as
external dependencies when 'apt-get update' is called early on in the
build process. This is not happening when building packages for
Precise (which is the Ubuntu series we primarily work off of). Here
is a pastebin of an actual log:
https://pastebin.canonical.com/91731/
Here's what we know:
- The credentials used to access the external dependency are valid
(confirmed by timrc and lamont)
- The external dependency sources are reachable from a buildd where
the "apt-get update" failed via wget (confirmed by timrc, lamont, and
mthaddon)
- The problem does not appear architecture specific - the build
failure is confirmed for i386, amd64, and armhf (confirmed by timrc,
lamont, and infinity)
- The problem does not appear buildd specific - the build failure
will happen on which ever builder is used to build the package
(confirmed by timrc)
- The problem can be reproduced by downloading the raring chroot from
LP (e.g. chroot-ubuntu-raring-amd64.tar.bz2), adding the sources to
chroot-autobuild/etc/apt/sources.list.d/bootstrap.list (as they appear
in the external_dependency PPA field), and running "chroot chroot-
autobuild apt-get update" (confirmed by timrc, lamont, infinity)
- The problem occurs on Quantal (apt 0.9.7.5ubuntu5.4), Raring (apt
0.9.7.7ubuntu4), and Saucy (apt 0.9.7.7ubuntu4). Precise (
0.8.16~exp12ubuntu10.10) is fine (confirmed by infinity)
Other info:
- Quantal fails with a slightly different log message, e.g.
https://pastebin.canonical.com/91733/
- At least for the armhf failures on Raring, the build log shows apt-
get update printing garbage to the log when referencing one of these
external dependencies. Could it be that there is some sort of memory
corruption, here?
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: apt-transport-https 0.9.7.7ubuntu4
Uname: Linux 3.8.0-19-generic x86_64
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
Date: Tue May 28 19:34:07 2013
MarkForUpload: True
ProcEnviron: Error: [Errno 2] No such file or directory: '/proc/22833/environ'
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1185159/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
