[Bug 2064166] [NEW] Exclude alacritty from Ubuntu Cinnamon ISOs

2024-04-29 Thread Jeremy Bícha
Public bug reported:

alacritty is unintentionally included in Ubuntu Cinnamon 24.04 LTS even
though the Ubuntu Cinnamon metapackages do not recommend or depend on
it.

I'm filing the bug here even though ubuntucinnamon-meta won't need to be
updated, just the seed, because there is nowhere else to report bugs
about seeds.

A few things that could be tried:
- move the gnome-terminal dependency to a higher location in the seed
- try adding !alacritty to the seed. ! usually does not make any difference but 
maybe it would here?

You probably want to get this working in oracular before trying to
backport whatever is successful to the noble seed.

Unfortunately, because there is nothing depending on alacritty, I do not
believe it is possible for alacritty to be automatically safely removed
from people's computers who install Ubuntu Cinnamon using Ubuntu 23.10
or the original 24.04 LTS, but it can be excluded from the 24.04.1 LTS
ISO that will be published a few months from now.

Additional info about how it got seeded and if it is working

https://ubuntu-archive-team.ubuntu.com/germinate-output/ubuntucinnamon.noble/
https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/noble/ubuntucinnamon/
https://cdimage.ubuntu.com/ubuntucinnamon/daily-live/current/ (especially the 
manifest file)

** Affects: ubuntucinnamon-meta (Ubuntu)
 Importance: Undecided
 Status: Triaged


** Tags: noble

-- 
You received this bug notification because you are a member of Ubuntu
Cinnamon Developers, which is subscribed to ubuntucinnamon-meta in
Ubuntu.
https://bugs.launchpad.net/bugs/2064166

Title:
  Exclude alacritty from Ubuntu Cinnamon ISOs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntucinnamon-meta/+bug/2064166/+subscriptions


-- 
universe-bugs mailing list
universe-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/universe-bugs


[Bug 2064112] Re: mk-sbuild fails to add user to group on first run if $USER is not set

2024-04-29 Thread Benjamin Drung
** Summary changed:

- mk-sbuild fails to add user to group on first run
+ mk-sbuild fails to add user to group on first run if $USER is not set

-- 
You received this bug notification because you are a member of MOTU,
which is subscribed to ubuntu-dev-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2064112

Title:
  mk-sbuild fails to add user to group on first run if $USER is not set

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/2064112/+subscriptions


-- 
universe-bugs mailing list
universe-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/universe-bugs


[Bug 2064112] Re: mk-sbuild fails to add user to group on first run

2024-04-29 Thread James Howe
Sorry, I was running in a Docker container, and $USER was undefined.

** Changed in: ubuntu-dev-tools (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of MOTU,
which is subscribed to ubuntu-dev-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2064112

Title:
  mk-sbuild fails to add user to group on first run

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/2064112/+subscriptions


-- 
universe-bugs mailing list
universe-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/universe-bugs


[Bug 2064112] [NEW] mk-sbuild fails to add user to group on first run

2024-04-29 Thread James Howe
Public bug reported:

/usr/bin/mk-sbuild line 301:

sudo adduser "$USER" sbuild

should be:

sudo usermod -a -G sbuild "$USER"

otherwise it fails with the message:

fatal: Only one or two names allowed.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: ubuntu-dev-tools 0.201ubuntu2
Uname: Linux 5.15.146.1-microsoft-standard-WSL2 x86_64
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CloudBuildName: ubuntu-oci:minimized
CloudSerial: 20240423
Date: Mon Apr 29 11:54:10 2024
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 TERM=xterm
SourcePackage: ubuntu-dev-tools
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-dev-tools (Ubuntu)
 Importance: Undecided
 Status: Invalid


** Tags: amd64 apport-bug cloud-image noble

** Description changed:

  /usr/bin/mk-sbuild line 301:
  
- sudo adduser "$USER" sbuild
+ sudo adduser "$USER" sbuild
  
  should be:
  
- sudo adduser "$USER" -G sbuild
+ sudo usermod -a -G sbuild "$USER"
  
  otherwise it fails with the message:
  
- fatal: Only one or two names allowed.
+ fatal: Only one or two names allowed.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: ubuntu-dev-tools 0.201ubuntu2
  Uname: Linux 5.15.146.1-microsoft-standard-WSL2 x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CloudBuildName: ubuntu-oci:minimized
  CloudSerial: 20240423
  Date: Mon Apr 29 11:54:10 2024
  PackageArchitecture: all
  ProcEnviron:
-  PATH=(custom, no user)
-  TERM=xterm
+  PATH=(custom, no user)
+  TERM=xterm
  SourcePackage: ubuntu-dev-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of MOTU,
which is subscribed to ubuntu-dev-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2064112

Title:
  mk-sbuild fails to add user to group on first run

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/2064112/+subscriptions


-- 
universe-bugs mailing list
universe-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/universe-bugs