terrywang / vagrantboxes Goto Github PK
View Code? Open in Web Editor NEWHandcrafted Arch Linux Vagrant base box with :heart:
Handcrafted Arch Linux Vagrant base box with :heart:
Hi!
I have modified my Vagrantfile and uncomment following lines for booting with gui:
config.vm.provider :virtualbox do |vb|
# Don't boot with headless mode
vb.gui = true
end
But the box starts every time in headless mode?
Kind regards
Torsten Kleiber
Due to pacman 4.2 changing database format and new community package manager added to the keyring the upgrading process is not seamless.
Hi,
I have an error executing a simple vagrant up
with the following Vagrantfile:
Vagrant.configure(2) do |config|
config.vm.define "dev" do |dev|
dev.vm.box = "archlinux-x86_64"
dev.vm.box_url = "http://cloud.terry.im/vagrant/archlinux-x86_64.box"
dev.vm.network :private_network, ip: "192.168.42.11" # PROBLEMATIC LINE
end
end
Log output:
$ vagrant up
Bringing machine 'dev' up with 'virtualbox' provider...
==> dev: Importing base box 'archlinux-x86_64'...
==> dev: Matching MAC address for NAT networking...
==> dev: Setting the name of the VM: ttp
==> dev: Clearing any previously set network interfaces...
==> dev: Preparing network interfaces based on configuration...
dev: Adapter 1: nat
dev: Adapter 2: hostonly
==> dev: Forwarding ports...
dev: 22 => 2222 (adapter 1)
==> dev: Running 'pre-boot' VM customizations...
==> dev: Booting VM...
==> dev: Waiting for machine to boot. This may take a few minutes...
dev: SSH address: 127.0.0.1:2222
dev: SSH username: vagrant
dev: SSH auth method: private key
dev: Warning: Connection timeout. Retrying...
==> dev: Machine booted and ready!
==> dev: Checking for guest additions in VM...
==> dev: Configuring and enabling network interfaces...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
ip link set eth1 down
Stdout from the command:
Stderr from the command:
Cannot find device "eth1"
Do you have an idea about this? The machine is booted up, I can do a vagrant ssh
, but the shared /vagrant folder does not exist.
Now, if I delete the line with the comment in the Vangrantfile, everything works fine.
Not really a bug, but why is /home
a separate, smaller filesystem? If I'd like to make use of the entire 10GB default storage allocation, this configuration makes things more difficult.
I'm using this simple vagrant file:
Vagrant.configure("2") do |config|
config.vm.define "acs" do |acs|
acs.vm.box = "ubuntu/trusty64"
acs.vm.hostname = "acs"
acs.vm.network "private_network", ip: "192.168.33.10"
end
config.vm.define "temp" do |temp|
temp.vm.box = "terrywang/archlinux"
temp.vm.hostname = "temp"
temp.vm.network "private_network", ip: "192.168.33.50"
end
config.vm.define "temp2" do |temp2|
temp2.vm.box = "ubuntu/trusty64"
temp2.vm.hostname = "temp2"
temp2.vm.network "private_network", ip: "192.168.33.60"
end
end
After vagrant up
I go to acs
and try a ping to temp and temp2. Ubuntu works, but Arch fails.
PS: I'm new to Vagrant so I might be missing something obvious, but found it odd given the fresh installs.
It would be nice if there was a box for the libvirt provider.
I had to run 'yum -y install puppet' in order for puppet to work. Perhaps this should be already installed in the box??
The new kernel may have some problems for archlinux box. Such as
The combination of linux-4.17.2-1 and virtualbox-guest-dkms-5.2.12-2 caused mouse clicking and scrolling to fail in strange ways, but reverting to linux-4.16.9-1 and virtualbox-guest-dkms-5.2.12-1 works until the issue is resolved.
The Arch image no longer updates (pacman -Syu
) without manual intervention because of a known issue with ca-certificats-utils
, see https://www.archlinux.org/news/ca-certificates-utils-20170307-1-upgrade-requires-manual-intervention/
It'd be great if you could include it, thanks!
Hi,
thanks for your hard work by providing this great box.
I could not get password-less sudo working. It's always asking for a password. And "vagrant" as PW is not accepted. Is /etc/sudoers
probably lacking:
vagrant ALL=(ALL) NOPASSWD: ALL
Thanks Marc
Issue: The oracle64 and oracle59 boxes have Ruby 2.0.0-p195 installed, which has rubygems 2.0.x, causing chef-solo
runs to fail.
$ chef-solo -v
/home/terry/.rbenv/versions/2.0.0-p195/lib/ruby/site_ruby/2.0.0/rubygems/core_ext/kernel_require.rb:45:in `require': cannot load such file -- rubygems/format (LoadError)
Cause: Chef CHEF-3933
Workaround: Downgrade rubygems to 1.8.25
gem update --system 1.8.25
We noticed your box has the old up2date
package still installed. yum
replaced this package, so I would guess you should remove it as well from the vagrant box image. By the way, this was for the 5.11 vagrant box.
When I did vagrant up
on the archlinux box, I got the following error:
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
The guest machine entered an invalid state while waiting for it
to boot. Valid states are 'starting, running'. The machine is in the
'poweroff' state. Please verify everything is configured
properly and try again.
If the provider you're using has a GUI that comes with it,
it is often helpful to open that and watch the machine, since the
GUI often has more helpful error messages than Vagrant can retrieve.
For example, if you're using VirtualBox, run `vagrant up` while the
VirtualBox GUI is open.
Manually starting the powered off instance from VirtualBox gives me the following error:
Failed to open session for the virtual machine arch_default_xxx
Implementation of the USB 2.0 controller not found!
Because the USB 2.0 controller state is part of the saved VM state, the VM cannot be started. To fix this problem, either install the 'Oracle VM VirtualBox Extension Pack' or disable USB 2.0 support in the VM settings (VERR_NOT_FOUND).
Is the USB 2.0 controller required by default to run this VM? Or is there something wrong with my config?
Cheers!
vm.box = "terrywang/archlinux"
$ vagrant ssh arch64
Last login: Mon Feb 1 12:15:15 2016
vagrant@archlinux:~$ cd /vagrant/
-bash: cd: /vagrant/: Permission denied
On my host, where I to the best of my knowledge have never changed the umask:
$ sudo bash -c umask
0022
$ grep ^umask /etc/profile
umask 022
On the Arch Linux Vagrant box:
vagrant@archlinux:~$ sudo bash -c umask
0027
vagrant@archlinux:~$ grep ^umask /etc/profile
umask 022
vagrant@archlinux:~$ sudo grep ^umask /root/.profile
umask 027
Why is this more restrictive than normal?
Got this issue with vagrant 1.7.x
$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'arch64' could not be found. Attempting to find and install...
default: Box Provider: virtualbox
default: Box Version: >= 0
==> default: Adding box 'arch64' (v0) for provider: virtualbox
default: Downloading: http://cloud.terry.im/vagrant/archlinux-x86_64.box
==> default: Box download is resuming from prior download progress
==> default: Successfully added box 'arch64' (v0) for 'virtualbox'!
==> default: Importing base box 'arch64'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: myproject_default_1419353941248_40826
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
default: Adapter 2: hostonly
==> default: Forwarding ports...
default: 22 => 2222 (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2222
default: SSH username: vagrant
default: SSH auth method: private key
default: Warning: Connection timeout. Retrying...
default:
default: Vagrant insecure key detected. Vagrant will automatically replace
default: this with a newly generated keypair for better security.
default:
default: Inserting generated public key within guest...
default: Removing insecure key from the guest if its present...
default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
==> default: Configuring and enabling network interfaces...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
mv /tmp/vagrant_network
/etc/netctl/
Stdout from the command:
Stderr from the command:
mv: missing destination file operand after ‘/tmp/vagrant_network’
Try 'mv --help' for more information.
bash: line 3: /etc/netctl/: Is a directory
This is a follow up of #25. Thanks for so quickly releasing a fixed image. However, there seems to be a problem obtaining it from atlas.hashicorp.com (404):
$ vagrant box update
==> default: Checking for updates to 'terrywang/archlinux'
default: Latest installed version: 1.0.0
default: Version constraints:
default: Provider: virtualbox
==> default: Updating 'terrywang/archlinux' with provider 'virtualbox' from version
==> default: '1.0.0' to '201704'...
==> default: Loading metadata for box 'https://atlas.hashicorp.com/terrywang/archlinux'
==> default: Adding box 'terrywang/archlinux' (v201704) for provider: virtualbox
default: Downloading: https://atlas.hashicorp.com/terrywang/boxes/archlinux/versions/201704/providers/virtualbox.box
An error occurred while downloading the remote file. The error
message, if any, is reproduced below. Please fix this error and try
again.
The requested URL returned error: 404 Not Found
Same thing if I delete it manually and re-add instead of update:
$ vagrant box add terrywang/archlinux
==> box: Loading metadata for box 'terrywang/archlinux'
box: URL: https://atlas.hashicorp.com/terrywang/archlinux
==> box: Adding box 'terrywang/archlinux' (v201704) for provider: virtualbox
box: Downloading: https://atlas.hashicorp.com/terrywang/boxes/archlinux/versions/201704/providers/virtualbox.box
An error occurred while downloading the remote file. The error
message, if any, is reproduced below. Please fix this error and try
again.
The requested URL returned error: 404 Not Found
Is there something I'm missing or did it not get published correctly?
Oracle Linux 7.0 x86_64 Vagrant base box is missing the package libselinux-ruby
, which is required by puppet
.
NOTE: This affects the Veewee definition for Oracle Linux 7.0 as well.
Looks like Oracle Linux 7.0 base repo (Public YUM) does NOT have libselinux-ruby
for some reason. RHEL 7 Install DVD doesn't have it either but somehow CentOS 7 does.
This issue will be kept open as a place holder until Oracle provides the package via Public YUM.
Temporary workaround is to borrow the package from CentOS 7 simply by using the command below and then do yum install puppet
.
rpm -ivh http://mirror.centos.org/centos/7/os/x86_64/Packages/libselinux-ruby-2.2.2-6.el7.x86_64.rpm
When running yum-builddep kernel
, it'll report missing asciidoc
. The same command works flawlessly on CentOS 7.0.
Workaround is similar to #6 borrow the package (and its deps) from CentOS 7.
vagrant box add ol5 http://cloud.terry.im/vagrant/oraclelinux-5-x86_64.box
getting Proxy Configuration from Host...
==> box: Box file was not detected as metadata. Adding it directly...
==> box: Adding box 'ol5' (v0) for provider:
box: Downloading: http://cloud.terry.im/vagrant/oraclelinux-5-x86_64.box
box:
An error occurred while downloading the remote file. The error
message, if any, is reproduced below. Please fix this error and try
again.
Hi,
looks like your dropbox public account is generating too much traffic (victim of its own success ??) ;(
The requested URL returned error: 509 Bandwidth Error
Any chance to get your boxes from another source ?
thanks for sharing anyway
ozb
Vagrant box: Arch Linux x86_64 Base Box
I don't know if this is intended but the configuration for tmux specifies bind C-a send-prefix
but then some lines down also bind-key C-a last-window
.
It seems C-a
is effectively bound to last-window
with send-prefix
unbound.
P.S.: What is the difference between bind
and bind-key
? the manual does not mention this.
First of all I'm not really sure if the issue came form your box or from salt or vagrant.
Bootstraping salt master is not working with your Archlinux vagrant box but it work fine with xezpeleta/wheezy64 box for example. And it work if the only part to install is the minion.
Here is the output of vagrant up
:
Writing /usr/lib/python2.7/site-packages/salt-2014.7.0rc1-py2.7.egg-info
* INFO: Running install_arch_linux_git_post()
* WARN: /tmp/git/salt/pkg/rpm/salt-api.service does not exist!
* INFO: Running install_arch_linux_restart_daemons()
Job for salt-master.service failed. See 'systemctl status salt-master.service' and 'journalctl -xn' for details.
* INFO: Running daemons_running()
* ERROR: salt-master was not found running
* ERROR: Failed to run daemons_running()!!!
* ERROR: salt-minion was not found running. Pass '-D' to bootstrap-salt.sh when bootstrapping for additional debugging information...
* ERROR: salt-master was not found running. Pass '-D' to bootstrap-salt.sh when bootstrapping for additional debugging information...
There is what sudo systemctl status salt-master.service
return:
● salt-master.service - The Salt Master Server
Loaded: loaded (/usr/lib/systemd/system/salt-master.service; enabled)
Active: failed (Result: timeout) since Sat 2014-09-13 00:28:59 AEST; 21min ago
Process: 3539 ExecStart=/usr/bin/salt-master (code=exited, status=0/SUCCESS)
Main PID: 3539 (code=exited, status=0/SUCCESS)
Sep 13 00:28:59 dev-noisette systemd[1]: salt-master.service start operation timed out. Terminating.
Sep 13 00:28:59 dev-noisette salt-master[3539]: [WARNING ] Caught signal 15, stopping the Salt Master
Sep 13 00:28:59 dev-noisette salt-master[3539]: [WARNING ] Caught signal 15, stopping the Salt Master
Sep 13 00:28:59 dev-noisette salt-master[3539]: [WARNING ] Caught signal 15, stopping the Salt Master
Sep 13 00:28:59 dev-noisette salt-master[3539]: [WARNING ] Caught signal 15, stopping the Salt Master
Sep 13 00:28:59 dev-noisette salt-master[3539]: [WARNING ] Caught signal 15, stopping the Salt Master
Sep 13 00:28:59 dev-noisette salt-master[3539]: [WARNING ] Caught signal 15, stopping the Salt Master
Sep 13 00:28:59 dev-noisette systemd[1]: Failed to start The Salt Master Server.
Sep 13 00:28:59 dev-noisette systemd[1]: Unit salt-master.service entered failed state.
Here is my Vagrantfile:
VAGRANTFILE_API_VERSION = "2"
Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
config.vm.box = "terrywang/archlinux"
config.vm.synced_folder "salt/roots/", "/srv/salt/"
config.vm.provision :salt do |salt|
salt.install_type = 'git'
salt.install_args = 'v2014.7.0rc1'
salt.install_master = true
salt.master_config = "salt/master"
salt.minion_config = "salt/minion"
salt.colorize = true
salt.log_level = "all"
end
end
After struggling for a while with no gems being available on the path after installation (as root or vagrant), it seems the reason is the /etc/gemrc
containing --user-install
. Is this necessary for the proper functioning of the VM?
It would be nice if we have an nfs client in the Oracle Linux box.
I'm presently trying the Oracle 6.5 x86-64 box with vagrant and it's failing because I'm using nfs-based synced folders. It's not easy to fix it by adding nfs client
as provisioning step since nfs mount is attempted before the provisioning.
My current manual fix is to install nfs-utils
package.
Hello Terry. I use your boxes for my open source projects on github. I found that there is a simpler way how to share these boxes than using one's own site. It is called Atlas (by hashicorp). I hope it is free :) The nice thing is that you don't need to specify URL in your vagrantfile, you put there only e.g. terrywang/oraclelinux7 and that's it.
What do you think about it? Did you consider this option?
Thanks in advance for your response and thanks for your boxes! 👍
Thanks for creating this box and I've been using this for a while.
One thing that bothers me is that this box does not support NFS by default, which is kind of a must if you are trying to use vagrant file sharing feature. Please consider install nfs-utils and enable related services.
I'm using this box: http://cloud.terry.im/vagrant/archlinux-x86_64.box
I get this when I run vagrant up
:
default: /vagrant => /home/djhaskin987/Workspace/libgpg-error-git
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
mkdir -p /vagrant
Stdout from the command:
Stderr from the command:
We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:
#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.
sudo: no tty present and no askpass program specified
The synced folder does not show up:
$ vagrant ssh
Last login: Mon Aug 25 10:13:20 2014
vagrant@archlinux:~$ ls /
bin boot dev etc home lib lib64 lost+found mnt opt proc root run sbin srv sys tmp usr var
get puppet installed.
It seems that the state of the arch packages in your box has some issues regarding doing a full system upgrade due to libxfont
.
vagran
vagrant up
vagrant ssh
yaourt -Syua --noconfirm
vagrant@archlinux:~$ yaourt -Syua --noconfirm
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
archlinuxfr is up to date
Foreign packages: | 20 / 20
==> Package upgrade only (new release):
core/binutils 2.29.1-1 1 -> 2
core/bzip2 1.0.6-6 6 -> 7
core/glibc 2.26-5 5 -> 11
core/grub 2:2.02-3 3 -> 4
core/iptables 1.6.1-1 1 -> 2
core/ldns 1.7.0-3 3 -> 4
core/libsasl 2.1.26-11 11 -> 12
core/libseccomp 2.3.2-1 1 -> 2
core/libtirpc 1.0.2-1 1 -> 3
core/libtool 2.4.6+40+g6ca5e224-1 1 -> 4
core/openssh 7.6p1-1 1 -> 2
core/perl 5.26.1-1 1 -> 2
core/procps-ng 3.3.12-1 1 -> 2
core/rpcbind 0.2.4-3 3 -> 4
core/shadow 4.5-2 2 -> 4
extra/libice 1.0.9-1 1 -> 2
extra/libxau 1.0.8-2 2 -> 3
extra/libxdamage 1.1.4-2 2 -> 3
extra/libxfixes 5.0.3-1 1 -> 2
extra/libxrandr 1.5.1-1 1 -> 2
extra/python2 2.7.14-1 1 -> 2
extra/zsh 5.4.2-1 1 -> 2
community/glances 2.11.1-1 1 -> 2
community/schedtool 1.3.0-3 3 -> 4
community/tmux 2.6-1 1 -> 2
aur/srm 1.2.15-1 1 -> 2
==> Software upgrade (new version) :
core/archlinux-keyring 20171020-1 -> 20180108-1
core/bash 4.4.012-2 -> 4.4.018-1
core/btrfs-progs 4.13-1 -> 4.15-1
core/ca-certificates-mozilla 3.33-2 -> 3.35-1
core/coreutils 8.28-1 -> 8.29-1
core/cryptsetup 1.7.5-1 -> 2.0.1-1
core/curl 7.56.1-1 -> 7.58.0-1
core/dbus 1.12.0-1 -> 1.12.4-1
core/device-mapper 2.02.175-1 -> 2.02.177-1
core/e2fsprogs 1.43.7-1 -> 1.43.9-1
core/expat 2.2.4-1 -> 2.2.5-1
core/filesystem 2017.03-2 -> 2017.10-2
core/gawk 4.1.4-2 -> 4.2.0-3
core/gcc 7.2.0-3 -> 7.3.0-1
core/gcc-libs 7.2.0-3 -> 7.3.0-1
core/gdbm 1.13-1 -> 1.14.1-1
core/glib2 2.54.2-2 -> 2.54.3+2+g94b38beff-1
core/gnupg 2.2.1-1 -> 2.2.4-2
core/gnutls 3.5.16-1 -> 3.5.17-1
core/gpgme 1.9.0-3 -> 1.10.0-1
core/gzip 1.8-2 -> 1.9-1
core/hwids 20170715-1 -> 20171003-1
core/iana-etc 20170824-1 -> 20180131-1
core/icu 59.1-2 -> 60.2-1
core/iproute2 4.13.0-1 -> 4.15.0-1
core/json-c 0.12.1-1 -> 0.13-1
core/krb5 1.15.2-1 -> 1.16-1
core/libassuan 2.4.3-1 -> 2.5.1-1
core/libgcrypt 1.8.1-1 -> 1.8.2-1
core/libmpc 1.0.3-2 -> 1.1.0-1
core/libnftnl 1.0.7-1 -> 1.0.9-1
core/libnghttp2 1.23.1-1 -> 1.29.0-1
core/libpipeline 1.4.2-1 -> 1.5.0-1
core/libpsl 0.18.0-1 -> 0.19.1-1
core/libsystemd 235.38-1 -> 237.31-1
core/libtasn1 4.12-2 -> 4.13-1
core/libunistring 0.9.7-1 -> 0.9.8-1
core/libutil-linux 2.31-1 -> 2.31.1-1
core/linux 4.13.11-1 -> 4.15.3-1
core/linux-api-headers 4.12.7-1 -> 4.14.8-1
core/linux-firmware 20171009.bf04291-1 -> 20180119.2a713be-1
core/linux-headers 4.13.11-1 -> 4.15.3-1
core/logrotate 3.12.3-1 -> 3.13.0-1
core/lvm2 2.02.175-1 -> 2.02.177-1
core/lz4 1:1.8.0-1 -> 1:1.8.1.2-1
core/man-db 2.7.6.1-2 -> 2.8.1-1
core/man-pages 4.13-1 -> 4.15-1
core/mpfr 3.1.5.p2-1 -> 4.0.0-1
core/nano 2.8.7-1 -> 2.9.3-1
core/netctl 1.14-1 -> 1.15-1
core/nettle 3.3-1 -> 3.4-1
core/nfsidmap 0.26-1 -> 2.3.1-1
core/nfs-utils 2.1.1-4 -> 2.3.1-1
core/pacman-mirrorlist 20171027-1 -> 20180203-1
core/patch 2.7.5-1 -> 2.7.6-1
core/pciutils 3.5.5-1 -> 3.5.6-1
core/pinentry 1.0.0-1 -> 1.1.0-1
core/reiserfsprogs 3.6.25-1 -> 3.6.27-1
core/run-parts 4.8.1-1 -> 4.8.3-1
core/s-nail 14.9.5-1 -> 14.9.6-1
core/sqlite 3.21.0-1 -> 3.22.0-1
core/sudo 1.8.21.p2-1 -> 1.8.22-1
core/systemd 235.38-1 -> 237.31-1
core/systemd-sysvcompat 235.38-1 -> 237.31-1
core/tar 1.29-2 -> 1.30-1
core/thin-provisioning-tools 0.7.4-1 -> 0.7.5-1
core/tzdata 2017c-1 -> 2018c-1
core/usbutils 008-1 -> 009-1
core/util-linux 2.31-1 -> 2.31.1-1
core/xfsprogs 4.12.0-1 -> 4.14.0-1
extra/bind-tools 9.11.2-2 -> 9.12.0-1
extra/dkms 2.4.0-2 -> 2.5-1
extra/ethtool 1:4.13-1 -> 1:4.15-1
extra/expect 5.45-4 -> 5.45.3-1
extra/fontconfig 2.12.6-1 -> 2.12.6+5+g665584a-1
extra/freetype2 2.8.1-1 -> 2.9-2
extra/fuse3 3.2.0-1 -> 3.2.1-1
extra/fuse-common 3.2.0-1 -> 3.2.1-1
extra/gdb 8.0.1-1 -> 8.1-1
extra/gdb-common 8.0.1-1 -> 8.1-1
extra/geoip-database 20171007-1 -> 20180206-1
extra/git 2.15.0-1 -> 2.16.1-1
extra/guile 2.2.2-1 -> 2.2.3-1
extra/harfbuzz 1.6.3-1 -> 1.7.5-1
extra/htop 2.0.2-2 -> 2.1.0-1
extra/libatomic_ops 7.4.6-1 -> 7.6.2-1
extra/libdrm 2.4.87-1 -> 2.4.89-1
extra/libevdev 1.5.7-1 -> 1.5.8-1
extra/libglvnd 0.2.999+g4ba53457-2 -> 1.0.0-1
extra/libinput 1.9.1-1 -> 1.9.4-1
extra/libnetfilter_queue 1.0.2-2 -> 1.0.3-1
extra/libwacom 0.24-1 -> 0.27-1
extra/libxfont2 2.0.2-1 -> 2.0.3-1
extra/libxml2 2.9.5+6+g07e227ed-1 -> 2.9.7+4+g72182550-2
extra/llvm-libs 5.0.0-1 -> 5.0.1-2
extra/mesa 17.2.4-1 -> 17.3.3-2
extra/nftables 1:0.7-3 -> 1:0.8.2-1
extra/python 3.6.3-1 -> 3.6.4-2
extra/python-setuptools 1:36.6.0-1 -> 1:38.5.1-1
extra/recode 3.6-10 -> 3.7-1
extra/rsync 3.1.2-8 -> 3.1.3-1
extra/ruby 2.4.2-1 -> 2.5.0-4
extra/strace 4.19-1 -> 4.20-1
extra/tcl 8.6.7-1 -> 8.6.8-1
extra/vim 8.0.1272-1 -> 8.0.1476-1
extra/vim-runtime 8.0.1272-1 -> 8.0.1476-1
extra/wget 1.19.2-1 -> 1.19.4-1
extra/whois 5.2.18-1 -> 5.2.20-1
extra/xkeyboard-config 2.22-1 -> 2.23.1-2
extra/xorg-bdftopcf 1.0.5-1 -> 1.1-1
extra/xorg-server 1.19.5-1 -> 1.19.6+13+gd0d1a694f-1
extra/xorg-server-common 1.19.5-1 -> 1.19.6+13+gd0d1a694f-1
community/ack 2.18-3 -> 2.22-1
community/aria2 1.33.0-1 -> 1.33.1-1
community/dd_rescue 1.99.5-1 -> 1.99.8-1
community/fortune-mod 1.99.1-6 -> 1.99.5-1
community/hwinfo 21.38-1 -> 21.50-1
community/inxi 2.3.43-1 -> 2.3.56-1
community/libconfig 1.6-2 -> 1.7.2-1
community/libmicrohttpd 0.9.55-1 -> 0.9.59-1
community/lynis 2.5.7-1 -> 2.6.1-1
community/moreutils 0.61-1 -> 0.62-1
community/ncdu 1.12-1 -> 1.13-1
community/ngrep 1.45-12 -> 1.47-1
community/oniguruma 6.6.1-1 -> 6.7.1-1
community/python-psutil 5.4.0-1 -> 5.4.3-1
community/ranger 1.8.1-1 -> 1.9.0-1
community/ripgrep 0.7.1-1 -> 0.8.0-1
community/sslh 1.18-3 -> 1.19c-1
community/sysstat 11.4.6-1 -> 11.6.2-1
community/tig 2.3.0-1 -> 2.3.2-1
community/vifm 0.9-1 -> 0.9.1-1
community/virtualbox-guest-dkms 5.2.0-1 -> 5.2.6-2
community/virtualbox-guest-utils 5.2.0-1 -> 5.2.6-2
aur/entr 3.9-1 -> 4.0-1
aur/makeself 2.3.0-2 -> 2.3.1-0
==> New package :
core/argon2 20171227-3 (required by cryptsetup)
core/libidn2 2.0.4-2 (required by libpsl)
core/zstd 1.3.3-1 (required by btrfs-progs)
The resulting issue:
==> Continue upgrade ? [Y/n]
==> [V]iew package detail [M]anually select packages
==> --------------------------------------------------
==> :: Starting full system upgrade...
:: Replace compositeproto with extra/xorgproto? [Y/n]
:: Replace damageproto with extra/xorgproto? [Y/n]
:: Replace fixesproto with extra/xorgproto? [Y/n]
:: Replace fontsproto with extra/xorgproto? [Y/n]
:: Replace kbproto with extra/xorgproto? [Y/n]
:: Replace randrproto with extra/xorgproto? [Y/n]
:: Replace renderproto with extra/xorgproto? [Y/n]
:: Replace xextproto with extra/xorgproto? [Y/n]
:: Replace xf86vidmodeproto with extra/xorgproto? [Y/n]
:: Replace xproto with extra/xorgproto? [Y/n]
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: libxfont: removing fontsproto breaks dependency 'fontsproto>=2.1.3'
Also, it seems that srm fails to build with
==> Continue building srm ? [Y/n]
==> -----------------------------
==>
==> Building and installing package
==> Making package: srm 1.2.15-2 (Wed Feb 14 16:00:43 AEDT 2018)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Downloading srm-1.2.15.tar.gz...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 652 100 652 0 0 2608 0 --:--:-- --:--:-- --:--:-- 2608
==> Validating source files with sha512sums...
srm-1.2.15.tar.gz ... FAILED
==> ERROR: One or more files did not pass the validity check!
==> ERROR: Makepkg was unable to build srm.
==> Restart building srm ? [y/N]
==> ----------------------------
I am not clear on what srm, libxfont, and fontsproto are for, but it seems they are blocking the user from being able to do a good ole yaourt -Syua
.
Would you be OK with including the veewee (or other) files used to create the Arch Linux box? I'd like to fork them for my own nefarious purposes :)
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.