tprasadtp / ubuntu-post-install Goto Github PK

As described, when used with gists, it fails to parse options and reverts to defaults. Probably because script uses two spaces for indentation and assumes so.
Temporary solution, use default yaml from config folder as template and edit it to your requirements. Don't copy paste it to gist. It will fail. Use -Y -C config.yaml option.

Support for 20.04 is pending. Though at the moment you can use it with --pre-release flag.

Why is this list of categories is strict?

What about adding custom cateogry?

With YAML Schema, it is easy to know which data we can write.

Actually, for JSON Schema there are a lot of auto generator engines for creating a form to build the JSON.

I think if someone knows about a generator for YAML it will be good.

Examples:

• https://containership.github.io/konstellate-editor/: Not by schema and written by Clojure lang. But it is good and it also shows the documentation.
• https://github.com/json-editor/json-editor: I think it the most known library, used by Swagger, but it does not support YAML as you can see here: json-editor/json-editor#772 (example)

You know what? Maybe we can use a JSON builder and convert the output to YAML?

Upgrade Packages functionality waits for input from user whether to write a new configuration file or to keep existing configuration files, if they have been changed (noticed on mint 17.3). Script waits for input forever.

Hi, one of the features I'm looking for in this context (but after found your project I prefer it even without them), is to also reconfigure my .bashrc changes.

I can list some use cases in ascending order according to complexity:

• Run custom command. For example, configure my git by git config --global user.name "my name"
• re-configure my aliases, just for example alias cd=pushd
• re-configure config file, for example, just download my git config file from remote URL to the right place.
• Add lines to the .bashrc (or link to these lines in another file), for example, oh-my-zsh configs.

/shared/after-effects -s -y
Fails to use the files as the paths are relative to after-effects

[   Installing  ] packages from list :./data/utilities.list:
cat: ./data/utilities.list: No such file or directory
package list to install is empty!!
[   Installing  ] packages from list :./data/security.list:
cat: ./data/security.list: No such file or directory

Support Flatpak packages.

First, I'd like to say that this is a very good project, really help me and saved me a lot of time.
Secondly, I try to install vscode with snap:

    snaps:
      classic:
        - vscode

and an error happened:

[sáb set 28 18:47:09 -03 2019] [     Info      ] Installig Snaps [Classic Packages]
[sáb set 28 18:47:09 -03 2019] [    Snap PKG   ] vscode...
[sáb set 28 18:47:10 -03 2019] [    Snap PKG   ] error: This revision of snap "vscode" was published using classic confinement and thus may perform
[sáb set 28 18:47:10 -03 2019] [    Snap PKG   ]        arbitrary system changes outside of the security sandbox that snaps are usually confined to,
[sáb set 28 18:47:10 -03 2019] [    Snap PKG   ]        which may put your system at risk.
[sáb set 28 18:47:10 -03 2019] [    Snap PKG   ] 
[sáb set 28 18:47:10 -03 2019] [    Snap PKG   ]        If you understand and want to proceed repeat the command including --classic.
[sáb set 28 18:47:10 -03 2019] [     Oh No!    ] Some Error occured while installing .

It seems that the snap option --classic isn't been used to install the app. Is this a bug?

When using non-autopilot mode let user choose multiple actions (instead of just one) in whiptail dialog.

Hey,

found your cool script in the net, and played around with it in a VM.
I tried to purge the games from your config, but it is not working.

 ~/shared  sudo ./after-effects -c ae.yml -d -A
✈ Initialize & run checks
  ➜ Permission checks
  ✔ Running as root 
  ✦ Using local config file
  ✦ Purge packages is set to true.
  ⚠ No checks are being made on the packages in the list. 
  ⚠ Use carefully!. Purging system packages is stupid idea! 
  ⚠ $bool_purge_pkgs=true  <------ HERE
  ➜ Checking dependencies...
  ✦ Hostname      : osboxes
  ✦ OS            : Ubuntu 20.04 LTS
  ✦ Distro        : Ubuntu
  ✦ Code Name     : bionic
  ✦ Arch          : amd64
  ✦ Version/Number: 6.1.0-RC1/610
  ➜ Check for conflicting apps...
  ✔ No conflicts detected. 
  ➜ Checking connectivity
  ✔ Connected! 
✈ Running environment checks... 
✈ Checking for Ubuntu derivates/Debian 
  ➜ This is a LTS release of Ubuntu
  ✔ Keeping the codename as: bionic. 
  ✔ Applied release specific settings and fixes. 
✈ Check if config is defined 
✈ Checking for updates 
  ✔ Running the latest and greatest! 
  ⚠ $bool_purge_pkgs=true  <------ HERE 
✈ Processing configuration... 
  ✦ Config file - ae.yml
  ➜ Parsing config file 
  ⚠ $bool_purge_pkgs=false  <------ HERE 
✈ Check if autopilot is set/required 
  ✔ Autopilot is ENABLED 
  ⚠ $bool_purge_pkgs=false  <------ HERE 
✖ Purge switch is set to false. Did you pass -d along with the command? 

After processing the config the variable $bool_purge_pkgs was set back to false

At least I've to set

config:
  # Enabled Tasks
  tasks:
    purge: true
  flags:
    purge_enabled: true

to make it working, but according to your documentation

Warning
It is necessary to pass command line argument -d or set config.flags.purge_enabled: true in config.

only one of these is needed. With config.flags.purge_enabled: true the parameter -d has no effect.

Kind regards
Frank

Good day,

I've noticed that you're "setting UMASK to 0022 for the script to avoid APT errors" on line 1418 of the script. Can you please elaborate on the relation between the two? Is this how you deal with packagekitd locking the file /var/lib/apt/lists/lock during apt updates? Why not to disable the apt-daily*** services and then re-enable them when necessary instead?

I'm asking because I'm working on a similar but less sophisticated script myself for Pop!_OS and currently stuck with an apt problem caused by packagekitd, as I described above. To solve it, I simply stop the daemon, which is re-started by apt during the update anyway.

Thank you!

Do you expect more than one run per machine?

Because for building my config, every new software I want to install, I adding it to the config first, then running the script again.

Now I'm getting a lot of this:

Wed 27 Jan 21:56:58 IST 2021 [EXT] (APT) W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:58 and /etc/apt/sources.list.d/github-cli.list:1
Wed 27 Jan 21:56:58 IST 2021 [EXT] (APT) W: Target Packages (main/binary-i386/Packages) is configured multiple times in /etc/apt/sources.list:58 and /etc/apt/sources.list.d/github-cli.list:1
Wed 27 Jan 21:56:58 IST 2021 [EXT] (APT) W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:58 and /etc/apt/sources.list.d/github-cli.list:1

I know this warning. I'm asking if you considering it as a bug or it just not the right using of your script.

BTW, sorry for just opening issues without contributing. We need to be patient, because I almost don't know bash, so I will contribute when I will feel the invest worth the value :-)