Den 21. aug. 2010 10:55, skrev Stephen Kitt:
On Sat, Aug 21, 2010 at 04:02:37AM +0200, Ove Kaaven wrote:
Den 21. aug. 2010 03:01, skrev Svante Signell:
Please take this request seriously. Even if Squeeze is frozen,
distributing the same version (1.0.x) of Wine as Lenny does not look
good
Den 21. aug. 2010 03:01, skrev Svante Signell:
Please take this request seriously. Even if Squeeze is frozen,
distributing the same version (1.0.x) of Wine as Lenny does not look
good! People are trying to help out!
I wouldn't hold much hope. These are the options:
1. Get wine-gecko built on D
A couple of days ago, I uploaded Wine 1.0.1 to unstable. Although 1.0.1
was released by upstream, this is a maintenance release with only minor
bugfixes, there were no significant changes. (Significant changes and
major bugfixes currently happen in the 1.1.x series, not 1.0.x. Any
1.0.x fixes h
Neil McGovern skrev:
On Fri, May 09, 2008 at 12:35:07PM +0200, Ove Kaaven wrote:
These three packages must be migrated simultaneously because I changed
the name of the simgear library package, so migrating simgear alone
makes the other two packages uninstallable because simgear0 would no
The flightgear package trio (flightgear, simgear, fgfs-atlas) won't
migrate to testing, apparently britney is caught in a loop here.
These three packages must be migrated simultaneously because I changed
the name of the simgear library package, so migrating simgear alone
makes the other two pa
Andreas Barth skrev:
* Lennart Sorensen ([EMAIL PROTECTED]) [080415 22:26]:
I suspect by the time a fully working multiarch is done, x86 won't need
it anymore because everything will be fully 64bit. :)
As Wine maintainer, I'd disagree with that.
People, we want to release soon. Anyone is wel
Steve Langasek wrote:
Wow. No, definitely not. If the package can't be built on amd64, I'm not
ok with shipping binary blobs that get unpacked this way.
What are the difficulties with building 32-bit wine on amd64?
There are not enough 32-bit libs on amd64 to satisfy all of Wine's core
buil
søn, 22,.05.2005 kl. 00.10 -0700, skrev Steve Langasek:
> Having four versions of gmime in a stable release means a four-fold increase
> in the security team's workload if a security bug is found. (This is true
> even if the bug only applies to one version, because the security team still
> has to
lør, 21,.05.2005 kl. 12.13 -0700, skrev Steve Langasek:
> Hi Ove, Guus,
>
> It looks like there are four versions of gmime in testing currently (gmime,
> gmime1, gmime2, gmime2.1), only one of which is actually used by any other
> packages. Is there any reason not to remove gmime{,1,2} from testi
9 matches
Mail list logo
