I meant I'll add to d/rules:
export VENDOR=$(shell dpkg-vendor --query Vendor && dpkg-parsechangelog -S
Version)
and replace in version-string.patch (which applies to a Makefile)
"Debian" with "$(VENDOR)".
Then "wine --version" should give something like these examples:
wine-1.8.2 (Debian
@LocutusOfBorg
Nevermind, I'll change it do display vendor and the Debian version
(dpkg-parsechangelog).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1558480
Title:
Make Wine packages synced from
@LocutusOfBorg: Thanks! After writing my comment I wondered about
automating this, but didn't know what to call.
version-string.patch is mainly intended to make upstream's life easier
if bugreports are filed directly with them. It gives you this:
$ wine --version
wine-1.8.2 (Debian)
What is
** Bug watch removed: Debian Bug tracker #819255
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819255
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1558480
Title:
Make Wine packages synced
I don't really know the Ubuntu packages, so what I offer is mainly to
help explaining what Debian does in its wine packages. Whatever ...
1.)
I assume the wineprefixes, notably the default prefix in $HOME/.wine, would
just continue to work. Since the WoW64 changes I made in January there
I'm jre from Debian's pkg-wine.
It would be great if Ubuntu based its wine packages on Debian.
If you've got any questions or need help, please just ask. I'd be happy to work
on this closely together.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The last message was for the update issues.
For the gray screen you probably have to install libfontconfig1:i386
(it's recommended, but not depended on by libwine).
Greets
jre
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
wine64-development-tools now ships
/usr/share/man/man1/winegcc-development.1.gz, before it was
/usr/share/man/man1/winegcc64-development.1.gz.
Similar for wine32-development-tools.
However I don't understand how winegcc-development.1.gz, ended up in
wine-development. It wasn't there in 1.9.0-1
This was fixed in Debian 1.7.42-2 by splitting the fonts off to a
sepaerate package fonts-wine-development.
Ubuntu has:
vivid 1.7.29-4
wily 1.7.49-1
xenial 1.7.55-3
So if at all, this bug only relates to vivid, but I see no reports for
that anywhere, while I'd definitely expect them in this
Hello Michael Clark (the previous message was directed at Michael Vogt)
This problem just appears if Wine is compiled with GCC 4.9. When Wine
1.6 was released this wasn't the case. So Ubuntu (and other dists)
introduced this bug when they compiled with the wrong GCC. Just have a
look at the
Hello Michael,
it's great to see that you took care of this, thanks!
Any chance that you can also fix this for 14.04 LTS (Trusty)?
Greets
jre
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1383214
I agree to your comment in
https://bugs.launchpad.net/ubuntu/+source/wine1.6/+bug/1383214 that this
is most probably a dupe.
Did you actually verify yourself that the problem also exists in 14.04
and earlier versions and is really the same (at least the same
err:msidb:get_tablecolumns lines)?
The above mentioned bug is a dupe of
https://bugs.winehq.org/show_bug.cgi?id=36139.
This bug causes quite many windows programs to fail to install with
wine. Upstream suggests in the bugreport to reach out for the packagers,
what seems not to have happened yet, so here we are. (ARCH and Debian
The official successor of moblock, blockcontrol and mobloquer is
PeerGuardian Linux (pgl). All previous authors agreed on that.
Upstream: https://sourceforge.net/projects/peerguardian/
Debian packages: moblock-deb.sourceforge.net and
https://launchpad.net/~jre-phoenix/+archive/ppa
Debian RFP
Beginning with jaunty, I offer my moblock, mobloquer, blockcontrol and
nfblock packages in my ppa here at launchpad (instead of moblock-
deb.sourceforge.net, where other dists get their packages).
Use this apt sources.list entry:
deb http://ppa.launchpad.net/jre-phoenix/ppa/ubuntu jaunty main
Haven't heard anything.
But instead of moblock-control (1.2), its successor, the soon to be released
blockcontrol (1.3), should be used.
At least for the officicial repository we should avoid this transition trouble.
The nearly finished version of blockcontrol is available here:
Hi, I'm jre, the maintainer of http://moblock-deb.sourceforge.net/. There I
offer packages for moblock and mobloquer for Debian etch and lenny and Ubuntu
Feisty, Gutsy, Hardy. Intrepid will be added soon.
Somehow I got subscribed to this thread, fine ;-)
Whoever is interested in adding MoBlock
17 matches
Mail list logo
