[Touch-packages] [Bug 1801338] Re: apt fails to properly handle server-side connection closure

2020-08-04 Thread Julian Andres Klode
I can't reproduce this anymore, so closing it.

** Changed in: apt (Ubuntu)
   Status: Triaged => Invalid

** Changed in: apt (Ubuntu)
   Status: Invalid => Incomplete

** Changed in: apt (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: apt (Ubuntu Xenial)
   Status: Confirmed => Invalid

** Changed in: apt (Ubuntu Bionic)
   Status: Triaged => 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/1801338

Title:
  apt fails to properly handle server-side connection closure

Status in apt package in Ubuntu:
  Invalid
Status in apt source package in Xenial:
  Invalid
Status in apt source package in Bionic:
  Invalid

Bug description:
  [Impact]
  In some cases, apt does not correctly handle server-side connection closure 
after a pipeline, and aborts the file being downloaded with an "Undetermined 
Error" when the connection has been closed.

  [Test case]
  This could be seen by running apt build-dep evince on cosmic with a recent 
apt with the pipelining fix (such as 1.6.6) against a local mirror running 
apache from trusty. It remains to be seen whether this is easily reproducible 
for anyone.

  [Regression potential]
  N/A yet.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1801338/+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


[Touch-packages] [Bug 1890006] Re: Hash mismatch on "apt update"

2020-08-02 Thread Julian Andres Klode
Don't see any reason for any apport collecting here.

This needs a clean reproducer or someone with the issue to do the work
to analyse what's wrong.

Looking at the bug report, the output from the reproducer matches that
of the commandline tools?

-- 
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/1890006

Title:
  Hash mismatch on "apt update"

Status in apt package in Ubuntu:
  New

Bug description:
  This is a really weird bug that is happening on Ubuntu 20.04 LTS (Live
  ISO!!!) and Kali 2020.2, but not Debian 10 (so, it affects at least
  apt 2.0.2ubuntu0.1 and does not affect 1.8.2.1). It also only occurs
  on a single PC (as far as I know). All testing was done in Virtualbox
  and moving VM's to another PC fixed issue (without changing anything
  inside the VM).

  On running "apt update", there is an error "Hash Sum mismatch" which
  shows that SHA1 and SHA256 hashes differ from expected (while MD5 and
  file size is correct). E.g.:

Hash Sum mismatch
Hashes of expected file:
 - Filesize:314536 [weak]
 - SHA256:aa1c6c96b09a0c695dc475d99b407c675e564fbfe51b3e26230c6320b45666d0
 - SHA1:4f438d7e0c78dfb0486f86dc0a3dba30575eb617 [weak]
 - MD5Sum:5269212c54feb3dceabadb66583f6778 [weak]
Hashes of received file:
 - SHA256:f47a968e7a10aff91df8b1d3f682ce11d161ff1b17056268b9ae1c10447523b2
 - SHA1:2839e062232ed234d0c04e60fe6b2a687c950e5b [weak]
 - MD5Sum:5269212c54feb3dceabadb66583f6778 [weak]
 - Filesize:314536 [weak]

  I ran packet capture and extracted archives which are getting
  verified. All of their hashes are correct (exactly as expected).

  It seems that calculating SHA1 and SHA256 the way APT does it produces
  wrong result, while running command line tools sha1sum and sha256sum
  (on the same PC inside the same VM) produces correct result.

  I wrote the minimal reproducible example (hashtest.cc) that produces
  output such as this:

  Calculating hashes same way apt does.

   - MD5Sum:c89b13b76197d0d554400e00e46c0740
   - SHA1:f6901a4486e69a1f503401daa02b520f1b0e22ba
   - SHA256:9075301b3961aca23b69bf2868a18dca184b383a0ec1de35516f0a8a182c2cb6
   - 
SHA512:7506f6f5c5d5e97f8c6ecac2489e7d6260002bd530370c6193a04620f94285dca0f5cf2bb9ead40afbd72fdf3a239349a57f81165b5b857af6ad7ddeab8da036
   - Checksum-FileSize:892549

  Calculating hashes through command line tools.

   - md5sum: c89b13b76197d0d554400e00e46c0740
   - sha1sum: f6901a4486e69a1f503401daa02b520f1b0e22ba
   - sha256sum: 9075301b3961aca23b69bf2868a18dca184b383a0ec1de35516f0a8a182c2cb6
   - sha512sum: 
7506f6f5c5d5e97f8c6ecac2489e7d6260002bd530370c6193a04620f94285dca0f5cf2bb9ead40afbd72fdf3a239349a57f81165b5b857af6ad7ddeab8da036

  It's in the attachment alongside with an example file that causes this
  hash mismatch. There's also debug.log which contains various versions,
  etc (although as I said, it has been verified on latest Ubuntu Live
  ISO).

  I have a suspicion that the bug is in the gcrypt library, not apt
  itself, but I haven't yet verified it. The libgcrypt20 version in
  Ubuntu is 1.8.5-5ubuntu1 (in Kali as well), while Debian 10 (which
  isn't affected) uses 1.8.4-5.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1890006/+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


[Touch-packages] [Bug 1802718] Re: Allow people to do sudo apt-get build-dep without any further configuration

2020-07-25 Thread Julian Andres Klode
Should probably be

  add-apt-repository deb-src

?

** Package changed: apt (Ubuntu) => software-properties (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1802718

Title:
  Allow people to do sudo apt-get build-dep without any further
  configuration

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Or provide a reliable CLI method, a direct sed on
  /etc/atp/sources.list does not feel clean.

  Motivation: https://askubuntu.com/questions/496549/error-you-must-put-
  some-source-uris-in-your-sources-list

  This is specially important for Docker, but also a big annoyance on
  desktop, as there is no clean CLI way of enabling it.

  Why not just enable by default and save people the trouble?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1802718/+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


[Touch-packages] [Bug 1802718] Re: Allow people to do sudo apt-get build-dep without any further configuration

2020-07-25 Thread Julian Andres Klode
Enabling by default does not make much sense and people usually use
pull-lp-source instead which does not need sources.list entries and
pulls directly from launchpad.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1802718

Title:
  Allow people to do sudo apt-get build-dep without any further
  configuration

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Or provide a reliable CLI method, a direct sed on
  /etc/atp/sources.list does not feel clean.

  Motivation: https://askubuntu.com/questions/496549/error-you-must-put-
  some-source-uris-in-your-sources-list

  This is specially important for Docker, but also a big annoyance on
  desktop, as there is no clean CLI way of enabling it.

  Why not just enable by default and save people the trouble?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1802718/+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


[Touch-packages] [Bug 1885730] Re: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor

2020-07-24 Thread Julian Andres Klode
@Colin: I agree with all of that.

Our kernel-side default is not powersave, but performance, across
generic and oem, at the very least:

$ grep CPU_FREQ_DEFAULT_GOV_.*=y /boot/config-5.*
/boot/config-5.4.0-26-generic:CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
/boot/config-5.4.0-42-generic:CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
/boot/config-5.6.0-1018-oem:CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
/boot/config-5.6.0-1020-oem:CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y

We used to set that to powersave (and ondemand on non-pstate) in
ondemand.service, but have since removed the service in groovy.

I believe the default governor kernel-side outside Ubuntu is usually
CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND, which translates to ondemand pre-
pstates, and powersave on pstates (compare Fedora), whereas Enterprise
systems usually pick PERFORMANCE too (compare RHEL)

- probably because most distributions focus on normal end users and
enterprise on server and workstation. We don't have that distinction of
course, so I'm not sure what the best way out is - default to
powersave/ondemand and make server installer write performance - or vice
versa default to performance and make ubiquity configure powersave for
desktop.

-- 
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/1885730

Title:
  Bring back ondemand.service or switch kernel default governor for
  pstate - pstate now defaults to performance governor

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Groovy:
  Confirmed
Status in systemd source package in Groovy:
  Invalid

Bug description:
  In a recent merge from Debian we lost ondemand.service, meaning all
  CPUs now run in Turbo all the time when idle, which is clearly
  suboptimal.

  The discussion in bug 1806012 seems misleading, focusing on p-state vs
  other drivers, when in fact, the script actually set the default
  governor for the pstate driver on platforms that use pstate.
  Everything below only looks at systems that use pstate.

  pstate has two governors: performance and powerstate. performance runs
  CPU at maximum frequency constantly, and powersave can be configured
  using various energy profiles energy profiles:

  - performance
  - balanced performance
  - balanced power
  - power

  It defaults to balanced performance, I think, but I'm not sure.

  Whether performance governor is faster than powersave governor is not
  even clear.
  https://www.phoronix.com/scan.php?page=article=linux50-pstate-
  cpufreq=5 benchmarked them, but did not benchmark the individual
  energy profiles.

  For a desktop/laptop, the expected behavior is the powersave governor
  with balanced_performance on AC and balanced_power on battery.

  I don't know about servers or VMs, but the benchmark series seems to
  indicate it does not really matter much performance wise.

  I think most other distributions configure their kernels to use the
  powersave governor by default, whereas we configure it to use the
  performance governor and then switch it later in the boot to get the
  maximum performance during bootup. It's not clear to me that's
  actually useful.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885730/+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


[Touch-packages] [Bug 1886161] Re: UU should work on roaming laptops

2020-07-23 Thread Julian Andres Klode
We'll eventually get a retry support in apt, if updating failed, but
there are no plans to react to connection state changes.

The retry will be linear every 10 minutes or so I suppose, but can't be
sure, we'll have to see - I'd do exponential, but systemd does not give
us an option for that.

Any change is not suitable for backporting to old releases.

Tthis is a tough topic, but our behavior wrt to updating is not
different from other major platforms - e.g. Android only installs
updates in the same conditions. It just gets the service triggered
automatically if it missed it due to conditions, but systemd does not
retrigger nor does it know about network state.

FWIW, I believe that all desktops do have their own integration, because
they need to for every other distribution, because that's how PackageKit
works.

-- 
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/1886161

Title:
  UU should work on roaming laptops

Status in apt package in Ubuntu:
  New
Status in gnome-settings-daemon package in Ubuntu:
  Invalid

Bug description:
  For many if not most laptop computers, Unattended Upgrades seems all
  but useless by design.

  For upgrades to happen, with default config, 3 conditions must be met:

  - an internet connection must be up and running when the timer or cron or 
anacron tries the unattended upgrade
  - the connection must not be metered, whatever that means 
(Skip-Updates-On-Metered-Connections "true")
  - the computer must be plugged in (OnlyOnACPower "true")

  These are insurmountable problems for many laptops on the go.
  Inevitably, security upgrades will almost never run unattended on such
  computers. I discovered with shock that Unattended Upgrades had almost
  never run on my laptop. I tried all possible config tweaks. Nothing
  worked reliably and in the end I gave up and wrote a upgrade script
  which uses Network Manager's connection-up hook. Unattended Upgrades
  needs to do something like this out of the box. Users should not need
  to write scripts to ensure security upgrades.

  Unattended upgrades is an excellent project for servers. But it really
  needs to work, out of the box, on laptops too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1886161/+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


[Touch-packages] [Bug 1886161] Re: UU should work on roaming laptops

2020-07-22 Thread Julian Andres Klode
This is not going to happen in apt. It's a question for desktop how to
do that, probably disabling the downloading in apt, and using gnome's
package kit refresh stuff instead.

** Also affects: gnome-settings-daemon (Ubuntu)
   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/1886161

Title:
  UU should work on roaming laptops

Status in apt package in Ubuntu:
  New
Status in gnome-settings-daemon package in Ubuntu:
  New

Bug description:
  For many if not most laptop computers, Unattended Upgrades seems all
  but useless by design.

  For upgrades to happen, with default config, 3 conditions must be met:

  - an internet connection must be up and running when the timer or cron or 
anacron tries the unattended upgrade
  - the connection must not be metered, whatever that means 
(Skip-Updates-On-Metered-Connections "true")
  - the computer must be plugged in (OnlyOnACPower "true")

  These are insurmountable problems for many laptops on the go.
  Inevitably, security upgrades will almost never run unattended on such
  computers. I discovered with shock that Unattended Upgrades had almost
  never run on my laptop. I tried all possible config tweaks. Nothing
  worked reliably and in the end I gave up and wrote a upgrade script
  which uses Network Manager's connection-up hook. Unattended Upgrades
  needs to do something like this out of the box. Users should not need
  to write scripts to ensure security upgrades.

  Unattended upgrades is an excellent project for servers. But it really
  needs to work, out of the box, on laptops too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1886161/+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


[Touch-packages] [Bug 1885730] Re: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor

2020-07-22 Thread Julian Andres Klode
passing intel_pstate=disable_hwp on the kernel commandline causes the
kernel to scale the Core i5-8250U down to 1.6 GHz in performance mode,
but that's still a bit off from the 900 MHz it scales down to in
powersave mode.

I believe Windows also does not run the CPUs in performance mode by
default on mobile devices (but in balanced or balanced performance), I
don't know about stationary ones.

Performance governor on laptops should be restricted to gamemode.

-- 
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/1885730

Title:
  Bring back ondemand.service or switch kernel default governor for
  pstate - pstate now defaults to performance governor

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Groovy:
  Confirmed
Status in systemd source package in Groovy:
  Invalid

Bug description:
  In a recent merge from Debian we lost ondemand.service, meaning all
  CPUs now run in Turbo all the time when idle, which is clearly
  suboptimal.

  The discussion in bug 1806012 seems misleading, focusing on p-state vs
  other drivers, when in fact, the script actually set the default
  governor for the pstate driver on platforms that use pstate.
  Everything below only looks at systems that use pstate.

  pstate has two governors: performance and powerstate. performance runs
  CPU at maximum frequency constantly, and powersave can be configured
  using various energy profiles energy profiles:

  - performance
  - balanced performance
  - balanced power
  - power

  It defaults to balanced performance, I think, but I'm not sure.

  Whether performance governor is faster than powersave governor is not
  even clear.
  https://www.phoronix.com/scan.php?page=article=linux50-pstate-
  cpufreq=5 benchmarked them, but did not benchmark the individual
  energy profiles.

  For a desktop/laptop, the expected behavior is the powersave governor
  with balanced_performance on AC and balanced_power on battery.

  I don't know about servers or VMs, but the benchmark series seems to
  indicate it does not really matter much performance wise.

  I think most other distributions configure their kernels to use the
  powersave governor by default, whereas we configure it to use the
  performance governor and then switch it later in the boot to get the
  maximum performance during bootup. It's not clear to me that's
  actually useful.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885730/+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


[Touch-packages] [Bug 1885730] Re: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor

2020-07-22 Thread Julian Andres Klode
The performance governor is the right choice for servers, but it's not
the right choice on non-server platforms, it's also not the default
kernel setting, it was set because we have the ondemand.service in
userspace that can change it back to ondemand (or well we have the
service because of that change in the kernel :D).

Fans do not necessarily spin, and you might not actually notice any
significant changes in power usage, but the expectation of a desktop
user is that the CPU scales its frequencies down, which recent-ish Intel
CPUs (Skylake+) on like a ThinkPad T480s - which manage the pstates in
hardware instead of software like the old MacBook does - don't do.

If we compare this to Red Hat, what they do is
CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y in RHEL and
CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y in fedora.

Power usage, at 3-6% CPU usage:

Powersave: I see 0.9-1.4W power usage on the cores
Performance, I see 1.6-2.5W

-- 
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/1885730

Title:
  Bring back ondemand.service or switch kernel default governor for
  pstate - pstate now defaults to performance governor

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Groovy:
  Confirmed
Status in systemd source package in Groovy:
  Invalid

Bug description:
  In a recent merge from Debian we lost ondemand.service, meaning all
  CPUs now run in Turbo all the time when idle, which is clearly
  suboptimal.

  The discussion in bug 1806012 seems misleading, focusing on p-state vs
  other drivers, when in fact, the script actually set the default
  governor for the pstate driver on platforms that use pstate.
  Everything below only looks at systems that use pstate.

  pstate has two governors: performance and powerstate. performance runs
  CPU at maximum frequency constantly, and powersave can be configured
  using various energy profiles energy profiles:

  - performance
  - balanced performance
  - balanced power
  - power

  It defaults to balanced performance, I think, but I'm not sure.

  Whether performance governor is faster than powersave governor is not
  even clear.
  https://www.phoronix.com/scan.php?page=article=linux50-pstate-
  cpufreq=5 benchmarked them, but did not benchmark the individual
  energy profiles.

  For a desktop/laptop, the expected behavior is the powersave governor
  with balanced_performance on AC and balanced_power on battery.

  I don't know about servers or VMs, but the benchmark series seems to
  indicate it does not really matter much performance wise.

  I think most other distributions configure their kernels to use the
  powersave governor by default, whereas we configure it to use the
  performance governor and then switch it later in the boot to get the
  maximum performance during bootup. It's not clear to me that's
  actually useful.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885730/+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


[Touch-packages] [Bug 1886814] Re: posix_spawn usage in gnu make causes failures on s390x

2020-07-21 Thread Julian Andres Klode
Andreas, I've not gotten it more isolated, the minimum I had was running
debian/tests/gnome-desktop-testing in a flatpak-builder source tree (apt
source/pull-lp-source flatpak-builder).

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to make-dfsg in Ubuntu.
https://bugs.launchpad.net/bugs/1886814

Title:
  posix_spawn usage in gnu make causes failures on s390x

Status in Ubuntu on IBM z Systems:
  New
Status in glibc package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in make-dfsg package in Ubuntu:
  New

Bug description:
  posix_spawn usage in gnu make causes failures on s390x

  Recently in gnu-make v4.3 https://paste.ubuntu.com/p/tYhbJFKN76/ it
  started to use posix_spawn, instead of fork()/exec().

  This has caused failure of an unrelated package flatpak-builder
  autopkgtests on s390x only, like so

echo Building
make: echo: Operation not permitted
make: *** [Makefile:2: all] Error 127

  Julian Klaude investigated this in-depth. His earlier research also
  indicated that this is a heisenbug, if one tries to print to stderr
  before printing to stdout, no issue occurs.

  We are configuring GNU make to be build with --disable-posix-spawn on
  s390x only. We passed these details to Debian https://bugs.debian.org
  /cgi-bin/bugreport.cgi?bug=964541 too.

  But I do wonder, if there is something different or incorrect about
  posix_spawn() implementation in either glibc, or linux kernel, on
  s390x. Or gnu-make's usage of posix_spawn().

  As otherise, using posix_spawn() in gnu-make works on other
  architectures, and flatpak-builder autopkgtests pass too.

  It seems very weird that stdout does not appear to be functional,
  unless stderr was opened/written to, from gnu-make execution compiled
  with posix-spawn feature.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1886814/+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


[Touch-packages] [Bug 1876506] Re: eoan to focal upgrade hangs when lvm snapshot is present

2020-07-17 Thread Julian Andres Klode
The maintainer script becomes a zombie, because perl -w ...
debconf/frontend ... memtest86+.postinst is stuck in a read() from fd 9,
which is a pipe.

** Package changed: memtest86+ (Ubuntu) => ubuntu

** Package changed: ubuntu => debconf (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to debconf in Ubuntu.
https://bugs.launchpad.net/bugs/1876506

Title:
  eoan to focal upgrade hangs when lvm snapshot is present

Status in debconf package in Ubuntu:
  Confirmed
Status in debconf source package in Focal:
  Confirmed

Bug description:
  When upgrading from 19.10 (w/ LVM + encypted disks) to 20.04, the
  installer hangs when trying to probe an LVM snapshot volume created
  before the upgrade.

  Steps to reproduce:

  lvcreate -s -L 20G -n preupgrade /dev/vgubuntu/root 
  do-release-upgrade -d

  The installer will hang after the following message:

  /usr/sbin/grub-probe: error: unknown filesystem.
  Found Ubuntu 19.10 (19.10) on /dev/mapper/vgubuntu-preupgrade
  done

  Resolution:

  Killing the grub-mount process which is probing the LVM snapshot seems
  to unhang the installer and allow the upgrade to complete without
  issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1876506/+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


[Touch-packages] [Bug 1876035] Re: Automatically retry downloads on failures

2020-07-15 Thread Julian Andres Klode
** Changed in: apt (Ubuntu Groovy)
   Status: Confirmed => 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/1876035

Title:
  Automatically retry downloads on failures

Status in apt package in Ubuntu:
  Triaged
Status in apt source package in Groovy:
  Triaged

Bug description:
  Hi,

  We operate archive.ubuntu.com as well as mirrors of it in various
  places. We're getting reports of various CI/CD jobs failing. Sometimes
  due to routing issues, issues with overloaded servers/VMs hosting
  archive, etc.

  Any chance we can make '-o Acquire::Retries=3' the default for 'apt-
  get update/install/dist-upgrade'? Preferably with a randomised skew
  between retries.

  Also, any chance of having apt-get retry with different IPs/hosts
  returned from the DNS lookup? (e.g. for archive.ubuntu.com -
  91.189.88.142, 91.189.88.152, ...).

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1876035/+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


[Touch-packages] [Bug 1615381] Re: apt-get autoremove may remove current kernel

2020-07-14 Thread Julian Andres Klode
I have code to fix that just need to merge it and like update tests

** Changed in: apt (Ubuntu)
   Status: Confirmed => In Progress

-- 
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/1615381

Title:
  apt-get autoremove may remove current kernel

Status in apt package in Ubuntu:
  In Progress
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Trusty:
  Won't Fix
Status in unattended-upgrades source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Artful:
  Won't Fix

Bug description:
  This may happen, if you boot one of the older kernels, that is not
  protected by /etc/apt/apt.conf.d/01autoremove-kernels

  Workaround: run
  /etc/kernel/postinst.d/apt-auto-removal
  during each boot (e.g. by using cron).
  Note: The workaround breaks autoremoving feature of new unneeded kernels in  
unattended-upgrades i.e. the setting 
'Unattended-Upgrade::Remove-New-Unused-Dependencies "true"' (which is default 
in 16.04 unless 'Unattended-Upgrade::Remove-Unused-Dependencies "true"' is set 
in '/etc/apt/apt.conf.d/50unattended-upgrades'.

  
  In shell:

  $ uname -r
  4.4.0-22-generic
  $ apt-get -s autoremove
  NOTE: This is only a simulation!
    apt-get needs root privileges for real execution.
    Keep also in mind that locking is deactivated,
    so don't depend on the relevance to the real current situation!
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following packages will be REMOVED:
    linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-headers-4.4.0-22
    linux-headers-4.4.0-22-generic linux-headers-4.4.0-31-generic
    linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic
    linux-image-4.4.0-31-generic linux-image-extra-4.4.0-21-generic
    linux-image-extra-4.4.0-22-generic linux-image-extra-4.4.0-31-generic
  0 upgraded, 0 newly installed, 11 to remove and 13 not upgraded.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.12~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Aug 21 16:11:27 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-28 (114 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.kernel.postinst.d.apt-auto-removal: [modified]
  mtime.conffile..etc.kernel.postinst.d.apt-auto-removal: 
2016-07-30T12:15:32.706300

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1615381/+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


[Touch-packages] [Bug 1887277] Re: apt-get install REMOVES packages without replacing them and with barely any warning

2020-07-12 Thread Julian Andres Klode
You not liking apt's solution and only realizing that after you
confirmed and applied it is not a bug in apt.

-- 
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/1887277

Title:
  apt-get install REMOVES packages without replacing them and with
  barely any warning

Status in apt package in Ubuntu:
  Invalid

Bug description:
  I did:

    $ sudo apt-get install ettercap-common

  (by the way I don't even know what that is, but it is one of a few
  packages being "held back" by apt and that prevents me from upgrading
  from 18.04 to 20.04. Since apt itself doesn't give me a clue what to
  do and there doesn't seem to be a guide anywhere, I'm blindly trying
  stuff)

  and I got:

    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    The following packages were automatically installed and are no longer 
required:
  [...]
    Use 'sudo apt autoremove' to remove them.
    The following additional packages will be installed:
  ettercap-graphical libcurl4
    The following packages will be REMOVED:
  libcurl3 php7.2-curl virtualbox-6.0   < NOTE THIS !!
    The following NEW packages will be installed:
  libcurl4
    The following packages will be upgraded:
  ettercap-common ettercap-graphical
    2 upgraded, 1 newly installed, 3 to remove and 6 not upgraded.

  I didn't notice the part that said that some apparently unrelated
  packages, one of which I had installed manually (Virtual Box) would be
  removed.

  Technically it asked me for confirmation, but it was in the middle of
  a bunch of other much more trivial stuff, and you can't just put
  "REMOVE" in caps and expect me to notice it.

  If an INSTALL command is going to UNINSTALL something that huge (not
  just a library that had been installed automatically and is no longer
  required, but an entire application that I installed manually!), you
  must give a very specific and explicit prompt (defaulting to No rather
  than Yes) with a gigantic warning, something like:

   **
   *   A T T E N T I O N    *
   **
   *  The following packages will be REMOVED*
   **
   *  and NO SUITABLE REPLACEMENT will be installed *
   **
   **

   Are you REALLY sure you wish to continue? [y/N]

  (possibly red and blinking)

  NEVER before, in my entire life, have I ever seen an instance where
  "apt-get INSTALL" would REMOVE packages without at the same time
  replacing them with some more recent version or something, and even
  that is rare.

  I can't see a reason why the installation of a package would require
  the removal of another, unless it is to replace it with something that
  supersedes it.

  Usually the list of stuff, that you're asked confirmation for when
  running "apt-get install", only includes stuff to be installed,
  upgraded and left untouched, never removed, so I'm used to responding
  "Yes" almost automatically.

  Here's the rest of the output

  -

  $ sudo apt-get install ettercap-common
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
    gdal-data libaec0 libaio1 libarmadillo8 libarpack2 libcharls1 libdap25 
libdapclient6v5 libepsilon1 libfreexl1 libfyba0 libgeos-3.6.2 libgeos-c1v5
    libgeotiff2 libgsasl7 libhdf4-0-alt libhdf5-100 libieee1284-3:i386 
libkmlbase1 libkmldom1 libkmlengine1 libkyotocabinet16v5 libminizip1 libnetcdf13
    libntlm0 libogdi3.2 libopencv-core3.2 libopencv-imgproc3.2 libopencv-ml3.2 
libopencv-video3.2 libproj12 libqhull7 libsdl-ttf2.0-0 libsocket++1
    libspatialite7 libsuperlu5 libsz2 liburiparser1 
linux-image-4.4.0-142-generic mailutils-common odbcinst odbcinst1debian2 
proj-bin proj-data
  Use 'sudo apt autoremove' to remove them.
  The following additional packages will be installed:
    ettercap-graphical libcurl4
  The following packages will be REMOVED:
    libcurl3 php7.2-curl virtualbox-6.0
  The following NEW packages will be installed:
    libcurl4
  The following packages will be upgraded:
    ettercap-common ettercap-graphical
  2 upgraded, 1 newly installed, 3 to remove and 6 not upgraded.
  Need to get 1.178 kB of archives.
  After this operation, 248 MB disk space will be freed.
  Do you want to continue? [Y/n] y
  Get:1 http://es.archive.ubuntu.com/ubuntu bionic/universe amd64 
ettercap-graphical amd64 1:0.8.2-10build4 [193 kB]
  Get:2 http://es.archive.ubuntu.com/ubuntu bionic/universe amd64 
ettercap-common amd64 1:0.8.2-10build4 [771 kB]
  Get:3 http://es.archive.ubuntu.com/ubuntu 

[Touch-packages] [Bug 1887277] Re: apt-get install REMOVES packages without replacing them and with barely any warning

2020-07-12 Thread Julian Andres Klode
** 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/1887277

Title:
  apt-get install REMOVES packages without replacing them and with
  barely any warning

Status in apt package in Ubuntu:
  Invalid

Bug description:
  I did:

$ sudo apt-get install ettercap-common

  (by the way I don't even know what that is, but it is one of a few
  packages being "held back" by apt and that prevents me from upgrading
  from 18.04 to 20.04. Since apt itself doesn't give me a clue what to
  do and there doesn't seem to be a guide anywhere, I'm blindly trying
  stuff)

  
  and I got:

Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages were automatically installed and are no longer 
required:
  [...]
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  ettercap-graphical libcurl4
The following packages will be REMOVED:
  libcurl3 php7.2-curl virtualbox-6.0   < NOTE THIS !!
The following NEW packages will be installed:
  libcurl4
The following packages will be upgraded:
  ettercap-common ettercap-graphical
2 upgraded, 1 newly installed, 3 to remove and 6 not upgraded.

  
  I didn't notice the part that said that some apparently unrelated packages, 
one of which I had installed manually (Virtual Box) would be removed.

  Technically it asked me for confirmation, but it was in the middle of
  a bunch of other much more trivial stuff, and you can't just put
  "REMOVE" in caps and expect me to notice it.

  If an INSTALL command is going to UNINSTALL something that huge (not
  just a library that had been installed automatically and is no longer
  required, but an entire application that I installed manually!), you
  must give a very specific and explicit prompt (defaulting to No rather
  than Yes) with a gigantic warning, something like:

   ***
   *     A T T E N T I O N   *
   * *
   *  If you proceed, the following packages will be REMOVED *
   * *
   *  and NO SUITABLE REPLACEMENT will be installed  *
   * *
   ***

   Are you REALLY sure you wish to continue? [y/N]

  (possibly red and blinking)

  
  NEVER before, in my entire life, have I ever seen an instance where "apt-get 
INSTALL" would REMOVE packages without at the same time replacing them with 
some more recent version or something, and even that is rare.

  I can't see a reason why the installation of a package would require
  the removal of another, unless it is to replace it with something that
  superseeds it.

  Usually the list of stuff, that you're asked confirmation for when running 
"apt-get install", only includes stuff to be installed, upgraded and left 
untouched, never removed, so I'm used to responding "Yes" almost automatically.
   

  
  Here's the rest of the output

  
  -

  
  $ sudo apt-get install ettercap-common 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
gdal-data libaec0 libaio1 libarmadillo8 libarpack2 libcharls1 libdap25 
libdapclient6v5 libepsilon1 libfreexl1 libfyba0 libgeos-3.6.2 libgeos-c1v5
libgeotiff2 libgsasl7 libhdf4-0-alt libhdf5-100 libieee1284-3:i386 
libkmlbase1 libkmldom1 libkmlengine1 libkyotocabinet16v5 libminizip1 libnetcdf13
libntlm0 libogdi3.2 libopencv-core3.2 libopencv-imgproc3.2 libopencv-ml3.2 
libopencv-video3.2 libproj12 libqhull7 libsdl-ttf2.0-0 libsocket++1
libspatialite7 libsuperlu5 libsz2 liburiparser1 
linux-image-4.4.0-142-generic mailutils-common odbcinst odbcinst1debian2 
proj-bin proj-data
  Use 'sudo apt autoremove' to remove them.
  The following additional packages will be installed:
ettercap-graphical libcurl4
  The following packages will be REMOVED:
libcurl3 php7.2-curl virtualbox-6.0
  The following NEW packages will be installed:
libcurl4
  The following packages will be upgraded:
ettercap-common ettercap-graphical
  2 upgraded, 1 newly installed, 3 to remove and 6 not upgraded.
  Need to get 1.178 kB of archives.
  After this operation, 248 MB disk space will be freed.
  Do you want to continue? [Y/n] y
  Get:1 http://es.archive.ubuntu.com/ubuntu bionic/universe amd64 
ettercap-graphical amd64 1:0.8.2-10build4 [193 kB]
  Get:2 http://es.archive.ubuntu.com/ubuntu bionic/universe amd64 
ettercap-common amd64 1:0.8.2-10build4 [771 kB]
 

[Touch-packages] [Bug 1886618] Re: command-not-found gets stuck on locales with non-English-like collation rules

2020-07-07 Thread Julian Andres Klode
** Package changed: apt (Ubuntu) => command-not-found (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/1886618

Title:
  command-not-found gets stuck on locales with non-English-like
  collation rules

Status in command-not-found package in Ubuntu:
  Confirmed

Bug description:
  The bug in question: https://askubuntu.com/q/1142923/162831
  Namely, cnf-update-db takes forever and eats almost all your disk time if 
your locale has different collation rules from English such as different 
sorting and/or case conversion.
  A workaround by supplying a C locale: https://askubuntu.com/a/1147303/162831

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1886618/+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


[Touch-packages] [Bug 1885730] Re: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor

2020-07-02 Thread Julian Andres Klode
** Changed in: linux (Ubuntu)
   Status: Incomplete => New

** Changed in: linux (Ubuntu)
   Status: New => Confirmed

-- 
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/1885730

Title:
  Bring back ondemand.service or switch kernel default governor for
  pstate - pstate now defaults to performance governor

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  In a recent merge from Debian we lost ondemand.service, meaning all
  CPUs now run in Turbo all the time when idle, which is clearly
  suboptimal.

  The discussion in bug 1806012 seems misleading, focusing on p-state vs
  other drivers, when in fact, the script actually set the default
  governor for the pstate driver on platforms that use pstate.
  Everything below only looks at systems that use pstate.

  pstate has two governors: performance and powerstate. performance runs
  CPU at maximum frequency constantly, and powersave can be configured
  using various energy profiles energy profiles:

  - performance
  - balanced performance
  - balanced power
  - power

  It defaults to balanced performance, I think, but I'm not sure.

  Whether performance governor is faster than powersave governor is not
  even clear.
  https://www.phoronix.com/scan.php?page=article=linux50-pstate-
  cpufreq=5 benchmarked them, but did not benchmark the individual
  energy profiles.

  For a desktop/laptop, the expected behavior is the powersave governor
  with balanced_performance on AC and balanced_power on battery.

  I don't know about servers or VMs, but the benchmark series seems to
  indicate it does not really matter much performance wise.

  I think most other distributions configure their kernels to use the
  powersave governor by default, whereas we configure it to use the
  performance governor and then switch it later in the boot to get the
  maximum performance during bootup. It's not clear to me that's
  actually useful.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885730/+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


[Touch-packages] [Bug 1885730] Re: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor

2020-06-30 Thread Julian Andres Klode
@rbalint As said before the kernel messages and bugs are irrelevant and
wrong. They pretend like intel_pstate is different, when in fact it's
this script that is configuring it here. And yes, it needs OS config.

Nor do other distros not do this, but we do it differently. We set the
CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y option, and then transition to
that at the end of the boot. Other distributions do not set
CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE and hence the kernel has
powersave as the default.

By removing this script, we are diverging from other distros, not
becoming closer to them - for pstates, anyway.

-- 
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/1885730

Title:
  Bring back ondemand.service or switch kernel default governor for
  pstate - pstate now defaults to performance governor

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  In a recent merge from Debian we lost ondemand.service, meaning all
  CPUs now run in Turbo all the time when idle, which is clearly
  suboptimal.

  The discussion in bug 1806012 seems misleading, focusing on p-state vs
  other drivers, when in fact, the script actually set the default
  governor for the pstate driver on platforms that use pstate.
  Everything below only looks at systems that use pstate.

  pstate has two governors: performance and powerstate. performance runs
  CPU at maximum frequency constantly, and powersave can be configured
  using various energy profiles energy profiles:

  - performance
  - balanced performance
  - balanced power
  - power

  It defaults to balanced performance, I think, but I'm not sure.

  Whether performance governor is faster than powersave governor is not
  even clear.
  https://www.phoronix.com/scan.php?page=article=linux50-pstate-
  cpufreq=5 benchmarked them, but did not benchmark the individual
  energy profiles.

  For a desktop/laptop, the expected behavior is the powersave governor
  with balanced_performance on AC and balanced_power on battery.

  I don't know about servers or VMs, but the benchmark series seems to
  indicate it does not really matter much performance wise.

  I think most other distributions configure their kernels to use the
  powersave governor by default, whereas we configure it to use the
  performance governor and then switch it later in the boot to get the
  maximum performance during bootup. It's not clear to me that's
  actually useful.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885730/+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


[Touch-packages] [Bug 1885730] Re: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor

2020-06-30 Thread Julian Andres Klode
Someone probably needs to look at non-pstate systems as I have no idea
about them.

-- 
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/1885730

Title:
  Bring back ondemand.service or switch kernel default governor for
  pstate - pstate now defaults to performance governor

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  In a recent merge from Debian we lost ondemand.service, meaning all
  CPUs now run in Turbo all the time when idle, which is clearly
  suboptimal.

  The discussion in bug 1806012 seems misleading, focusing on p-state vs
  other drivers, when in fact, the script actually set the default
  governor for the pstate driver on platforms that use pstate.
  Everything below only looks at systems that use pstate.

  pstate has two governors: performance and powerstate. performance runs
  CPU at maximum frequency constantly, and powersave can be configured
  using various energy profiles energy profiles:

  - performance
  - balanced performance
  - balanced power
  - power

  It defaults to balanced performance, I think, but I'm not sure.

  Whether performance governor is faster than powersave governor is not
  even clear.
  https://www.phoronix.com/scan.php?page=article=linux50-pstate-
  cpufreq=5 benchmarked them, but did not benchmark the individual
  energy profiles.

  For a desktop/laptop, the expected behavior is the powersave governor
  with balanced_performance on AC and balanced_power on battery.

  I don't know about servers or VMs, but the benchmark series seems to
  indicate it does not really matter much performance wise.

  I think most other distributions configure their kernels to use the
  powersave governor by default, whereas we configure it to use the
  performance governor and then switch it later in the boot to get the
  maximum performance during bootup. It's not clear to me that's
  actually useful.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885730/+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


[Touch-packages] [Bug 1885730] [NEW] Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor

2020-06-30 Thread Julian Andres Klode
Public bug reported:

In a recent merge from Debian we lost ondemand.service, meaning all CPUs
now run in Turbo all the time when idle, which is clearly suboptimal.

The discussion in bug 1806012 seems misleading, focusing on p-state vs
other drivers, when in fact, the script actually set the default
governor for the pstate driver on platforms that use pstate. Everything
below only looks at systems that use pstate.

pstate has two governors: performance and powerstate. performance runs
CPU at maximum frequency constantly, and powersave can be configured
using various energy profiles energy profiles:

- performance
- balanced performance
- balanced power
- power

It defaults to balanced performance, I think, but I'm not sure.

Whether performance governor is faster than powersave governor is not
even clear. https://www.phoronix.com/scan.php?page=article=linux50
-pstate-cpufreq=5 benchmarked them, but did not benchmark the
individual energy profiles.

For a desktop/laptop, the expected behavior is the powersave governor
with balanced_performance on AC and balanced_power on battery.

I don't know about servers or VMs, but the benchmark series seems to
indicate it does not really matter much performance wise.

I think most other distributions configure their kernels to use the
powersave governor by default, whereas we configure it to use the
performance governor and then switch it later in the boot to get the
maximum performance during bootup. It's not clear to me that's actually
useful.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: rls-gg-incoming

** Summary changed:

- Bring back ondemand.service - pstate now defaults to performance governor
+ Bring back ondemand.service or switch kernel default governor for pstate - 
pstate now defaults to performance governor

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

-- 
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/1885730

Title:
  Bring back ondemand.service or switch kernel default governor for
  pstate - pstate now defaults to performance governor

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  In a recent merge from Debian we lost ondemand.service, meaning all
  CPUs now run in Turbo all the time when idle, which is clearly
  suboptimal.

  The discussion in bug 1806012 seems misleading, focusing on p-state vs
  other drivers, when in fact, the script actually set the default
  governor for the pstate driver on platforms that use pstate.
  Everything below only looks at systems that use pstate.

  pstate has two governors: performance and powerstate. performance runs
  CPU at maximum frequency constantly, and powersave can be configured
  using various energy profiles energy profiles:

  - performance
  - balanced performance
  - balanced power
  - power

  It defaults to balanced performance, I think, but I'm not sure.

  Whether performance governor is faster than powersave governor is not
  even clear.
  https://www.phoronix.com/scan.php?page=article=linux50-pstate-
  cpufreq=5 benchmarked them, but did not benchmark the individual
  energy profiles.

  For a desktop/laptop, the expected behavior is the powersave governor
  with balanced_performance on AC and balanced_power on battery.

  I don't know about servers or VMs, but the benchmark series seems to
  indicate it does not really matter much performance wise.

  I think most other distributions configure their kernels to use the
  powersave governor by default, whereas we configure it to use the
  performance governor and then switch it later in the boot to get the
  maximum performance during bootup. It's not clear to me that's
  actually useful.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885730/+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


[Touch-packages] [Bug 1885410] Re: apt 2.0.2 lacks * wildcard support

2020-06-29 Thread Julian Andres Klode
*** This bug is a duplicate of bug 1872200 ***
https://bugs.launchpad.net/bugs/1872200

** This bug has been marked a duplicate of bug 1872200
   apt does not accept globs and regexes in some cases

-- 
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/1885410

Title:
  apt 2.0.2 lacks * wildcard support

Status in apt package in Ubuntu:
  Invalid

Bug description:
  Upstream removed support for * as a wildcard in apt 2.0.0

  They subsequently reinstated it in apt 2.1.0

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953531
  https://lists.debian.org/deity/2020/03/msg00055.html
  
https://metadata.ftp-master.debian.org/changelogs//main/a/apt/apt_2.1.6_changelog

  Will focal look to update apt to 2.1.x or backport this fix?

  The lack of this simple syntax for using apt with wildcards really
  destroys the utility of apt on the command line.

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1885410/+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


[Touch-packages] [Bug 1669517] Re: apt-key del must absolutely detect all errors, and then provide NON-zero return code and error message

2020-06-25 Thread Julian Andres Klode
We will not be changing the behavior here. apt-key del working if they
key was not present in the keyring is important to maintain, so that we
do not break the maintainer scripts using it (which should be tested,
and should be the only users of this).

** Changed in: apt (Ubuntu)
   Status: Triaged => Won't Fix

-- 
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/1669517

Title:
  apt-key del must absolutely detect all errors, and then provide NON-
  zero return code and error message

Status in apt package in Ubuntu:
  Won't Fix

Bug description:
  Currently, 'apt-key del' does NOT detect that the keyid given in parameter is 
invalid :
  It displays 'OK' and provides a return code equal to zero (see log below).

  I consider that letting erroneously believe that a GPG key has been
  successfully removed is a security issue.

  In fact 'apt-key del' must absolutely detect all errors, and then
  provide NON-zero return code and error message.

  
  # wget  -q  -O -  https://oss.oracle.com/el4/RPM-GPG-KEY-oracle  |  apt-key  
--keyring /etc/apt/trusted.gpg.d/oracle.gpg  add  -
  OK

  # apt-key  --keyring /etc/apt/trusted.gpg.d/oracle.gpg  list
  /etc/apt/trusted.gpg.d/oracle.gpg
  -
  pub   1024D/B38A8516 2006-09-05 [expired: 2013-09-06]
  uid  Oracle OSS group (Open Source Software group) 


  
  # apt-key  --keyring /etc/apt/trusted.gpg.d/oracle.gpg  del 1024D/B38A8516
  OK

  # echo $?
  0

  # apt-key  --keyring /etc/apt/trusted.gpg.d/oracle.gpg  list
  /etc/apt/trusted.gpg.d/oracle.gpg
  -
  pub   1024D/B38A8516 2006-09-05 [expired: 2013-09-06]
  uid  Oracle OSS group (Open Source Software group) 


  
  # apt-key  --keyring /etc/apt/trusted.gpg.d/oracle.gpg  del B38A8516
  OK

  # apt-key  --keyring /etc/apt/trusted.gpg.d/oracle.gpg  list

  #

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.19
  ProcVersionSignature: Ubuntu 4.4.0-65.86-generic 4.4.49
  Uname: Linux 4.4.0-65-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Thu Mar  2 17:34:07 2017
  InstallationDate: Installed on 2014-11-03 (849 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  SourcePackage: apt
  UpgradeStatus: Upgraded to xenial on 2016-05-09 (297 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1669517/+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


[Touch-packages] [Bug 1883723] Re: Some official repositories changed compression method from gzip to lz4 leading to checksum errors during apt-get update

2020-06-16 Thread Julian Andres Klode
You have enabled storing indexes in compressed form, which is a non-
default setting that does not work very well. In early days, this used
to store files in the form the server offered them, but this was changed
to recompress to lz4 in order to improve the run time performance of
apt.

Unfortunately, we are going to need a way to reproduce the issue,
otherwise we can't do much about it. There are likely various bugs in
various places of the downloading process that lead to it using files in
the wrong states.

** 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/1883723

Title:
  Some official repositories changed compression method from gzip to lz4
  leading to checksum errors during apt-get update

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  This includes bionic-security repositories:

  Reading package lists... Done
  E: Failed to fetch 
store:/var/lib/apt/lists/partial/pl.archive.ubuntu.com_ubuntu_dists_bionic-security_Contents-i386.gz
  Hash Sum mismatch
     Hashes of expected file:
  - Filesize:821731759 [weak]
  - SHA256:03b7fe601ba17908a5bfc628c8eb8309cd682f88ea5c2ed8139a4d46bb02df09
  - SHA1:5b0ca78303b67f3e1e78c828ac10474f4acf8c10 [weak]
  - MD5Sum:fa890ae0f75a803fa744ce126739bfa6 [weak]
     Hashes of received file:
  - SHA256:9cd965c8d4f68b92cfc20484aabf19899b53718f810dc316f7983c4b194108dd
  - SHA1:7c27b4efd7c3ca176b3e7ed85dec5d865a8928b8 [weak]
  - MD5Sum:c1a1a8baef4d45ce444962b981a

  Failed files:
  nusch@xps13:/etc/apt$ sudo ls -l /var/lib/apt/lists/partial/ | grep FAILED
  lrwxrwxrwx 1 root root   87 cze 16 16:52 
pl.archive.ubuntu.com_ubuntu_dists_bionic-proposed_Contents-i386.gz.FAILED -> 
/var/lib/apt/lists/pl.archive.ubuntu.com_ubuntu_dists_bionic-proposed_Contents-i386.lz4
  lrwxrwxrwx 1 root root   87 cze 16 16:52 
pl.archive.ubuntu.com_ubuntu_dists_bionic-security_Contents-i386.gz.FAILED -> 
/var/lib/apt/lists/pl.archive.ubuntu.com_ubuntu_dists_bionic-security_Contents-i386.lz4

  Not sure from where this issue comes - manual browsing of repository
  discovers only .gz file while downloaded copy have lz4 extension.
  After manual downloading .gz one and uncompromising diff command
  confirms both produce the same file.  Apt-get clean and deleting cache
  doesn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6.12ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-107.108-generic 4.15.18
  Uname: Linux 4.15.0-107-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 16 16:49:31 2020
  InstallationDate: Installed on 2015-05-08 (1866 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: apt
  UpgradeStatus: Upgraded to bionic on 2018-08-26 (659 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1883723/+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


[Touch-packages] [Bug 1883451] Re: can't pip isntall python-apt==1.6.5+ubuntu0.2

2020-06-14 Thread Julian Andres Klode
You can install python-apt from apt, we do not provide python-apt on
pip. I recently got control over the pypi entry and need to do something
with it. I'm not keen on providing python-apt outside of the distro,
though (python-apt and apt versions x.y need to match), so I'd rather
just get rid of it, so people stop with questions about outdated
versions.

** 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1883451

Title:
  can't pip isntall python-apt==1.6.5+ubuntu0.2

Status in python-apt package in Ubuntu:
  Invalid

Bug description:
  was recently able to install this version, but I think it stopped
  working:

  ```
  (scratch) [14/06/20 2:26:46] ➜  temp pip install python-apt==1.6.5+ubuntu0.2
  Collecting python-apt==1.6.5+ubuntu0.2
Could not find a version that satisfies the requirement 
python-apt==1.6.5+ubuntu0.2 (from versions: 0.0.0, 0.7.8)
  No matching distribution found for python-apt==1.6.5+ubuntu0.2
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1883451/+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


[Touch-packages] [Bug 1883079] Re: The "MMap::MMap(FileFd&, unsigned long)" symbol is missing in libapt-pkg.so

2020-06-11 Thread Julian Andres Klode
MMap is an internal implementation detail that people have been using
accidentally when they wanted to open the cache, where they should use
pkgCacheFile for.

** Changed in: apt (Ubuntu)
   Status: Incomplete => 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/1883079

Title:
  The "MMap::MMap(FileFd&, unsigned long)" symbol is missing in libapt-
  pkg.so

Status in apt package in Ubuntu:
  Invalid

Bug description:
  The "MMap::MMap(FileFd&, unsigned long)" function is missing in
  libapt-pkg.so.6.0.0.

  
  nm -D -C /usr/lib/x86_64-linux-gnu/libapt-pkg.so.6.0.0 | grep MMap

  001701f0 T pkgCacheGenerator::MakeStatusCache(pkgSourceList&, 
OpProgress*, MMap**, bool)
  0016e9c0 T pkgCacheGenerator::MakeOnlyStatusCache(OpProgress*, 
DynamicMMap**)
  00167b10 T pkgCache::pkgCache(MMap*, bool)
  00167b10 T pkgCache::pkgCache(MMap*, bool)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1883079/+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


[Touch-packages] [Bug 1883079] Re: The "MMap::MMap(FileFd&, unsigned long)" symbol is missing in libapt-pkg.so

2020-06-11 Thread Julian Andres Klode
Yes, that's by design.

** 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/1883079

Title:
  The "MMap::MMap(FileFd&, unsigned long)" symbol is missing in libapt-
  pkg.so

Status in apt package in Ubuntu:
  Invalid

Bug description:
  The "MMap::MMap(FileFd&, unsigned long)" function is missing in
  libapt-pkg.so.6.0.0.

  
  nm -D -C /usr/lib/x86_64-linux-gnu/libapt-pkg.so.6.0.0 | grep MMap

  001701f0 T pkgCacheGenerator::MakeStatusCache(pkgSourceList&, 
OpProgress*, MMap**, bool)
  0016e9c0 T pkgCacheGenerator::MakeOnlyStatusCache(OpProgress*, 
DynamicMMap**)
  00167b10 T pkgCache::pkgCache(MMap*, bool)
  00167b10 T pkgCache::pkgCache(MMap*, bool)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1883079/+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


[Touch-packages] [Bug 1876035] Re: Automatically retry downloads on failures

2020-06-05 Thread Julian Andres Klode
Summary is that I don't believe the option as is is sufficient, and
needs to be reworked, so I'm changing the title accordingly.

** Summary changed:

- Consider making '-o Acquire::Retries=3' the default for 'apt-get 
update/install/dist-upgrade'
+ Automatically retry downloads on failures

-- 
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/1876035

Title:
  Automatically retry downloads on failures

Status in apt package in Ubuntu:
  Confirmed
Status in apt source package in Groovy:
  Confirmed

Bug description:
  Hi,

  We operate archive.ubuntu.com as well as mirrors of it in various
  places. We're getting reports of various CI/CD jobs failing. Sometimes
  due to routing issues, issues with overloaded servers/VMs hosting
  archive, etc.

  Any chance we can make '-o Acquire::Retries=3' the default for 'apt-
  get update/install/dist-upgrade'? Preferably with a randomised skew
  between retries.

  Also, any chance of having apt-get retry with different IPs/hosts
  returned from the DNS lookup? (e.g. for archive.ubuntu.com -
  91.189.88.142, 91.189.88.152, ...).

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1876035/+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


[Touch-packages] [Bug 574287] Re: tasksel: forcefully removes packages when tasks overlap

2020-05-28 Thread Julian Andres Klode
The easiest way out would be to just remove tasksel once the d-i images
are gone, and it's no longer needed.

-- 
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/574287

Title:
  tasksel: forcefully removes packages when tasks overlap

Status in apt package in Ubuntu:
  Invalid
Status in tasksel package in Ubuntu:
  Confirmed
Status in tasksel package in Debian:
  Fix Released

Bug description:
  TEST CASE

  1. Boot Lucid LiveCD

  2. run "sudo tasksel" and select "virtual machine host"

  3. run "sudo tasksel" and deselect "virtual machine host"

  4. watch how tasksel uninstalls your system

  OBSERVATIONS

  What seems to happen is that apt vengefully removes ALL of the items
  associated with one task, including several base dependencies of other
  tasks (e.g. ubuntu-desktop)

  One illustrative example is the openssh-server task:
  This one includes the packages openssh-server, tcpd and libwrap0.
  From a normal ubuntu-desktop (e.g. ~liveCD) both tcpd and libwrap0 are 
already installed, and the task-install pulls in only openssh-server.
  However when the task is removed, all these three packages (openssh-server, 
tcpd and libwrap0) are forcefully removed.
  Since libwrap0 is a core dependency of gnome, a large part of gnome will be 
removed alongside the removal of the task.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/574287/+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


[Touch-packages] [Bug 1713219] Re: 'apt-mark showauto' and 'apt show' is slow

2020-05-28 Thread Julian Andres Klode
I'm not going to add a second independent reader to apt just so that
apt-mark runs a bit faster.

-- 
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/1713219

Title:
  'apt-mark showauto' and 'apt show' is slow

Status in apt package in Ubuntu:
  Triaged

Bug description:
  $ time apt-mark showauto >/dev/null

  real  0m0.587s
  user  0m0.552s
  sys   0m0.016s

  When I run the command first time, it is even much slower.

  I could do the job in fraction of a time using awk in POSIX shell
  script:

  auto_file='/var/lib/apt/extended_states'
  eval $(apt-config shell auto_file Dir::State::extended_states/f)
  awk '/^Package:/ {
pkg=$2
getline; arch=$2
getline
if($2==1) print pkg ":" arch
  }' "$auto_file" | CL_ALL=C sort -u

  real  0m0.019s
  user  0m0.008s
  sys   0m0.000s

  That prints architecture for every package and shows entries in
  slightly different order, though. And the file could be out of date
  showing packages that are not installed?!?

  Similarly

  apt show 

  is slow. (It also shows whether a package is manually or automatically
  installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apt 1.0.1ubuntu2.17
  ProcVersionSignature: Ubuntu 4.4.0-92.115~14.04.1-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Aug 26 12:59:00 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-21 (1070 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.1)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.cron.daily.apt: [modified]
  modified.conffile..etc.kernel.postinst.d.apt.auto.removal: [modified]
  mtime.conffile..etc.cron.daily.apt: 2017-05-03T10:27:27.617839
  mtime.conffile..etc.kernel.postinst.d.apt.auto.removal: 
2017-06-01T14:39:39.236080

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1713219/+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


[Touch-packages] [Bug 1713219] Re: 'apt-mark showauto' and 'apt show' is slow

2020-05-28 Thread Julian Andres Klode
The problem is that the code that reads the state reads it into the
depcache.

-- 
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/1713219

Title:
  'apt-mark showauto' and 'apt show' is slow

Status in apt package in Ubuntu:
  Triaged

Bug description:
  $ time apt-mark showauto >/dev/null

  real  0m0.587s
  user  0m0.552s
  sys   0m0.016s

  When I run the command first time, it is even much slower.

  I could do the job in fraction of a time using awk in POSIX shell
  script:

  auto_file='/var/lib/apt/extended_states'
  eval $(apt-config shell auto_file Dir::State::extended_states/f)
  awk '/^Package:/ {
pkg=$2
getline; arch=$2
getline
if($2==1) print pkg ":" arch
  }' "$auto_file" | CL_ALL=C sort -u

  real  0m0.019s
  user  0m0.008s
  sys   0m0.000s

  That prints architecture for every package and shows entries in
  slightly different order, though. And the file could be out of date
  showing packages that are not installed?!?

  Similarly

  apt show 

  is slow. (It also shows whether a package is manually or automatically
  installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apt 1.0.1ubuntu2.17
  ProcVersionSignature: Ubuntu 4.4.0-92.115~14.04.1-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Aug 26 12:59:00 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-21 (1070 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.1)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.cron.daily.apt: [modified]
  modified.conffile..etc.kernel.postinst.d.apt.auto.removal: [modified]
  mtime.conffile..etc.cron.daily.apt: 2017-05-03T10:27:27.617839
  mtime.conffile..etc.kernel.postinst.d.apt.auto.removal: 
2017-06-01T14:39:39.236080

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1713219/+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


[Touch-packages] [Bug 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded

2020-05-22 Thread Julian Andres Klode
There are two things:

- On servers, ubuntu-server depends on mdadm, so removing mdadm also
removes ubuntu-server package, which means it's not really supported

- In general, the installers don't offer installing like that.

I don't know why we did not have a task for xenial.

** Description changed:

  [Impact]
  system does not boot after converting lvm volume to raid1 w/o having mdadm 
installed.
  
  [Test case]
  
- 1. Install server with subiquity to LVM
+ 1. Install server to LVM
  2. Add second disk to it
  3. Run pvcreate /dev/vdb
  4. Run vgextend ubuntu-vg /dev/vdb
- 5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv
+ 5. Run lvconvert -m1 --type raid1 ubuntu-vg/ubuntu-lv
  
  Reboot and check that it still boots.
  
  6. Remove mdadm
  7. Upgrade to lvm2 from proposed
  
  Reboot and check that it still boots.
  
  8. Downgrade lvm2 to release
  
  Reboot and check that it fails to boot
  
  [Regression potential]
  Not really anything, we just add the raid1 module to initramfs, so it might 
be loaded during boot, and raid1 logical volumes might appear earlier.
  
  [Original bug report]
  After upgrading to Wily, raid1 LVs don't activate during the initrd phase. 
Since the root LV is also RAID1-mirrored, the system doesn't boot.
  
  I get the following message each time LVM tries to activate a raid1 LV:
  md: personality for level 1 is not loaded!
  
  Everything was fine with Vivid. I had to downgrade to Vivid kernel
  (3.19.0-30) to get my system to a usable state. I pretty much hope it to
  be a temporary workaround and I'll get the new 4.2.0 kernel work with
  Wily in days.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1509717

Title:
  Wily LVM-RAID1 – md: personality for level 1 is not loaded

Status in linux package in Ubuntu:
  Invalid
Status in lvm2 package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Invalid
Status in lvm2 source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Invalid
Status in lvm2 source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Invalid
Status in lvm2 source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Invalid
Status in lvm2 source package in Eoan:
  Fix Released
Status in lvm2 package in Debian:
  Incomplete

Bug description:
  [Impact]
  system does not boot after converting lvm volume to raid1 w/o having mdadm 
installed.

  [Test case]

  1. Install server to LVM
  2. Add second disk to it
  3. Run pvcreate /dev/vdb
  4. Run vgextend ubuntu-vg /dev/vdb
  5. Run lvconvert -m1 --type raid1 ubuntu-vg/ubuntu-lv

  Reboot and check that it still boots.

  6. Remove mdadm
  7. Upgrade to lvm2 from proposed

  Reboot and check that it still boots.

  8. Downgrade lvm2 to release

  Reboot and check that it fails to boot

  [Regression potential]
  Not really anything, we just add the raid1 module to initramfs, so it might 
be loaded during boot, and raid1 logical volumes might appear earlier.

  [Original bug report]
  After upgrading to Wily, raid1 LVs don't activate during the initrd phase. 
Since the root LV is also RAID1-mirrored, the system doesn't boot.

  I get the following message each time LVM tries to activate a raid1 LV:
  md: personality for level 1 is not loaded!

  Everything was fine with Vivid. I had to downgrade to Vivid kernel
  (3.19.0-30) to get my system to a usable state. I pretty much hope it
  to be a temporary workaround and I'll get the new 4.2.0 kernel work
  with Wily in days.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509717/+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


[Touch-packages] [Bug 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded

2020-05-22 Thread Julian Andres Klode
That's certainly incorrect, lvm2 was fixed in focal (and hence groovy).
That only leaves xenial, but updating xenial close to its EOL for
something as unusual as this seems unneccessary. The supported
configuration for raid1 is mdadm after all, not removing mdadm and the
meta packages that depend on it and using lvm's raid support.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1509717

Title:
  Wily LVM-RAID1 – md: personality for level 1 is not loaded

Status in linux package in Ubuntu:
  Invalid
Status in lvm2 package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Invalid
Status in lvm2 source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Invalid
Status in lvm2 source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Invalid
Status in lvm2 source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Invalid
Status in lvm2 source package in Eoan:
  Fix Released
Status in lvm2 package in Debian:
  Incomplete

Bug description:
  [Impact]
  system does not boot after converting lvm volume to raid1 w/o having mdadm 
installed.

  [Test case]

  1. Install server with subiquity to LVM
  2. Add second disk to it
  3. Run pvcreate /dev/vdb
  4. Run vgextend ubuntu-vg /dev/vdb
  5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv

  Reboot and check that it still boots.

  6. Remove mdadm
  7. Upgrade to lvm2 from proposed

  Reboot and check that it still boots.

  8. Downgrade lvm2 to release

  Reboot and check that it fails to boot

  [Regression potential]
  Not really anything, we just add the raid1 module to initramfs, so it might 
be loaded during boot, and raid1 logical volumes might appear earlier.

  [Original bug report]
  After upgrading to Wily, raid1 LVs don't activate during the initrd phase. 
Since the root LV is also RAID1-mirrored, the system doesn't boot.

  I get the following message each time LVM tries to activate a raid1 LV:
  md: personality for level 1 is not loaded!

  Everything was fine with Vivid. I had to downgrade to Vivid kernel
  (3.19.0-30) to get my system to a usable state. I pretty much hope it
  to be a temporary workaround and I'll get the new 4.2.0 kernel work
  with Wily in days.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509717/+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


[Touch-packages] [Bug 645404] Re: Support Private PPAs

2020-05-20 Thread Julian Andres Klode
I was about ready to get back to reviewing this (or just saying meh, I
don't see anything obviously wrong, so just upload it) 3 months ago when
you declared that you gave up on the MR.

I don't see how creating a new tool is easier than just uploading your
changes. Both have the same effect of ignoring feedback.

I do believe the changes are too big to be backported into older release
series.

It's next to impossible to review the merge requests because it just
keeps growing and growing, and mixing all sort of work together in one
gigantic diff.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/645404

Title:
  Support Private PPAs

Status in software-properties package in Ubuntu:
  Confirmed
Status in software-properties source package in Bionic:
  Won't Fix
Status in software-properties source package in Cosmic:
  Won't Fix
Status in software-properties source package in Disco:
  Won't Fix
Status in software-properties source package in Eoan:
  Won't Fix
Status in software-properties source package in Focal:
  Won't Fix

Bug description:
  Software properties add-apt-repository currently does not support
  adding private PPAs.

  software-properties should connect to the API and observe that it gets
  permission denied trying to read the ppa. Then it can reconnect to the
  API asking for authentication, which will open a browser window where
  you can do the openid ritual. Then using that token it ought to be
  possible for it to get the password etc.

  
  ProblemType: BugDistroRelease: Ubuntu 12.04
  Package: python-software-properties 0.82.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/645404/+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


[Touch-packages] [Bug 1876035] Re: Consider making '-o Acquire::Retries=3' the default for 'apt-get update/install/dist-upgrade'

2020-05-18 Thread Julian Andres Klode
A few points to think about:

1. I am not aware of anyone using that option, we don't know if it works
and how it behaves

2. Given 1, what kind of testing can we do? This needs to be thoroughly
tested, given that it's not been tested at all.

3. Switching IPs might be useful, but it's not clear to me yet how that
would work in practice. We can basically blacklist certain IPs so it
jumps to the next one, but we need to make sure we don't run out of IPs
I guess. Also we use one connection per hostname, so each failure would
switch the connection to a different IP address for all following
requests.

4. Does it have any kind of delay right now? I don't think it does, and
it sounds hard, and also pointless if we switch IPs.

5. I'd like to retry across different host names 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/1876035

Title:
  Consider making '-o Acquire::Retries=3' the default for 'apt-get
  update/install/dist-upgrade'

Status in apt package in Ubuntu:
  Confirmed
Status in apt source package in Groovy:
  Confirmed

Bug description:
  Hi,

  We operate archive.ubuntu.com as well as mirrors of it in various
  places. We're getting reports of various CI/CD jobs failing. Sometimes
  due to routing issues, issues with overloaded servers/VMs hosting
  archive, etc.

  Any chance we can make '-o Acquire::Retries=3' the default for 'apt-
  get update/install/dist-upgrade'? Preferably with a randomised skew
  between retries.

  Also, any chance of having apt-get retry with different IPs/hosts
  returned from the DNS lookup? (e.g. for archive.ubuntu.com -
  91.189.88.142, 91.189.88.152, ...).

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1876035/+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


[Touch-packages] [Bug 1877987] Re: apt search coredumping

2020-05-18 Thread Julian Andres Klode
Fixed in 2.1.3, will look into adding a test case and backporting this
to 2.0 shortly.

** Changed in: apt (Ubuntu)
   Status: New => Fix Committed

** Also affects: apt (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: apt (Ubuntu Focal)
   Importance: Undecided
   Status: New

** No longer affects: apt (Ubuntu Bionic)

** Changed in: apt (Ubuntu Focal)
   Status: New => 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/1877987

Title:
  apt search coredumping

Status in apt package in Ubuntu:
  Fix Committed
Status in apt source package in Focal:
  Triaged

Bug description:
  root@citoyx:/var/crash# apt search jdk
  Sorting... Done
  Segmentation fault (core dumped)

  May 11 12:34:25 citoyx kernel: [ 1354.337907] apt[10418]: segfault at 
7f67292dcfc0 ip 7f6309ce4997 sp 7ffdab880930 error 4 in 
libapt-pkg.so.6.0.0[7f6309bb5000+147000]
  May 11 12:34:25 citoyx kernel: [ 1354.337916] Code: 48 8b 45 18 48 8b 04 d0 
48 83 c4 08 5b 5d c3 0f 1f 40 00 f3 0f 1e fa 55 48 89 fd 53 48 89 f3 48 83 ec 
08 48 8b 06 48 8b 4e 08 <8b> 10 48 8d 04 d5 00 00 00 00 48 29 d0 48 8b 51 60 48 
8d 04 c2 0f

  
  root@citoyx:/var/crash# cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=20.04
  DISTRIB_CODENAME=focal
  DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS"

  
  apt search is coredumping 
  While apt install/upgrade/update is running fine 

  crash file in attachment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1877987/+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


[Touch-packages] [Bug 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded

2020-05-18 Thread Julian Andres Klode
The regressions in bionic seem unrelated to me adding the raid1 module
to the list of modules installed to the initramfs.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1509717

Title:
  Wily LVM-RAID1 – md: personality for level 1 is not loaded

Status in linux package in Ubuntu:
  Invalid
Status in lvm2 package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Invalid
Status in lvm2 source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Invalid
Status in lvm2 source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Invalid
Status in lvm2 source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Invalid
Status in lvm2 source package in Eoan:
  Fix Committed
Status in lvm2 package in Debian:
  Incomplete

Bug description:
  [Impact]
  system does not boot after converting lvm volume to raid1 w/o having mdadm 
installed.

  [Test case]

  1. Install server with subiquity to LVM
  2. Add second disk to it
  3. Run pvcreate /dev/vdb
  4. Run vgextend ubuntu-vg /dev/vdb
  5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv

  Reboot and check that it still boots.

  6. Remove mdadm
  7. Upgrade to lvm2 from proposed

  Reboot and check that it still boots.

  8. Downgrade lvm2 to release

  Reboot and check that it fails to boot

  [Regression potential]
  Not really anything, we just add the raid1 module to initramfs, so it might 
be loaded during boot, and raid1 logical volumes might appear earlier.

  [Original bug report]
  After upgrading to Wily, raid1 LVs don't activate during the initrd phase. 
Since the root LV is also RAID1-mirrored, the system doesn't boot.

  I get the following message each time LVM tries to activate a raid1 LV:
  md: personality for level 1 is not loaded!

  Everything was fine with Vivid. I had to downgrade to Vivid kernel
  (3.19.0-30) to get my system to a usable state. I pretty much hope it
  to be a temporary workaround and I'll get the new 4.2.0 kernel work
  with Wily in days.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509717/+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


[Touch-packages] [Bug 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded

2020-05-18 Thread Julian Andres Klode
eoan verified.

So, eoan is tougher. I installed it with subiquity and tried to follow
the steps, but failed to convert to raid1, apparently, subiquity created
the LV 1 PE larger than before or something, so it needed 1 free PE in
the original PV to be able to add the raid1 metadata, which it did not
have.

Worked around this by extending the PV size after the install (after
tryin to shrink the existing LV first, messing up the install, and
reinstalling ...).


With proposed lvm2 ubuntu6.1 it boots as wanted, downgrading to ubuntu6 in 
release breaks it again.

** Tags removed: verification-needed verification-needed-eoan
** Tags added: verification-done verification-done-eoan

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1509717

Title:
  Wily LVM-RAID1 – md: personality for level 1 is not loaded

Status in linux package in Ubuntu:
  Invalid
Status in lvm2 package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Invalid
Status in lvm2 source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Invalid
Status in lvm2 source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Invalid
Status in lvm2 source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Invalid
Status in lvm2 source package in Eoan:
  Fix Committed
Status in lvm2 package in Debian:
  Incomplete

Bug description:
  [Impact]
  system does not boot after converting lvm volume to raid1 w/o having mdadm 
installed.

  [Test case]

  1. Install server with subiquity to LVM
  2. Add second disk to it
  3. Run pvcreate /dev/vdb
  4. Run vgextend ubuntu-vg /dev/vdb
  5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv

  Reboot and check that it still boots.

  6. Remove mdadm
  7. Upgrade to lvm2 from proposed

  Reboot and check that it still boots.

  8. Downgrade lvm2 to release

  Reboot and check that it fails to boot

  [Regression potential]
  Not really anything, we just add the raid1 module to initramfs, so it might 
be loaded during boot, and raid1 logical volumes might appear earlier.

  [Original bug report]
  After upgrading to Wily, raid1 LVs don't activate during the initrd phase. 
Since the root LV is also RAID1-mirrored, the system doesn't boot.

  I get the following message each time LVM tries to activate a raid1 LV:
  md: personality for level 1 is not loaded!

  Everything was fine with Vivid. I had to downgrade to Vivid kernel
  (3.19.0-30) to get my system to a usable state. I pretty much hope it
  to be a temporary workaround and I'll get the new 4.2.0 kernel work
  with Wily in days.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509717/+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


[Touch-packages] [Bug 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded

2020-05-18 Thread Julian Andres Klode
verified in bionic

Did all the steps (install vm, create pv, extend pv, remove dmadm,
upgrade).

It booted after the upgrade to 2.02.176-4.1ubuntu3.18.04.3, and it
failed again following a downgrade to the 2.02.176-4.1ubuntu3.18.04.2
from updates pocket.

** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

** Tags removed: id-5d0ba914f340e31a8e9f2cf1 removal-candidate
** Tags added: id-5d0ba914f340e31a8e9f2cf

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1509717

Title:
  Wily LVM-RAID1 – md: personality for level 1 is not loaded

Status in linux package in Ubuntu:
  Invalid
Status in lvm2 package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Invalid
Status in lvm2 source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Invalid
Status in lvm2 source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Invalid
Status in lvm2 source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Invalid
Status in lvm2 source package in Eoan:
  Fix Committed
Status in lvm2 package in Debian:
  Incomplete

Bug description:
  [Impact]
  system does not boot after converting lvm volume to raid1 w/o having mdadm 
installed.

  [Test case]

  1. Install server with subiquity to LVM
  2. Add second disk to it
  3. Run pvcreate /dev/vdb
  4. Run vgextend ubuntu-vg /dev/vdb
  5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv

  Reboot and check that it still boots.

  6. Remove mdadm
  7. Upgrade to lvm2 from proposed

  Reboot and check that it still boots.

  8. Downgrade lvm2 to release

  Reboot and check that it fails to boot

  [Regression potential]
  Not really anything, we just add the raid1 module to initramfs, so it might 
be loaded during boot, and raid1 logical volumes might appear earlier.

  [Original bug report]
  After upgrading to Wily, raid1 LVs don't activate during the initrd phase. 
Since the root LV is also RAID1-mirrored, the system doesn't boot.

  I get the following message each time LVM tries to activate a raid1 LV:
  md: personality for level 1 is not loaded!

  Everything was fine with Vivid. I had to downgrade to Vivid kernel
  (3.19.0-30) to get my system to a usable state. I pretty much hope it
  to be a temporary workaround and I'll get the new 4.2.0 kernel work
  with Wily in days.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509717/+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


[Touch-packages] [Bug 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded

2020-05-18 Thread Julian Andres Klode
** Description changed:

  [Impact]
  system does not boot after converting lvm volume to raid1 w/o having mdadm 
installed.
  
  [Test case]
  
  1. Install server with subiquity to LVM
  2. Add second disk to it
  3. Run pvcreate /dev/vdb
  4. Run vgextend ubuntu-vg /dev/vdb
  5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv
  
  Reboot and check that it still boots.
  
- 6. Remove demsetup
+ 6. Remove mdadm
  
  Reboot and check that it fails to boot
  
  7. Upgrade to lvm2 from proposed
  
  Reboot and check that it still boots.
  
  [Regression potential]
  Not really anything, we just add the raid1 module to initramfs, so it might 
be loaded during boot, and raid1 logical volumes might appear earlier.
  
  [Original bug report]
  After upgrading to Wily, raid1 LVs don't activate during the initrd phase. 
Since the root LV is also RAID1-mirrored, the system doesn't boot.
  
  I get the following message each time LVM tries to activate a raid1 LV:
  md: personality for level 1 is not loaded!
  
  Everything was fine with Vivid. I had to downgrade to Vivid kernel
  (3.19.0-30) to get my system to a usable state. I pretty much hope it to
  be a temporary workaround and I'll get the new 4.2.0 kernel work with
  Wily in days.

** Description changed:

  [Impact]
  system does not boot after converting lvm volume to raid1 w/o having mdadm 
installed.
  
  [Test case]
  
  1. Install server with subiquity to LVM
  2. Add second disk to it
  3. Run pvcreate /dev/vdb
  4. Run vgextend ubuntu-vg /dev/vdb
  5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv
  
  Reboot and check that it still boots.
  
  6. Remove mdadm
- 
- Reboot and check that it fails to boot
- 
  7. Upgrade to lvm2 from proposed
  
  Reboot and check that it still boots.
+ 
+ 8. Downgrade lvm2 to release
+ 
+ Reboot and check that it fails to boot
  
  [Regression potential]
  Not really anything, we just add the raid1 module to initramfs, so it might 
be loaded during boot, and raid1 logical volumes might appear earlier.
  
  [Original bug report]
  After upgrading to Wily, raid1 LVs don't activate during the initrd phase. 
Since the root LV is also RAID1-mirrored, the system doesn't boot.
  
  I get the following message each time LVM tries to activate a raid1 LV:
  md: personality for level 1 is not loaded!
  
  Everything was fine with Vivid. I had to downgrade to Vivid kernel
  (3.19.0-30) to get my system to a usable state. I pretty much hope it to
  be a temporary workaround and I'll get the new 4.2.0 kernel work with
  Wily in days.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1509717

Title:
  Wily LVM-RAID1 – md: personality for level 1 is not loaded

Status in linux package in Ubuntu:
  Invalid
Status in lvm2 package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Invalid
Status in lvm2 source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Invalid
Status in lvm2 source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Invalid
Status in lvm2 source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Invalid
Status in lvm2 source package in Eoan:
  Fix Committed
Status in lvm2 package in Debian:
  Incomplete

Bug description:
  [Impact]
  system does not boot after converting lvm volume to raid1 w/o having mdadm 
installed.

  [Test case]

  1. Install server with subiquity to LVM
  2. Add second disk to it
  3. Run pvcreate /dev/vdb
  4. Run vgextend ubuntu-vg /dev/vdb
  5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv

  Reboot and check that it still boots.

  6. Remove mdadm
  7. Upgrade to lvm2 from proposed

  Reboot and check that it still boots.

  8. Downgrade lvm2 to release

  Reboot and check that it fails to boot

  [Regression potential]
  Not really anything, we just add the raid1 module to initramfs, so it might 
be loaded during boot, and raid1 logical volumes might appear earlier.

  [Original bug report]
  After upgrading to Wily, raid1 LVs don't activate during the initrd phase. 
Since the root LV is also RAID1-mirrored, the system doesn't boot.

  I get the following message each time LVM tries to activate a raid1 LV:
  md: personality for level 1 is not loaded!

  Everything was fine with Vivid. I had to downgrade to Vivid kernel
  (3.19.0-30) to get my system to a usable state. I pretty much hope it
  to be a temporary workaround and I'll get the new 4.2.0 kernel work
  with Wily in days.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509717/+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


[Touch-packages] [Bug 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded

2020-05-18 Thread Julian Andres Klode
** Description changed:

  [Impact]
  system does not boot after converting lvm volume to raid1 w/o having mdadm 
installed.
  
  [Test case]
  
  1. Install server with subiquity to LVM
- 2. Add second disk to it
- 3. Run pvcreate /dev/vdb
- 4. Run vgextend ubuntu-vg /dev/vdb
- 5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv
+ 2. Remove demsetup
+ 3. Add second disk to it
+ 4. Run pvcreate /dev/vdb
+ 5. Run vgextend ubuntu-vg /dev/vdb
+ 6. Run lvconvert -m1 --type raid1 ubuntu-vg/lv
  
  Reboot and check that it still boots.
  
  [Regression potential]
  Not really anything, we just add the raid1 module to initramfs, so it might 
be loaded during boot, and raid1 logical volumes might appear earlier.
  
  [Original bug report]
  After upgrading to Wily, raid1 LVs don't activate during the initrd phase. 
Since the root LV is also RAID1-mirrored, the system doesn't boot.
  
  I get the following message each time LVM tries to activate a raid1 LV:
  md: personality for level 1 is not loaded!
  
  Everything was fine with Vivid. I had to downgrade to Vivid kernel
  (3.19.0-30) to get my system to a usable state. I pretty much hope it to
  be a temporary workaround and I'll get the new 4.2.0 kernel work with
  Wily in days.

** Description changed:

  [Impact]
  system does not boot after converting lvm volume to raid1 w/o having mdadm 
installed.
  
  [Test case]
  
  1. Install server with subiquity to LVM
- 2. Remove demsetup
- 3. Add second disk to it
- 4. Run pvcreate /dev/vdb
- 5. Run vgextend ubuntu-vg /dev/vdb
- 6. Run lvconvert -m1 --type raid1 ubuntu-vg/lv
+ 2. Add second disk to it
+ 3. Run pvcreate /dev/vdb
+ 4. Run vgextend ubuntu-vg /dev/vdb
+ 5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv
+ 
+ Reboot and check that it still boots.
+ 
+ 6. Remove demsetup
+ 
+ Reboot and check that it fails to boot
+ 
+ 7. Upgrade to lvm2 from proposed
  
  Reboot and check that it still boots.
  
  [Regression potential]
  Not really anything, we just add the raid1 module to initramfs, so it might 
be loaded during boot, and raid1 logical volumes might appear earlier.
  
  [Original bug report]
  After upgrading to Wily, raid1 LVs don't activate during the initrd phase. 
Since the root LV is also RAID1-mirrored, the system doesn't boot.
  
  I get the following message each time LVM tries to activate a raid1 LV:
  md: personality for level 1 is not loaded!
  
  Everything was fine with Vivid. I had to downgrade to Vivid kernel
  (3.19.0-30) to get my system to a usable state. I pretty much hope it to
  be a temporary workaround and I'll get the new 4.2.0 kernel work with
  Wily in days.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1509717

Title:
  Wily LVM-RAID1 – md: personality for level 1 is not loaded

Status in linux package in Ubuntu:
  Invalid
Status in lvm2 package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Invalid
Status in lvm2 source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Invalid
Status in lvm2 source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Invalid
Status in lvm2 source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Invalid
Status in lvm2 source package in Eoan:
  Fix Committed
Status in lvm2 package in Debian:
  Incomplete

Bug description:
  [Impact]
  system does not boot after converting lvm volume to raid1 w/o having mdadm 
installed.

  [Test case]

  1. Install server with subiquity to LVM
  2. Add second disk to it
  3. Run pvcreate /dev/vdb
  4. Run vgextend ubuntu-vg /dev/vdb
  5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv

  Reboot and check that it still boots.

  6. Remove mdadm
  7. Upgrade to lvm2 from proposed

  Reboot and check that it still boots.

  8. Downgrade lvm2 to release

  Reboot and check that it fails to boot

  [Regression potential]
  Not really anything, we just add the raid1 module to initramfs, so it might 
be loaded during boot, and raid1 logical volumes might appear earlier.

  [Original bug report]
  After upgrading to Wily, raid1 LVs don't activate during the initrd phase. 
Since the root LV is also RAID1-mirrored, the system doesn't boot.

  I get the following message each time LVM tries to activate a raid1 LV:
  md: personality for level 1 is not loaded!

  Everything was fine with Vivid. I had to downgrade to Vivid kernel
  (3.19.0-30) to get my system to a usable state. I pretty much hope it
  to be a temporary workaround and I'll get the new 4.2.0 kernel work
  with Wily in days.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509717/+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


[Touch-packages] [Bug 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded

2020-05-18 Thread Julian Andres Klode
** Description changed:

  [Impact]
  system does not boot after converting lvm volume to raid1 w/o having mdadm 
installed.
  
  [Test case]
  
- 1. Install server with subiquity to VM
+ 1. Install server with subiquity to LVM
  2. Add second disk to it
  3. Run pvcreate /dev/vdb
  4. Run vgextend ubuntu-vg /dev/vdb
  5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv
  
  Reboot and check that it still boots.
  
  [Regression potential]
  Not really anything, we just add the raid1 module to initramfs, so it might 
be loaded during boot, and raid1 logical volumes might appear earlier.
  
  [Original bug report]
  After upgrading to Wily, raid1 LVs don't activate during the initrd phase. 
Since the root LV is also RAID1-mirrored, the system doesn't boot.
  
  I get the following message each time LVM tries to activate a raid1 LV:
  md: personality for level 1 is not loaded!
  
  Everything was fine with Vivid. I had to downgrade to Vivid kernel
  (3.19.0-30) to get my system to a usable state. I pretty much hope it to
  be a temporary workaround and I'll get the new 4.2.0 kernel work with
  Wily in days.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1509717

Title:
  Wily LVM-RAID1 – md: personality for level 1 is not loaded

Status in linux package in Ubuntu:
  Invalid
Status in lvm2 package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Invalid
Status in lvm2 source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Invalid
Status in lvm2 source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Invalid
Status in lvm2 source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Invalid
Status in lvm2 source package in Eoan:
  Fix Committed
Status in lvm2 package in Debian:
  Incomplete

Bug description:
  [Impact]
  system does not boot after converting lvm volume to raid1 w/o having mdadm 
installed.

  [Test case]

  1. Install server with subiquity to LVM
  2. Add second disk to it
  3. Run pvcreate /dev/vdb
  4. Run vgextend ubuntu-vg /dev/vdb
  5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv

  Reboot and check that it still boots.

  [Regression potential]
  Not really anything, we just add the raid1 module to initramfs, so it might 
be loaded during boot, and raid1 logical volumes might appear earlier.

  [Original bug report]
  After upgrading to Wily, raid1 LVs don't activate during the initrd phase. 
Since the root LV is also RAID1-mirrored, the system doesn't boot.

  I get the following message each time LVM tries to activate a raid1 LV:
  md: personality for level 1 is not loaded!

  Everything was fine with Vivid. I had to downgrade to Vivid kernel
  (3.19.0-30) to get my system to a usable state. I pretty much hope it
  to be a temporary workaround and I'll get the new 4.2.0 kernel work
  with Wily in days.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509717/+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


[Touch-packages] [Bug 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded

2020-05-18 Thread Julian Andres Klode
sorry, working on verifying it, got distracted by other stuff.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1509717

Title:
  Wily LVM-RAID1 – md: personality for level 1 is not loaded

Status in linux package in Ubuntu:
  Invalid
Status in lvm2 package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Invalid
Status in lvm2 source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Invalid
Status in lvm2 source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Invalid
Status in lvm2 source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Invalid
Status in lvm2 source package in Eoan:
  Fix Committed
Status in lvm2 package in Debian:
  Incomplete

Bug description:
  [Impact]
  system does not boot after converting lvm volume to raid1 w/o having mdadm 
installed.

  [Test case]

  1. Install server with subiquity to VM
  2. Add second disk to it
  3. Run pvcreate /dev/vdb
  4. Run vgextend ubuntu-vg /dev/vdb
  5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv

  Reboot and check that it still boots.

  [Regression potential]
  Not really anything, we just add the raid1 module to initramfs, so it might 
be loaded during boot, and raid1 logical volumes might appear earlier.

  [Original bug report]
  After upgrading to Wily, raid1 LVs don't activate during the initrd phase. 
Since the root LV is also RAID1-mirrored, the system doesn't boot.

  I get the following message each time LVM tries to activate a raid1 LV:
  md: personality for level 1 is not loaded!

  Everything was fine with Vivid. I had to downgrade to Vivid kernel
  (3.19.0-30) to get my system to a usable state. I pretty much hope it
  to be a temporary workaround and I'll get the new 4.2.0 kernel work
  with Wily in days.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509717/+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


[Touch-packages] [Bug 1872200] Re: apt does not accept globs and regexes in some cases

2020-05-14 Thread Julian Andres Klode
FWIW, The upload has been superceded by a security update, and will need
revalidation when 2.0.4 is uploaded.

-- 
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/1872200

Title:
  apt does not accept globs and regexes in some cases

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Focal:
  Fix Committed
Status in apt source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  Users can't use * wildcards anymore in focal, except by accident in apt list.

  For apt list, we now start restricting wildcard syntax to the same
  syntax install now accepts, and at the same time we remove the
  restrictions on which patterns are accepted (which only accepted
  patterns starting in ~ or ?), so !~napt now works, and does not
  accidentally match as a wildcard.

  
  [Test case]

  Test that * wildcards work for both install and list, and test that a
  ? wildcard does not.

  We included autopkgtests for those:

   BEGIN TESTS #

  # * wildcards should still work
  testsuccessequal "Listing...
  automatic1/now 1.0 i386 [installed,local]
  automatic2/now 1.0 i386 [installed,local]" apt list 'automatic*'

  testfailureequal "Reading package lists...
  Building dependency tree...
  Reading state information...
  Note, selecting 'automatic1' for glob 'automatic*'
  Note, selecting 'automatic2' for glob 'automatic*'
  automatic1 is already the newest version (1.0).
  automatic1 set to manually installed.
  automatic2 is already the newest version (1.0).
  automatic2 set to manually installed.
  You might want to run 'apt --fix-broken install' to correct these.
  The following packages have unmet dependencies:
   broken : Depends: does-not-exist but it is not installable
  E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution)." apt install -s 'automatic*'

  # other wildcards should fail

  testfailureequal "Listing...
  E: input:0-10: error: Expected pattern
 automatic?
 ^^" apt list 'automatic?'

  testfailureequal "Reading package lists...
  Building dependency tree...
  Reading state information...
  E: Unable to locate package automatic?" apt install -s 'automatic?'

  
   END TESTS #

  Also it might be worth checking that apt list !~napt works. This used
  to produce an empty list, as it was accidentally matched as a wildcard
  and produced no result - now it produces every package whose name does
  not contain "apt".

  
  [Regression potential]
  The changes only affect interactive users, as apt(8) is not stable for 
in-script use, hence they can fix up their command-line if it stops working for 
them (though, really, more should work now).

  No scripts will be broken :)

  [Squashed in changes]
  The SRU also fixes potential build failures by correctly prefxing nullptr_t 
with the std:: namespace, and includes updated Dutch documentation.

  [Original bug report]
  Observed with Ubuntu 20.04 Beta.

  apt remove 'mypackage*' does not remove all installed packages
  starting with “mypackage”.  Instead:

  $ sudo apt remove 'mypackage*'
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  E: Unable to locate package mypackage*

  However:

  $ sudo apt list --installed 'mypackage*'
  Listing... Done
  mypackage-data-v1/focal,focal,now 0.3.2-5build1 all [installed,automatic]
  mypackage1/focal,now 0.3.2-5build1 amd64 [installed]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1872200/+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


[Touch-packages] [Bug 1877987] Re: apt search coredumping

2020-05-13 Thread Julian Andres Klode
I believe that https://salsa.debian.org/apt-
team/apt/-/merge_requests/120 fixes this.

** Information type changed from Private Security to Private

** Information type changed from Private to Public

-- 
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/1877987

Title:
  apt search coredumping

Status in apt package in Ubuntu:
  New

Bug description:
  root@citoyx:/var/crash# apt search jdk
  Sorting... Done
  Segmentation fault (core dumped)

  May 11 12:34:25 citoyx kernel: [ 1354.337907] apt[10418]: segfault at 
7f67292dcfc0 ip 7f6309ce4997 sp 7ffdab880930 error 4 in 
libapt-pkg.so.6.0.0[7f6309bb5000+147000]
  May 11 12:34:25 citoyx kernel: [ 1354.337916] Code: 48 8b 45 18 48 8b 04 d0 
48 83 c4 08 5b 5d c3 0f 1f 40 00 f3 0f 1e fa 55 48 89 fd 53 48 89 f3 48 83 ec 
08 48 8b 06 48 8b 4e 08 <8b> 10 48 8d 04 d5 00 00 00 00 48 29 d0 48 8b 51 60 48 
8d 04 c2 0f

  
  root@citoyx:/var/crash# cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=20.04
  DISTRIB_CODENAME=focal
  DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS"

  
  apt search is coredumping 
  While apt install/upgrade/update is running fine 

  crash file in attachment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1877987/+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


[Touch-packages] [Bug 1877987] Re: apt search coredumping

2020-05-13 Thread Julian Andres Klode
(I also believe this is the same issue as
https://errors.ubuntu.com/bucket/?id=/usr/bin/apt%3A11%3Aoperator%3ApkgCache%3A%3ADescFileIterator%3A%3AFile%3ApkgRecords%3A%3ALookup%3AFullTextSearch%3ADoSearch)

-- 
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/1877987

Title:
  apt search coredumping

Status in apt package in Ubuntu:
  New

Bug description:
  root@citoyx:/var/crash# apt search jdk
  Sorting... Done
  Segmentation fault (core dumped)

  May 11 12:34:25 citoyx kernel: [ 1354.337907] apt[10418]: segfault at 
7f67292dcfc0 ip 7f6309ce4997 sp 7ffdab880930 error 4 in 
libapt-pkg.so.6.0.0[7f6309bb5000+147000]
  May 11 12:34:25 citoyx kernel: [ 1354.337916] Code: 48 8b 45 18 48 8b 04 d0 
48 83 c4 08 5b 5d c3 0f 1f 40 00 f3 0f 1e fa 55 48 89 fd 53 48 89 f3 48 83 ec 
08 48 8b 06 48 8b 4e 08 <8b> 10 48 8d 04 d5 00 00 00 00 48 29 d0 48 8b 51 60 48 
8d 04 c2 0f

  
  root@citoyx:/var/crash# cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=20.04
  DISTRIB_CODENAME=focal
  DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS"

  
  apt search is coredumping 
  While apt install/upgrade/update is running fine 

  crash file in attachment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1877987/+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


[Touch-packages] [Bug 1875910] Re: Command to update mirror list

2020-05-13 Thread Julian Andres Klode
On the (python-apt) client side, this involves adding an apt.conf
snippet to configure a new index target and then change the code to read
from there.

-- 
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/1875910

Title:
  Command to update mirror list

Status in Launchpad itself:
  New
Status in python-apt package in Ubuntu:
  Triaged

Bug description:
  I see a lot of issues regarding outdated Ubuntu.mirrors file, I think
  there should be a command that imports the list of mirrors from
  https://launchpad.net/ubuntu/+archivemirrors and updates the
  templates/Ubuntu.mirrors file, then in the UI add a button that can
  update the list of Mirrors. I don't see the point of needing a new
  release every time the list needs to be updated.

  I want a mirror that was updated yesterday, because is the closest to
  my location, but it is not in the list, and as you can see there are
  lots of issues from people that could have been avoided with this.

  This is not really a bug, but a feature.
  Also could be great if there was some kind of filter, like if you select now 
in Ubuntu 19.10 a ftp mirror and update it will fail, and the UI gets broken 
(you can't even close the window, you have to kill it), so doing this update 
should just import those mirrors that are safe to use.

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/1875910/+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


[Touch-packages] [Bug 1875910] Re: Command to update mirror list

2020-05-13 Thread Julian Andres Klode
Mirror lists change on a daily basis, python-apt on less than a point
release basis (it should update mirror lists before point release, but
this does not always happen afaict).

** Changed in: python-apt (Ubuntu)
   Importance: Undecided => High

-- 
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/1875910

Title:
  Command to update mirror list

Status in Launchpad itself:
  New
Status in python-apt package in Ubuntu:
  Triaged

Bug description:
  I see a lot of issues regarding outdated Ubuntu.mirrors file, I think
  there should be a command that imports the list of mirrors from
  https://launchpad.net/ubuntu/+archivemirrors and updates the
  templates/Ubuntu.mirrors file, then in the UI add a button that can
  update the list of Mirrors. I don't see the point of needing a new
  release every time the list needs to be updated.

  I want a mirror that was updated yesterday, because is the closest to
  my location, but it is not in the list, and as you can see there are
  lots of issues from people that could have been avoided with this.

  This is not really a bug, but a feature.
  Also could be great if there was some kind of filter, like if you select now 
in Ubuntu 19.10 a ftp mirror and update it will fail, and the UI gets broken 
(you can't even close the window, you have to kill it), so doing this update 
should just import those mirrors that are safe to use.

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/1875910/+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


[Touch-packages] [Bug 1875910] Re: Command to update mirror list

2020-05-13 Thread Julian Andres Klode
I think Launchpad should start shipping mirror lists in -updates pocket
(only; probably), so that we can update the mirror lists of installed
systems as part of apt update and don't have to rebuild python-apt and
upgrade everywhere.

** Also affects: launchpad
   Importance: Undecided
   Status: New

** Changed in: python-apt (Ubuntu)
   Status: New => Triaged

-- 
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/1875910

Title:
  Command to update mirror list

Status in Launchpad itself:
  New
Status in python-apt package in Ubuntu:
  Triaged

Bug description:
  I see a lot of issues regarding outdated Ubuntu.mirrors file, I think
  there should be a command that imports the list of mirrors from
  https://launchpad.net/ubuntu/+archivemirrors and updates the
  templates/Ubuntu.mirrors file, then in the UI add a button that can
  update the list of Mirrors. I don't see the point of needing a new
  release every time the list needs to be updated.

  I want a mirror that was updated yesterday, because is the closest to
  my location, but it is not in the list, and as you can see there are
  lots of issues from people that could have been avoided with this.

  This is not really a bug, but a feature.
  Also could be great if there was some kind of filter, like if you select now 
in Ubuntu 19.10 a ftp mirror and update it will fail, and the UI gets broken 
(you can't even close the window, you have to kill it), so doing this update 
should just import those mirrors that are safe to use.

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/1875910/+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


[Touch-packages] [Bug 1877233] Re: Remove inactive Mirrors to Colombia

2020-05-13 Thread Julian Andres Klode
My goal for future releases is to shift that info out of the python-apt
package and into the -updates pocket of the archive, so that the mirror
list is updated as part of apt update.

-- 
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/1877233

Title:
  Remove inactive Mirrors to Colombia

Status in Ubuntu:
  Invalid
Status in python-apt package in Ubuntu:
  Fix Released
Status in The Bionic Beaver:
  Invalid
Status in python-apt source package in Bionic:
  Invalid

Bug description:
  Hallo,

  Our mirror at the mirror.upb.edu.co is being hosted any longer but it
  is still showing up on the "Software & Updates" application. Could you
  please remove it? The server is already removed from this list
  https://launchpad.net/ubuntu/+archivemirrors in the Colombia section.

  Thanks a lot.

  Present on bionic (18.04)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1877233/+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


[Touch-packages] [Bug 1877233] Re: Remove inactive Mirrors to Colombia

2020-05-13 Thread Julian Andres Klode
I don't think it's worth tracking this. There are a ton of mirror
changes on a daily basis, and we can't update the python-apt package
that often.

Releases that will get a point release should get a python-apt update
for that.

Other releases will get the mirror update together with a regular
update.

FWIW, a regular update is in the unapproved queue for all releases.


** Changed in: python-apt (Ubuntu Bionic)
   Status: Triaged => Invalid

-- 
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/1877233

Title:
  Remove inactive Mirrors to Colombia

Status in Ubuntu:
  Invalid
Status in python-apt package in Ubuntu:
  Fix Released
Status in The Bionic Beaver:
  Invalid
Status in python-apt source package in Bionic:
  Invalid

Bug description:
  Hallo,

  Our mirror at the mirror.upb.edu.co is being hosted any longer but it
  is still showing up on the "Software & Updates" application. Could you
  please remove it? The server is already removed from this list
  https://launchpad.net/ubuntu/+archivemirrors in the Colombia section.

  Thanks a lot.

  Present on bionic (18.04)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1877233/+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


[Touch-packages] [Bug 1877233] Re: Remove inactive Mirrors to Colombia

2020-05-13 Thread Julian Andres Klode
We do not update mirror lists on their own, except for point releases,
and as part of other updates (the python-apt release process
automatically triggers mirror list updates, so this bug won't be
updated).

-- 
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/1877233

Title:
  Remove inactive Mirrors to Colombia

Status in Ubuntu:
  Invalid
Status in python-apt package in Ubuntu:
  Fix Released
Status in The Bionic Beaver:
  Invalid
Status in python-apt source package in Bionic:
  Triaged

Bug description:
  Hallo,

  Our mirror at the mirror.upb.edu.co is being hosted any longer but it
  is still showing up on the "Software & Updates" application. Could you
  please remove it? The server is already removed from this list
  https://launchpad.net/ubuntu/+archivemirrors in the Colombia section.

  Thanks a lot.

  Present on bionic (18.04)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1877233/+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


[Touch-packages] [Bug 1311056] Re: [SRU] apt-add-repository adds duplicate commented/disabled source lines

2020-05-11 Thread Julian Andres Klode
** Changed in: python-apt (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: python-apt (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: python-apt (Ubuntu Eoan)
   Status: New => In Progress

-- 
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/1311056

Title:
  [SRU] apt-add-repository adds duplicate commented/disabled source
  lines

Status in python-apt package in Ubuntu:
  Fix Released
Status in python-apt source package in Xenial:
  In Progress
Status in python-apt source package in Bionic:
  In Progress
Status in python-apt source package in Eoan:
  In Progress

Bug description:
  Impact
  ==

  Under most circumstances, the impact is minimal (a few extra redundant
  comment lines in apt sources. However, if users are automating source
  removal / addition on a machine (as in comment 11), there is the
  potential to wind up with an excessively large (and thus slow to
  parse) apt sources configuration.

  Test packages for the supported releases are available from the
  following PPA:

  https://launchpad.net/~waveform/+archive/ubuntu/python-apt

  Built from the source which can be found in the following branches:

  https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git
  /python-apt/+ref/sru-dupe-ppa-xenial

  https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git
  /python-apt/+ref/sru-dupe-ppa-bionic

  https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git
  /python-apt/+ref/sru-dupe-ppa-eoan

  Test Case
  =

  * sudo add-apt-repository -y ppa:deadsnakes/ppa
  * cat /etc/apt/sources.list.d/deadsnakes*.list
  * Note the presence of one uncommented "deb" line, and one commented 
"deb-src" line
  * sudo add-apt-repository -y ppa:deadsnakes/ppa
  * cat /etc/apt/sources.list.d/deadsnakes*.list
  * Note the uncommented "deb" line is still there but the commented "deb-src" 
line has now been duplicated
  * sudo add-apt-repository ppa:waveform/python-apt
  * sudo apt upgrade  # update python-apt to fixed version
  * sudo add-apt-repository -y ppa:deadsnakes/ppa
  * cat /etc/apt/sources.list.d/deadsnakes*.list
  * Note there has been no further duplication of the commented "deb-src" line

  Regression Potential
  

  Minimal; test cases have been added to cover the duplication case, and
  to cover the enabling of sources (which was not covered by existing
  tests, but was part of the code altered to fix the duplication case),
  and insertion of sources at a position (again, not covered by existing
  tests but modified as part of the fix). The test case has been used
  successfully on all targeted releases (xenial, bionic, and eoan).

  Original Description
  

  Trusty Tahr 14.04

  0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list
  deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  0 root@osprey:/etc/apt/sources.list.d#apt-add-repository -y 
ppa:aims/aims-desktop
  gpg: keyring `/tmp/tmp0ufdhnmv/secring.gpg' created
  gpg: keyring `/tmp/tmp0ufdhnmv/pubring.gpg' created
  gpg: requesting key BE796FF2 from hkp server keyserver.ubuntu.com
  gpg: /tmp/tmp0ufdhnmv/trustdb.gpg: trustdb created
  gpg: key BE796FF2: public key "Launchpad PPA for AIMS" imported
  gpg: Total number processed: 1
  gpg:   imported: 1  (RSA: 1)
  OK
  0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list deb 
http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  0 root@osprey:/etc/apt/sources.list.d#

  That deb-src line should have stayed commented out, and not been
  duplicated. (Commented deb lines should of course be uncommented, as
  already fixed per https://bugs.launchpad.net/ubuntu/+source/python-
  apt/+bug/1042916 .)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1311056/+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


[Touch-packages] [Bug 1829401] Re: gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support

2020-05-07 Thread Julian Andres Klode
Oh wow, there are multiple bugs, and I thought this bug was about the
actual crash:

pk-client-error-quark: could not do untrusted question as no klass
support (8)


but it is about the handling of the crash:

TypeError: could not convert value for property `transient_for' from
DialogCacheOutdated to GtkWindow

-- 
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/1829401

Title:
  gi.repository.GLib.GError: pk-client-error-quark: could not do
  untrusted question as no klass support

Status in packagekit package in Ubuntu:
  Triaged
Status in packagekit source package in Eoan:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
software-properties.  This problem was most recently seen with package version 
0.98.2, the problem page at 
https://errors.ubuntu.com/problem/300ff7bf9068dc50ace4c5db5c4a34ba0dfc926d 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

  [Back trace]
  Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py", 
line 86, in on_pktask_finish
  results = self._pktask.generic_finish(result)
  gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted 
question as no klass support (8)

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py", 
line 89, in on_pktask_finish
  Gtk.ButtonsType.CANCEL, _("Error while refreshing cache"))
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, 
in new_init
  return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 575, in 
__init__
  self._init(*args, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, 
in new_init
  return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 521, in 
__init__
  _window_init(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, 
in new_init
  return super_init_func(self, **new_kwargs)
  TypeError: could not convert value for property `transient_for' from 
DialogCacheOutdated to GtkWindow

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1829401/+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


[Touch-packages] [Bug 1872200] Re: apt does not accept globs and regexes in some cases

2020-05-05 Thread Julian Andres Klode
** Description changed:

+ [Impact]
+ Users can't use * wildcards anymore in focal, except by accident in apt list.
+ 
+ For apt list, we now start restricting wildcard syntax to the same
+ syntax install now accepts, and at the same time we remove the
+ restrictions on which patterns are accepted (which only accepted
+ patterns starting in ~ or ?), so !~napt now works, and does not
+ accidentally match as a wildcard.
+ 
+ 
+ [Test case]
+ 
+ Test that * wildcards work for both install and list, and test that a ?
+ wildcard does not.
+ 
+ We included autopkgtests for those:
+ 
+  BEGIN TESTS #
+ 
+ # * wildcards should still work
+ testsuccessequal "Listing...
+ automatic1/now 1.0 i386 [installed,local]
+ automatic2/now 1.0 i386 [installed,local]" apt list 'automatic*'
+ 
+ testfailureequal "Reading package lists...
+ Building dependency tree...
+ Reading state information...
+ Note, selecting 'automatic1' for glob 'automatic*'
+ Note, selecting 'automatic2' for glob 'automatic*'
+ automatic1 is already the newest version (1.0).
+ automatic1 set to manually installed.
+ automatic2 is already the newest version (1.0).
+ automatic2 set to manually installed.
+ You might want to run 'apt --fix-broken install' to correct these.
+ The following packages have unmet dependencies:
+  broken : Depends: does-not-exist but it is not installable
+ E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution)." apt install -s 'automatic*'
+ 
+ # other wildcards should fail
+ 
+ testfailureequal "Listing...
+ E: input:0-10: error: Expected pattern
+automatic?
+^^" apt list 'automatic?'
+ 
+ testfailureequal "Reading package lists...
+ Building dependency tree...
+ Reading state information...
+ E: Unable to locate package automatic?" apt install -s 'automatic?'
+ 
+ 
+  END TESTS #
+ 
+ Also it might be worth checking that apt list !~napt works. This used to
+ produce an empty list, as it was accidentally matched as a wildcard and
+ produced no result - now it produces every package whose name does not
+ contain "apt".
+ 
+ 
+ [Regression potential]
+ The changes only affect interactive users, as apt(8) is not stable for 
in-script use, hence they can fix up their command-line if it stops working for 
them (though, really, more should work now).
+ 
+ No scripts will be broken :)
+ 
+ [Squashed in changes]
+ The SRU also fixes potential build failures by correctly prefxing nullptr_t 
with the std:: namespace, and includes updated Dutch documentation.
+ 
+ [Original bug report]
  Observed with Ubuntu 20.04 Beta.
  
  apt remove 'mypackage*' does not remove all installed packages starting
  with “mypackage”.  Instead:
  
  $ sudo apt remove 'mypackage*'
  Reading package lists... Done
- Building dependency tree   
+ Building dependency tree
  Reading state information... Done
  E: Unable to locate package mypackage*
  
  However:
  
  $ sudo apt list --installed 'mypackage*'
  Listing... Done
  mypackage-data-v1/focal,focal,now 0.3.2-5build1 all [installed,automatic]
  mypackage1/focal,now 0.3.2-5build1 amd64 [installed]

** Also affects: apt (Ubuntu Groovy)
   Importance: Undecided
   Status: Fix Committed

** Also affects: apt (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: apt (Ubuntu Focal)
   Status: New => 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/1872200

Title:
  apt does not accept globs and regexes in some cases

Status in apt package in Ubuntu:
  Fix Committed
Status in apt source package in Focal:
  Triaged
Status in apt source package in Groovy:
  Fix Committed

Bug description:
  [Impact]
  Users can't use * wildcards anymore in focal, except by accident in apt list.

  For apt list, we now start restricting wildcard syntax to the same
  syntax install now accepts, and at the same time we remove the
  restrictions on which patterns are accepted (which only accepted
  patterns starting in ~ or ?), so !~napt now works, and does not
  accidentally match as a wildcard.

  
  [Test case]

  Test that * wildcards work for both install and list, and test that a
  ? wildcard does not.

  We included autopkgtests for those:

   BEGIN TESTS #

  # * wildcards should still work
  testsuccessequal "Listing...
  automatic1/now 1.0 i386 [installed,local]
  automatic2/now 1.0 i386 [installed,local]" apt list 'automatic*'

  testfailureequal "Reading package lists...
  Building dependency tree...
  Reading state information...
  Note, selecting 'automatic1' for glob 'automatic*'
  Note, selecting 'automatic2' for glob 'automatic*'
  automatic1 is already the newest version (1.0).
  automatic1 set to manually installed.
  automatic2 is already the newest version (1.0).
  automatic2 set to manually installed.
  You might want to run 'apt --fix-broken install' to correct these.
  The 

[Touch-packages] [Bug 1872200] Re: apt does not accept globs and regexes in some cases

2020-05-04 Thread Julian Andres Klode
Yes, wildcard matching went away, I just re-added wildcard matching for
"*" wildcards, as promised; and also changed apt list to reject
unsupported wildcards (any other special character, we do not support ?
or [] stuff).


@Jakub The "no pattern matching at all" I had to LOL a bit about. Because apt 
2/1.9 introduces patterns, see apt-patterns(8). For example,

apt remove ?name(mypackage)?installed

apt remove ?obsolete

apt list ?essential

There's quite a few of them, and it's much more powerful than just
matching on names.

** Changed in: apt (Ubuntu)
   Status: Confirmed => Fix Committed

-- 
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/1872200

Title:
  apt does not accept globs and regexes in some cases

Status in apt package in Ubuntu:
  Fix Committed

Bug description:
  Observed with Ubuntu 20.04 Beta.

  apt remove 'mypackage*' does not remove all installed packages
  starting with “mypackage”.  Instead:

  $ sudo apt remove 'mypackage*'
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  E: Unable to locate package mypackage*

  However:

  $ sudo apt list --installed 'mypackage*'
  Listing... Done
  mypackage-data-v1/focal,focal,now 0.3.2-5build1 all [installed,automatic]
  mypackage1/focal,now 0.3.2-5build1 amd64 [installed]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1872200/+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


[Touch-packages] [Bug 1876495] Re: bash-completion incorrectly shows source package names for APT

2020-05-02 Thread Julian Andres Klode
Though maybe it only needs work in apt, we'll see.

-- 
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/1876495

Title:
  bash-completion incorrectly shows source package names for APT

Status in apt package in Ubuntu:
  Triaged
Status in bash-completion package in Ubuntu:
  Triaged

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 20.04 LTS installed
  2. Open terminal, enter one of the commands below

  2a. apt install brisk
  2b. apt source brisk-menu
  2c. apt-get install brisk
  2d. apt-get source brisk-menu
  2e. apt-cache policy brisk 

  Expected results:
  * The bash-completion should not lead to package name as there are no binary 
packages named with starting part "brisk" (see 
https://packages.ubuntu.com/search?suite=all=names=brisk )

  Actual results:
  * all commands below get completed to the name of source package - in this 
example named "brisk-menu"
  (see 
https://packages.ubuntu.com/search?suite=all=all=any=brisk=sourcenames).
 This is absolutely unexpected, as user can not really install this package in 
binary form.

  ProblemType: Bug
  DistroRelease: Ubuntu Kylin 20.04
  Package: bash-completion 1:2.10-1ubuntu1 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 5.4.0-28.32-lowlatency 5.4.30
  Uname: Linux 5.4.0-28-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Sat May  2 20:35:48 2020
  Dependencies:
   
  InstallationDate: Installed on 2020-04-22 (9 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200422)
  PackageArchitecture: all
  SourcePackage: bash-completion
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1876495/+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


[Touch-packages] [Bug 1876495] Re: bash-completion incorrectly shows source package names for APT

2020-05-02 Thread Julian Andres Klode
source is certainly a bad example, as it does take source names. But
yes, this is a minor inconvenience sometimes.

This needs quite a bit of work to fix, in a coordinated fashion, across
the two packages, and I'm not sure it's worth it. Probably needs some
investigation whether we already return some other invalid names.

** Changed in: bash-completion (Ubuntu)
   Importance: Undecided => Medium

** Changed in: bash-completion (Ubuntu)
   Importance: Medium => Low

** Changed in: apt (Ubuntu)
   Importance: Undecided => Low

** Changed in: bash-completion (Ubuntu)
   Status: New => Triaged

** Changed in: apt (Ubuntu)
   Status: New => 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/1876495

Title:
  bash-completion incorrectly shows source package names for APT

Status in apt package in Ubuntu:
  Triaged
Status in bash-completion package in Ubuntu:
  Triaged

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 20.04 LTS installed
  2. Open terminal, enter one of the commands below

  2a. apt install brisk
  2b. apt source brisk-menu
  2c. apt-get install brisk
  2d. apt-get source brisk-menu
  2e. apt-cache policy brisk 

  Expected results:
  * The bash-completion should not lead to package name as there are no binary 
packages named with starting part "brisk" (see 
https://packages.ubuntu.com/search?suite=all=names=brisk )

  Actual results:
  * all commands below get completed to the name of source package - in this 
example named "brisk-menu"
  (see 
https://packages.ubuntu.com/search?suite=all=all=any=brisk=sourcenames).
 This is absolutely unexpected, as user can not really install this package in 
binary form.

  ProblemType: Bug
  DistroRelease: Ubuntu Kylin 20.04
  Package: bash-completion 1:2.10-1ubuntu1 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 5.4.0-28.32-lowlatency 5.4.30
  Uname: Linux 5.4.0-28-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Sat May  2 20:35:48 2020
  Dependencies:
   
  InstallationDate: Installed on 2020-04-22 (9 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200422)
  PackageArchitecture: all
  SourcePackage: bash-completion
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1876495/+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


[Touch-packages] [Bug 1875190] Re: Apt update takes around a full minute to read state information when I run it for the first time since boot even though there are no updates available.

2020-04-27 Thread Julian Andres Klode
No, that's the apt help output.

-- 
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/1875190

Title:
  Apt update takes around a full minute to read state information when I
  run it for the first time since boot even though there are no updates
  available.

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  When I ran "sudo apt update && sudo apt dist-upgrade", apt hit all the
  repositories. However, when it was reading state information, that
  process took a full minute even though there were no new updates.

  This is too slow, even though the subsequent time I ran the command,
  it was much faster. No, this was not the first time I ever ran the
  command on the current install, as I ran it the day before without
  reinstalling Ubuntu, on Ubuntu 20.04, and the process took less than
  15 seconds.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apt 2.0.2
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 26 11:42:21 2020
  InstallationDate: Installed on 2020-04-25 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-25 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: apt 2.0.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1875190/+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


[Touch-packages] [Bug 1709699] Re: gpk-update-viewer fails with "Spawn of helper 'usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py' failed ... (No such file or directory)"

2020-04-26 Thread Julian Andres Klode
Marking this as fix released in PackageKit then, seeing that we ship
1.1.13.

Given that we never used that updating stuff, I don't think it is worth
fixing that in old releases.


** Changed in: packagekit (Ubuntu)
   Status: New => Fix Released

-- 
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/1709699

Title:
  gpk-update-viewer fails with "Spawn of helper
  'usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py' failed ...
  (No such file or directory)"

Status in gnome-packagekit package in Ubuntu:
  Confirmed
Status in packagekit package in Ubuntu:
  Fix Released

Bug description:
  gpk-update-viewer fails with
  Spawn of helper '/usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py' 
failed: failed to spawn 
/usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py: Failed to execute 
child process “/usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py” (No 
such file or directory)

  This was detected by Robert Reinsch on a Ubuntu 17.04 system and was
  verified by me on a 17.10 daily build from 2017-08-09

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-packagekit 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Aug  9 21:00:48 2017
  ExecutablePath: /usr/bin/gpk-update-viewer
  InstallationDate: Installed on 2017-08-09 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170807)
  SourcePackage: gnome-packagekit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-packagekit/+bug/1709699/+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


[Touch-packages] [Bug 1875190] Re: Apt update takes around a full minute to read state information when I run it for the first time since boot even though there are no updates available.

2020-04-26 Thread Julian Andres Klode
I'm not aware of any performance issues in those parts of apt, and spent
a considerable time optimizing it.

You probably want to strace or gdb apt when it's hanging and figure out
where the issue is, because there's nothing that can be done here by
anyone else so far.

** 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/1875190

Title:
  Apt update takes around a full minute to read state information when I
  run it for the first time since boot even though there are no updates
  available.

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  When I ran "sudo apt update && sudo apt dist-upgrade", apt hit all the
  repositories. However, when it was reading state information, that
  process took a full minute even though there were no new updates.

  This is too slow, even though the subsequent time I ran the command,
  it was much faster. No, this was not the first time I ever ran the
  command on the current install, as I ran it the day before without
  reinstalling Ubuntu, on Ubuntu 20.04, and the process took less than
  15 seconds.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apt 2.0.2
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 26 11:42:21 2020
  InstallationDate: Installed on 2020-04-25 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-25 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: apt 2.0.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1875190/+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


[Touch-packages] [Bug 1874880] Re: error running apt-add-repository

2020-04-25 Thread Julian Andres Klode
Hang on, the new base-files is not even in the release pocket yet. Are
you running the development series (groovy) with proposed enabled?
That's not wise.

-- 
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/1874880

Title:
  error running apt-add-repository

Status in python-apt package in Ubuntu:
  New

Bug description:
  today I accepted apt upgrades of some ubuntu repositories to Groove, after 
that I tried to add a new repo and got this messages:
   
  root@etm:/etc/apt/sources.list.d# apt-add-repository ppa:linuxuprising/apps
  Traceback (most recent call last):
File "/usr/bin/apt-add-repository", line 107, in 
  sp = SoftwareProperties(options=options)
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
118, in __init__
  self.reload_sourceslist()
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
613, in reload_sourceslist
  self.distro.get_sources(self.sourceslist)
File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 91, in 
get_sources
  raise NoDistroTemplateException(
  aptsources.distro.NoDistroTemplateException: Error: could not find a 
distribution template for Ubuntu/groovy

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: apt 2.0.2
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 15:18:26 2020
  InstallationDate: Installed on 2020-01-28 (87 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1874880/+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


[Touch-packages] [Bug 1874880] Re: error running apt-add-repository

2020-04-25 Thread Julian Andres Klode
Well yes, that's normal. We are still opening the release.

** Package changed: apt (Ubuntu) => python-apt (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/1874880

Title:
  error running apt-add-repository

Status in python-apt package in Ubuntu:
  New

Bug description:
  today I accepted apt upgrades of some ubuntu repositories to Groove, after 
that I tried to add a new repo and got this messages:
   
  root@etm:/etc/apt/sources.list.d# apt-add-repository ppa:linuxuprising/apps
  Traceback (most recent call last):
File "/usr/bin/apt-add-repository", line 107, in 
  sp = SoftwareProperties(options=options)
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
118, in __init__
  self.reload_sourceslist()
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
613, in reload_sourceslist
  self.distro.get_sources(self.sourceslist)
File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 91, in 
get_sources
  raise NoDistroTemplateException(
  aptsources.distro.NoDistroTemplateException: Error: could not find a 
distribution template for Ubuntu/groovy

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: apt 2.0.2
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 15:18:26 2020
  InstallationDate: Installed on 2020-01-28 (87 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1874880/+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


[Touch-packages] [Bug 1750625] Re: update misinterprets 304 response on Packages.gz

2020-04-20 Thread Julian Andres Klode
That release file is sort of invalid, as we also need the uncompressed
Packages file hashed, because we check hashes after decompression too.

So usually you generate Packages, compress it (having both around), then
create Release file, and then delete the uncompressed Packages file if
you don't need it anymore.

I guess this should work more automatically, apt-ftparchive could
transparently decompress compressed files to add them to Release file.

-- 
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/1750625

Title:
  update misinterprets 304 response on Packages.gz

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  ii  apt  1.2.24   
   amd64commandline package manager
  ii  apt-transport-https  1.2.24   
   amd64https download transport for APT
  ii  apt-utils1.2.24   
   amd64package management related utility programs
  ii  libapt-inst2.0:amd64 1.2.24   
   amd64deb package format runtime library
  ii  libapt-pkg5.0:amd64  1.2.24   
   amd64package management runtime library

  Expected behaviour:

  If apt-get gets a 304 Not Modified when requesting Packages.gz, it
  should ignore the package list (i.e., there's no update).

  Observed behaviour:

  Added a local repository to
  /etc/apt/sources.list.d/instafreight_php.list:

  > deb [arch=amd64 trusted=yes] http://ubuntu/instafreight xenial php

  The first time running apt-get update succeeds; in addition,
  apache.log shows:

  > 10.0.4.72 - - [20/Feb/2018:12:01:39 -0500] "GET
  /instafreight/dists/xenial/php/binary-amd64/Packages.gz HTTP/1.1" 200
  745 "-" "Debian APT-HTTP/1.3 (1.2.24)"

  I am able to install packages from that repo without error.

  Running apt-get a 2nd time succeeds. apache.log doesn't show a request
  for Packages.gz

  Running apt-get a 3rd time, apache.log shows:

  > 10.0.4.72 - - [20/Feb/2018:12:04:45 -0500] "GET
  /instafreight/dists/xenial/php/binary-amd64/Packages.gz HTTP/1.1" 304
  124 "-" "Debian APT-HTTP/1.3 (1.2.24)"

  However, on the console where I ran apt-get, the corresponding output
  is:

  > Err:15 http://ubuntu/instafreight xenial/php amd64 Packages
  >   404  Not Found
  > ...
  > E: Failed to fetch 
http://ubuntu/instafreight/dists/xenial/php/binary-amd64/Packages.gz  404  Not 
Found
  > E: Some index files failed to download. They have been ignored, or old ones 
used instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1750625/+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


[Touch-packages] [Bug 1750625] Re: update misinterprets 304 response on Packages.gz

2020-04-20 Thread Julian Andres Klode
I guess that's good to know that it does not really work without a
release file now anyway, it is a good argument for removing support for
such repos completely. I made a plan a year or two ago, but have not
acted on it yet :/

Please add a Release file. It gives you download progress, hash checks,
and avoids all kinds of tries for files that don't exist. Then sign it
so apt can verify it fetched it correctly, which is beneficial even in a
trusted environment.

-- 
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/1750625

Title:
  update misinterprets 304 response on Packages.gz

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  ii  apt  1.2.24   
   amd64commandline package manager
  ii  apt-transport-https  1.2.24   
   amd64https download transport for APT
  ii  apt-utils1.2.24   
   amd64package management related utility programs
  ii  libapt-inst2.0:amd64 1.2.24   
   amd64deb package format runtime library
  ii  libapt-pkg5.0:amd64  1.2.24   
   amd64package management runtime library

  Expected behaviour:

  If apt-get gets a 304 Not Modified when requesting Packages.gz, it
  should ignore the package list (i.e., there's no update).

  Observed behaviour:

  Added a local repository to
  /etc/apt/sources.list.d/instafreight_php.list:

  > deb [arch=amd64 trusted=yes] http://ubuntu/instafreight xenial php

  The first time running apt-get update succeeds; in addition,
  apache.log shows:

  > 10.0.4.72 - - [20/Feb/2018:12:01:39 -0500] "GET
  /instafreight/dists/xenial/php/binary-amd64/Packages.gz HTTP/1.1" 200
  745 "-" "Debian APT-HTTP/1.3 (1.2.24)"

  I am able to install packages from that repo without error.

  Running apt-get a 2nd time succeeds. apache.log doesn't show a request
  for Packages.gz

  Running apt-get a 3rd time, apache.log shows:

  > 10.0.4.72 - - [20/Feb/2018:12:04:45 -0500] "GET
  /instafreight/dists/xenial/php/binary-amd64/Packages.gz HTTP/1.1" 304
  124 "-" "Debian APT-HTTP/1.3 (1.2.24)"

  However, on the console where I ran apt-get, the corresponding output
  is:

  > Err:15 http://ubuntu/instafreight xenial/php amd64 Packages
  >   404  Not Found
  > ...
  > E: Failed to fetch 
http://ubuntu/instafreight/dists/xenial/php/binary-amd64/Packages.gz  404  Not 
Found
  > E: Some index files failed to download. They have been ignored, or old ones 
used instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1750625/+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


[Touch-packages] [Bug 1750625] Re: update misinterprets 304 response on Packages.gz

2020-04-20 Thread Julian Andres Klode
I think the answer is simple: We should stop sending If-Modified-Since.
There's no advantage to sending that compared to getting back the same
release file, and it's a bad design.

-- 
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/1750625

Title:
  update misinterprets 304 response on Packages.gz

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  ii  apt  1.2.24   
   amd64commandline package manager
  ii  apt-transport-https  1.2.24   
   amd64https download transport for APT
  ii  apt-utils1.2.24   
   amd64package management related utility programs
  ii  libapt-inst2.0:amd64 1.2.24   
   amd64deb package format runtime library
  ii  libapt-pkg5.0:amd64  1.2.24   
   amd64package management runtime library

  Expected behaviour:

  If apt-get gets a 304 Not Modified when requesting Packages.gz, it
  should ignore the package list (i.e., there's no update).

  Observed behaviour:

  Added a local repository to
  /etc/apt/sources.list.d/instafreight_php.list:

  > deb [arch=amd64 trusted=yes] http://ubuntu/instafreight xenial php

  The first time running apt-get update succeeds; in addition,
  apache.log shows:

  > 10.0.4.72 - - [20/Feb/2018:12:01:39 -0500] "GET
  /instafreight/dists/xenial/php/binary-amd64/Packages.gz HTTP/1.1" 200
  745 "-" "Debian APT-HTTP/1.3 (1.2.24)"

  I am able to install packages from that repo without error.

  Running apt-get a 2nd time succeeds. apache.log doesn't show a request
  for Packages.gz

  Running apt-get a 3rd time, apache.log shows:

  > 10.0.4.72 - - [20/Feb/2018:12:04:45 -0500] "GET
  /instafreight/dists/xenial/php/binary-amd64/Packages.gz HTTP/1.1" 304
  124 "-" "Debian APT-HTTP/1.3 (1.2.24)"

  However, on the console where I ran apt-get, the corresponding output
  is:

  > Err:15 http://ubuntu/instafreight xenial/php amd64 Packages
  >   404  Not Found
  > ...
  > E: Failed to fetch 
http://ubuntu/instafreight/dists/xenial/php/binary-amd64/Packages.gz  404  Not 
Found
  > E: Some index files failed to download. They have been ignored, or old ones 
used instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1750625/+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


[Touch-packages] [Bug 1872902] Re: Upgrade to Focal now removes chrony

2020-04-16 Thread Julian Andres Klode
Marking the apt task as invalid  as per xnox's analysis

** 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/1872902

Title:
  Upgrade to Focal now removes chrony

Status in apt package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Invalid
Status in ntp package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed

Bug description:
  Due to changes in systemd for bug 1849156 this issue now happens.

  On an upgrade for people that had chrony installed on a do-release upgrade it 
now will:
  Calculating the changes
MarkInstall systemd-timesyncd:amd64 < none -> 245.4-4ubuntu1 @un uN Ib > 
FU=1
 Removing: chrony
  MarkDelete chrony:amd64 < 3.2-4ubuntu4.2 -> 3.5-6ubuntu3 @ii umU Ib > FU=0

  That isn't what users want, those who had chrony installed would want
  to get chrony upgraded and systemd-timesyncd (which now is a separate
  pacakge) not installed.

  I'd ask you to revise the dependencies that got changes in systemd
  245.4-2ubuntu1 so that on an upgrade from e.g. Bionic chrony stays
  installed as that was an opt-in chances are quite high people would
  want to keep it that way.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1872902/+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


[Touch-packages] [Bug 1873274] Re: "Updating snaps" is not translated on update-manager

2020-04-16 Thread Julian Andres Klode
** Package changed: update-manager (Ubuntu) => language-pack-fr (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to language-pack-fr in
Ubuntu.
https://bugs.launchpad.net/bugs/1873274

Title:
  "Updating snaps" is not translated on update-manager

Status in Ubuntu Translations:
  New
Status in language-pack-fr package in Ubuntu:
  New

Bug description:
  On Focal, the string "Updating snaps" is not translated in french
  whereas the string is translated on
  https://translations.launchpad.net/ubuntu/focal/+source/update-
  manager/+pots/update-manager/fr/5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1873274/+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


[Touch-packages] [Bug 1872557] Re: apt-get error: cnf-update-db - KeyError: 'suite' (focal)

2020-04-15 Thread Julian Andres Klode
** No longer affects: apt (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/1872557

Title:
  apt-get error: cnf-update-db - KeyError: 'suite' (focal)

Status in command-not-found:
  New

Bug description:
  "apt-get update" fails to run when command-not-found is installed on
  Ubuntu 20.04.

  To reproduce with Docker:
  docker pull ubuntu:20.04# Pull latest Ubuntu 20.04 docker image
  docker run -it ubuntu:20.04 # Start an Ubuntu 20.04 docker container

  # Within the container run:
  apt-get update
  apt-get -yy dist-upgrade
  apt-get -yy install command-not-found
  exec bash  # Reload bash to load command-not-found
  apt-get update # Update command-not-found database

  Traceback (most recent call last):
    File "/usr/lib/cnf-update-db", line 26, in 
  col.create(db)
    File "/usr/lib/python3/dist-packages/CommandNotFound/db/creator.py", line 
93, in create
  self._fill_commands(con)
    File "/usr/lib/python3/dist-packages/CommandNotFound/db/creator.py", line 
127, in _fill_commands
  self._parse_single_commands_file(con, fp)
    File "/usr/lib/python3/dist-packages/CommandNotFound/db/creator.py", line 
165, in _parse_single_commands_file
  suite=tagf.section["suite"]
  KeyError: 'suite'
  Reading package lists... Done
  E: Problem executing scripts APT::Update::Post-Invoke-Success 'if 
/usr/bin/test -w /var/lib/command-not-found/ -a -e /usr/lib/cnf-update-db; then 
/usr/lib/cnf-update-db > /dev/null; fi'
  E: Sub-process returned an error code

To manage notifications about this bug go to:
https://bugs.launchpad.net/command-not-found/+bug/1872557/+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


[Touch-packages] [Bug 1872200] Re: apt does not accept globs and regexes in some cases

2020-04-11 Thread Julian Andres Klode
glob actually needs to come back to some extend (* only), but otherwise
yes, read the NEWS.

-- 
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/1872200

Title:
  apt does not accept globs and regexes in some cases

Status in apt package in Ubuntu:
  New

Bug description:
  Observed with Ubuntu 20.04 Beta.

  apt remove 'mypackage*' does not remove all installed packages
  starting with “mypackage”.  Instead:

  $ sudo apt remove 'mypackage*'
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  E: Unable to locate package mypackage*

  However:

  $ sudo apt list --installed 'mypackage*'
  Listing... Done
  mypackage-data-v1/focal,focal,now 0.3.2-5build1 all [installed,automatic]
  mypackage1/focal,now 0.3.2-5build1 amd64 [installed]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1872200/+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


[Touch-packages] [Bug 1872200] Re: apt does not accept globs and regexes in some cases

2020-04-11 Thread Julian Andres Klode
Hmm seems I missed disabling that in apt list, good catch.

-- 
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/1872200

Title:
  apt does not accept globs and regexes in some cases

Status in apt package in Ubuntu:
  New

Bug description:
  Observed with Ubuntu 20.04 Beta.

  apt remove 'mypackage*' does not remove all installed packages
  starting with “mypackage”.  Instead:

  $ sudo apt remove 'mypackage*'
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  E: Unable to locate package mypackage*

  However:

  $ sudo apt list --installed 'mypackage*'
  Listing... Done
  mypackage-data-v1/focal,focal,now 0.3.2-5build1 all [installed,automatic]
  mypackage1/focal,now 0.3.2-5build1 amd64 [installed]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1872200/+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


[Touch-packages] [Bug 1872145] Re: explicit key offered after all agent keys, auth can fail before explicit key used

2020-04-11 Thread Julian Andres Klode
It also prefers configured key files over smart cards, causing similar
issues. Luckily there is a work around for that by adding /dev/null as
an identify file in the config, but that's super ugly.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1872145

Title:
  explicit key offered after all agent keys, auth can fail before
  explicit key used

Status in openssh package in Ubuntu:
  New

Bug description:
  A user creates an ssh key and specifies it on the cmdline with 'ssh -i
  new_key user@host'.  The connection fails with the message "Too many
  authentication failures" displayed to the user.

  This would lead the user to believe that they failed to put the public
  portion of the new key on the destination and it will probably be hard
  for the average user to debug this.

  The root of this issue is that the user has a number of keys in
  ~/.ssh/ registered with their ssh agent.  The ssh command is offering
  each of these keys from the agent to the remote system before trying
  the explicit key from the command line.  There are enough agent keys
  to reach the failure limit (usually 5 keys) with the remote before
  they get to the explicit key.

  The solution today for the user is to head down into the ssh_config
  man page to find '-o IdentitiesOnly=yes' to skip the agent keys and
  only use the specified key.  But they're unlikely to do this because
  '-i' in the ssh man page doesn't suggest this and they'd only look for
  this if they actually understood the root cause of the problem, which
  is a bit cruel.

  We should consider changing the order of the keys offered to the
  remote to use explicit keys first followed by agent keys.  It would
  seem to me that this would honor the users intent of explicitly
  specifying a key to use.

  The current order makes this difficult for anyone fielding a user's
  authentication failure report as they must double check that ssh
  managed to actually try the key the user specified before it raised an
  error message about authentication failures.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1872145/+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


[Touch-packages] [Bug 1825000] Re: Add ability for mirrors to distinguish interactive and non-interactive apt runs

2020-04-09 Thread Julian Andres Klode
** Changed in: apt (Ubuntu)
   Status: In Progress => Fix Committed

-- 
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/1825000

Title:
  Add ability for mirrors to distinguish interactive and non-interactive
  apt runs

Status in apt package in Ubuntu:
  Fix Committed
Status in apt source package in Eoan:
  Triaged

Bug description:
  As part of a larger scale plan to manage traffic to the main archive
  servers it would be useful if apt could provide a facility for us to
  identify interactive vs. non-interactive traffic on the server side,
  ideally via a header of some kind.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1825000/+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


[Touch-packages] [Bug 1871679] Re: apt install libavcodec-extra asks for cdrom

2020-04-08 Thread Julian Andres Klode
Then either supply the medium you installed from or remove the entry.
What did you install from?

** Changed in: apt (Ubuntu)
   Status: New => Incomplete

** Package changed: apt (Ubuntu) => 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/1871679

Title:
  apt install libavcodec-extra asks for cdrom

Status in Ubuntu:
  Incomplete

Bug description:
  Netflix does not work on Firefox on 20.04, even after enabling DRM. A
  guide somewhere tells me I need libavcodec-extra, this reports:

  ```
  $ sudo apt install libavcodec-extra
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following additional packages will be installed:
i965-va-driver intel-media-va-driver libaom0 libaribb24-0 
libavcodec-extra58 libavutil56 libcodec2-0.9 libgsm1 libigdgmm11 
libopencore-amrnb0 libopencore-amrwb0 libshine3 libsnappy1v5 libswresample3
libva-drm2 libva-x11-2 libva2 libvdpau1 libvo-amrwbenc0 libx264-155 
libx265-179 libxvidcore4 libzvbi-common libzvbi0 mesa-va-drivers 
mesa-vdpau-drivers ocl-icd-libopencl1 va-driver-all vdpau-driver-all
  Suggested packages:
i965-va-driver-shaders opencl-icd libvdpau-va-gl1 nvidia-vdpau-driver 
nvidia-legacy-340xx-vdpau-driver nvidia-legacy-304xx-vdpau-driver
  The following NEW packages will be installed:
i965-va-driver intel-media-va-driver libaom0 libaribb24-0 libavcodec-extra 
libavcodec-extra58 libavutil56 libcodec2-0.9 libgsm1 libigdgmm11 
libopencore-amrnb0 libopencore-amrwb0 libshine3 libsnappy1v5
libswresample3 libva-drm2 libva-x11-2 libva2 libvdpau1 libvo-amrwbenc0 
libx264-155 libx265-179 libxvidcore4 libzvbi-common libzvbi0 mesa-va-drivers 
mesa-vdpau-drivers ocl-icd-libopencl1 va-driver-all
vdpau-driver-all
  0 upgraded, 30 newly installed, 0 to remove and 0 not upgraded.
  Need to get 0 B/24,4 MB of archives.
  After this operation, 136 MB of additional disk space will be used.
  Do you want to continue? [Y/n] 
  Media change: please insert the disc labeled
   'Ubuntu 20.04 LTS _Focal Fossa_ - Beta amd64 (20200402)'
  in the drive '/cdrom/' and press [Enter]
  ```

  Pressing enter keeps repeating the last text.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1871679/+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


[Touch-packages] [Bug 1871149] Re: False apt_pkg.CacheMismatchError

2020-04-08 Thread Julian Andres Klode
Needs a reproducer

** Changed in: python-apt (Ubuntu)
   Status: New => Incomplete

-- 
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/1871149

Title:
  False apt_pkg.CacheMismatchError

Status in python-apt package in Ubuntu:
  Incomplete

Bug description:
  Python-apt throws CacheMismatchError which is almost certainly false:

  Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 2512, in 
  sys.exit(main(options))
File "/usr/bin/unattended-upgrade", line 1986, in main
  res = run(options, rootdir, mem_log, logfile_dpkg,
File "/usr/bin/unattended-upgrade", line 2398, in run
  new_pending_autoremovals = get_auto_removable(cache)
File "/usr/bin/unattended-upgrade", line 1789, in get_auto_removable
  return {pkg.name for pkg in cache
File "/usr/bin/unattended-upgrade", line 1790, in 
  if pkg.is_auto_removable}
File "/usr/lib/python3/dist-packages/apt/package.py", line 1269, in 
is_auto_removable
  self._pcache._depcache.is_garbage(self._pkg))
  apt_pkg.CacheMismatchError: Object of different cache passed as argument to 
apt_pkg.DepCache method

  The relevant code in u-u:

  def get_auto_removable(cache):


  # type: (apt.Cache) -> AbstractSet[str]   


  return {pkg.name for pkg in cache 


  if pkg.is_auto_removable}

  ---

  The Ubuntu Error Tracker has been receiving reports about a problem 
  regarding unattended-upgrades.  This problem was most recently seen with 
package version 2.1, the problem page at 
https://errors.ubuntu.com/problem/ff08f6aa104f8e3233da3081835ecc2e9f0452f5 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1871149/+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


[Touch-packages] [Bug 1871145] Re: apt.Cache.clear() -> apt.Cache._depcache.init() raises Error

2020-04-08 Thread Julian Andres Klode
If clear() fails, you're a bit lost, but I'm not sure what you'd want to
do here, the system is completely broken at that point.

** Changed in: python-apt (Ubuntu)
   Status: New => Opinion

** Changed in: unattended-upgrades (Ubuntu)
   Status: Opinion => New

-- 
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/1871145

Title:
  apt.Cache.clear() -> apt.Cache._depcache.init() raises Error

Status in python-apt package in Ubuntu:
  Opinion
Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  Unattended-upgrades 2.1 triggers the following crash in python-apt:

File "/usr/bin/unattended-upgrade", line 1706, in try_to_upgrade
  cache.mark_upgrade_adjusted(pkg, from_user=not pkg.is_auto_installed)
File "/usr/bin/unattended-upgrade", line 438, in mark_upgrade_adjusted
  self.call_adjusted(apt.package.Package.mark_upgrade, pkg, **kwargs)
File "/usr/bin/unattended-upgrade", line 397, in call_adjusted
  self.clear()
File "/usr/lib/python3/dist-packages/apt/cache.py", line 700, in clear
  self._depcache.init()
  apt_pkg.Error: E:The package intellij-idea-ultimate needs to be reinstalled, 
but I can't find an archive for it.

  I think .clear() should not raise an error, but if it should u-u can
  catch that.

  ---

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
2.1, the problem page at 
https://errors.ubuntu.com/problem/798f1ab5a4a2784a0fadd6034a875901345682f9 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1871145/+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


[Touch-packages] [Bug 1871540] Re: Include IPs in apt-get output

2020-04-08 Thread Julian Andres Klode
Neither of those is available when the message is logged, the message is
logged _before_ the item is being fetched, and multiple items may be in
progress at the same time, you can't go back and edit the previous line.

So you could display double the amount of entries, but that seems very
distracting. I think you could have

Con: Connected to foo (...)

where  is the first package for which we need to (re-, in case
of host closing connection)connect to a host.

Speed measurements I'm not sure. We only record total speed now. It
might make sense to record per-host speed. Then you could display a
message per host every $N seconds (N=30?) showing the current speed
[well, total average, really].

Note that we just had an ABI/API break, and not intend to break it again
for the next 2-4 years, which might prevent this from happening, or at
least make it harder.

-- 
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/1871540

Title:
  Include IPs in apt-get output

Status in apt package in Ubuntu:
  New

Bug description:
  Hi,

  When running apt-get update/dist-upgrade, output looks like this:

  | Hit:6 http://archive.ubuntu.com/ubuntu focal-updates InRelease
  | Get:7 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages [972 kB]
  | Get:8 http://archive.ubuntu.com/ubuntu focal/main amd64 c-n-f Metadata 
[29.1 kB]
  | ...
  | Need to get 101 MB of archives.
  | After this operation, 10.5 MB of additional disk space will be used.
  | Do you want to continue? [Y/n] y
  | Get:1 http://archive.ubuntu.com/ubuntu focal/main amd64 dpkg amd64 
1.19.7ubuntu3 [1128 kB]
  | Get:2 http://archive.ubuntu.com/ubuntu focal/main amd64 login amd64 
1:4.8.1-1ubuntu4 [221 kB]
  | Get:3 http://archive.ubuntu.com/ubuntu focal/main amd64 libc6-dbg amd64 
2.31-0ubuntu7 [5673 kB]

  With various online CI/CD services such as GitHub Actions, it looks
  like this:

  | Get:14 http://azure.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages [833 kB]
  | Get:16 http://azure.archive.ubuntu.com/ubuntu bionic-updates/main 
Translation-en [292 kB]
  | Get:17 http://azure.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages [1044 kB]
  | ...
  | Get:31 http://azure.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
cmake amd64 3.10.2-1ubuntu2.18.04.1 [3152 kB]
  | Get:32 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu bionic/main 
amd64 gdb amd64 8.2-0ubuntu1~18.04 [3024 kB]
  | Get:33 http://azure.archive.ubuntu.com/ubuntu bionic/universe amd64 epstool 
amd64 3.08+repack-7 [108 kB]

  archive.u.c resolves to multiple IPs. azure.archive.u.c resolves to a
  load balancer (Azure's Traffic Manager). It would be nice if we also
  had the IPs of the servers/hosts in the output and would really help
  us in determining which servers or regions users may be experiencing
  issues with.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1871540/+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


[Touch-packages] [Bug 1868988] Re: apt assert failure: malloc(): mismatching next->prev_size (unsorted)

2020-04-08 Thread Julian Andres Klode
There is a memory corruption somewhere, but it's not evident from the
data where, so this needs someone to reproduce the issue in valgrind.

** 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/1868988

Title:
  apt assert failure: malloc(): mismatching next->prev_size (unsorted)

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  libwxbase3.0-0v5 libwxgtk3.0-gtk3-0v5

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: apt 2.0.0
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  AssertionMessage: malloc(): mismatching next->prev_size (unsorted)
  Date: Wed Mar 25 14:19:48 2020
  ExecutablePath: /usr/bin/apt
  InstallationDate: Installed on 2020-03-17 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
  ProcCmdline: apt upgrade
  Signal: 6
  SourcePackage: apt
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f5e92ba0285 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
   malloc_printerr (str=str@entry=0x7f5e92ba2aa0 "malloc(): mismatching 
next->prev_size (unsorted)") at malloc.c:5347
   _int_malloc (av=av@entry=0x7f5e92bd1b80 , bytes=bytes@entry=128) 
at malloc.c:3741
   __GI___libc_malloc (bytes=128) at malloc.c:3058
   operator new(unsigned long) () from /lib/x86_64-linux-gnu/libstdc++.so.6
  Title: apt assert failure: malloc(): mismatching next->prev_size (unsorted)
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1868988/+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


[Touch-packages] [Bug 1871540] Re: Include IPs in apt-get output

2020-04-08 Thread Julian Andres Klode
FWIW, these are all status messages. They are not persistently logged,
but are in the [...] per item things in the last line of an interactive
session.

I guess we could display the "Connected to %s" messages somehow, but I
don't want to display the "Connecting to ..." messages, as there might
be a ton of them and that gets really distracting (worst case it's more
than the number of IP addresses per address, it tries an additional IP
address every 250ms).

So, that at least means that status messages would get priorities, and
we'd log the higher priority ones.

methods/http.cc
317:   Owner->Status(_("Connecting to %s (%s)"), "HTTP proxy", 
URI::SiteOnly(Proxy).c_str());

methods/rsh.cc
457:   Status(_("Connecting to %s"), Get.Host.c_str());

methods/aptmethod.h
387:  PrintStatus("104 Warning", Format, args);

methods/basehttp.cc
53:   Owner->Status(_("Waiting for headers"));

methods/connect.cc
150:  Owner->Status(_("Connected to %s (%s)"), Host.c_str(), Name);
167:   Owner->Status(_("Connecting to %s (%s)"),Host.c_str(),Name);
364:  Owner->Status(_("Connecting to %s"),Host.c_str());
576:   Owner->Status(_("Connecting to %s (%s)"), "SOCKS5h proxy", 
ProxyInfo.c_str());

methods/ftp.cc
174:   Owner->Status(_("Logging in"));
1071:   Status(_("Query"));

-- 
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/1871540

Title:
  Include IPs in apt-get output

Status in apt package in Ubuntu:
  New

Bug description:
  Hi,

  When running apt-get update/dist-upgrade, output looks like this:

  | Hit:6 http://archive.ubuntu.com/ubuntu focal-updates InRelease
  | Get:7 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages [972 kB]
  | Get:8 http://archive.ubuntu.com/ubuntu focal/main amd64 c-n-f Metadata 
[29.1 kB]
  | ...
  | Need to get 101 MB of archives.
  | After this operation, 10.5 MB of additional disk space will be used.
  | Do you want to continue? [Y/n] y
  | Get:1 http://archive.ubuntu.com/ubuntu focal/main amd64 dpkg amd64 
1.19.7ubuntu3 [1128 kB]
  | Get:2 http://archive.ubuntu.com/ubuntu focal/main amd64 login amd64 
1:4.8.1-1ubuntu4 [221 kB]
  | Get:3 http://archive.ubuntu.com/ubuntu focal/main amd64 libc6-dbg amd64 
2.31-0ubuntu7 [5673 kB]

  With various online CI/CD services such as GitHub Actions, it looks
  like this:

  | Get:14 http://azure.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages [833 kB]
  | Get:16 http://azure.archive.ubuntu.com/ubuntu bionic-updates/main 
Translation-en [292 kB]
  | Get:17 http://azure.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages [1044 kB]
  | ...
  | Get:31 http://azure.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
cmake amd64 3.10.2-1ubuntu2.18.04.1 [3152 kB]
  | Get:32 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu bionic/main 
amd64 gdb amd64 8.2-0ubuntu1~18.04 [3024 kB]
  | Get:33 http://azure.archive.ubuntu.com/ubuntu bionic/universe amd64 epstool 
amd64 3.08+repack-7 [108 kB]

  archive.u.c resolves to multiple IPs. azure.archive.u.c resolves to a
  load balancer (Azure's Traffic Manager). It would be nice if we also
  had the IPs of the servers/hosts in the output and would really help
  us in determining which servers or regions users may be experiencing
  issues with.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1871540/+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


[Touch-packages] [Bug 1871540] Re: Include IPs in apt-get output

2020-04-08 Thread Julian Andres Klode
Oh I guess error messages post-connect do not include the IP address, as
we don't know it anymore.

Given the structure of the non-interactive log, I slightly fail to see
how we could include connection messages. UX-wise, it does not make much
sense to give you details you're not going to need 99.9% of the time.

-- 
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/1871540

Title:
  Include IPs in apt-get output

Status in apt package in Ubuntu:
  New

Bug description:
  Hi,

  When running apt-get update/dist-upgrade, output looks like this:

  | Hit:6 http://archive.ubuntu.com/ubuntu focal-updates InRelease
  | Get:7 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages [972 kB]
  | Get:8 http://archive.ubuntu.com/ubuntu focal/main amd64 c-n-f Metadata 
[29.1 kB]
  | ...
  | Need to get 101 MB of archives.
  | After this operation, 10.5 MB of additional disk space will be used.
  | Do you want to continue? [Y/n] y
  | Get:1 http://archive.ubuntu.com/ubuntu focal/main amd64 dpkg amd64 
1.19.7ubuntu3 [1128 kB]
  | Get:2 http://archive.ubuntu.com/ubuntu focal/main amd64 login amd64 
1:4.8.1-1ubuntu4 [221 kB]
  | Get:3 http://archive.ubuntu.com/ubuntu focal/main amd64 libc6-dbg amd64 
2.31-0ubuntu7 [5673 kB]

  With various online CI/CD services such as GitHub Actions, it looks
  like this:

  | Get:14 http://azure.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages [833 kB]
  | Get:16 http://azure.archive.ubuntu.com/ubuntu bionic-updates/main 
Translation-en [292 kB]
  | Get:17 http://azure.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages [1044 kB]
  | ...
  | Get:31 http://azure.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
cmake amd64 3.10.2-1ubuntu2.18.04.1 [3152 kB]
  | Get:32 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu bionic/main 
amd64 gdb amd64 8.2-0ubuntu1~18.04 [3024 kB]
  | Get:33 http://azure.archive.ubuntu.com/ubuntu bionic/universe amd64 epstool 
amd64 3.08+repack-7 [108 kB]

  archive.u.c resolves to multiple IPs. azure.archive.u.c resolves to a
  load balancer (Azure's Traffic Manager). It would be nice if we also
  had the IPs of the servers/hosts in the output and would really help
  us in determining which servers or regions users may be experiencing
  issues with.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1871540/+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


[Touch-packages] [Bug 1871540] Re: Include IPs in apt-get output

2020-04-08 Thread Julian Andres Klode
All error messages and progress messages (e.g. connecting to ...)
include ip addresses. Hence if connecting failed, you get all addresses
it tried, for example.

Now. You will likely not see those messages. If it connects fast enough,
you'll never see the IP. In non-interactive mode, I don't think the
progress messages are shown at all.

So I'm not sure what you're after, given that you get addresses for
errors. Investigating slowness? Surely there are better ways to figure
that out?

-- 
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/1871540

Title:
  Include IPs in apt-get output

Status in apt package in Ubuntu:
  New

Bug description:
  Hi,

  When running apt-get update/dist-upgrade, output looks like this:

  | Hit:6 http://archive.ubuntu.com/ubuntu focal-updates InRelease
  | Get:7 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages [972 kB]
  | Get:8 http://archive.ubuntu.com/ubuntu focal/main amd64 c-n-f Metadata 
[29.1 kB]
  | ...
  | Need to get 101 MB of archives.
  | After this operation, 10.5 MB of additional disk space will be used.
  | Do you want to continue? [Y/n] y
  | Get:1 http://archive.ubuntu.com/ubuntu focal/main amd64 dpkg amd64 
1.19.7ubuntu3 [1128 kB]
  | Get:2 http://archive.ubuntu.com/ubuntu focal/main amd64 login amd64 
1:4.8.1-1ubuntu4 [221 kB]
  | Get:3 http://archive.ubuntu.com/ubuntu focal/main amd64 libc6-dbg amd64 
2.31-0ubuntu7 [5673 kB]

  With various online CI/CD services such as GitHub Actions, it looks
  like this:

  | Get:14 http://azure.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages [833 kB]
  | Get:16 http://azure.archive.ubuntu.com/ubuntu bionic-updates/main 
Translation-en [292 kB]
  | Get:17 http://azure.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages [1044 kB]
  | ...
  | Get:31 http://azure.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
cmake amd64 3.10.2-1ubuntu2.18.04.1 [3152 kB]
  | Get:32 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu bionic/main 
amd64 gdb amd64 8.2-0ubuntu1~18.04 [3024 kB]
  | Get:33 http://azure.archive.ubuntu.com/ubuntu bionic/universe amd64 epstool 
amd64 3.08+repack-7 [108 kB]

  archive.u.c resolves to multiple IPs. azure.archive.u.c resolves to a
  load balancer (Azure's Traffic Manager). It would be nice if we also
  had the IPs of the servers/hosts in the output and would really help
  us in determining which servers or regions users may be experiencing
  issues with.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1871540/+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


[Touch-packages] [Bug 1825000] Re: Add ability for mirrors to distinguish interactive and non-interactive apt runs

2020-04-02 Thread Julian Andres Klode
Well, nothing, absence of service is interactive?

-- 
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/1825000

Title:
  Add ability for mirrors to distinguish interactive and non-interactive
  apt runs

Status in apt package in Ubuntu:
  In Progress
Status in apt source package in Eoan:
  Triaged

Bug description:
  As part of a larger scale plan to manage traffic to the main archive
  servers it would be useful if apt could provide a facility for us to
  identify interactive vs. non-interactive traffic on the server side,
  ideally via a header of some kind.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1825000/+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


[Touch-packages] [Bug 1825000] Re: Add ability for mirrors to distinguish interactive and non-interactive apt runs

2020-04-02 Thread Julian Andres Klode
Note that there were some I think somewhat valid privacy concerns to
exposing the service name.

Maybe it's enough to know if apt ran as part of a systemd service, but
not which service, or we build a whitelist of services (or check if they
are inside /lib/systemd/system - so we do not send local service names).
Currently we do have a blacklist that matches user@ services.

Another approach was to send whether a tty is attached, but I believe
that's a bit less useful

-- 
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/1825000

Title:
  Add ability for mirrors to distinguish interactive and non-interactive
  apt runs

Status in apt package in Ubuntu:
  In Progress
Status in apt source package in Eoan:
  Triaged

Bug description:
  As part of a larger scale plan to manage traffic to the main archive
  servers it would be useful if apt could provide a facility for us to
  identify interactive vs. non-interactive traffic on the server side,
  ideally via a header of some kind.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1825000/+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


[Touch-packages] [Bug 1824088] Re: unattended upgrade ran one day after schedule

2020-04-01 Thread Julian Andres Klode
It seems systemd actually supports restarting oneshot services now, so
any options for timestamps will be removed (anything other than 0 will
behave as always), and systemd timers will have to be configured via
drop-ins instead. Finally.

That said, it seems a bit late for focal now.

Hmm, yeah, I guess that works, because we then take the date in UTC and
compare that.

-- 
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/1824088

Title:
  unattended upgrade ran one day after schedule

Status in apt package in Ubuntu:
  Triaged

Bug description:
  I have noticed a strange behaviour in unattended upgrades. The host in
  question is scheduled to run upgrades on Mondays every second week.
  However, this week it ran upgrades on Tuesday instead (2019-04-09).

  This is the first time I’ve noticed this behaviour. I checked the logs
  in /var/log/apt/history.log* and I saw that worked as intended up
  until this week. Upgrades ran as expected on 2019-03-11 and
  2019-03-25, which where both Mondays.

  The schedule was set with the line 'APT::Periodic::Unattended-Upgrade
  "14";' in the file /etc/apt/apt.conf.d/20auto-upgrades.

  Could it be daylight savings time that has caused skewing of the
  schedule?

  The server is located in Sweden and on 2019-03-31 we switched from CET
  to CEST. If the time diff is calculated with hours instead of calendar
  days passed, perhaps the missing hour on 2019-03-31 caused the
  scheduler to believe that on Monday 2019-03-08, two weeks (336 hours)
  had not yet passed.

  
  ADDITIONAL INFO

  Description:Ubuntu 16.04.6 LTS
  Release:16.04

  apt:
Installed: 1.2.29ubuntu0.1
Candidate: 1.2.31
Version table:
   1.2.31 500
  500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
   *** 1.2.29ubuntu0.1 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.2.10ubuntu1 500
  500 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  unattended-upgrades:
Installed: 0.90ubuntu0.10
Candidate: 0.90ubuntu0.10
Version table:
   *** 0.90ubuntu0.10 500
  500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main i386 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main i386 
Packages
  100 /var/lib/dpkg/status
   0.90 500
  500 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://se.archive.ubuntu.com/ubuntu xenial/main i386 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.29ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
  Uname: Linux 4.4.0-142-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Wed Apr 10 09:06:49 2019
  InstallationDate: Installed on 2017-12-28 (467 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  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/1824088/+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


[Touch-packages] [Bug 1824088] Re: unattended upgrade ran one day after schedule

2020-04-01 Thread Julian Andres Klode
But if I live in UTC+11, I don't want it to run when the day has changed
in UTC+0?

As for date +%s being time zone dependent, hmm, I thought iso-8601
included a timezone, but it does not.

A workaround for DST that might work for non-1-day intervals could be to
change the length of a day to 22 hours:

$ git diff
diff --git a/debian/apt.systemd.daily b/debian/apt.systemd.daily
index 0d336ddb2..567316df9 100755
--- a/debian/apt.systemd.daily
+++ b/debian/apt.systemd.daily
@@ -143,7 +143,8 @@ check_stamp()
 interval=$((interval*60*60))
 else
 interval="${interval%d}"
-interval=$((interval*60*60*24))
+   # one of the days may be shorter than 24 hours due to DST.
+   interval=$(((interval-1)*60*60*24 + 60*60*22))
 fi
 
 debug_echo "check_stamp: interval=$interval, now=$now, stamp=$stamp, 
delta=$delta (sec)"


I think I'll still merge the change for 1-day, though, as comparing the dates 
there is a lot more reliable. It will also deal with you changing time zones, I 
guess.

-- 
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/1824088

Title:
  unattended upgrade ran one day after schedule

Status in apt package in Ubuntu:
  Triaged

Bug description:
  I have noticed a strange behaviour in unattended upgrades. The host in
  question is scheduled to run upgrades on Mondays every second week.
  However, this week it ran upgrades on Tuesday instead (2019-04-09).

  This is the first time I’ve noticed this behaviour. I checked the logs
  in /var/log/apt/history.log* and I saw that worked as intended up
  until this week. Upgrades ran as expected on 2019-03-11 and
  2019-03-25, which where both Mondays.

  The schedule was set with the line 'APT::Periodic::Unattended-Upgrade
  "14";' in the file /etc/apt/apt.conf.d/20auto-upgrades.

  Could it be daylight savings time that has caused skewing of the
  schedule?

  The server is located in Sweden and on 2019-03-31 we switched from CET
  to CEST. If the time diff is calculated with hours instead of calendar
  days passed, perhaps the missing hour on 2019-03-31 caused the
  scheduler to believe that on Monday 2019-03-08, two weeks (336 hours)
  had not yet passed.

  
  ADDITIONAL INFO

  Description:Ubuntu 16.04.6 LTS
  Release:16.04

  apt:
Installed: 1.2.29ubuntu0.1
Candidate: 1.2.31
Version table:
   1.2.31 500
  500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
   *** 1.2.29ubuntu0.1 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.2.10ubuntu1 500
  500 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  unattended-upgrades:
Installed: 0.90ubuntu0.10
Candidate: 0.90ubuntu0.10
Version table:
   *** 0.90ubuntu0.10 500
  500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main i386 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main i386 
Packages
  100 /var/lib/dpkg/status
   0.90 500
  500 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://se.archive.ubuntu.com/ubuntu xenial/main i386 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.29ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
  Uname: Linux 4.4.0-142-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Wed Apr 10 09:06:49 2019
  InstallationDate: Installed on 2017-12-28 (467 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  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/1824088/+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


[Touch-packages] [Bug 1824088] Re: unattended upgrade ran one day after schedule

2020-04-01 Thread Julian Andres Klode
https://salsa.debian.org/apt-team/apt/-/merge_requests/115 implements
the proposed change for daily runs, and warns if intervals are
configured to anything other than 1 or 0 (and soon, always), telling
people to configure their systemd timer instead.

-- 
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/1824088

Title:
  unattended upgrade ran one day after schedule

Status in apt package in Ubuntu:
  Triaged

Bug description:
  I have noticed a strange behaviour in unattended upgrades. The host in
  question is scheduled to run upgrades on Mondays every second week.
  However, this week it ran upgrades on Tuesday instead (2019-04-09).

  This is the first time I’ve noticed this behaviour. I checked the logs
  in /var/log/apt/history.log* and I saw that worked as intended up
  until this week. Upgrades ran as expected on 2019-03-11 and
  2019-03-25, which where both Mondays.

  The schedule was set with the line 'APT::Periodic::Unattended-Upgrade
  "14";' in the file /etc/apt/apt.conf.d/20auto-upgrades.

  Could it be daylight savings time that has caused skewing of the
  schedule?

  The server is located in Sweden and on 2019-03-31 we switched from CET
  to CEST. If the time diff is calculated with hours instead of calendar
  days passed, perhaps the missing hour on 2019-03-31 caused the
  scheduler to believe that on Monday 2019-03-08, two weeks (336 hours)
  had not yet passed.

  
  ADDITIONAL INFO

  Description:Ubuntu 16.04.6 LTS
  Release:16.04

  apt:
Installed: 1.2.29ubuntu0.1
Candidate: 1.2.31
Version table:
   1.2.31 500
  500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
   *** 1.2.29ubuntu0.1 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.2.10ubuntu1 500
  500 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  unattended-upgrades:
Installed: 0.90ubuntu0.10
Candidate: 0.90ubuntu0.10
Version table:
   *** 0.90ubuntu0.10 500
  500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main i386 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main i386 
Packages
  100 /var/lib/dpkg/status
   0.90 500
  500 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://se.archive.ubuntu.com/ubuntu xenial/main i386 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.29ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
  Uname: Linux 4.4.0-142-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Wed Apr 10 09:06:49 2019
  InstallationDate: Installed on 2017-12-28 (467 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  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/1824088/+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


[Touch-packages] [Bug 1824088] Re: unattended upgrade ran one day after schedule

2020-04-01 Thread Julian Andres Klode
** Tags removed: patch

-- 
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/1824088

Title:
  unattended upgrade ran one day after schedule

Status in apt package in Ubuntu:
  Triaged

Bug description:
  I have noticed a strange behaviour in unattended upgrades. The host in
  question is scheduled to run upgrades on Mondays every second week.
  However, this week it ran upgrades on Tuesday instead (2019-04-09).

  This is the first time I’ve noticed this behaviour. I checked the logs
  in /var/log/apt/history.log* and I saw that worked as intended up
  until this week. Upgrades ran as expected on 2019-03-11 and
  2019-03-25, which where both Mondays.

  The schedule was set with the line 'APT::Periodic::Unattended-Upgrade
  "14";' in the file /etc/apt/apt.conf.d/20auto-upgrades.

  Could it be daylight savings time that has caused skewing of the
  schedule?

  The server is located in Sweden and on 2019-03-31 we switched from CET
  to CEST. If the time diff is calculated with hours instead of calendar
  days passed, perhaps the missing hour on 2019-03-31 caused the
  scheduler to believe that on Monday 2019-03-08, two weeks (336 hours)
  had not yet passed.

  
  ADDITIONAL INFO

  Description:Ubuntu 16.04.6 LTS
  Release:16.04

  apt:
Installed: 1.2.29ubuntu0.1
Candidate: 1.2.31
Version table:
   1.2.31 500
  500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
   *** 1.2.29ubuntu0.1 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.2.10ubuntu1 500
  500 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  unattended-upgrades:
Installed: 0.90ubuntu0.10
Candidate: 0.90ubuntu0.10
Version table:
   *** 0.90ubuntu0.10 500
  500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main i386 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main i386 
Packages
  100 /var/lib/dpkg/status
   0.90 500
  500 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://se.archive.ubuntu.com/ubuntu xenial/main i386 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.29ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
  Uname: Linux 4.4.0-142-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Wed Apr 10 09:06:49 2019
  InstallationDate: Installed on 2017-12-28 (467 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  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/1824088/+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


[Touch-packages] [Bug 1824088] Re: unattended upgrade ran one day after schedule

2020-04-01 Thread Julian Andres Klode
Oh but we have the other issue where we have more interval options than
systemd services. Sigh.

-- 
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/1824088

Title:
  unattended upgrade ran one day after schedule

Status in apt package in Ubuntu:
  Triaged

Bug description:
  I have noticed a strange behaviour in unattended upgrades. The host in
  question is scheduled to run upgrades on Mondays every second week.
  However, this week it ran upgrades on Tuesday instead (2019-04-09).

  This is the first time I’ve noticed this behaviour. I checked the logs
  in /var/log/apt/history.log* and I saw that worked as intended up
  until this week. Upgrades ran as expected on 2019-03-11 and
  2019-03-25, which where both Mondays.

  The schedule was set with the line 'APT::Periodic::Unattended-Upgrade
  "14";' in the file /etc/apt/apt.conf.d/20auto-upgrades.

  Could it be daylight savings time that has caused skewing of the
  schedule?

  The server is located in Sweden and on 2019-03-31 we switched from CET
  to CEST. If the time diff is calculated with hours instead of calendar
  days passed, perhaps the missing hour on 2019-03-31 caused the
  scheduler to believe that on Monday 2019-03-08, two weeks (336 hours)
  had not yet passed.

  
  ADDITIONAL INFO

  Description:Ubuntu 16.04.6 LTS
  Release:16.04

  apt:
Installed: 1.2.29ubuntu0.1
Candidate: 1.2.31
Version table:
   1.2.31 500
  500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
   *** 1.2.29ubuntu0.1 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.2.10ubuntu1 500
  500 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  unattended-upgrades:
Installed: 0.90ubuntu0.10
Candidate: 0.90ubuntu0.10
Version table:
   *** 0.90ubuntu0.10 500
  500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main i386 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main i386 
Packages
  100 /var/lib/dpkg/status
   0.90 500
  500 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://se.archive.ubuntu.com/ubuntu xenial/main i386 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.29ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
  Uname: Linux 4.4.0-142-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Wed Apr 10 09:06:49 2019
  InstallationDate: Installed on 2017-12-28 (467 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  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/1824088/+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


[Touch-packages] [Bug 1824088] Re: unattended upgrade ran one day after schedule

2020-04-01 Thread Julian Andres Klode
It seems reasonable that setting TZ=UTC0 for date --iso-8601 could help
(as that's where a time zone is relevant, the +%s conversion it is not
relevant for).

But then this causes unwanted behaviour for people far off UTC, I guess,
so it's not a solution - It's entirely unclear to me whether a solution
exists given that we allow arbitrary intervals in settings.

Always-on machines (or well, always connected machines) should be
configured with the interval set to 0 (disabling timestamp checks), and
the timer should be configured to run at the appropriate times.

To resolve issues with skipped runs elsewhere, we really need to resolve
the issue that systemd can't reschedule failed timer services, and then
remove the options inside apt.conf, as having dynamic timers in systemd
and then a fixed check inside the script does not really work (hence why
we annoyingly run it twice a day to give it a chance to fixup time
skew).

** Changed in: apt (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: apt (Ubuntu)
   Status: Won't Fix => 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/1824088

Title:
  unattended upgrade ran one day after schedule

Status in apt package in Ubuntu:
  Triaged

Bug description:
  I have noticed a strange behaviour in unattended upgrades. The host in
  question is scheduled to run upgrades on Mondays every second week.
  However, this week it ran upgrades on Tuesday instead (2019-04-09).

  This is the first time I’ve noticed this behaviour. I checked the logs
  in /var/log/apt/history.log* and I saw that worked as intended up
  until this week. Upgrades ran as expected on 2019-03-11 and
  2019-03-25, which where both Mondays.

  The schedule was set with the line 'APT::Periodic::Unattended-Upgrade
  "14";' in the file /etc/apt/apt.conf.d/20auto-upgrades.

  Could it be daylight savings time that has caused skewing of the
  schedule?

  The server is located in Sweden and on 2019-03-31 we switched from CET
  to CEST. If the time diff is calculated with hours instead of calendar
  days passed, perhaps the missing hour on 2019-03-31 caused the
  scheduler to believe that on Monday 2019-03-08, two weeks (336 hours)
  had not yet passed.

  
  ADDITIONAL INFO

  Description:Ubuntu 16.04.6 LTS
  Release:16.04

  apt:
Installed: 1.2.29ubuntu0.1
Candidate: 1.2.31
Version table:
   1.2.31 500
  500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
   *** 1.2.29ubuntu0.1 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.2.10ubuntu1 500
  500 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  unattended-upgrades:
Installed: 0.90ubuntu0.10
Candidate: 0.90ubuntu0.10
Version table:
   *** 0.90ubuntu0.10 500
  500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main i386 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main i386 
Packages
  100 /var/lib/dpkg/status
   0.90 500
  500 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://se.archive.ubuntu.com/ubuntu xenial/main i386 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.29ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
  Uname: Linux 4.4.0-142-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Wed Apr 10 09:06:49 2019
  InstallationDate: Installed on 2017-12-28 (467 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  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/1824088/+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


[Touch-packages] [Bug 1824088] Re: unattended upgrade ran one day after schedule

2020-04-01 Thread Julian Andres Klode
Arguably, a workaround might be to remove support for the interval
options now, and then treat it as "one day", and just check that
%Y-%m-%d for today != the one for the stamp.

This addresses the problem with DST, and breaks every non-default
configuration. Which is something we will have to live with eventually
anyway I guess.

So basically speaking, under systemd, intervals will always be "not the
same day", other settings will be ignored and produce a warning, and
you're supposed to configure the timer. This still allows us to play
catch up by running the timer multiple times per day, until we get a
fixed systemd.

Under non-systemd systems in Debian, stuff will continue to work as it
does 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/1824088

Title:
  unattended upgrade ran one day after schedule

Status in apt package in Ubuntu:
  Triaged

Bug description:
  I have noticed a strange behaviour in unattended upgrades. The host in
  question is scheduled to run upgrades on Mondays every second week.
  However, this week it ran upgrades on Tuesday instead (2019-04-09).

  This is the first time I’ve noticed this behaviour. I checked the logs
  in /var/log/apt/history.log* and I saw that worked as intended up
  until this week. Upgrades ran as expected on 2019-03-11 and
  2019-03-25, which where both Mondays.

  The schedule was set with the line 'APT::Periodic::Unattended-Upgrade
  "14";' in the file /etc/apt/apt.conf.d/20auto-upgrades.

  Could it be daylight savings time that has caused skewing of the
  schedule?

  The server is located in Sweden and on 2019-03-31 we switched from CET
  to CEST. If the time diff is calculated with hours instead of calendar
  days passed, perhaps the missing hour on 2019-03-31 caused the
  scheduler to believe that on Monday 2019-03-08, two weeks (336 hours)
  had not yet passed.

  
  ADDITIONAL INFO

  Description:Ubuntu 16.04.6 LTS
  Release:16.04

  apt:
Installed: 1.2.29ubuntu0.1
Candidate: 1.2.31
Version table:
   1.2.31 500
  500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
   *** 1.2.29ubuntu0.1 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.2.10ubuntu1 500
  500 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  unattended-upgrades:
Installed: 0.90ubuntu0.10
Candidate: 0.90ubuntu0.10
Version table:
   *** 0.90ubuntu0.10 500
  500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main i386 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main i386 
Packages
  100 /var/lib/dpkg/status
   0.90 500
  500 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://se.archive.ubuntu.com/ubuntu xenial/main i386 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.29ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
  Uname: Linux 4.4.0-142-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Wed Apr 10 09:06:49 2019
  InstallationDate: Installed on 2017-12-28 (467 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  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/1824088/+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


[Touch-packages] [Bug 1824088] Re: unattended upgrade ran one day after schedule

2020-04-01 Thread Julian Andres Klode
I know that we can sometimes miss a beat so to say, but fixing this will
require fixing systemd to allow retrying of failed timer services, and
then removing the options for intervals inside of apt.

-- 
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/1824088

Title:
  unattended upgrade ran one day after schedule

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  I have noticed a strange behaviour in unattended upgrades. The host in
  question is scheduled to run upgrades on Mondays every second week.
  However, this week it ran upgrades on Tuesday instead (2019-04-09).

  This is the first time I’ve noticed this behaviour. I checked the logs
  in /var/log/apt/history.log* and I saw that worked as intended up
  until this week. Upgrades ran as expected on 2019-03-11 and
  2019-03-25, which where both Mondays.

  The schedule was set with the line 'APT::Periodic::Unattended-Upgrade
  "14";' in the file /etc/apt/apt.conf.d/20auto-upgrades.

  Could it be daylight savings time that has caused skewing of the
  schedule?

  The server is located in Sweden and on 2019-03-31 we switched from CET
  to CEST. If the time diff is calculated with hours instead of calendar
  days passed, perhaps the missing hour on 2019-03-31 caused the
  scheduler to believe that on Monday 2019-03-08, two weeks (336 hours)
  had not yet passed.

  
  ADDITIONAL INFO

  Description:Ubuntu 16.04.6 LTS
  Release:16.04

  apt:
Installed: 1.2.29ubuntu0.1
Candidate: 1.2.31
Version table:
   1.2.31 500
  500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
   *** 1.2.29ubuntu0.1 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.2.10ubuntu1 500
  500 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  unattended-upgrades:
Installed: 0.90ubuntu0.10
Candidate: 0.90ubuntu0.10
Version table:
   *** 0.90ubuntu0.10 500
  500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main i386 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main i386 
Packages
  100 /var/lib/dpkg/status
   0.90 500
  500 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://se.archive.ubuntu.com/ubuntu xenial/main i386 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.29ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
  Uname: Linux 4.4.0-142-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Wed Apr 10 09:06:49 2019
  InstallationDate: Installed on 2017-12-28 (467 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  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/1824088/+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


[Touch-packages] [Bug 1824088] Re: unattended upgrade ran one day after schedule

2020-04-01 Thread Julian Andres Klode
I'm not convinced there is a bug here or that the patch actually fixes
it. We convert our times to Unix time stamps, which are independent of
time zones and DST.

The proposed patch should not be doing anything.

And no, we apt folks do not need or want a duplicate bug report in
Debian.

-- 
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/1824088

Title:
  unattended upgrade ran one day after schedule

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  I have noticed a strange behaviour in unattended upgrades. The host in
  question is scheduled to run upgrades on Mondays every second week.
  However, this week it ran upgrades on Tuesday instead (2019-04-09).

  This is the first time I’ve noticed this behaviour. I checked the logs
  in /var/log/apt/history.log* and I saw that worked as intended up
  until this week. Upgrades ran as expected on 2019-03-11 and
  2019-03-25, which where both Mondays.

  The schedule was set with the line 'APT::Periodic::Unattended-Upgrade
  "14";' in the file /etc/apt/apt.conf.d/20auto-upgrades.

  Could it be daylight savings time that has caused skewing of the
  schedule?

  The server is located in Sweden and on 2019-03-31 we switched from CET
  to CEST. If the time diff is calculated with hours instead of calendar
  days passed, perhaps the missing hour on 2019-03-31 caused the
  scheduler to believe that on Monday 2019-03-08, two weeks (336 hours)
  had not yet passed.

  
  ADDITIONAL INFO

  Description:Ubuntu 16.04.6 LTS
  Release:16.04

  apt:
Installed: 1.2.29ubuntu0.1
Candidate: 1.2.31
Version table:
   1.2.31 500
  500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
   *** 1.2.29ubuntu0.1 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.2.10ubuntu1 500
  500 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  unattended-upgrades:
Installed: 0.90ubuntu0.10
Candidate: 0.90ubuntu0.10
Version table:
   *** 0.90ubuntu0.10 500
  500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main i386 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main i386 
Packages
  100 /var/lib/dpkg/status
   0.90 500
  500 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://se.archive.ubuntu.com/ubuntu xenial/main i386 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.29ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
  Uname: Linux 4.4.0-142-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Wed Apr 10 09:06:49 2019
  InstallationDate: Installed on 2017-12-28 (467 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  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/1824088/+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


[Touch-packages] [Bug 1824088] Re: unattended upgrade ran one day after schedule

2020-03-30 Thread Julian Andres Klode
It's hardly and issue given that the script runs twice per day, which
compensates for that by running it after 36 hours instead of 24.

-- 
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/1824088

Title:
  unattended upgrade ran one day after schedule

Status in apt package in Ubuntu:
  New

Bug description:
  I have noticed a strange behaviour in unattended upgrades. The host in
  question is scheduled to run upgrades on Mondays every second week.
  However, this week it ran upgrades on Tuesday instead (2019-04-09).

  This is the first time I’ve noticed this behaviour. I checked the logs
  in /var/log/apt/history.log* and I saw that worked as intended up
  until this week. Upgrades ran as expected on 2019-03-11 and
  2019-03-25, which where both Mondays.

  The schedule was set with the line 'APT::Periodic::Unattended-Upgrade
  "14";' in the file /etc/apt/apt.conf.d/20auto-upgrades.

  Could it be daylight savings time that has caused skewing of the
  schedule?

  The server is located in Sweden and on 2019-03-31 we switched from CET
  to CEST. If the time diff is calculated with hours instead of calendar
  days passed, perhaps the missing hour on 2019-03-31 caused the
  scheduler to believe that on Monday 2019-03-08, two weeks (336 hours)
  had not yet passed.

  
  ADDITIONAL INFO

  Description:Ubuntu 16.04.6 LTS
  Release:16.04

  apt:
Installed: 1.2.29ubuntu0.1
Candidate: 1.2.31
Version table:
   1.2.31 500
  500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
   *** 1.2.29ubuntu0.1 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.2.10ubuntu1 500
  500 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  unattended-upgrades:
Installed: 0.90ubuntu0.10
Candidate: 0.90ubuntu0.10
Version table:
   *** 0.90ubuntu0.10 500
  500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main i386 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main i386 
Packages
  100 /var/lib/dpkg/status
   0.90 500
  500 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://se.archive.ubuntu.com/ubuntu xenial/main i386 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.29ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
  Uname: Linux 4.4.0-142-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Wed Apr 10 09:06:49 2019
  InstallationDate: Installed on 2017-12-28 (467 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  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/1824088/+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


[Touch-packages] [Bug 1824088] Re: unattended upgrade ran one day after schedule

2020-03-30 Thread Julian Andres Klode
Yes we know that the script does not necessarily run once a day, that's
not a surprise.

-- 
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/1824088

Title:
  unattended upgrade ran one day after schedule

Status in apt package in Ubuntu:
  New

Bug description:
  I have noticed a strange behaviour in unattended upgrades. The host in
  question is scheduled to run upgrades on Mondays every second week.
  However, this week it ran upgrades on Tuesday instead (2019-04-09).

  This is the first time I’ve noticed this behaviour. I checked the logs
  in /var/log/apt/history.log* and I saw that worked as intended up
  until this week. Upgrades ran as expected on 2019-03-11 and
  2019-03-25, which where both Mondays.

  The schedule was set with the line 'APT::Periodic::Unattended-Upgrade
  "14";' in the file /etc/apt/apt.conf.d/20auto-upgrades.

  Could it be daylight savings time that has caused skewing of the
  schedule?

  The server is located in Sweden and on 2019-03-31 we switched from CET
  to CEST. If the time diff is calculated with hours instead of calendar
  days passed, perhaps the missing hour on 2019-03-31 caused the
  scheduler to believe that on Monday 2019-03-08, two weeks (336 hours)
  had not yet passed.

  
  ADDITIONAL INFO

  Description:Ubuntu 16.04.6 LTS
  Release:16.04

  apt:
Installed: 1.2.29ubuntu0.1
Candidate: 1.2.31
Version table:
   1.2.31 500
  500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
   *** 1.2.29ubuntu0.1 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.2.10ubuntu1 500
  500 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  unattended-upgrades:
Installed: 0.90ubuntu0.10
Candidate: 0.90ubuntu0.10
Version table:
   *** 0.90ubuntu0.10 500
  500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main i386 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main i386 
Packages
  100 /var/lib/dpkg/status
   0.90 500
  500 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://se.archive.ubuntu.com/ubuntu xenial/main i386 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.29ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
  Uname: Linux 4.4.0-142-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Wed Apr 10 09:06:49 2019
  InstallationDate: Installed on 2017-12-28 (467 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  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/1824088/+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


[Touch-packages] [Bug 1869721] Re: Apt error message gives incorrect syntax

2020-03-30 Thread Julian Andres Klode
Thanks for your bug report, but it seems you made a typo somewhere, as
both `--fix-broken install` and `install --fix-broken` work - apt does
not care about argument order.

** 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/1869721

Title:
  Apt error message gives incorrect syntax

Status in apt package in Ubuntu:
  Invalid

Bug description:
  in Apt, when trying to reinstall or remove problem packages, if the
  process is unable to run, it says there are unmet dependencies.  It
  then suggest a command to run to fix the problems.  This would be the
  proper procedure for this, however the suggested command it provides
  is wrong.

  
  $ lsb_release -rd
  Description:  Linux Mint 19.3 Tricia
  Release:  19.3

  apt:
Installed: 1.6.12
Candidate: 1.6.12
Version table:
   *** 1.6.12 500
  500 http://mirrors.tripadvisor.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.6.6ubuntu0.1 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   1.6.1 500
  500 http://mirrors.tripadvisor.com/ubuntu bionic/main amd64 Packages

  Expected behavior:

  failed reinstall/uninstall command should show correct syntax for
  recommended command.  In this case it should be "apt install --fix-
  broken", or "sudo apt install --fix-broken" (verified myself by
  running that command).

  
  Actual behavior:

  output from failed command ended with
  "E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution)."
  Running the command as it is shown there results in apt giving a syntax 
summary, rather than running the intended command.
  It was only by guessing at alternative formats on the command that got it to 
work.  The format as shown in the incorrect example would have seemed more 
logical, as the older apt-get equivalent was "apt-get -f install", with the 
option switch before the command.

  It is up to the devs to decide whether the switch before or after the
  command is correct, just as long as the correct and functional form is
  shown in the error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1869721/+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


[Touch-packages] [Bug 1825000] Re: Add ability for mirrors to distinguish interactive and non-interactive apt runs

2020-03-25 Thread Julian Andres Klode
https://salsa.debian.org/apt-team/apt/-/merge_requests/114

** 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/1825000

Title:
  Add ability for mirrors to distinguish interactive and non-interactive
  apt runs

Status in apt package in Ubuntu:
  In Progress
Status in apt source package in Eoan:
  Triaged

Bug description:
  As part of a larger scale plan to manage traffic to the main archive
  servers it would be useful if apt could provide a facility for us to
  identify interactive vs. non-interactive traffic on the server side,
  ideally via a header of some kind.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1825000/+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


[Touch-packages] [Bug 1825000] Re: Add ability for mirrors to distinguish interactive and non-interactive apt runs

2020-03-25 Thread Julian Andres Klode
The attached merge proposal adds the name of the systemd unit that we
are running under to the HTTP User-Agent field. Is that sufficient?

-- 
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/1825000

Title:
  Add ability for mirrors to distinguish interactive and non-interactive
  apt runs

Status in apt package in Ubuntu:
  In Progress
Status in apt source package in Eoan:
  Triaged

Bug description:
  As part of a larger scale plan to manage traffic to the main archive
  servers it would be useful if apt could provide a facility for us to
  identify interactive vs. non-interactive traffic on the server side,
  ideally via a header of some kind.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1825000/+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


[Touch-packages] [Bug 1868988] Re: apt assert failure: malloc(): mismatching next->prev_size (unsorted)

2020-03-25 Thread Julian Andres Klode
** Information type changed from Private to Public

-- 
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/1868988

Title:
  apt assert failure: malloc(): mismatching next->prev_size (unsorted)

Status in apt package in Ubuntu:
  New

Bug description:
  libwxbase3.0-0v5 libwxgtk3.0-gtk3-0v5

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: apt 2.0.0
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  AssertionMessage: malloc(): mismatching next->prev_size (unsorted)
  Date: Wed Mar 25 14:19:48 2020
  ExecutablePath: /usr/bin/apt
  InstallationDate: Installed on 2020-03-17 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
  ProcCmdline: apt upgrade
  Signal: 6
  SourcePackage: apt
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f5e92ba0285 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
   malloc_printerr (str=str@entry=0x7f5e92ba2aa0 "malloc(): mismatching 
next->prev_size (unsorted)") at malloc.c:5347
   _int_malloc (av=av@entry=0x7f5e92bd1b80 , bytes=bytes@entry=128) 
at malloc.c:3741
   __GI___libc_malloc (bytes=128) at malloc.c:3058
   operator new(unsigned long) () from /lib/x86_64-linux-gnu/libstdc++.so.6
  Title: apt assert failure: malloc(): mismatching next->prev_size (unsorted)
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1868988/+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


[Touch-packages] [Bug 1868771] Re: Job for virtualbox.service failed because the control process exited with error code.

2020-03-24 Thread Julian Andres Klode
*** This bug is a duplicate of bug 1868770 ***
https://bugs.launchpad.net/bugs/1868770

** This bug has been marked a duplicate of bug 1868770
   Job for virtualbox.service failed because the control process exited with 
error code.

-- 
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/1868771

Title:
  Job for virtualbox.service failed because the control process exited
  with error code.

Status in apt package in Ubuntu:
  New

Bug description:
  DKMS: install completed.
  virtualbox (5.2.34-dfsg-0~ubuntu18.04.1) wird eingerichtet ...
  vboxweb.service is a disabled or a static unit, not starting it.
  Job for virtualbox.service failed because the control process exited with 
error code.
  See "systemctl status virtualbox.service" and "journalctl -xe" for details.
  invoke-rc.d: initscript virtualbox, action "restart" failed.
  ● virtualbox.service - LSB: VirtualBox Linux kernel module
 Loaded: loaded (/etc/init.d/virtualbox; generated)
 Active: failed (Result: exit-code) since Tue 2020-03-24 16:53:16 CET; 7ms 
ago
   Docs: man:systemd-sysv-generator(8)
Process: 13282 ExecStart=/etc/init.d/virtualbox start (code=exited, 
status=1/FAILURE)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6.12
  ProcVersionSignature: Ubuntu 4.15.0-1076.86-oem 4.15.18
  Uname: Linux 4.15.0-1076-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  Date: Tue Mar 24 16:55:20 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+loki-n3-v3-kbl+X28
  InstallationDate: Installed on 2019-10-04 (172 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  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/1868771/+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


[Touch-packages] [Bug 1868770] Re: Job for virtualbox.service failed because the control process exited with error code.

2020-03-24 Thread Julian Andres Klode
** Package changed: apt (Ubuntu) => virtualbox (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/1868770

Title:
  Job for virtualbox.service failed because the control process exited
  with error code.

Status in virtualbox package in Ubuntu:
  New

Bug description:
  DKMS: install completed.
  virtualbox (5.2.34-dfsg-0~ubuntu18.04.1) wird eingerichtet ...
  vboxweb.service is a disabled or a static unit, not starting it.
  Job for virtualbox.service failed because the control process exited with 
error code.
  See "systemctl status virtualbox.service" and "journalctl -xe" for details.
  invoke-rc.d: initscript virtualbox, action "restart" failed.
  ● virtualbox.service - LSB: VirtualBox Linux kernel module
 Loaded: loaded (/etc/init.d/virtualbox; generated)
 Active: failed (Result: exit-code) since Tue 2020-03-24 16:53:16 CET; 7ms 
ago
   Docs: man:systemd-sysv-generator(8)
Process: 13282 ExecStart=/etc/init.d/virtualbox start (code=exited, 
status=1/FAILURE)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6.12
  ProcVersionSignature: Ubuntu 4.15.0-1076.86-oem 4.15.18
  Uname: Linux 4.15.0-1076-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  Date: Tue Mar 24 16:55:20 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+loki-n3-v3-kbl+X28
  InstallationDate: Installed on 2019-10-04 (172 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1868770/+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


[Touch-packages] [Bug 1868276] Re: Libgcrypt warning: missing initialization - please fix the application

2020-03-20 Thread Julian Andres Klode
This is fixed in 2.0 in proposed.

** 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/1868276

Title:
  Libgcrypt warning: missing initialization - please fix the application

Status in apt package in Ubuntu:
  Invalid

Bug description:
  In Focal, running 'apt update' result in the following messages being
  logged:

  Mar 20 15:24:12 fa1 http[3392]: Libgcrypt warning: missing initialization - 
please fix the application
  Mar 20 15:24:12 fa1 http[3393]: Libgcrypt warning: missing initialization - 
please fix the application
  Mar 20 15:24:13 fa1 store[3550]: Libgcrypt warning: missing initialization - 
please fix the application

  # Steps to reproduce

  $ lxc launch images:ubuntu/focal fa1
  $ lxc shell fa1
  root@fa1:~# rm /var/lib/apt/lists/*InRelease  # make sure we pull from the 
network
  root@fa1:~# apt update
  root@fa1:~# journalctl -b0 | grep -i Libgcrypt
  Mar 20 15:24:12 fa1 http[3392]: Libgcrypt warning: missing initialization - 
please fix the application
  Mar 20 15:24:12 fa1 http[3393]: Libgcrypt warning: missing initialization - 
please fix the application
  Mar 20 15:24:13 fa1 store[3550]: Libgcrypt warning: missing initialization - 
please fix the application

  
  # Additional information
  root@fa1:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@fa1:~# apt-cache policy apt
  apt:
Installed: 1.9.10
Candidate: 1.9.10
Version table:
   *** 1.9.10 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1868276/+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


  1   2   3   4   5   6   7   8   9   10   >