It's fine, it's pretty non-obvious that the two differ in some behaviors
and even more so that it's intentional.
--
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/2038490
Title:
@Krister If you are interested in driving the process to get the patch
landed, you can follow the procedure at
https://packaging.ubuntu.com/html/fixing-a-bug.html
And
https://wiki.ubuntu.com/StableReleaseUpdates
To prepare updates for all releases. Feel free to ask for help on IRC.
If not, no
** Description changed:
[Impact]
The snapshot service provides users access to older states of the archive
with ease of use, and enables a consistent user experience across all supported
releases, as otherwise users would have to rewrite their sources.list to make
use of snapshots and set u
** Changed in: apt (Ubuntu Jammy)
Status: Confirmed => In Progress
** Changed in: apt (Ubuntu Focal)
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.l
jammy and focal packages uploaded to the archive for SRU
jammy, focal, and bionic also uploaded to
https://launchpad.net/~deity/+archive/ubuntu/apt/+packages
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
htt
@mruffel did you mean to get sponsoring for the patches? you might then
want to subscribe ~ubuntu-sponsors so this can be merged by the patch
pilots.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https:/
trusty and xenial receive bug updates via Pro and not via the main
archive anymore, you'll have to get SEG to add bug tasks for Pro and
prepare +esm updates with them.
** Changed in: e2fsprogs (Ubuntu Trusty)
Status: In Progress => Won't Fix
** Changed in: e2fsprogs (Ubuntu Xenial)
Public bug reported:
[Impact]
autopkgtest suite on arm64 is basically useless, as about a third of the tests
do not work, because they rely on apt-ftparchive generating an archive
[Test case]
Substantially less tests should fail, there should be no segfaults.
[Regression potential]
I am cherry-
Public bug reported:
[Impact]
apt autopkgtest on armhf fails in trusty, as it applies the no_proxy setting to
the apt.conf defined proxy, which fails a test that requires using the proxy.
Cherry pick a fix to unset all proxy related variables that we've been
using in apt since 2015.
[Test case]
Public bug reported:
[Impact]
test-apt-progress-fd-error is failing on trusty due to a space difference, but
the failure is not causing the tests to fail.
[Test case]
The fix fixes the test case and rewrites it to also detect failure. We can
however, only detect success in the testsuite, as we
** Description changed:
[Impact]
Dpkg::Post-Invoke is run only when dpkg had to be run. We'd like to be able
to show some extra output even if no changes had been made. Imagine "the user
disabled the security repo, and does not get any updates shown scenario" - we'd
like to be able to tell
** Description changed:
[Impact]
json hooks ending with EPIPE on first read fail, but should simply do
nothing.This causes spurious failures of uninstalled hooks.
[Test case]
- TODO
+ Cannot generate one. This was discovered by snapd ci, but I did not find a
reproducer yet.
+
+ FWIW, t
** Description changed:
[Impact]
These are not driven from a direct user experience, but are related to other
developments:
(1) unattended-upgrades could use the never pinning to disable
repositories rather than switching candidates. That would simplify code
quite a bit.
(2) Pac
** Description changed:
[Impact]
- json hooks ending with EPIPE on first read fail, but should simply do
nothing.This causes spurious failures of uninstalled hooks.
+ json hooks ending with EPIPE on first read fail, but should simply do
nothing. This causes spurious failures of uninstalled hoo
** Also affects: apt (Ubuntu Trusty)
Importance: Undecided
Status: New
--
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/1815760
Title:
Additional hooks for update
Sta
** Description changed:
[Impact]
These are not driven from a direct user experience, but are related to other
developments:
(1) unattended-upgrades could use the never pinning to disable
repositories rather than switching candidates. That would simplify code
quite a bit.
(2) Pac
I don't see anything to work with in those bugs anyway, sounds like
memory corruption _somewhere_; the stack trace is basically irrelevant.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.lau
** Description changed:
[Impact]
Backport auth.conf.d support to allow specifying per-repository
authentication data in separate files, so packages can setup authenticated
repositories.
[Regression potential]
We ignore errors from opening auth.conf.d files, so regressions can only
oc
** CVE removed: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-3462
--
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/1787460
Title:
Unattended upgrades removed linux-image-
** CVE removed: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-3462
--
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/1812696
Title:
APT doc and manpage uses wrong ubuntu-co
** Also affects: apt (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: linux-meta (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: linux-meta-hwe (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: apt (Ubuntu Xenial)
** Changed in: apt (Ubuntu Trusty)
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/1817048
Title:
apt/trusty: Stack overflow in apt-ftparc
** Changed in: apt (Ubuntu Xenial)
Status: Triaged => In Progress
** Changed in: apt (Ubuntu Trusty)
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.lau
** Changed in: apt (Ubuntu Trusty)
Status: New => In Progress
** Changed in: apt (Ubuntu Xenial)
Status: New => In Progress
** Changed in: apt (Ubuntu Bionic)
Status: New => In Progress
** Changed in: apt (Ubuntu Cosmic)
Status: New => In Progress
** Changed in: apt
** Changed in: apt (Ubuntu Bionic)
Status: New => In Progress
** Changed in: apt (Ubuntu Cosmic)
Status: New => 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.n
** Changed in: apt (Ubuntu Trusty)
Status: New => In Progress
** Changed in: apt (Ubuntu Xenial)
Status: New => In Progress
** Changed in: apt (Ubuntu Bionic)
Status: New => In Progress
** Changed in: apt (Ubuntu Cosmic)
Status: New => In Progress
--
You received th
** Changed in: apt (Ubuntu Trusty)
Status: New => In Progress
** Changed in: apt (Ubuntu Xenial)
Status: New => In Progress
** Changed in: apt (Ubuntu Bionic)
Status: New => In Progress
** Changed in: apt (Ubuntu Cosmic)
Status: New => In Progress
--
You received th
** Description changed:
+ [Impact]
+ packagekit (sometimes) crashes when there are errors.
+
+ [Test case]
+ Check that there are no further cases on the error tracker with the proposed
version.
+
+ [Regression potential]
+ Given that this just changes the return type of a function only used in
SRUs uploaded for bionic and cosmic. Since we do not use packagekit in
gnome-software in xenial, not fixing it there.
Also not fixing it in trusty, as it's close to EOL.
** Changed in: packagekit (Ubuntu Cosmic)
Status: New => In Progress
** Changed in: packagekit (Ubuntu Bionic)
S
** Also affects: apport (Ubuntu)
Importance: Undecided
Status: New
** Changed in: apport (Ubuntu)
Status: New => Fix Committed
** Changed in: apport
Status: In Progress => Fix Committed
** Also affects: apport (Ubuntu Bionic)
Importance: Undecided
Status: New
*
Sure
** Changed in: apt (Ubuntu Disco)
Status: Incomplete => 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/1814727
Title:
Backport never pinning and Pack
Verified - 1.2.30 in xenial-proposed passes the tests
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to a
Verified - The complete test suite now passes on arm64 with
apt/1.0.1ubuntu2.21.
** Tags removed: verification-needed verification-needed-trusty
** Tags added: verification-done verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Touch seeded package
Verified - the test is now passing in the 1.0.1ubuntu2.21 autopkgtest
run.
** Tags removed: verification-needed verification-needed-trusty
** Tags added: verification-done verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, whi
I have verfied from the autopkgtest runs that the specified tests have
passed in all releases:
- 1.7.3 in cosmic
- 1.6.9 in bionic
- 1.2.30 in xenial
- 1.0.1ubuntu2.21 in trusty
I specifically checked that test-packages-require-authorization run, and
that test-policy-pinning has more tests run th
bionic 1.6.9 verified:
# man sources.list apt_preferences | grep bionic; grep -H bionic
/usr/share/doc/apt/examples/sources.list
deb http://us.archive.ubuntu.com/ubuntu bionic main restricted
deb http://security.ubuntu.com/ubuntu bionic-security main restricted
de
Verfied cosmic 1.7.3:
# man sources.list apt_preferences | grep cosmic
deb http://us.archive.ubuntu.com/ubuntu cosmic main restricted
deb http://security.ubuntu.com/ubuntu cosmic-security main restricted
deb http://us.archive.ubuntu.com/ubuntu cosmic-updates main
xenial 1.2.30 verified:
deb http://us.archive.ubuntu.com/ubuntu xenial main restricted
deb http://security.ubuntu.com/ubuntu xenial-security main restricted
deb http://us.archive.ubuntu.com/ubuntu xenial-updates main
restricted
Suites: xenial xenial-upd
** Changed in: apt (Ubuntu Trusty)
Status: In Progress => 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/1815760
Title:
Additional hooks for update
Status in a
Verified by running echo TEST1815761 as the hook, across all releases
with their SRU versions (as shown in the log below).
$ lxc exec apt-cosmic -- apt upgrade apt -tnow -o
APT::Install::Post-Invoke-Success::="/bin/echo TEST1815761"
Reading package lists... Done
Building dependency tree
Verified - I ran the specified command, and saw exactly two lines for
both bionic's 1.6.9 and cosmic's 1.7.3; as expected (one for each hook
variant).
$ lxc exec apt-bionic -- apt -o AptCli::Hooks::Install::="/usr/bin/printf
'{error should be json}\n\n' >&3" install
Reading package lists... Done
Public bug reported:
[Impact]
apt in disco and the current set of SRUs introduce support for .conf snippets
in auth.conf.d, but accidentally did not introduce the auth.conf.d directory,
making it hard to discover if support for it exists, and requiring users to
create the dir if it is missing -
There is a bug in that we do not install the auth.conf.d directory in
the package, I'm tracking this in bug 1818996 and will soon push out new
SRUs with the additional directory and a fix for a wrong hook name.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Also affects: apt (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: apt (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: apt (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: apt (Ubuntu Cosmic)
Importance: Un
Ugh, the hook name is wrong (should be Update:: vs Update-), fix
incoming later.
** Description changed:
[Impact]
We want to write some scripts for apt that run on update if apt shows an
update count, to provide further details about the new cache.
[Test case]
- Specify a APT::Update
The auth.conf.d support in trusty and xenial does not seem to be working
for https repos at least. Gotta re-investigate, it was working when I
committed it, and xenial has a test case for it, so odd.
** Tags removed: verification-needed-trusty verification-needed-xenial
** Tags added: verification
Oh, this is slightly embarrassing: THe reason it failed is that I forgot
to update apt-transport-https in trusty and xenial.
After upgrading apt-transport-https, auth.conf.d support is working
correctly in both 1.0.1ubuntu2.21 in trusty-proposed, and 1.2.30 in
xenial-proposed.
** Tags removed: ve
That should be fixed in trusty or newer, as apt does not allow different
versions of M-A: same to be marked for install since 486d190
** Changed in: apt (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded package
** Changed in: apt (Ubuntu Trusty)
Status: Won't Fix => 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/1815760
Title:
Additional hooks for update
Status in apt
FWIW, the same seems to apply to me, but not just HDMI.
I have:
* Digital output on external DAC
* Analog output on external DAC
* HDMI
* Speakers
I can change as I want to, the active output device does not change.
I think it's the same for recording devices, seeing as pacmd stat lists
the sam
Opening pavucontrol after changing the setting in gnome-control-center
switches it half of the time, so there seems to be a problem in
pulseaudio with listening to changes and applying them.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is s
OK, so:
* add-apt-repository should support logging in to launchpad and adding
private ppas
* private PPAs should be added with auth.conf.d for the auth data
* to avoid having to login to launchpad on a server, something like:
- add-apt-repository should gain a --stdin switch that contains li
Reverified against 1.2.31 and 1.0.1ubuntu2.22, updating with an
auth.conf.d snippet worked fine.
** Tags removed: verification-needed verification-needed-trusty
verification-needed-xenial
** Tags added: verification-done verification-done-trusty
verification-done-xenial
--
You received this bu
I have reverfied from the autopkgtest runs that the specified tests have
passed in all releases:
- 1.7.4 in cosmic
- 1.6.10 in bionic
- 1.2.31 in xenial
- 1.0.1ubuntu2.22 in trusty
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic verification-needed-trus
All tests passed with 1.0.1ubuntu2.22 as well.
** Tags removed: verification-needed verification-needed-trusty
** Tags added: verification-done verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in U
Tests still passing in ubuntu2.22
** Tags removed: verification-needed verification-needed-trusty
** Tags added: verification-done verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https:
All reverified against the new versions (versions in log below).
$ lxc exec apt-cosmic -- apt upgrade apt libapt-pkg5.0 -tnow -o
APT::Install::Post-Invoke-Success::="/bin/echo TEST1815761"
Reading package lists... Done
Building dependency tree
Reading state information... Done
apt is alrea
New uploads verified.
$ lxc exec apt-cosmic -- sh -c "apt-cache policy apt | grep -o Installed.* &&
dpkg -S /etc/apt/auth.conf.d"
Installed: 1.7.4
apt: /etc/apt/auth.conf.d
$ lxc exec apt-bionic -- sh -c "apt-cache policy apt | grep -o Installed.* &&
dpkg -S /etc/apt/auth.conf.d"
Installed: 1.6
Cosmic remains fixed as well.
** Tags removed: verification-needed verification-needed-cosmic
** Tags added: verification-done verification-done-cosmic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bu
(cosmic being 1.7.4)
--
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/1812696
Title:
APT doc and manpage uses wrong ubuntu-codename
Status in apt package in Ubuntu:
Fix Relea
1.2.31 is good as well.
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.lau
xenial 1.2.31 looks good:
+ apt-cache policy apt
+ grep -o Installed.*
Installed: 1.2.31
+ apt update -o APT::Update::Post-Invoke-Stats::=/bin/echo TEST1815760
Hit:1 http://archive.ubuntu.com/ubuntu xenial InRelease
Get:2 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [109 kB]
bionic 1.6.10 looks good as well:
+ apt-cache policy apt
+ grep -o Installed.*
Installed: 1.6.10
+ apt update -o APT::Update::Post-Invoke-Stats::=/bin/echo TEST1815760
Hit:1 http://archive.ubuntu.com/ubuntu bionic InRelease
Get:2 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB
Reverified with 1.7.4 and 1.6.10
$ lxc exec apt-bionic -- apt -o AptCli::Hooks::Install::="/usr/bin/printf
'{error should be json}\n\n' >&3" install
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following package was automatically installed a
As does cosmic 1.7.4:
+ apt-cache policy apt
+ grep -o Installed.*
Installed: 1.7.4
+ apt update -o APT::Update::Post-Invoke-Stats::=/bin/echo TEST1815760
Get:1 http://security.ubuntu.com/ubuntu cosmic-security InRelease [88.7 kB]
Hit:2 http://archive.ubuntu.com/ubuntu cosmic InRelease
Get:3 http
There do not seem to be any more of these crashes, and no regression in
terms of new crashes appearing with that version, so it should be good
to release.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic
** Tags added: verification-done verification-done-
So, unattended-upgrades refused to treat linux-image-generic as
autoremovable in xenial and trusty; so let's look at apt itself:
In both cases (1.2.31, and 1.0.1ubuntu2.22), linux-image-generic is not
autoremovable after removing linux-generic, whereas it was in released
updates - fix verified.
*
Please provide apt-cache policy output, and there are probably other
pinnings in your preferences files.
** 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 Ubun
apt-cache policy burp, that is
--
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/1821308
Title:
apt-get upgrade ignores pinning preferences since 1.0.1ubuntu2.22
Status in apt p
ged in: apt (Ubuntu Trusty)
Importance: Undecided => Critical
** Changed in: apt (Ubuntu Trusty)
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 Ub
** Description changed:
+ [Impact]
+ Pinning on local-only package versions is ignored, causing them to be
upgraded.
+
+ [Test case]
+ The integration tests include an automated test case that contains a package
called coolstuff in three versions. We are specifying a Pin for the installed
one,
Well, the version of apt is irrelevant. The version of libapt-pkg4.12 is
what matters - is that one upgraded 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/1821308
Title:
The test case also passed successfully on the autopkgtest for
1.0.1ubuntu2.23
Check that local-only versions can be pinned correctly (LP: #1821308)
Test for successful execution of apt-cache policy coolstuff … PASS
Test for correctness of file /tmp/tmp.PtSrwfN8WU/rootdir/tmp/testsuccess.output
…
Hmm, but linux-image-unsigned-$foo should not be installed in the first
place.
** Changed in: apt (Ubuntu)
Status: New => Triaged
** Changed in: apt (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, wh
I mean, usually people should have linux-image- installed, not
linux-image-unsigned - they are basically only artifacts used for
building the signed kernel images that are installed by the
metapackages.
Since there is no metapackage that pulls in unsigned kernels, there is
no reason to add unsigne
** Changed in: apt (Ubuntu)
Status: New => Triaged
** Changed in: apt (Ubuntu)
Assignee: (unassigned) => Julian Andres Klode (juliank)
** Changed in: apt (Ubuntu)
Importance: Undecided => High
** Changed in: apt (Ubuntu)
Importance: High => Medium
--
You recei
This has been on my agenda for quite some time. It means apt will need
to talk dbus, and it might need to be able to react to a shutdown
notification from dbus, which might get pretty complex, but I have not
checked in detail.
It's not clear yet which dbus library to use. Starting with systemd's
l
@Mathew Hodson please stop messing with tasks. It's important we have
those invalid tasks to say that it does not apply to that branch vs. we
just forgot about it.
** Also affects: apt (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: apt (Ubuntu Trusty)
Status: Ne
@mathew-hodson It's in git, and will make it's way in in a future
release
--
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/1821308
Title:
apt-get upgrade ignores pinning prefere
It actually did not fix the issue.
** Changed in: apt (Ubuntu)
Status: Fix Released => Triaged
--
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/1801338
Title:
apt fails
Yes, exactly, that's why it was removed from disco-proposed and I
quickly reverted it in the followup upload. Though, the problem only
seems to happen with apache based servers, if you put a squid in front
of them, you're fine.
--
You received this bug notification because you are a member of Ubu
This is caused by unattended-upgrades having an ActionGroup during the
clear. So, UnattendedUpgrades cache should likely overwrite clear() and
make it reset the action group, for example (after making actiongroup
global):
def clear(self):
global actiongroup
actiongroup.release() # pyflake
I think the key is:
W: Sources disagree on hashes for supposely identical version '2.1.0-1'
of 'python-swagger-spec-validator:amd64'.
That is, you have two sources for that version and they disagree.
** Changed in: apt (Ubuntu)
Status: New => Incomplete
--
You received this bug notifica
** 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/1804908
Title:
Fails to load 'gmpy'
Status in apt package in Ubuntu:
Public bug reported:
When resuming a machine that should have run unattended-upgrades in the
time it was down, and it has containers for which the same applies, the
host and all containers run their upgrades in parallel, creating a lot
of load.
** Affects: apt (Ubuntu)
Importance: Medium
** Description changed:
[Impact]
Add support to python-apt for frontend locking. This is a bit more
complicated, and also requires some other restructuring:
(1) The archives lock was only taken for a short time, when it should
have been kept for the duration of an installation, as othe
The fix is to put .asc or .gpg files in trusted.gpg.d and not use apt-
key.
--
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/1433761
Title:
apt-key and add-apt-repository don't
The variables are usually http_proxy and https_proxy, not uppercase
versions. That said, gpg does not seem to honor either. It does,
however, honor an option --keyserver-options http-proxy=, although it is
deprecated.
--
You received this bug notification because you are a member of Ubuntu
Touch
@Elzix: You might want to talk to your ISP, or check your hardware, as
something is broken.
jak@jak-t480s:~:master$ curl -s
http://gb.archive.ubuntu.com/ubuntu/dists/bionic-updates/main/binary-i386/by-hash/SHA256/54181e4ce10a58ed362cac0b1a98f48989710d6697291b81e0ad7a2c9320a462
| sha256sum
54181e
First of all, dhclient remaining in place is not a bug. Systems are not
switching to netplan and networkd on upgrade.
The restart caused by /etc/dhcp/dhclient-enter-hooks.d/resolved to tell
systemd-resolved about new servers and search domains, and hence
expected to happen (resolved does not suppo
Ah no, 229, not 239 it seems.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1805183
Title:
systemd-resolved constantly restarts on Bionic upgraded from Xenial
Status in
The dbus API is only available in 239, which means we can't use it in
bionic.
We could maybe make the hook just restart resolved if the new files it
wrote are different from the old files.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is su
** No longer affects: ubuntu-release-upgrader (Ubuntu)
** Changed in: systemd (Ubuntu)
Status: New => Triaged
** Changed in: systemd (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribe
The posted output does not look like a correct Ubuntu system, hence this
is the wrong place for this.
** Changed in: python-apt (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt
Here's a patch while the git branch is pushing.
** Changed in: systemd (Ubuntu)
Status: Triaged => In Progress
** Patch added:
"0001-Only-restart-resolved-on-changes-in-dhclient-enter-h.patch"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1805183/+attachment/5222922/+files/00
If we want to backport this to stable releases, we need a test case.
What I came up with, as I was not able to simulate dhcp lease refreshes,
is:
(1) Append make_resolv_conf to the end of the file, so it gets executed
(2) Execute the file with bash -x and different settings and ensure there are
** 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 unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1806076
Title:
unattended-upgrade --help raises
xenial:
- ubuntu-make not a regression, same bug as before
- apport retried
- snapcraft not a regression, same issues as before
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/b
xenial: None of the failures are regressions; the apport one we can also
see just with apport as trigger.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1826870
Title:
bionic: Only apt-clone and snapcraft left after retries. Retried them
both with themselves as triggers, and they're still failing, so no
regressions either.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
901 - 1000 of 2639 matches
Mail list logo
