out of date snapshot

[Jason A. Donenfeld]

[Impact]
* This package should stay in -proposed/sid
[Test Case]
* Upgrading shows an empty package, with a clear message telling to use a ppa instead
[Regression Potential]
* none: broken package is the expected result :p

[Other info]

This package *MUST* be consistently sync'd against the upstream Debian package, since its version is a fastly moving *snapshot* with no security guarantees. The Debian package makes careful note of it, which is why it's pinned to sid. The WireGuard documentation also is very explicit about this.

So, please set this package up to automatically mirror the Debian sid one. If you're unable to do that, then this package needs to not be included in any Ubuntu repository until we actually make a non-snapshot release. Pick one of these options; obviously, I prefer the former -- mirror the Debian sid package. The current status-quo, however, is not okay under any circumstances.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Adam Conrad (adconrad)]

$ demote-to-proposed -m 'LP: #1685522' wireguard
Demoting packages to artful-proposed:
 wireguard 0.0.20170214-1 in artful
Comment: LP: #1685522
Demote [y|N]? y
Remove wireguard from release [y|N]? y
1 package successfully demoted.

[Jason A. Donenfeld (zx2c4)]

As discussed on IRC, the following empty package should be put into Zesty.

[Jason A. Donenfeld (zx2c4)]

This appears to have been added to the queue and is now waiting for approval:

https://launchpad.net/ubuntu/zesty/+queue?queue_state=1&queue_text=wireguard

[Jason A. Donenfeld (zx2c4)]

[Impact]
 * After discussion on IRC with the release team, it seems clear that this package should have stayed in Debian sid and not migrated into a stable release of Ubuntu. This sentiment is reflected in the original Debian bug report about such.
 * Thus, rather than keep a rolling package up to date in a stable distro, this update simply removes the package and informs users about the situation.
 * This was determined to be the right path forward in discussions with cjwatson and infinity.

[Test Case]
  * This package was tested by installing both resultant .deb files on a fresh VM.
  * The behavior was perfect, seeing as this package is so simple.

[Regression Potential]

 * There is little regression potential at all for removing this experimental snapshot. Users wanting to user WireGuard on Ubuntu already use the up to date PPA instead.

[Andy Whitcroft (apw)]

Hello Jason, or anyone else affected,

Accepted wireguard into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/wireguard/0.0.20170214-1ubuntu0.17.04 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

[Jason A. Donenfeld (zx2c4)]

The uploaded package is wrong. This tarball contains actual minimal contents, as it should be.

[Andy Whitcroft (apw)]

Hello Jason, or anyone else affected,

Accepted wireguard into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/wireguard/0.0.20170214-1ubuntu0.17.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

[Jason A. Donenfeld (zx2c4)]

Using the .deb builds provided on https://launchpad.net/ubuntu/+source/wireguard/0.0.20170214-1ubuntu0.17.04.1/+build/12474101 , I can confirm that the packages work exactly as intended.

[Jason A. Donenfeld (zx2c4)]

I have performed testing with four separate VMs:

1. A fresh install of the -proposed package on a minimal server.
2. An update from the previous package to the -proposed package on a minimal server.
3. A fresh install of the -proposed package on a desktop with many packages.
4. An update from the previous package to the -proposed package on a desktop with many packages.

I can confirm that this process worked exactly as intended. Therefore, this SRU can proceed.

[Jason A. Donenfeld (zx2c4)]

Any update on this SRU?

[Gianfranco Costamagna (costamagnagianfranco)]

they are usually processed after 7-10 days from the verification-done tag.

[Launchpad Janitor (janitor)]

This bug was fixed in the package wireguard - 0.0.20170214-1ubuntu0.17.04.1

---------------
wireguard (0.0.20170214-1ubuntu0.17.04.1) zesty; urgency=medium

  * WireGuard is not yet released software and was supposed to stay in Debian
    sid and certainly not migrate to Ubuntu stable. Since pre-releases do not
    belong in a non-rolling distribution like Ubuntu, this update is an empty
    package placeholder. As soon as WireGuard upstream releases their first
    real release, this package will be updated again. Until then, you're best
    using ppa:wireguard/wireguard or following the directions on
    <https://www.wireguard.io/install>. (LP: #1685522)

 -- <email address hidden> (Jason A. Donenfeld) Mon, 24 Apr 2017 00:39:58 +0200

[Andy Whitcroft (apw)]

The verification of the Stable Release Update for wireguard has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[Jason A. Donenfeld (zx2c4)]

Hey apw and adconrad -- a long time ago (2.5 years) we decided to keep WireGuard from migrating into Ubuntu. There's been tons of progress since then. It's now in the progress of migrating down into Debian testing and stable. I think it's time we let it migrate into Ubuntu too. Is there anything that needs to be done on your part of the build infra to unblock this?