Uploaded.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/1610714
Title:
Evince crashes with _cairo_gstate_set_dash
Status in Poppler:
Unknown
Status in poppler package
All commands have bash completion since recent releases (1.3~exp2,
1.2.13). The former is in yakkety, the latter will hit xenial at some
point (or actually 1.2.14 or 1.2.15 will). We just have another bug
preventing 1.3~exp3 from being in yakkety, so we cannot start the 1.2.14
transition in xenial
It will come to (yakkety and) xenial eventually. But it's not urgent
enough to warrant a prioritised upload on its own IMO. There's some
other stuff I want to figure out first - like merging new translations,
and some other bug fixes from the 1.4 series.
--
You received this bug notification
The service is started by a (persistent) timer. The timer runs at 0600
and 1800 (+/-13). Apparently that timer elapsed before your boot.
That said, the reason it starts before a login manager is that it does
not depend on a login manager - why would it, it does not need that. And
systemd starts
It would be nice to have some more details, but I think it's a bit
unrealistic to display a web page in apt's error handling system.
** Changed in: apt (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: apt (Ubuntu)
Status: New => Triaged
--
You received this bug notification
Think about that: Your proxy returns 403 and you have 20 repositories,
and now get 20 messages, each 100 lines long because your proxy decided
to go fancy.
And of course: If reported as an actual error message, these things also
become python exceptions.
Or did you really just mean the message
** Package changed: python-apt (Ubuntu) => python2.7 (Ubuntu)
** Changed in: python2.7 (Ubuntu)
Status: Confirmed => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
Yes, please file a new bug. And that really seems more like an
unattended-upgrades bug, I can't believe it's a regression in 1.2.19 -
the change in 1.2.19 is just that:
+ Uri.Path = QuoteString(Uri.Path, "+~ ");
- just quoting the path component of the Uri before downloading it (in
the https
This does not happen only with apt-get update. A new temporary file is
created by (almost) every APT command if at least one of the main cache
files is outdated. It is then renamed to the final file. If APT exits
before the rename, the temporary filename might stay around until you
run clean.
Fix committed:
https://anonscm.debian.org/cgit/apt/apt.git/commit/?id=4759a70
commit 4759a702081297bde66982efed8b2b7fd39ca27c
Author: Julian Andres Klode <j...@debian.org>
Date: Wed Jan 18 20:39:27 2017 +0100
basehttp: Only read Content-Range on 416 and 206 responses
This
Locale wrongly configured. Needs to be UTF-8.
** Changed in: python-apt (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
*** This bug is a duplicate of bug 1667769 ***
https://bugs.launchpad.net/bugs/1667769
Marking as duplicate of bug #1667769, that one has more details.
** This bug has been marked a duplicate of bug 1667769
apt-daily.service running too early in boot process
--
You received this bug
Unfortunately for us, systemd provides no good interface to improve
things. There's the ability to wait on network, but AFAIUI that does not
really help much, as it does not deal with resume. Also waiting on the
network could time out, and the service would then be marked as failed
and also run 12
This has been released in zesty too, but seems we forgot to close it.
Doing so 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 apt in Ubuntu.
Add a systemd drop-in if you want to constraint times. Note that it
schedules a random time, not 6 and 18:00 (it is randomized by 12 hours).
** Changed in: apt (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Queued for 1.2.20:
https://github.com/Debian/apt/compare/1.2.19...julian-
klode:1.2.y?expand=1
Queued for 1.3.5:
https://github.com/Debian/apt/compare/1.3.4...julian-
klode:1.3.y?expand=1
** Also affects: apt (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: apt
Queued for 1.2.20:
https://github.com/Debian/apt/compare/1.2.19...julian-
klode:1.2.y?expand=1
Queued for 1.3.5:
https://github.com/Debian/apt/compare/1.3.4...julian-
klode:1.3.y?expand=1
** Also affects: apt (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects
Queued for 1.2.20:
https://github.com/Debian/apt/compare/1.2.19...julian-
klode:1.2.y?expand=1
Queued for 1.3.5:
https://github.com/Debian/apt/compare/1.3.4...julian-
klode:1.3.y?expand=1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Public bug reported:
Errors when running xdiagnose.
Errors when playing audio and sound player.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
Uname: Linux 4.8.0-37-generic i686
.tmp.unity_support_test.0:
@Samuel Matzek (smatzek) Your comment is far too long, I did not read
that. I only read the first sentence, and thus conclude that you believe
the patch fixes this issue.
If you want to help, provide a *concise* instructions to test this by
editing the bug report using the guidelines specified in
Fixed in 1.4~beta1. This will be cherry picked into the 1.3 and 1.2
(yakkety and xenial) branches in the next weeks.
** Changed in: apt (Ubuntu)
Status: Confirmed => Fix Released
** Also affects: apt (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: apt
Did you upgrade libapt-pkg5.0? No? This bug has been fixed. If you
already have a partial file, it fails due to bug 1657567 - but the space
-> %20 encoding in the redirect *has* been fixed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Changed in: packagekit (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1664303
Title:
Merge packagekit 1.1.5-1 (main)
Releases uploaded. The fix is exactly the same as in zesty, I just added
an additional test case based on the new 1.4~beta4 release (the test
case also needed some porting because the framework between 1.4 and 1.3
is a bit different).
** Changed in: apt (Ubuntu Xenial)
Status: Triaged =>
@llucax there are two versions (and two calls for testing). 1.2.19 for
xenial and 1.3.4 for yakkety.
--
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
Could you provide logs with -o debug::acquire::https=1 and
debug::acquire::http=1
Maybe thw redirect changed and the test case this started working again?
I'll check soon.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt
Another test case is downloading
"https://people.debian.org/~jak/a b/c"
with apt-helper. That fails in 1.2.18 and succeeds in 1.2.19.
** Description changed:
[Impact]
- Downloads via HTTPS fail if the URL contains a space. This breaks packages
like ttf-mscorefonts-installer and various
Again: You need to install apt-transport-https, not apt. Nobody cares
about your version of the apt package, the fix is in apt-transport-
https.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
@Robin: I just confirmed that apt 1.2.19 fixes the corefonts issue:
All fonts downloaded and installed.
Setting up ttf-mscorefonts-installer (3.4+nmu1ubuntu2) ...
Did you really upgrade apt-transport-https or only apt?
But bdmurray is right, the ardour thing works fine in 1.2.18. In xenial
The first log looks entirely correct. The server is broken, vorboss does
not support partial requests, but instead of responding correctly with
all the content, it just redirects to another location. That other
location is http, so unencrypted which we do not allow for security
reasons.
Re the
And note that the redirect from vorboss is to a site that indicates a
failure, not the file.
Or in short: Sourceforge sucks, don't use it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
This problem does not occur with that file on xenial, as it first
redirects to an https URI without a space which then redirects to an
HTTPS uri with a space (http w/o space -> https w/o space -> https w/
space). In xenial, https->https redirects where handled internally by
curl.
Another test
Public bug reported:
APT only allows Content-Range: */ to be specified on a 416
response. Sourceforge sometimes replies with that in a 302 redirect.
We should probably just accept and silently ignore that content-range
field for other values.
** Affects: apt (Ubuntu)
Importance: Low
The Content-Range issue with partial downloads on SF is tracked in bug
1657567 now. That's less urgent though, so we may just want to roll that
one out when I do the next "scheduled" bugfix update.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
OK. We now have comments of success from yakkety and xenial, and I have
also checked both, so marking it verified-done.
I'll open up a new bug for the partial download issue.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you
** Changed in: apt (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/1657567
Title:
"Conte
Fix has been committed upstream with an additional test case:
https://anonscm.debian.org/cgit/apt/apt.git/commit/?id=994515e689dcc5f963f5fed58284831750a5da03
I'll sync the new version from Debian unstable once I have uploaded and
it is known by Launchpad. I will also upload SRUs tomorrow - the
** Description changed:
+ [Impact]
+ Downloads via HTTPS fail if the URL contains a space. This breaks packages
like ttf-mscorefonts-installer and various third party hosters.
+
+ [Test case]
+ Check that /usr/lib/apt/apt-helper download-file
** Changed in: apt (Ubuntu Xenial)
Status: Triaged => In Progress
** Changed in: apt (Ubuntu Yakkety)
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.
** Changed in: apt (Ubuntu Xenial)
Status: Triaged => In Progress
** Changed in: apt (Ubuntu Yakkety)
Status: Triaged => In Progress
** Changed in: apt (Ubuntu Xenial)
Importance: Undecided => Low
** Changed in: apt (Ubuntu Yakkety)
Importance: Undecided => Low
--
You
** Changed in: apt (Ubuntu Xenial)
Status: Triaged => In Progress
** Changed in: apt (Ubuntu Yakkety)
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.
Oh, sorry, did not notice that it did not have one.
--
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/1657567
Title:
"Content-Range: */" on non-416 responses considered invalid
Seems like sourceforge is fixed now, so we need to come up with a new
test.
** Description changed:
APT only allows Content-Range: */ to be specified on a 416
response. Sourceforge sometimes replies with that in a 302 redirect.
We should probably just accept and silently ignore that
** Summary changed:
- New upstream microrelease 1.3.5
+ [SRU] Update apt/yakkety to1.3.5
** Summary changed:
- [SRU] Update apt/yakkety to1.3.5
+ [SRU] Update apt/yakkety to 1.3.5
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
kasz Kawczynski ]
* Honour Acquire::ForceIPv4/6 in the https transport
[ Julian Andres Klode ]
* basehttp: Only read Content-Range on 416 and 206 responses (LP: #1657567)
* Only merge acquire items with the same meta key (Closes: #838441)
* Do not package names representing .dsc/.deb/... f
Also see #1668285 for the xenial bug.
** Also affects: apt (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Changed in: apt (Ubuntu)
Status: New => Fix Released
** Changed in: apt (Ubuntu Yakkety)
Status: New => In Progress
--
You received this bug notification
Only complete understood file paths for install
(LP: #1645815)
[ Lukasz Kawczynski ]
* Honour Acquire::ForceIPv4/6 in the https transport
[ Julian Andres Klode ]
* basehttp: Only read Content-Range on 416 and 206 responses (LP: #1657567)
* Only merge acquire items with
Uploaded now.
--
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/1668280
Title:
[SRU] Update apt/yakkety to 1.3.5
Status in apt package in Ubuntu:
Fix Released
Status in apt
Public bug reported:
[Impact]
This collects several bug fixes from the 1.4 branch. Most of the stuff has been
in Debian since 20 days, and in testing since Feb 12.
Fixes in the acquire system - mostly error cases.
* basehttp: Only read Content-Range on 416 and 206 responses (LP: #1657567)
*
Michael and I don't have any different opinion here at all. You are
complaining about root/.synaptic/tmp//tmp_cl - which is owned by
synaptics - not about the /var/cache/apt/archives/partial or another apt
owned directory.
A directory inside your (well, root's) home directory is a different
case
We should probably drop the 1.2.14 SRU - there is a regression in the
proxy autodetection code in which it now reads output scripts write on
stderr. Fix is:
https://anonscm.debian.org/git/apt/apt.git/commit/?id=0ecceb5bb9cc8727c117195945b7116aceb984fe
This is already fixed in 1.3.1, and I'll
Notably, there has been no related change of the mirror method since the
trusty release. So if it started working later, than that is related to
the reworked acquire system.
As such, I'd like this bug to be closed as invalid, as it's not worth
it. The pre 1.1 acquire system cannot really deal
"Marking dev + xenial as Invalid since it works from Xenial onward"
You marked trusty and dev as invalid, and kept xenial open?
Unfortunately, there have been huge changes in the acquire system in
1.1, so there is likely no way to fix this in trusty.
--
You received this bug notification
Essential packages not installed will be installed automatically by APT,
packages with the Important field will not be. Important also does not
have the same ordering requirements as Essential. It's main use case is
building configuration metapackages:
Note that a normal user should never see this: They normally do not
remove the init package.
--
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/1624681
Title:
"Important" control
Going to upload a fixed APT shortly. There's also some other broken
stuff in installation ordering, and missing large file support that
should really be fixed now.
** Changed in: apt (Ubuntu)
Assignee: (unassigned) => Julian Andres Klode (juliank)
--
You received this bug notificat
To clarify what happened here:
(1) *vcard is an fnmatch() expression matching 2vcard
(2) vcard* is an unanchored regular expression matching 2vard.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
There are three types of patterns
(1) word
(2) fnmatch() style
(3) regex
They're all intermangled together, so: A bare word only matches a direct
match. If it includes a special character like * then it tries matching
a fnmatch pattern first, and if that fails, tries to match a regex. And
these
Nothing to be done for apt here due to legal reasons. I'm marking this
as invalid, but might just remove the task completely later on
** Changed in: apt (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
** 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/1640267
Title:
Softwarecenter there's no Employment
Status in
now. This change also
needs the two refactoring commits for the removal methods and the new
pretty printers mentioned in the changelog.
apt (1.2.15) xenial; urgency=medium
[ Julian Andres Klode ]
* methods/ftp: Cope with weird PASV responses.
Thanks to Lukasz Stelmach
by then).
** Changed in: apt (Ubuntu Xenial)
Status: Triaged => In Progress
** Changed in: apt (Ubuntu Xenial)
Assignee: (unassigned) => Julian Andres Klode (juliank)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
OK, Launchpad lost the comment, so let me repeat it:
No, we cannot legally link APT's https method against OpenSSL, the
licenses are not compatible.
** Package changed: apt (Ubuntu) => gnutls28 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
APT recommends gnupg, and gnupg recommends dirmngr, so all is working as
intended. If you want to use optional (deprecated) features of apt-key
like adv, you have to manually install gnupg. If you want to use
optional features depending on key servers, you have to install dirmngr
manually.
The
This bug seems to be a duplicate of bug 1633754
--
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/1634234
Title:
apt-key leaves files in /dev open after exit
Status in apt
I get you what you say. But there is a distinction between (manually)
upgradeable packages and packages that will be upgraded (automatically).
I'm not going to decide whether the status is Opinion, Won't Fix, or
Triaged, as I'm not entirely sure what we really want to do.
--
You received this
*** This bug is a duplicate of bug 1592817 ***
https://bugs.launchpad.net/bugs/1592817
Marking this as a duplicate of bug 1592817. This is an APT bug to be
fixed in the upcoming 1.2.16, which is hopefully passing CI soon.
** This bug has been marked a duplicate of bug 1592817
gdebi-gtk
** Changed in: bash (Ubuntu Trusty)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/1422795
Title:
bash crashes often if inputrc
Public bug reported:
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 propagates into
further calls).
I'll revert that for 1.2.16, as it depends on
This never affected any other release than xenial
** 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.
https://bugs.launchpad.net/bugs/1641905
Title:
SRU was rejected. See bug 1644363 for the actual cause of the issue
(hint: ld crashes during static configure).
We might still want to get that fixed in new releases though, but I'm
unsure if this needs updates in stable releases (maybe it improves
security, who knows...).
** Changed in: bash
Thanks for verifying. I should have the final update ready within the
next 16-48 hours.
--
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/1642386
Title:
At least one invalid
** Description changed:
Enviroment: Ubuntu 16.10.5 Yakkety Yak http://cdimage.ubuntu.com/daily-
live/current/
HW: Toshiba portege Z30-A12T | Intel i5+intel graphics | SSD hd
Preconditions: W10+Xenial xerus installed, internet connection, 3rd
party sw and updates selected
No, there is no such print() equivalent. You have puts() which just
takes a string, but that appends a newline. Or fwrite(), but that
requires size and count, which is boring.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Description changed:
Enviroment: Ubuntu 16.10.5 Yakkety Yak http://cdimage.ubuntu.com/daily-
live/current/
HW: Toshiba portege Z30-A12T | Intel i5+intel graphics | SSD hd
Preconditions: W10+Xenial xerus installed, internet connection, 3rd
party sw and updates selected
+
** Description changed:
Continuously get that warning when using synaptic to reload the sources.
This happen with apt 1.3-exp2 only.
This seems a regression as per that old report:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809329
ProblemType: Bug
DistroRelease: Ubuntu
** Description changed:
Errors Bucket
-
https://errors.ubuntu.com/problem/31a80b4c477107c659b93a4277ed46c14a3c8c53
and
https://errors.ubuntu.com/problem/c349b36522b1d43e2604357f75f0215fdafe1c7a
- Gdebi crashed while installing Google Chrome .deb-fil bur the error
- didn't
Public bug reported:
This weirdly only fails on arm64.
../.././builtins/../.././builtins/help.def:130:7: error: format not a
string literal and no format arguments [-Werror=format-security]
The attached debdiff will be uploaded to trusty-proposed soon.
** Affects: bash (Ubuntu)
Apparently zesty has the same code in it, but it weirdly works there.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/1644048
Title:
4.3-7ubuntu1.6 FTBFS on arm64
Status in
The build failure on arm64 is tracked in bug 1644048 now. Moving this to
in progress again, until we figured out why it fails (or rather why it
does not fail on most platforms) and fixed it.
** Changed in: bash (Ubuntu Trusty)
Status: Fix Committed => In Progress
--
You received this bug
** Summary changed:
- 4.3-7ubuntu1.6 FTBFS on arm64
+ 4.3-7ubuntu1.6 FTBFS on arm64 only with format-security error
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/1644048
Uploaded 1.2.17 to xenial-proposed
apt (1.2.17) xenial; urgency=medium
[ David Kalnischkies ]
* apt-key: warn instead of fail on unreadable keyrings (LP: #1642386)
* show apt-key warnings in apt update (Closes: 834973)
[ Julian Andres Klode ]
* test-releasefile-verification
Notably the first commit just causes the thing to fail silently, the
second one makes apt forward the warning on an update.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
** Description changed:
- This weirdly only fails on arm64.
+ [Impact]
+ Breaks build on arm64 in trusty:
../.././builtins/../.././builtins/help.def:130:7: error: format not a
string literal and no format arguments [-Werror=format-security]
- The attached debdiff will be uploaded to
** Description changed:
[Impact]
Breaks build on arm64 in trusty:
../.././builtins/../.././builtins/help.def:130:7: error: format not a
string literal and no format arguments [-Werror=format-security]
[Test case]
Check it builds
[Regression potential]
- Indefinitely low.
+
Turns out it does not build on arm64 because the internal gettext is
used because binutils (ld) crashes during the configure test for the
static build.
That's tracked in bug 1644363 and this SRU basically has to wait for
that to get fixed...
--
You received this bug notification because you are
** Tags removed: verification-done
** Tags added: verification-failed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/1422795
Title:
bash crashes often if inputrc contains
Don't change the assignment on a (fixed) issue please, yon.
** Changed in: apt (Ubuntu)
Assignee: yon (thornyon) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
It works perfectly fine for me. Can you re-run this with:
-o Debug::Acquire::gpgv=1
** 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.
Oh, you may also want to try moving lists/ out of the way and running
apt update again.
And perhaps send me a tarball of /var/lib/apt and /etc/apt - then I
might have luck reproducing it.
If you want to, you could try bisecting this in the apt git repo,
starting with
git bisect start
git bisect
Your coworker seems to have caught a crash in appstream, BTW, not in
apt. Not sure why the files fail their hashes or have no sections in
them, though.
** Changed in: apt (Ubuntu)
Assignee: (unassigned) => Julian Andres Klode (juliank)
--
You received this bug notification because
** Changed in: apt (Ubuntu)
Importance: Undecided => High
--
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/1642386
Title:
At least one invalid signature was encountered.
What we see from your debug output is that gpgv is not returning any
sensible information:
Summary:
Good:
Bad:
Worthless:
SoonWorthless:
NoPubKey:
You could try running apt-key verify manually on a few InRelease files (like
apt-key verify
First thanks for the files. Unfortunately, I can't reproduce it with the
files either. It must be a fairly system-specific bug.
> HEAD is now at 235347e... Release 1.2.12
> $ make fast
> [... with errors]
Whoa, if it happens with the 1.2.12 checkout too, then something else
seems wrong. I picked
Ah, apt-key explains it. We did not catch that in the bisect correctly,
as I forgot to specify -o Dir::Bin::apt-key=$PWD/build/bin/apt-key :/
This means it is a regression introduced in:
commit b515fe3a0012c1f155dbf6a4199e919fec102578
Author: David Kalnischkies
Date:
105503b4b470c124bc0c271bd8a50e25ecbe9133. I cherry-picked that change in
my for-1.2/apt-key branch in https://github.com/julian-klode/apt.
You should be able to verify this by adding -o Dir::Bin::Apt-
Key="$PWD/build/bin/apt-key" to the apt-get invocation in the script and
then running it once with the normal 1.
Yeah, valgrind is a bit noisy always because we are building the cache
in memory before (1) writing it to the disk and the write includes
unused regions and (2) we are hashing the entire thing before writing
it, including the uninitialised bytes. So that means while we do have a
few uninitialized
Failed to build on arm64:
../.././builtins/../.././builtins/help.def: In function 'help_builtin':
../.././builtins/../.././builtins/help.def:130:7: error: format not a string
literal and no format arguments [-Werror=format-security]
--
You received this bug notification because you are a
You can fix your permissions on your trusted.gpg and trusted.gpg.d files
in /etc/apt, so that the files are world-readable (chmod ugo+r
/etc/apt/trusted.gpg /etc/apt/trusted.gpg.d -R) [or give access to root
and _apt via acls].
You don't have to do that, though - it will start "working" again in
But of course: If you safely want to get apt 1.2.17 via apt 1.2.15, you
have to have correct permissions first - otherwise your old apt won't
see the new apt.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
301 - 400 of 2559 matches
Mail list logo