[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[pkg-wine-party] Bug#793551: marked as done (wine-development: Consider providing through Backports instead of Stable)

Your message dated Thu, 3 Sep 2015 21:58:25 +0200
with message-id <55E8A661.7020202@gmail.com>
and subject line wine-development packages are now in jessie-backports
has caused the Debian Bug report #793551,
regarding wine-development: Consider providing through Backports instead of Stable
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
793551: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793551
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: wine-development
Version: 1.7.29-4
Severity: wishlist

Hello,

Upstream at the wine developers' mailing list, we recently had a
conversation about the wine & wine-development packages. There was some
confusion at first about what wine-development was for, but we've
worked that out. You can read the whole thread, starting here:
https://www.winehq.org/pipermail/wine-devel/2015-July/108513.html

It's great to have an official Debian package of wine's development
release that can live happily alongside the stable one. Kudos to
everyone that put in the hard work to make that happen.

However, I would like to propose, in the future, providing
wine-development (and all the other -development packages) to Stable
through Backports, instead of the Stable repo proper. The version of
wine-development in Jessie is 1.7.29, which was released last October.
Especially with a code-base that's still as fluid as wine's, that
mostly defeats the purpose of a development release.

Won't a version that lacks upstream's guarantee of stability, but falls
out of step with current work, also contradict the goals of Debian
Stable some and be harder to maintain? My gut feeling is that offering
Testing's version of wine-development through Backports would be better
for everyone. It would confuse end users less, keep clearer boundaries
between Stable & Testing, and simplify things for the Debian wine team.

Cheers,
Kyle


-- System Information:
Debian Release: 8.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

--- End Message ---
--- Begin Message --- 
Package: wine-development
Version: 1.7.50-1

Backported wine-development packages are now in jessie-backports.
The first version is 1.7.50-1~bpo8+1.
Further versions will be added as soon as they arrive in Debian Stretch
(testing) (plus an undefined timespan for the human handling).

I noted that the upgrade of wine-development from jessie to
jessie-backports may need some manual intervention to update the whole
set of packages, because backports has the apt pin priority 100. I'll
look into improving this.
Once the jessie-backports packages are installed, update works flawlessly.


@Kyle:
I suggest to change the link on https://www.winehq.org/download/ from
 https://packages.debian.org/stable/wine-development
to
 https://packages.debian.org/wine-development
The latter shows available versions for every Debian release, including
jessie-backports.

You may add a second link pointing to the stable Wine release (which
some people may prefer, or have to use because they are on Debian Wheezy
(oldstable)):
 https://packages.debian.org/wine

I've updated https://wiki.debian.org/Wine and will revisit
http://wiki.winehq.org/Debian soon.

Greets
jre

--- End Message ---
Reply to: