Re: wine

[Scott Howard]

On Sat, Oct 29, 2016 at 6:47 AM, Norbert de Jonge
 wrote:
> Is there any way you can get a more recent wine than 1.6.2 in the apt
> repository?
>
> Wine 1.6.2 was released more than 2.5 years ago, which in Wine-time is
> pretty ancient.
>
> And it's one of the packages that takes a tremendous amount of time to
> compile, especially on slower machines.
>
> That combination (very old + difficult to compile manually) is pretty
> bad.

It looks like you installed the package "wine" which is actually wine1.6.

See packages "wine-stable" or "wine-development" instead

wine-stable is version 1.8.5
http://packages.ubuntu.com/yakkety/wine-stable

wine-development is version 1.9.20
http://packages.ubuntu.com/source/yakkety/wine-development

-- 
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu

Re: Bitcoin and Ubuntu

[Scott Howard]

On Thu, Dec 12, 2013 at 5:00 PM, Micha Bailey  wrote:
> Apologies for the cross-post, but I wasn't sure which mailing list would be
> most appropriate.
> Also, please note that I am writing this as myself, not as a representative
> of the Bitcoin project or development community.

As one of the Debian maintainers for the package, I agree that the
network protocol is in such a flux that it is not suitable for stable
release yet. Old versions not only hurt users, but pose a threat to
the network as a whole. PPAs are more appropriate, at least for the
time being. Debian has an RC bug preventing migration to testing for
this and other reasons [1]. Perhaps blacklisting bitcoin import from
Debian, and removing it from the Ubuntu repositories, is reasonable.

This is difficult, because many users rely on the package - and
removing it from the repositories will leave them vulnerable. However,
keeping the package in the repositories potentially makes more users
vulnerable.

Another alternative would be to have a MOTU/dev that is interested
perform day-of-release backports, and encourage users to enable
backports. However, this could create a situation where the stable
release contains a harmful version, and only the backport version
would be safe to use. This is probably unacceptable to both Ubuntu and
Bitcoin.

Also, the bitcoin package is only really necessary to run a full node.
Users that want to run a wallet can use electrum (in ubuntu and
debian) or multibit (not in Debian yet, but someone is working on it).

At some point bitcoin should be stable enough that full node software
can be included in Ubuntu and Debian releases, but for now it is
probably best to use the PPA.

Regards,
Scott
[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718272

-- 
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu

Re: Daily builds for PPA. Versions problem

[Scott Howard]

On Sun, Jul 14, 2013 at 12:17 PM, Anton Balashov  wrote:
> Hello.
> I'm trying to make automatic daily builds if there is new commits in git.
> So, many commits have version 1.1.1 and I should to have many debs
> with different orig.tar.gz
> I want to have some like pkg-1.1.1-ppa1
> But when I'm trying to upload new version, I get an error:
> pkg-1.1.1.orig.tar.gz was changes. And it's true.
> I can put some part of commit hash in version (1.1.1~hash-date..) but
> it's breaks order.
> I can't have increment system here (or can but non-trivial).

use a + instead of ~ ,and put date first since hash is random and date
is ordered (higher dates are newer than lower dates).
1.1.1+date-hash

~Scott

-- 
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu