[Touch-packages] [Bug 1228038] Re: package tzdata 2013d-0ubuntu0.12.04 failed to install/upgrade: サブプロセス インストール済みの post-installation スクリプト はエラー終了ステータス 1 を返しました

2023-03-25 Thread Launchpad Bug Tracker
[Expired for tzdata (Ubuntu) because there has been no activity for 60
days.]

** Changed in: tzdata (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package tzdata 2013d-0ubuntu0.12.04 failed to install/upgrade: サブプロセス
  インストール済みの post-installation スクリプト はエラー終了ステータス 1 を返しました

Status in tzdata package in Ubuntu:
  Expired

Bug description:
  I don't know anything.

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: tzdata 2013d-0ubuntu0.12.04
  ProcVersionSignature: Ubuntu 3.2.0-52.78-generic 3.2.48
  Uname: Linux 3.2.0-52-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.4
  Architecture: amd64
  Date: Fri Sep 20 17:04:43 2013
  DuplicateSignature: package:tzdata:2013d-0ubuntu0.12.04:サブプロセス インストール済みの 
post-installation スクリプト はエラー終了ステータス 1 を返しました
  ErrorMessage: サブプロセス インストール済みの post-installation スクリプト はエラー終了ステータス 1 を返しました
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: tzdata
  Title: package tzdata 2013d-0ubuntu0.12.04 failed to install/upgrade: サブプロセス 
インストール済みの post-installation スクリプト はエラー終了ステータス 1 を返しました
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1228038/+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 1318669] Re: On move use same heuristics as Windows Explorer if NTFS inherit option is set

2023-03-25 Thread UlfZibis
This applies to all versions up to 22.10.

** Changed in: nemo (Ubuntu)
   Status: Invalid => New

** Changed in: glib2.0 (Ubuntu)
   Status: Invalid => New

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

Title:
  On move use same heuristics as Windows Explorer if NTFS inherit option
  is set

Status in glib2.0 package in Ubuntu:
  New
Status in nemo package in Ubuntu:
  New

Bug description:
  When moving a file or folder, which inherits its permissions from its parent 
folder, with original Windows Explorer within same NTFS file system, after the 
move the object always inherits its permissions from its destination parent 
folder in contrast to command line move, which never changes owner and 
permissions.
  IMO, Nautilus and also Nemo should behave same, if ntfs-3g "inherit" mount 
option is active.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1318669/+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 2002445] Re: udev NIC renaming race with mlx5_core driver

2023-03-25 Thread Chad Smith
Kinetic success for proposed launches, rename race seen and properly handled 
without delaying boot time due to systemd-networkd-wait-online.target.

 *** 251.4-1ubuntu7.3 500   
500 http://archive.ubuntu.com/ubuntu kinetic-proposed/main amd64 
Packages
100 /var/lib/dpkg/status   
...
- Test run complete: 100 attempted -
Successes without rename race: 81   
Successes with rename race and preserved altname: 19
Failures due to network delay: 0
Failures due to no altnames persisted: 81   
===

** Attachment added: "sru-systemd-kinetic.log"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2002445/+attachment/5657411/+files/sru-systemd-kinetic.log

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

Title:
  udev NIC renaming race with mlx5_core driver

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Jammy:
  Fix Committed
Status in systemd source package in Kinetic:
  Fix Committed
Status in systemd source package in Lunar:
  Fix Released

Bug description:
  [Impact]
  On systems with mellanox NICs, udev's NIC renaming races with the mlx5_core 
driver's own configuration of subordinate interfaces. When the kernel wins this 
race, the device cannot be renamed as udev has attempted, and this causes 
systemd-network-online.target to timeout waiting for links to be configured. 
This ultimately results in boot being delayed by about 2 minutes.

  [Test Plan]
  Repeated launches of Standard_D8ds_v5 instance types will generally hit this 
race around 1 in 10 runs. Create a vm snapshot with updated systemd from 
ppa:enr0n/systemd-245. Launch 100 Standard_D8ds_v5 instances with updated 
systemd. Assert not failure in cloud-init status and no 2 minute delay in 
network-online.target.

  To check for failure symptom:
    - Assert that network-online.target isn't the longest pole from 
systemd-analyze blame.

  To assert success condition during net rename busy race:
    - assert when "eth1" is still the primary device name, that two altnames 
are listed (preserving the altname due to the primary NIC rename being hit).

  Sample script uses pycloudlib to create modified base image for test
  and launches 100 VMs of type Standard_D8ds_v5, counting both successes
  and any failures seen.

  #!/usr/bin/env python3
  # This file is part of pycloudlib. See LICENSE file for license information.
  """Basic examples of various lifecycle with an Azure instance."""

  import json
  import logging
  import os
  import sys
  from enum import Enum

  import pycloudlib

  LOG = logging.getLogger()

  base_cfg = """#cloud-config
  ssh-import-id: [chad.smith, enr0n, falcojr, holmanb, aciba]
  """

  #source: "deb [allow-insecure=yes] 
https://ppa.launchpadcontent.net/enr0n/systemd-245/ubuntu focal main"
  # - apt install systemd udev -y --allow-unauthenticated

  apt_cfg = """
  # Add developer PPA
  apt:
   sources:
 systemd-testing:
   source: {source}
  # upgrade systemd after cloud-init is nearly done
  runcmd:
   - apt install systemd udev -y --allow-unauthenticated
  """

  debug_systemd_cfg = """
  # Create systemd-udev debug override.conf in base image
  write_files:
  - path: /etc/systemd/system/systemd-networkd.service.d/override.conf
owner: root:root
defer: {defer}
content: |
  [Service]
  Environment=SYSTEMD_LOG_LEVEL=debug
  
  - path: /etc/systemd/system/systemd-udevd.service.d/override.conf
owner: root:root
defer: {defer}
content: |
  [Service]
  Environment=SYSTEMD_LOG_LEVEL=debug
  LogRateLimitIntervalSec=0
  """

  cloud_config = base_cfg + apt_cfg + debug_systemd_cfg
  cloud_config2 = base_cfg + debug_systemd_cfg

  
  class BootCondition(Enum):
  SUCCESS_WITHOUT_RENAME_RACE = "network bringup success without rename 
race"
  SUCCESS_WITH_RENAME_RACE = "network bringup success rename race condition"
  ERROR_NETWORK_TIMEOUT = "error: timeout on systemd-networkd-wait-online"

  
  def batch_launch_vm(
  client, instance_type, image_id, user_data, instance_count=5
  ):
  instances = []
  while len(instances) < instance_count:
  instances.append(
  client.launch(
  image_id=image_id,
  instance_type=instance_type,
  user_data=user_data,
  )
  )
  return instances

  
  def get_boot_condition(test_idx, instance):
  blame = instance.execute("systemd-analyze blame").splitlines()
  try:
  LOG.info(

[Touch-packages] [Bug 2002445] Re: udev NIC renaming race with mlx5_core driver

2023-03-25 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 252.5-2ubuntu3

---
systemd (252.5-2ubuntu3) lunar; urgency=medium

  * udev: gracefully handle rename failures (LP: #2002445)
Files:
- debian/patches/lp2002445/core-device-ignore-failed-uevents.patch
- debian/patches/lp2002445/sd-device-introduce-device_get_property_int.patch
- 
debian/patches/lp2002445/sd-device-make-device_set_syspath-clear-sysname-and-sysnu.patch
- 
debian/patches/lp2002445/udev-restore-syspath-and-properties-on-failure.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=79536dbb165dbcc402629684e0911693626df5b1

 -- Nick Rosbrook   Mon, 20 Mar 2023
10:17:24 -0400

** Changed in: systemd (Ubuntu Lunar)
   Status: Fix Committed => Fix Released

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

Title:
  udev NIC renaming race with mlx5_core driver

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Jammy:
  Fix Committed
Status in systemd source package in Kinetic:
  Fix Committed
Status in systemd source package in Lunar:
  Fix Released

Bug description:
  [Impact]
  On systems with mellanox NICs, udev's NIC renaming races with the mlx5_core 
driver's own configuration of subordinate interfaces. When the kernel wins this 
race, the device cannot be renamed as udev has attempted, and this causes 
systemd-network-online.target to timeout waiting for links to be configured. 
This ultimately results in boot being delayed by about 2 minutes.

  [Test Plan]
  Repeated launches of Standard_D8ds_v5 instance types will generally hit this 
race around 1 in 10 runs. Create a vm snapshot with updated systemd from 
ppa:enr0n/systemd-245. Launch 100 Standard_D8ds_v5 instances with updated 
systemd. Assert not failure in cloud-init status and no 2 minute delay in 
network-online.target.

  To check for failure symptom:
    - Assert that network-online.target isn't the longest pole from 
systemd-analyze blame.

  To assert success condition during net rename busy race:
    - assert when "eth1" is still the primary device name, that two altnames 
are listed (preserving the altname due to the primary NIC rename being hit).

  Sample script uses pycloudlib to create modified base image for test
  and launches 100 VMs of type Standard_D8ds_v5, counting both successes
  and any failures seen.

  #!/usr/bin/env python3
  # This file is part of pycloudlib. See LICENSE file for license information.
  """Basic examples of various lifecycle with an Azure instance."""

  import json
  import logging
  import os
  import sys
  from enum import Enum

  import pycloudlib

  LOG = logging.getLogger()

  base_cfg = """#cloud-config
  ssh-import-id: [chad.smith, enr0n, falcojr, holmanb, aciba]
  """

  #source: "deb [allow-insecure=yes] 
https://ppa.launchpadcontent.net/enr0n/systemd-245/ubuntu focal main"
  # - apt install systemd udev -y --allow-unauthenticated

  apt_cfg = """
  # Add developer PPA
  apt:
   sources:
 systemd-testing:
   source: {source}
  # upgrade systemd after cloud-init is nearly done
  runcmd:
   - apt install systemd udev -y --allow-unauthenticated
  """

  debug_systemd_cfg = """
  # Create systemd-udev debug override.conf in base image
  write_files:
  - path: /etc/systemd/system/systemd-networkd.service.d/override.conf
owner: root:root
defer: {defer}
content: |
  [Service]
  Environment=SYSTEMD_LOG_LEVEL=debug
  
  - path: /etc/systemd/system/systemd-udevd.service.d/override.conf
owner: root:root
defer: {defer}
content: |
  [Service]
  Environment=SYSTEMD_LOG_LEVEL=debug
  LogRateLimitIntervalSec=0
  """

  cloud_config = base_cfg + apt_cfg + debug_systemd_cfg
  cloud_config2 = base_cfg + debug_systemd_cfg

  
  class BootCondition(Enum):
  SUCCESS_WITHOUT_RENAME_RACE = "network bringup success without rename 
race"
  SUCCESS_WITH_RENAME_RACE = "network bringup success rename race condition"
  ERROR_NETWORK_TIMEOUT = "error: timeout on systemd-networkd-wait-online"

  
  def batch_launch_vm(
  client, instance_type, image_id, user_data, instance_count=5
  ):
  instances = []
  while len(instances) < instance_count:
  instances.append(
  client.launch(
  image_id=image_id,
  instance_type=instance_type,
  user_data=user_data,
  )
  )
  return instances

  
  def get_boot_condition(test_idx, instance):
  blame = instance.execute("systemd-analyze blame").splitlines()
  try:
  LOG.info(
  f"--- Attempt {test_idx} ssh ubuntu@{instance.ip} Blame: 
{blame[0]}"
  )
  except IndexError:
  LOG.warning("--- Attempt {test_idx} Empty blame {blame}?")

[Touch-packages] [Bug 2002445] Re: udev NIC renaming race with mlx5_core driver

2023-03-25 Thread Chad Smith
Jammy success for proposed launches, rename race  seen and properly
handled without delaying boot time due to systemd-networkd-wait-
online.target.


 *** 249.11-0ubuntu3.9 500  
500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 
100 /var/lib/dpkg/status


- Test run complete: 100 attempted -
Successes without rename race: 93   
Successes with rename race and preserved altname: 7 
Failures due to network delay: 0
Failures due to no altnames persisted: 93   
===  


** Attachment added: "sru-systemd-jammy.log"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2002445/+attachment/5657410/+files/sru-systemd-jammy.log

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

Title:
  udev NIC renaming race with mlx5_core driver

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Jammy:
  Fix Committed
Status in systemd source package in Kinetic:
  Fix Committed
Status in systemd source package in Lunar:
  Fix Committed

Bug description:
  [Impact]
  On systems with mellanox NICs, udev's NIC renaming races with the mlx5_core 
driver's own configuration of subordinate interfaces. When the kernel wins this 
race, the device cannot be renamed as udev has attempted, and this causes 
systemd-network-online.target to timeout waiting for links to be configured. 
This ultimately results in boot being delayed by about 2 minutes.

  [Test Plan]
  Repeated launches of Standard_D8ds_v5 instance types will generally hit this 
race around 1 in 10 runs. Create a vm snapshot with updated systemd from 
ppa:enr0n/systemd-245. Launch 100 Standard_D8ds_v5 instances with updated 
systemd. Assert not failure in cloud-init status and no 2 minute delay in 
network-online.target.

  To check for failure symptom:
    - Assert that network-online.target isn't the longest pole from 
systemd-analyze blame.

  To assert success condition during net rename busy race:
    - assert when "eth1" is still the primary device name, that two altnames 
are listed (preserving the altname due to the primary NIC rename being hit).

  Sample script uses pycloudlib to create modified base image for test
  and launches 100 VMs of type Standard_D8ds_v5, counting both successes
  and any failures seen.

  #!/usr/bin/env python3
  # This file is part of pycloudlib. See LICENSE file for license information.
  """Basic examples of various lifecycle with an Azure instance."""

  import json
  import logging
  import os
  import sys
  from enum import Enum

  import pycloudlib

  LOG = logging.getLogger()

  base_cfg = """#cloud-config
  ssh-import-id: [chad.smith, enr0n, falcojr, holmanb, aciba]
  """

  #source: "deb [allow-insecure=yes] 
https://ppa.launchpadcontent.net/enr0n/systemd-245/ubuntu focal main"
  # - apt install systemd udev -y --allow-unauthenticated

  apt_cfg = """
  # Add developer PPA
  apt:
   sources:
 systemd-testing:
   source: {source}
  # upgrade systemd after cloud-init is nearly done
  runcmd:
   - apt install systemd udev -y --allow-unauthenticated
  """

  debug_systemd_cfg = """
  # Create systemd-udev debug override.conf in base image
  write_files:
  - path: /etc/systemd/system/systemd-networkd.service.d/override.conf
owner: root:root
defer: {defer}
content: |
  [Service]
  Environment=SYSTEMD_LOG_LEVEL=debug
  
  - path: /etc/systemd/system/systemd-udevd.service.d/override.conf
owner: root:root
defer: {defer}
content: |
  [Service]
  Environment=SYSTEMD_LOG_LEVEL=debug
  LogRateLimitIntervalSec=0
  """

  cloud_config = base_cfg + apt_cfg + debug_systemd_cfg
  cloud_config2 = base_cfg + debug_systemd_cfg

  
  class BootCondition(Enum):
  SUCCESS_WITHOUT_RENAME_RACE = "network bringup success without rename 
race"
  SUCCESS_WITH_RENAME_RACE = "network bringup success rename race condition"
  ERROR_NETWORK_TIMEOUT = "error: timeout on systemd-networkd-wait-online"

  
  def batch_launch_vm(
  client, instance_type, image_id, user_data, instance_count=5
  ):
  instances = []
  while len(instances) < instance_count:
  instances.append(
  client.launch(
  image_id=image_id,
  instance_type=instance_type,
  user_data=user_data,
  )
  )
  return instances

  
  def get_boot_condition(test_idx, instance):
  blame = instance.execute("systemd-analyze blame").splitlines()
  try:
  LOG.info(
  

[Touch-packages] [Bug 2002445] Re: udev NIC renaming race with mlx5_core driver

2023-03-25 Thread Chad Smith
Test script referenced in the bug description
https://paste.ubuntu.com/p/Xkc7bSZ8fB/


** Description changed:

  [Impact]
  On systems with mellanox NICs, udev's NIC renaming races with the mlx5_core 
driver's own configuration of subordinate interfaces. When the kernel wins this 
race, the device cannot be renamed as udev has attempted, and this causes 
systemd-network-online.target to timeout waiting for links to be configured. 
This ultimately results in boot being delayed by about 2 minutes.
  
  [Test Plan]
  Repeated launches of Standard_D8ds_v5 instance types will generally hit this 
race around 1 in 10 runs. Create a vm snapshot with updated systemd from 
ppa:enr0n/systemd-245. Launch 100 Standard_D8ds_v5 instances with updated 
systemd. Assert not failure in cloud-init status and no 2 minute delay in 
network-online.target.
  
  To check for failure symptom:
    - Assert that network-online.target isn't the longest pole from 
systemd-analyze blame.
  
  To assert success condition during net rename busy race:
-   - assert when "eth1" is still the primary device name, that two altnames 
are listed (preserving the altname due to the primary NIC rename being hit.
+   - assert when "eth1" is still the primary device name, that two altnames 
are listed (preserving the altname due to the primary NIC rename being hit).
  
  Sample script uses pycloudlib to create modified base image for test and
  launches 100 VMs of type Standard_D8ds_v5, counting both successes and
  any failures seen.
  
  #!/usr/bin/env python3
  # This file is part of pycloudlib. See LICENSE file for license information.
  """Basic examples of various lifecycle with an Azure instance."""
  
+ import json
  import logging
- import json
+ import os
+ import sys
+ from enum import Enum
  
  import pycloudlib
+ 
  LOG = logging.getLogger()
  
  base_cfg = """#cloud-config
- ssh-import-id: [chad.smith, enr0n]
+ ssh-import-id: [chad.smith, enr0n, falcojr, holmanb, aciba]
  """
+ 
+ #source: "deb [allow-insecure=yes] 
https://ppa.launchpadcontent.net/enr0n/systemd-245/ubuntu focal main"
+ # - apt install systemd udev -y --allow-unauthenticated
  
  apt_cfg = """
  # Add developer PPA
  apt:
-  sources:
-    systemd-testing:
-  source: "deb [allow-insecure=yes] 
https://ppa.launchpadcontent.net/enr0n/systemd-245/ubuntu focal main"
+  sources:
+systemd-testing:
+  source: {source}
  # upgrade systemd after cloud-init is nearly done
  runcmd:
-  - apt install systemd udev -y --allow-unauthenticated
+  - apt install systemd udev -y --allow-unauthenticated
  """
  
  debug_systemd_cfg = """
  # Create systemd-udev debug override.conf in base image
  write_files:
  - path: /etc/systemd/system/systemd-networkd.service.d/override.conf
-   owner: root:root
-   defer: {defer}
-   content: |
- [Service]
- Environment=SYSTEMD_LOG_LEVEL=debug
- 
+   owner: root:root
+   defer: {defer}
+   content: |
+ [Service]
+ Environment=SYSTEMD_LOG_LEVEL=debug
+ 
  - path: /etc/systemd/system/systemd-udevd.service.d/override.conf
-   owner: root:root
-   defer: {defer}
-   content: |
- [Service]
- Environment=SYSTEMD_LOG_LEVEL=debug
- LogRateLimitIntervalSec=0
+   owner: root:root
+   defer: {defer}
+   content: |
+ [Service]
+ Environment=SYSTEMD_LOG_LEVEL=debug
+ LogRateLimitIntervalSec=0
  """
  
  cloud_config = base_cfg + apt_cfg + debug_systemd_cfg
  cloud_config2 = base_cfg + debug_systemd_cfg
  
- def debug_systemd_image_launch_overlake_v5_with_snapshot():
- """Test overlake v5 timeouts
- 
- test procedure:
- - Launch base focal image
- - enable ppa:enr0n/systemd-245 and systemd/udev debugging
- - cloud-init clean --logs && deconfigure waalinux agent before shutdown
- - snapshot a base image
- - launch v5 system from snapshot
- - check systemd-analyze for expected timeout
- """
- client = pycloudlib.Azure(tag="azure")
- 
- image_id = client.daily_image(release="focal")
- pub_path = "/home/ubuntu/.ssh/id_rsa.pub"
- priv_path = "/home/ubuntu/.ssh/id_rsa"
- 
- client.use_key(pub_path, priv_path)
- 
- base_instance = client.launch(
- image_id=image_id,
- instance_type="Standard_DS1_v2",
- user_data=cloud_config.format(defer="true"),
- )
- 
- LOG.info(f"base instance: ssh ubuntu@{base_instance.ip}")
- base_instance.wait()
- LOG.info(base_instance.execute("apt cache policy systemd"))
- snapshotted_image_id = client.snapshot(base_instance)
- 
- reproducer = False
- tries = 0
- success_count_with_race = 0
- success_count_no_race = 0
- failure_count_network_delay = 0
- failure_count_no_altnames = 0
- TEST_SUMMARY_TMPL = """
- - Test run complete: {tries} attempted -
- Successes without rename race: {success_count_no_race}
- Successes with rename race and preserved altname: 
{success_count_with_race}
- Failures due to network delay: 

[Touch-packages] [Bug 1258646] Re: tzdata upgrade dies, killing apt w/o fixing the tty, when /etc/localtime is protected

2023-03-25 Thread Benjamin Drung
Thank you for taking the time to report this bug and helping to make
Ubuntu better.

/etc/localtime is a symlink and therefore setting the immutable flag is
not possible:

```
$ lsattr /etc/localtime 
lsattr: Operation not supported While reading flags on /etc/localtime
```

If you make files in /usr/share/zoneinfo immutable, it will be no
surprise that apt will fail to replace them on a tzdata update.

Can you describe how to replicate your setup step by step?

** Changed in: tzdata (Ubuntu)
   Status: New => Incomplete

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

Title:
  tzdata upgrade dies, killing apt w/o fixing the tty, when
  /etc/localtime is protected

Status in tzdata package in Ubuntu:
  Incomplete

Bug description:
  When /etc/localtime is protected from manipulation, such as with the
  immutable flag — something which is often required when leasing
  virtuals, to keep the vendors’ frameworks from screwing with the
  filesystem — an update to tzdata will crap out, killing dpkg and apt,
  which leaves the tty a mess.

  Instead, should it be impossible to overwrite the existing
  /etc/localtime, the script should continue without error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1258646/+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 2012692] Re: package tzdata 2022g-7ubuntu2 failed to install/upgrade: trying to overwrite '/usr/share/zoneinfo-icu/44/be/metaZones.res', which is also in package tzdata-icu 2022g

2023-03-25 Thread Benjamin Drung
Thank you for taking the time to report this bug and helping to make
Ubuntu better.

You are running Ubuntu 23.04 (lunar), but you want to install tzdata
2023a-0ubuntu0.22.10.0 from Ubuntu 22.10 (kinetic). I recommend to fix
your APT sources list.

tzdata was split in lunar. tzdata 2023b-1exp1ubuntu1 in lunar-proposed
ensures that it correctly conflicts even with tzdata updates in older
Ubuntu releases. So I am marking this bug as fixed.

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

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

Title:
  package tzdata 2022g-7ubuntu2 failed to install/upgrade: trying to
  overwrite '/usr/share/zoneinfo-icu/44/be/metaZones.res', which is also
  in package tzdata-icu 2022g-7ubuntu2

Status in tzdata package in Ubuntu:
  Fix Released

Bug description:
  Unpacking tzdata (2023a-0ubuntu0.22.10.0) over (2022g-7ubuntu2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/tzdata_2023a-0ubuntu0.22.10.0_all.deb (--unpack):
   trying to overwrite '/usr/share/zoneinfo-icu/44/be/metaZones.res', which is 
also in package tzdata-icu 2022g-7ubuntu2
  Errors were encountered while processing:
   /var/cache/apt/archives/tzdata_2023a-0ubuntu0.22.10.0_all.deb

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: tzdata 2022g-7ubuntu2
  Uname: Linux 6.2.7-060207-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Fri Mar 24 12:17:53 2023
  ErrorMessage: trying to overwrite 
'/usr/share/zoneinfo-icu/44/be/metaZones.res', which is also in package 
tzdata-icu 2022g-7ubuntu2
  InstallationDate: Installed on 2022-09-07 (197 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.21ubuntu1
   apt  2.6.0
  SourcePackage: tzdata
  Title: package tzdata 2022g-7ubuntu2 failed to install/upgrade: trying to 
overwrite '/usr/share/zoneinfo-icu/44/be/metaZones.res', which is also in 
package tzdata-icu 2022g-7ubuntu2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2012692/+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 1991606] Re: Invalid PEP440 package version breaking setuptools >= 66

2023-03-25 Thread Launchpad Bug Tracker
This bug was fixed in the package devscripts - 2.23.3ubuntu2

---
devscripts (2.23.3ubuntu2) lunar; urgency=medium

  * Drop debpkg to make devscripts architecture all. Instead of debpkg please
use sudo for debi (or, highly dangerous, make dpkg setuid root).
  * Revert special handling for i386

 -- Benjamin Drung   Mon, 20 Mar 2023 13:05:08 +0100

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

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

Title:
  Invalid PEP440 package version breaking setuptools >= 66

Status in devscripts package in Ubuntu:
  Fix Released
Status in distro-info package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  Fix Released
Status in gpgme1.0 package in Ubuntu:
  New
Status in python-debian package in Ubuntu:
  Fix Released
Status in reportbug package in Ubuntu:
  Fix Released
Status in ubuntu-dev-tools package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in devscripts source package in Bionic:
  New
Status in distro-info source package in Bionic:
  New
Status in drslib source package in Bionic:
  Invalid
Status in duecredit source package in Bionic:
  New
Status in gpgme1.0 source package in Bionic:
  New
Status in python-debian source package in Bionic:
  Invalid
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in update-manager source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  New
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in gpgme1.0 source package in Focal:
  New
Status in python-debian source package in Focal:
  New
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  New
Status in update-manager source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  New
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in gpgme1.0 source package in Jammy:
  New
Status in python-debian source package in Jammy:
  New
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in update-manager source package in Jammy:
  New
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  New
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in gpgme1.0 source package in Kinetic:
  New
Status in python-debian source package in Kinetic:
  Invalid
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid
Status in update-manager source package in Kinetic:
  New

Bug description:
  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources`
  module, can produce errors like this:

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
  self.scan(search_path)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1077, in scan
  self.add(dist)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1096, in add
  dists.sort(key=operator.attrgetter('hashcmp'), reverse=True)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2631, in hashcmp
  self.parsed_version,
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2678, in parsed_version
  self._parsed_version = parse_version(self.version)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/_vendor/packaging/version.py",
 line 266, in __init__
  raise InvalidVersion(f"Invalid version: '{version}'")
  pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 
'0.23ubuntu1'

  The official opinion of the setuptools maintainers seems to be that
  version strings of this form haven't *really* been allowed since about
  2014, and distributions need to change their package version naming
  scheme for Python packages they install, so that the resulting