Hah, you're right. Not much we can do about that though I think, as the
message comes from dpkg. Except maybe add a message stating that the
files are somewhere else than mentioned.
We are abusing dpkg's recursive unpacking feature to clean the ordering
code up a bit.
** Changed in: apt (Ubuntu)
That's not apt related, but gnome-software.
** Package changed: apt (Ubuntu) => gnome-software (Ubuntu)
--
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/1641936
Title:
Uploaded 1.2.16. We should really have a SRU [Test case] thingy, though.
--
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/1611010
Title:
yakkety desktop - non-english
1.2.16 uploaded.
** Changed in: apt (Ubuntu Xenial)
Status: Confirmed => In Progress
--
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/1592817
Title:
gdebi-gtk crashed
** Changed in: apt (Ubuntu Xenial)
Status: New => In Progress
** Description changed:
In 1.2.15 the unit tests (which run at build time) fail with an error
message in the atomic files test, because I picked a commit that
improved the error handling a bit (a previous error now
The issue is:
/<>/test/libapt/fileutl_test.cc:376: Failure
Value of: f.Close()
Actual: false
Expected: true
Note that the test suite is not guaranteed to run during the build -
there are dependency tracking issues in the build system, causing it to
not build sometimes. But where it builds,
Marking as Fix released as per previous comment.
** Changed in: apt (Ubuntu)
Status: Confirmed => Fix Released
--
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/1593583
The 1.2.16 SRU also references this bug, but there's no actual test case
for that: It just fixes a regression that would be introduced otherwise
in the very same upload.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in
This should actually be fix released. It's also fixed in xenial now with
1.2.15 being in -updates now
** Changed in: apt (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
That sounds like an interesting idea.
--
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/1637801
Title:
Incorrect Russian translation of "apt list --upgradeable" results
Status
apt 1.2.16~rc1 just hit the PPA (might take some time for processing,
though):
https://launchpad.net/~deity/+archive/ubuntu/apt-1.2
and should fix this bug. It would be great to have some confirmation of
that before uploading that, otherwise I'll go ahead with an SRU tomorrow
probably if I
apt 1.2.16~rc1 just hit the PPA (might take some time for processing,
though):
https://launchpad.net/~deity/+archive/ubuntu/apt-1.2
and should fix this bug. It would be great to have some confirmation of
that before uploading that, otherwise I'll go ahead with an SRU tomorrow
probably if I
And JFTR, I can confirm that the translations we ship with apt itself
are correct, so this really is a language pack-only issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
Ah right. It's fixed in 1.2.13 and newer, so see the relevant SRU bugs
for those.
** Changed in: apt (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
SRU bugs = bug #1595177 and bug #1638021
--
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/1637801
Title:
Incorrect Russian translation of "apt list --upgradeable" results
Let's clean this up.
** Package changed: python-apt (Ubuntu) => apt (Ubuntu)
** Changed in: apt (Ubuntu)
Status: Triaged => Fix Released
** Also affects: apt (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: gdebi (Ubuntu Xenial)
Importance: Undecided
*** This bug is a duplicate of bug 1472351 ***
https://bugs.launchpad.net/bugs/1472351
** This bug has been marked a duplicate of bug 1472351
autoremove keeps *all* providers of virtual rdeps unconditionally
--
You received this bug notification because you are a member of Ubuntu
Touch
*** This bug is a duplicate of bug 1472351 ***
https://bugs.launchpad.net/bugs/1472351
** This bug has been marked a duplicate of bug 1472351
autoremove keeps *all* providers of virtual rdeps unconditionally
--
You received this bug notification because you are a member of Ubuntu
Touch
This was fixed in yakkety. The fix is also in 1.2.15 in xenial-proposed.
But as that one is already uploaded, I'm not going to add an extra
xenial task to this bug.
** Changed in: apt (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a
Yes, the translations are updated to relatively recent ones from 1.3~rc3
in 1.2.15. I still need to write down a "merge translations" script, as
I forgot how I did it when I did that (otherwise we'd have the 1.3.1
translations already).
Basically what I'm doing is merge the 1.2 template with the
APT should keep those kernels in recent versions:
# Mark as not-for-autoremoval those kernel packages that are:
# - the currently booted version
# - the kernel version we've been called for
# - the latest kernel version (as determined by debian version number)
# - the second-latest kernel
Well, the script says your /etc/apt/apt.conf.d/ directory with all apt
configuration was deleted. Now, I'm not sure why this happened, but it
was probably an accident on your side.
Thus, there really is nothing to do here for us, but for you: Reinstall
your system and be more careful with the
*** This bug is a duplicate of bug 1633754 ***
https://bugs.launchpad.net/bugs/1633754
Let's merge it with the other one.
** This bug has been marked a duplicate of bug 1633754
dirmngr is used as daemon
--
You received this bug notification because you are a member of Ubuntu
Touch
Confirmed. Seems to crash in pkgSystem::ArchitecturesSupported(), called
transitively from pkgSourceList::Type::ParseLine()
** Changed in: apt (Ubuntu)
Importance: Undecided => Medium
** Changed in: apt (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification
Right, I understand this argument. We should think about this a bit
more.
** Changed in: apt (Ubuntu)
Importance: Undecided => Medium
** Changed in: apt (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Confirmed. Seems to crash in pkgSystem::ArchitecturesSupported(), called
transitively from pkgSourceList::Type::ParseLine()
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
Oh, it surely understands -h, that's why it prints you that message. It
does not understand that you want help on a command, though, and I'm not
sure that will be implemented soon. Possibly late 2017 / early 2018,
this requires breaking some interfaces.
** Changed in: apt (Ubuntu)
Status:
** Summary changed:
- no help for options
+ no help for commands
--
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/1606793
Title:
no help for commands
Status in apt package in
The passwd file is in an inconsistent state, someone did not clean up a
lock on it. We are using the same way to add users everyone else uses,
so it's not our fault :)
** Changed in: apt (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member
I can tell you that this will never even happen. Too many things can go
wrong with this.
** Changed in: dpkg (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: apt (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
** Package changed: apt (Ubuntu) => nvidia-graphics-drivers-352 (Ubuntu)
--
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/1637943
Title:
apt fails trying to upgrade nvidia-352
This is very likely fixed in 1.3, as that got a whole lot of reworking
in that area (and thus not backportable). If it pops up again with 1.3,
please reopen the bug or report a new one.
** Changed in: apt (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification
We actually need a log if we want to do something about this. Just
telling us that some postinst script failed does not help anyone.
You could look at the term.log files in /var/log/apt/
** Changed in: apt (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because
We actually need a log if we want to do something about this. Just
telling us that some postinst script failed does not help anyone.
You could look at the term.log files in /var/log/apt/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Well, this can happen if it conflicts on some level. There's nothing we
can do about that in apt.
** Package changed: apt (Ubuntu) => boo (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
Sorry, but your system is horribly broken: It cannot even find it's mv
command, which causes it to fail here. There's nothing we can do about
it if a system misses essential programs.
** Changed in: apt (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are
useradd: existing lock file /etc/gshadow.lock without a PID
That's not apt's fault. Something or somebody edited the user database
and did not unlock again. APT uses the same useradd command every other
package uses.
** Changed in: apt (Ubuntu)
Status: New => Invalid
--
You received
Did you place a command called sed somewhere in your bin directories?
Because that makes no sense at all:
ssh: connect to host sed.zoom.ph port 69: No route to host
sed is the stream editor, an essential part of the operating system.
** Changed in: apt (Ubuntu)
Status: New => Invalid
--
That system is broken: useradd: cannot open /etc/passwd
** Changed in: apt (Ubuntu)
Status: Confirmed => Invalid
--
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/1573862
Closing. It is not APT's job to make sure unrelated basic system
configuration is correct.
** Changed in: apt (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
These kind of things *should not* happen anymore today. In ancient
versions like the one in trusty, things are a bit more fragile, but
there was a lot of reworking in the 1.1 series and newer.
** Changed in: apt (Ubuntu)
Status: New => Fix Released
--
You received this bug notification
Well, this can happen. Talk to the repository owners, and perhaps ask
them to switch to by-hash layout if they update often - The normal
format is not safe against modification (see
https://wiki.debian.org/RepositoryFormat).
In any case, this is a bug in the repo, not in apt.
** Changed in: apt
As seth wrote, something really went wrong somewhere. But that system is
basically completely screwed up: Not only does it miss essential system
programs, it also misses files in the database. I don't think any
software caused that.
** Changed in: apt (Ubuntu)
Status: Confirmed => Invalid
> useradd: existing lock file /etc/gshadow.lock without a PID
Not sure why there is an existing lock file, but it's clearly not apt's
fault - we just do the same as every other package adding a user.
** Changed in: apt (Ubuntu)
Status: New => Invalid
--
You received this bug
You seem to have deleted all your APT configuration files, the entire
/etc/apt/apt.conf.d/ directory. That's why it's not working.
** Changed in: apt (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
This should not happen...
# Mark as not-for-autoremoval those kernel packages that are:
# - the currently booted version
# - the kernel version we've been called for
# - the latest kernel version (as determined by debian version number)
# - the second-latest kernel version
Not sure what went
*** This bug is a duplicate of bug 1483989 ***
https://bugs.launchpad.net/bugs/1483989
** This bug has been marked a duplicate of bug 1483989
prints nonsense diagnostics
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Well, that's what happens if a lot of other packages depend on the
package you want to remove.
** Changed in: apt (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
As Adam wrote, that is documented and by design: The order of sources
determines the source for a given package version.
** Changed in: apt (Ubuntu)
Status: New => Opinion
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Marking as incomplete, as per previous comments.
** Changed in: apt (Ubuntu)
Status: New => Incomplete
--
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/1502704
Title:
That's kind of expected, if _apt cannot write to that directory. But
it's a warning, not an error.
** Changed in: apt (Ubuntu)
Status: Confirmed => Invalid
** Summary changed:
- flashplugin-installer shows an error message after downloading the file with
apt 1.1.x
+
** Summary changed:
- prints nonsense diagnostics
+ prints wrong time after update
** Summary changed:
- prints wrong time after update
+ apt prints wrong time after update
** Summary changed:
- apt prints wrong time after update
+ apt prints wrong duration after update
--
You received this
The correct approach is to have gettext look into the langpack
translations first, and then fall back to the package's translations.
That's also the way it was explained to work: Packages ship initial
translations for bootstrapping purposes, and those can be updated via
language packs.
I have no
the
kernels not to be autoremoved or something. We have this code in Debian
testing and unstable since 1.3~pre1 early July and its in yakkety, and
are reasonably sure it's stable now.
apt (1.2.15) xenial; urgency=medium
(Most bugfixes until to and including 1.3.1)
[ Julian Andres Klode ]
* methods
commits for the removal methods and the new pretty printers
+ mentioned in the changelog.
apt (1.2.15) xenial; urgency=medium
- (Most bugfixes until to and including 1.3.1)
+ [ Julian Andres Klode ]
+ * methods/ftp: Cope with weird PASV responses.
+ Thanks to Lukasz Stelmach
It might have been mixed up with additional translations. That is, a
language missing in the package can still be translated by the language
pack. I'm not entirely sure what the argument was back then anymore, but
something like that was how it was explained to me.
OK let's be clearer: I want the
No, that's precisely why the error message exists. It's an optional
feature. There's a Recommends for gnupg2 for those who really really
want to use that stuff.
** Changed in: apt (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
This is a gnupg issue. During should notice that we took its home away
and shut itself down like the fog agent does.
** Changed in: apt (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
APT does not care about those keys. dpkg verifies them while unpacking
and gpgv here just prints a short key id instead of a fingerprint (long
id is broken as well).
The only thing we could do is disable the gpg signature check in dpkg-
source when APT calls it for a secure package (that is, pass
(tag change as per previous comment)
** Tags removed: verification-needed
** Tags added: verification-done
--
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/1611010
Title:
We are testing this exact case in the test suite, and it ran
successfully for 1.2.18, hence verification-done.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Confirming fixed in 1.2.18
** Tags removed: verification-needed
** Tags added: verification-done
--
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/1641905
Title:
Minor unit
We know. This is fixed in zesty-proposed (in 1.4~beta1 actually). It
will be backported into 1.3.3 later this month.
** Changed in: apt (Ubuntu)
Status: New => Fix Committed
** Also affects: apt (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Changed in: apt (Ubuntu
** Description changed:
+ [Impact]
+ Causes automatic upgrades by unattended-upgrades to be interrupted if apt is
configured, leaving the system in a partially configured state.
+
+ [Test case]
+ Install apt - make sure the apt-daily.service is not restarted (this systemd
service runs
Uploaded 1.3.3 to yakkety-proposed. There'll be another message once it
has been accepted to -proposed for testing.
** Changed in: apt (Ubuntu Yakkety)
Status: Confirmed => Fix Committed
** Changed in: apt (Ubuntu Yakkety)
Status: Fix Committed => In Progress
--
You received this
*** This bug is a duplicate of bug 1649959 ***
https://bugs.launchpad.net/bugs/1649959
Just to add: I marked this as a duplicate of bug #1649959 a few hours
ago, but I was on the go, so I did not have time to write a comment. See
the other bug for more information.
--
You received this bug
Proxy Auto detect for https works perfectly fine, but there's a catch:
The proxy needs to be the same type as the URL. So https only supports
an https proxy, not an http proxy url.
I'm not sure how far we should open that up, but https via http and http
via https are things you probably want to
*** This bug is a duplicate of bug 1651923 ***
https://bugs.launchpad.net/bugs/1651923
There is no regression. Period. It's a myth.
Sourceforge changed to include a space in some redirects, braking the
whole damn thing because we decode the redirect and https does not
reencode it.
Marking
I just uploaded 1.4~rc3ubuntu1 to zesty. It's building now, and should
hit zesty-proposed soon, and hopefully migrate without issues to zesty
release repository.
This is the included workaround for now:
commit 12d5863a6ecd358db5645a4c1ca75576ef3c6232
Author: Julian Andres Klode <j...@debian.
** Also affects: apt (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: apt (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: apt (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you
** No longer affects: apt (Ubuntu Trusty)
** Changed in: apt (Ubuntu Yakkety)
Status: Confirmed => Triaged
** Changed in: apt (Ubuntu Xenial)
Status: Confirmed => Triaged
** Changed in: apt (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug
*** This bug is a duplicate of bug 1651923 ***
https://bugs.launchpad.net/bugs/1651923
That does not really matter if it was there before or not. The problem
is that there is now a redirect. That apparently was not there before.
In any case, this might take months to resolve for xenial - I
** Changed in: apt (Ubuntu)
Status: Triaged => In Progress
--
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/1651923
Title:
apt https method decodes redirect locations
This is actually apt ordering code, and that's been reworked in yakkety
to the extend that this is very likely fixed (it now does far less
explicit ordering of actions).
** Package changed: dpkg (Ubuntu) => apt (Ubuntu)
** Changed in: apt (Ubuntu)
Status: Confirmed => Fix Released
--
** Tags added: verification-done
--
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/1647467
Title:
InRelease file splitter treats getline() errors as EOF
Status in apt package
*** This bug is a duplicate of bug 1651923 ***
https://bugs.launchpad.net/bugs/1651923
Duplicate of #1651923
** This bug has been marked a duplicate of bug 1651923
apt https method decodes redirect locations and sends them to the
destination undecoded.
--
You received this bug
(Ubuntu)
Assignee: (unassigned) => Julian Andres Klode (juliank)
--
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/1651923
Title:
apt https method decodes redirect locati
No regression. The quick hack we can try for now is parsing the URI we
get and then encoding the local part. This is what I'm aiming for this
month and it will fix this issue.
The correct fix requires restructuring the whole acquire system to not
decode URIs in redirect requests and encode given
*** This bug is a duplicate of bug 1651923 ***
https://bugs.launchpad.net/bugs/1651923
That is a problem on sourceforge:
E: Failed to fetch
https://netix.dl.sourceforge.net/project/corefonts/the%20fonts/final/andale32.exe
Redirection from https to
These are different bugs.Or rather, we definitely fixed the
if float(percent) != self.percent or status_str != self.status:
Aug 8 13:49:44 ubuntu /plugininstall.py: ValueError: could not convert string
to float: '0,'
thing here. And to keep our sanity (especially WRT to the SRU fixing
Not sure about the ubiquity task, though, I unmerged the other bug
reports (which actually are 2 distinct ones), but did not mark it as
fixed again.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
OK, we triaged this further on github. Reopening here, so we can track
progress on the distro side as well.
** Changed in: apt (Ubuntu)
Status: Invalid => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in
Likely. See, the whole thing happens when the call stack is unwound in
response to the first error here. In the other cases, the status update
happens elsewhere.
So, what happened here is that we fixed the first error on the apt side,
and used this bug to track that (and marked it as such in the
Actually:
jak@jak-x230:~/Downloads$ ls *.deb
AdbeRdr9.5.5-1_i386linux_enu.deb debhelper_9.20160115ubuntu3_all.deb
jak@jak-x230:~/Downloads$ _filedir "deb"
jak@jak-x230:~/Downloads$ echo $_
deb
jak@jak-x230:~/Downloads$ _filedir "*.deb"
jak@jak-x230:~/Downloads$ echo $_
Actually it seeAnd it seems the completion is working correctly:
(1) Without a leading ./, only package names are used
# apt install xy
xye xye-data xymon xymon-client xyscan
(2) With ./, only file names are used
# apt install ./x
xyzzy.deb
ms the completion is
The completion is still wrong anyway: apt only accepts ./package.deb,
not package.deb. And it seems to work here as it.
--
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/1645815
>From what I gathered, msttcorefonts and flashplugin-nonfree
(flashplugin-installer) are affected by this, hence adding tasks for
them.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
The message won't be removed. It's worded as good as it can be now.
Maintainer scripts using apt-helper to download stuff (or clients using
libapt-pkg) should be fixed to use proper permissions on the directories
so the _apt user can write files (best create a temporary directory I'd
say owned by
** Summary changed:
- 505 HTTP Version not supported - installing kxstudio packages
+ apt https method decodes redirect locations and sends them to the destination
undecoded.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Currently running CI on https://github.com/Debian/apt/compare/master
...julian-klode:bugfix/lp-1653094-https-quote?expand=1 let's see if that
simple change works or if it needs more work.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
*** This bug is a duplicate of bug 1651923 ***
https://bugs.launchpad.net/bugs/1651923
Oh wait. You did not pass the %20 one, but the other thing.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
The problem is: the http methods URL-encodes URLs before sending them,
the https one does not. And our redirecting code decodes the locations
given, because the http method encodes them.
This is of course horribly broken: We should not decode the location and
re-encode it in the first place. That
*** This bug is a duplicate of bug 1651923 ***
https://bugs.launchpad.net/bugs/1651923
It does work. The input URL you pass to it must not be encoded, though.
http://downloads.sourceforge.net/project/corefonts/the%20fonts/final/andale32.exe
will be encoded to
I believe this will take quite some time to fix. A correct fix will have
to wait until the end of the year, but we might be able to hack
something in like what I did there - but really only quoting the local
part and not the entire URL - which obviously fails.
--
You received this bug
*** This bug is a duplicate of bug 1651923 ***
https://bugs.launchpad.net/bugs/1651923
Duplicate of bug 1651923 - and the others too, of course.
** This bug has been marked a duplicate of bug 1651923
apt https method decodes redirect locations and sends them to the
destination undecoded.
Steve: Yes, the sandbox user exists to protect people from bugs in our
http protocol handler, ssl libraries, compressors, etc.
Now, why do we have to write a line about that (I'd not call that
noisy): First of all, we want scripts/programs using apt to also use
sandboxed downloading. Without a
*** This bug is a duplicate of bug 1649959 ***
https://bugs.launchpad.net/bugs/1649959
** This bug has been marked a duplicate of bug 1649959
unattended upgrade of apt kills running apt-daily job
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Ah no, my Debian was just using a proxy in between. It fails there too.
--
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/1651923
Title:
505 HTTP Version not supported -
Right:
/usr/lib/apt/apt-helper download-file
http://kxstudio.linuxaudio.org/repo/pool/free/ardour4_4.7.0-1kxstudio1_i386.deb
test.deb
Err:1
http://kxstudio.linuxaudio.org/repo/pool/free/ardour4_4.7.0-1kxstudio1_i386.deb
505 HTTP Version not supported
** Also affects: curl (Ubuntu)
Adding curl to the loop. It works fine on Debian, but fails in yakkety,
and there have been no changes in our https module.
Attaching a log: We send the server a HTTP/1.1 request and it responds
with one
** Attachment added: "HTTP log"
301 - 400 of 2457 matches
Mail list logo
