Fresh bite-sized bugs in snappy

Do you remember my previous post about bite-sized bugs in snappy? Those are bugs that are small and trivial to fix. A perfect way to get involved in a project or to get your feet wet in a new programming language.

I've just noticed that there are plenty of new bugs that have been tagged  "bitesized" in Snapcraft. As before I'd like to extend my invitation to the the community to have a look and send patches, pull requests or just a ping if they are interested in fixing them.

It usually takes just a few moments to understand the bug and a few moments to come up with a fix locally. While you do that you'll learn a lot about how the project works and, perhaps, you will make your first public contribution to a free software project (I remember how the journey started for me years ago :-)

Please give it a try, you can always ping us in #snappy on Freenode with any questions.

snapd 2.0.10 released to Fedora COPR

Hey there snappers

Fedora users can now get snapd 2.0.10 from the COPR repository. There are many bug fixes and new features in this release.

• interfaces: also allow @{PROC}/@{pid}/mountinfo and
  
• @{PROC}/@{pid}/mountstats
  
• interfaces: allow read access to /etc/machine-id and
  
• @{PROC}/@{pid}/smaps
  
• interfaces: miscelleneous policy updates for default, log-observe and system-observe
• snapstate: add logging after a successful doLinkSnap
  
• tests, integration-tests: port try tests to spread
  
• store, cmd/snapd: send a basic user-agent to the store
  
• store: add buy method
  
• client: retry on failed GETs
  
• tests: actual refresh test
  
• docs: REST API update
  
• interfaces: add mount support for hooks.
  
• interfaces: add udev support for hooks.
  
• interfaces: add dbus support for hooks.
  
• tests, integration-tests: port refresh test to spread
  
• tests, integration-tests: port change errors test to spread
  
• overlord/ifacestate: don't retry snap security setup
  
• integration-tests: remove unused file
  
• tests: manage the socket unit when reseting state
  
• overlord: improve organization of state patches
  
• tests: wait for snapd listening after reset
  
• interfaces/builtin: allow other sr*/scd* optical devices
  
• systemd: add support for squashfuse
  
• snap: make snaps vanishing less fatal for the system
  
• snap-exec: os.Exec() needs argv0 in the args[] slice too
  
• many: add new `create-user` command
  
• interfaces: auto-connect content interfaces with the same content and developer
• snapstate: add Current revision to SnapState
  
• readme: tweak readme blurb
  
• integration-tests: wait for listening port instead of active
  
• service reported by systemd
  
• many: rename Current -> {CurrentSideInfo,CurrentInfo}
  
• spread: fix home interface test after suite move
  
• many: name unversioned data.
  
• interfaces: add "content" interface
  
• overlord/snapstate: defaultBackend can go away now
  
• debian: comment to remember why the timer is setup like it is
  
• tests,spread.yaml: introduce an upgrade test, support/split into two suites for this
• overlord,overlord/snapstate: ensure we keep snap type in snapstate of each snap
• many: rework the firstboot support
  
• integration-tests: fix test failure
  
• spread: keep core on suite restore
  
• tests: temporary fix for state reset
  
• overlord: add infrastructure for simple state format/content migrations
• interfaces: add seccomp support for hooks.
  
• interfaces: allow gvfs shares in home and temporarily allow
  
• socketcall by default (LP: #1592901, LP: #1594675)
  
• tests, integration-tests: port network-bind interface tests to spread
• snap,snap/snaptest: use PopulateDir/MakeTestSnapWithFiles directly and remove MockSnapWithHooks
• interfaces: add mpris interface
  
• tests: enable `snap run` on i386
  
• tests, integration-tests: port network interface test to spread
  
• tests, integration-tests: port interfaces cli to spread
  
• tests, integration-tests: port leftover install tests to spread
  
• interfaces: add apparmor support for hooks.
  
• tests, integration-tests: port log-observe interface tests to spread
• asserts: improve Decode doc comment about assertion format
  
• tests: moved snaps to lib
  
• many: add the camera interface
  
• many: add optical-drive interface
  
• interfaces: auto-connect home if running on classic
  
• spread: bump gccgo test timeout
  
• interfaces: use security tags to index security snippets.
  
• daemon, overlord/snapstate, store: send confinement header to the store for install
• spread: run tests on 16.04 i386 concurrently
  
• tests,integration-tests: port install error tests to spread
  
• interfaces: add a serial-port interface
  
• tests, integration-tests, debian: port sideload install tests to spread
• interfaces: add new bind security backend and refactor backendtests
• snap: load and validate implicit hooks.
  
• tests: add a build/run test for gccgo in spread
  
• cmd/snap/cmd_login: Adjust message after adding support for wheel group
• tests, integration-tests: ported install from store tests ton spread
• snap: make `snap change <taskid>` show task progress
  
• tests, integration-tests: port search tests to spread
  
• overlord/state,daemon: make abort proceed immediately, fix doc comment, improve tests
• daemon: extend privileged access to users in "wheel" group
  
• snap: tweak `snap refresh` and `snap refresh --list` outputTiny
  
• interfaces: refactor auto-connection candidate check
  
• snap: add support for snap {install,refresh} --{edge,beta,candidate,stable}
• release: don't force KDE Neon into devmode.
  

Snappy in Arch moved to community repo

Hey there snappers!

I’d like to announce something that you may have noticed during the last update of snapd to version 2.0.10. The AUR package is no longer there, instead you can now get and update snappy on Arch simply by running this one-liner:

„pacman -S snapd"

That’s right, snapd and snap-confine have now moved to the official community repository. This means that the barrier to entry is now significantly lower and that installation is even faster than before. You still want to read the snapd wiki page to know the details about various post-install activities.