Your message dated Fri, 06 Sep 2013 21:05:06 +
with message-id
and subject line Bug#714664: fixed in mtink 1.0.16-7
has caused the Debian Bug report #714664,
regarding [mtink] please transition from lesstif2 to motif
to be marked as done.
This means that you claim that the problem has been
release of Jessie.
More information can be found in the Debian wiki [1].
Please update your package to build against the motif package instead.
In most cases this can be done by simply replacing the build-depends on
lesstif2-dev with libmotif-dev, however please do verify proper
behaviour before
release of Jessie.
More information can be found in the Debian wiki [1].
Please update your package to depend on the multiarch motif packages
instead, or simply remove lesstif2.
Regards
Paul and Graham
[1] http://wiki.debian.org/lesstif2motifTransition
--
To UNSUBSCRIBE, email to debian-qa-packages
release of Jessie.
More information can be found in the Debian wiki [1].
Please update your package to build against the motif package instead.
In most cases this can be done by simply replacing the build-depends on
lesstif2-dev with libmotif-dev, however please do verify proper
behaviour before
Source: geant321
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 1:3.21.14.dfsg-10
Severity: normal
X-Debbugs-CC: openmo...@packages.debian.org
Hi Maintainer
The lesstif2 package on which your package indirectly depends or
build-depends is destined to be removed from the arc
the release of Jessie.
More information can be found in the Debian wiki [1].
Please update your package to build against the motif package instead.
In most cases this can be done by simply replacing the build-depends on
lesstif2-dev with libmotif-dev, however please do verify proper
behaviour before
the release of Jessie.
More information can be found in the Debian wiki [1].
Please update your package to build against the motif package instead.
In most cases this can be done by simply replacing the build-depends on
lesstif2-dev with libmotif-dev, however please do verify proper
behaviour
Your message dated Fri, 05 Jul 2013 18:26:43 +0200
with message-id <51d6f3c3.3010...@debian.org>
and subject line xmhtml_1.1.7-19_amd64.changes ACCEPTED into unstable
has caused the Debian Bug report #714833,
regarding [xmhtml] please transition from lesstif2 to motif
to be marked as done.
ABI Compliance Checker [1] reports ABI changes in libXmHTML.so.1.1.7,
see attached.
However, the only changes are globals _XmHTMLStrings and _XmHTMLMessages
changing from char[] const to char, and XmSEE_DETAIL being added to enum
XmHighlightMode.
[1] http://ispras.linuxbase.org/index.php/ABI_c
release of Jessie.
More information can be found in the Debian wiki [1].
Please update your package to build against the motif package instead.
In most cases this can be done by simply replacing the build-depends on
lesstif2-dev with libmotif-dev, however please do verify proper
behaviour
of Jessie.
More information can be found in the Debian wiki [1].
Please update your package to build against the motif package instead.
In most cases this can be done by simply replacing the build-depends on
lesstif2-dev with libmotif-dev, however please do verify proper
behaviour before
release of Jessie.
More information can be found in the Debian wiki [1].
Please update your package to build against the motif package instead.
In most cases this can be done by simply replacing the build-depends on
lesstif2-dev with libmotif-dev, however please do verify proper
behaviour before
On 2 July 2013 18:28, Julien Cristau wrote:
>
> I think motif should provide a transitional lesstif2-dev package
> instead, if it's deemed safe to do so.
>
> I'm not sure this is going to be safe. It looks like ABI breakages in
xbae and xmhtml, and very likely in invent
of Jessie.
More information can be found in the Debian wiki [1].
Please update your package to build against the motif package instead.
In most cases this can be done by simply replacing the build-depends on
lesstif2-dev with libmotif-dev, however please do verify proper
behaviour before
release of Jessie.
More information can be found in the Debian wiki [1].
Please update your package to build against the motif package instead.
In most cases this can be done by simply replacing the build-depends on
lesstif2-dev with libmotif-dev, however please do verify proper
behaviour before
release of Jessie.
More information can be found in the Debian wiki [1].
Please update your package to build against the motif package instead.
In most cases this can be done by simply replacing the build-depends on
lesstif2-dev with libmotif-dev, however please do verify proper
behaviour
release of Jessie.
More information can be found in the Debian wiki [1].
Please update your package to build against the motif package instead.
In most cases this can be done by simply replacing the build-depends on
lesstif2-dev with libmotif-dev, however please do verify proper
behaviour before
of Jessie.
More information can be found in the Debian wiki [1].
Please update your package to build against the motif package instead.
In most cases this can be done by simply replacing the build-depends on
lesstif2-dev with libmotif-dev, however please do verify proper
behaviour before
release of Jessie.
More information can be found in the Debian wiki [1].
Please update your package to build against the motif package instead.
In most cases this can be done by simply replacing the build-depends on
lesstif2-dev with libmotif-dev, however please do verify proper
behaviour before
of Jessie.
More information can be found in the Debian wiki [1].
Please update your package to build against the motif package instead.
In most cases this can be done by simply replacing the build-depends on
lesstif2-dev with libmotif-dev, however please do verify proper
behaviour before
Source: xshisen
User: openmo...@packages.debian.org
Usertags: lesstif2motif
Version: 1:1.51-4
Severity: normal
Tags: patch
X-Debbugs-CC: openmo...@packages.debian.org
Hi Maintainer
The lesstif2 package on which your package depends or build-depends is
destined to be removed from the archive befor
release of Jessie.
More information can be found in the Debian wiki [1].
Please update your package to build against the motif package instead.
In most cases this can be done by simply replacing the build-depends on
lesstif2-dev with libmotif-dev, however please do verify proper
behaviour before
release of Jessie.
More information can be found in the Debian wiki [1].
Please update your package to build against the motif package instead.
In most cases this can be done by simply replacing the build-depends on
lesstif2-dev with libmotif-dev, however please do verify proper
behaviour before
release of Jessie.
More information can be found in the Debian wiki [1].
Please update your package to build against the motif package instead.
In most cases this can be done by simply replacing the build-depends on
lesstif2-dev with libmotif-dev, however please do verify proper
behaviour before
release of Jessie.
More information can be found in the Debian wiki [1].
Please update your package to build against the motif package instead.
In most cases this can be done by simply replacing the build-depends on
lesstif2-dev with libmotif-dev, however please do verify proper
behaviour
the release of Jessie.
More information can be found in the Debian wiki [1].
Please update your package to build against the motif package instead.
In most cases this can be done by simply replacing the build-depends on
lesstif2-dev with libmotif-dev, however please do verify proper
behaviour
release of Jessie.
More information can be found in the Debian wiki [1].
Please update your package to build against the motif package instead.
In most cases this can be done by simply replacing the build-depends on
lesstif2-dev with libmotif-dev, however please do verify proper
behaviour
release of Jessie.
More information can be found in the Debian wiki [1].
Please update your package to build against the motif package instead.
In most cases this can be done by simply replacing the build-depends on
lesstif2-dev with libmotif-dev, however please do verify proper
behaviour before
release of Jessie.
More information can be found in the Debian wiki [1].
Please update your package to build against the motif package instead.
In most cases this can be done by simply replacing the build-depends on
lesstif2-dev with libmotif-dev, however please do verify proper
behaviour before
release of Jessie.
More information can be found in the Debian wiki [1].
Please update your package to build against the motif package instead.
In most cases this can be done by simply replacing the build-depends on
lesstif2-dev with libmotif-dev, however please do verify proper
behaviour before
release of Jessie.
More information can be found in the Debian wiki [1].
Please update your package to build against the motif package instead.
In most cases this can be done by simply replacing the build-depends on
lesstif2-dev with libmotif-dev, however please do verify proper
behaviour before
release of Jessie.
More information can be found in the Debian wiki [1].
Please update your package to build against the motif package instead.
In most cases this can be done by simply replacing the build-depends on
lesstif2-dev with libmotif-dev, however please do verify proper
behaviour
release of Jessie.
More information can be found in the Debian wiki [1].
Please update your package to build against the motif package instead.
In most cases this can be done by simply replacing the build-depends on
lesstif2-dev with libmotif-dev, however please do verify proper
behaviour before
of Jessie.
More information can be found in the Debian wiki [1].
Please update your package to build against the motif package instead.
In most cases this can be done by simply replacing the build-depends on
lesstif2-dev with libmotif-dev, however please do verify proper
behaviour before
release of Jessie.
More information can be found in the Debian wiki [1].
Please update your package to build against the motif package instead.
In most cases this can be done by simply replacing the build-depends on
lesstif2-dev with libmotif-dev, however please do verify proper
behaviour
release of Jessie.
More information can be found in the Debian wiki [1].
Please update your package to build against the motif package instead.
In most cases this can be done by simply replacing the build-depends on
lesstif2-dev with libmotif-dev, however please do verify proper
behaviour before
of Jessie.
More information can be found in the Debian wiki [1].
Please update your package to build against the motif package instead.
In most cases this can be done by simply replacing the build-depends on
lesstif2-dev with libmotif-dev, however please do verify proper
behaviour before
of Jessie.
More information can be found in the Debian wiki [1].
Please update your package to build against the motif package instead.
In most cases this can be done by simply replacing the build-depends on
lesstif2-dev with libmotif-dev, however please do verify proper
behaviour before
release of Jessie.
More information can be found in the Debian wiki [1].
Please update your package to build against the motif package instead.
In most cases this can be done by simply replacing the build-depends on
lesstif2-dev with libmotif-dev, however please do verify proper
behaviour before
release of Jessie.
More information can be found in the Debian wiki [1].
Please update your package to build against the motif package instead.
In most cases this can be done by simply replacing the build-depends on
lesstif2-dev with libmotif-dev, however please do verify proper
behaviour before
release of Jessie.
More information can be found in the Debian wiki [1].
Please update your package to build against the motif package instead.
In most cases this can be done by simply replacing the build-depends on
lesstif2-dev with libmotif-dev, however please do verify proper
behaviour before
release of Jessie.
More information can be found in the Debian wiki [1].
Please update your package to build against the motif package instead.
In most cases this can be done by simply replacing the build-depends on
lesstif2-dev with libmotif-dev, however please do verify proper
behaviour
release of Jessie.
More information can be found in the Debian wiki [1].
Please update your package to build against the motif package instead.
In most cases this can be done by simply replacing the build-depends on
lesstif2-dev with libmotif-dev, however please do verify proper
behaviour before
release of Jessie.
More information can be found in the Debian wiki [1].
Please update your package to build against the motif package instead.
In most cases this can be done by simply replacing the build-depends on
lesstif2-dev with libmotif-dev, however please do verify proper
behaviour
of Jessie.
More information can be found in the Debian wiki [1].
Please update your package to build against the motif package instead.
In most cases this can be done by simply replacing the build-depends on
lesstif2-dev with libmotif-dev, however please do verify proper
behaviour before
the release of Jessie.
More information can be found in the Debian wiki [1].
Please update your package to build against the motif package instead.
In most cases this can be done by simply replacing the build-depends on
lesstif2-dev with libmotif-dev, however please do verify proper
ff
> inventor: haven't figured this one out yet.
> ncbi-tools6 (vibrant/vibrant.h): doesn't play nice with icheck as it
> actually BUILDS header files.
(ncbi-tools6 is already build depending on motif, I hope the maintainers
have checked this)
> sciplot: fails to check rig
On Mon, Jun 10, 2013 at 22:32:08 +0200, Paul Gevers wrote:
> glw: fails with GLwDrawA.h:147:0: Undefined identifier WidgetClass
defined in as "typedef struct _WidgetClassRec
*WidgetClass;"
> sciplot: fails to check right now on
> /usr/include/X11/Core.h:51:0: Undefined identifier _XFUNCPROTOBEG
On 09-06-13 11:05, Paul Gevers wrote:
> On 04-06-13 08:31, Julien Cristau wrote:
>> Do we know how many of the lesstif2 reverse dependencies are libraries
>> whose ABI would change if rebuilt with motif instead?
>
> No, but I can try to find out. The original idea of lesstif
dependencies [2], though.
>
> So my question basically is, what would be the most appropriate order to
> do things?
>
> My proposal would be (with your approval) to just get motif into
> unstable/main and start converting the dependencies with the help of
> their maintainers (th
against the reverse dependencies of lesstif2-dev in
> Debian.
Good, but I think it is also good to wait until all architectures have
build successfully.
> I will also file one in Ubuntu to remove openmotif and replace with motif.
Good. (Same holds as above. And please let me know the bug numbe
;t
> forget to tag them with the lesstif2motif usertag.
>
I will file the bugs against the reverse dependencies of lesstif2-dev in
Debian.
I will also file one in Ubuntu to remove openmotif and replace with motif.
Regards
Graham
Hmm,
Maybe I was too quick, although I don't understand why it works now, but
kfreebsd now builds with motif 2.3.4, where it didn't build with
openmotif 2.3.3.
https://buildd.debian.org/status/package.php?p=motif&suite=sid
Paul
On 25-05-13 17:47, Paul Gevers wrot
Hi Graham,
Congratulations...
Now that we have motif in Debian/main, I would like to fix the fact that
motif FTBFS on non-linux systems. That is needed if we want to replace
lesstif2 as that is now available on more Debian platforms than motif.
I think I know where it goes wrong (I have to
Processing commands for cont...@bugs.debian.org:
> # The new motif package was just accepted in main, replacing the
> # openmotif source package. Reassigning the only remaining bug.
> reassign 544554 motif
Bug #544554 [openmotif] manpages of libmotif should be fixed
Bug reassigned fro
Hi Luca,
On 23-05-13 08:43, Luca Falavigna wrote:
> 2013/5/22 Paul Gevers :
>> Ok. Then we just have to wait until the RT grants us a transition slot.
>> Will keep you updated.
>
> I don't think we need it for openmotif -> motif, as long as motif is
> ABI-comp
On Fri, May 24, 2013 at 08:36:38 +0200, Paul Gevers wrote:
> [Summary of previous mails: we are discussing how/when to move openmotif
> to motif].
>
> On 23-05-13 08:43, Luca Falavigna wrote:
> > 2013/5/22 Paul Gevers :
> >> Ok. Then we just have to wait until the RT
[Summary of previous mails: we are discussing how/when to move openmotif
to motif].
On 23-05-13 08:43, Luca Falavigna wrote:
> 2013/5/22 Paul Gevers :
>> Ok. Then we just have to wait until the RT grants us a transition slot.
>> Will keep you updated.
>
> I don't thin
As per the motif 2.3.4 release notes [1], motif 2.3.4 is binary compatible
all the way back to motif 2.2.
I believe this means bug #587683 [2] should have been solved by symlinks
rather than bumping the name libmotif3 to libmotif4.
I cannot say why upstream bumped the soname when it was not
2013/5/22 Paul Gevers :
> Ok. Then we just have to wait until the RT grants us a transition slot.
> Will keep you updated.
I don't think we need it for openmotif -> motif, as long as motif is
ABI-compatible with openmotf.
--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@li
On 20-05-13 11:55, Luca Falavigna wrote:
> I just checked, openmotif has only two rdeps, all of them in non-free,
> and just for i386 and amd64 architectures. I don't think removing
> openmotif from non-free and immediately accepting motif in main would
> cause a lot of trou
d64 architectures. I don't think removing
openmotif from non-free and immediately accepting motif in main would
cause a lot of trouble for those two packages, so the best action
would be that way. Feel free to upload motif in main, I'll process it
from NEW immediately after removing openmo
>> about the transition from lesstif2 to motif [1], I am considering to
>> have the motif package updated in non-free first.
>
> I don't think that would work because autobuilders don't usually pick
> packages from experimental.
I don't understand exactly what y
Hi Paul,
2013/5/18 Paul Gevers :
> While we are waiting for the release team to respond to my questions
> about the transition from lesstif2 to motif [1], I am considering to
> have the motif package updated in non-free first.
I don't think that would work because autobuilders don&
Hi Luca
On 06-05-13 00:22, Luca Falavigna wrote:
> 2013/5/5 Paul Gevers :
>> As the release of wheezy has happened this weekend. Is it now a good
>> time to follow up on the actions above?
>
> It should, yes.
> Feel free to upload motif to unstable, then I'll take
Another status update:
ferret-vis#707211 fix released in ferret-vis 6.6.2-2
gridengine#707937
hotswap#707621
mesa-glwUbuntu-only package, to be replaced by glw (LP: #1179164)
mgdiff #707943
sqshLP: #1134233 fix released in sqsh 2.1.7-2
tcm#707923
xabacus#707926 fix r
https://lists.debian.org/debian-release/2013/05/msg00161.html
or 51881a33.6030...@debian.org
I like to request a transition slot for lesstif2 to (open)motif.
To keep current unstable build-able and installable, I propose the
follow transition path:
On 07-05-13 21:32, Paul Gevers wrote:
>
Another status update:
ferret-vis#707211 fix released in ferret-vis 6.6.2-2
gridengine#707937
hotswap#707621
mesa-glwUbuntu-only package, to be replaced by glw (LP: #1179164)
mgdiff #707943
sqshLP: #1134233 fix released in sqsh 2.1.7-2
tcm#707923
xabacus#707926 fix r
/~ginggs/+archive/motif
Regards
Graham
--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/5190af97.5060...@nerve.org.za
t;
> Lesstif2 was originally created as an
> free alternative for motif, but in the mean time became unmaintained and
>
meantime - one word
> To ease the transition that will happen some time soon, we will follow
>
sometime - one word
...and then some of my own typos:
> hotsw
"
>
>
> Lesstif2 was originally created as an
> free alternative for motif, but in the mean time became unmaintained and
>
>
> meantime - one word
>
>
> To ease the transition that will happen some time soon, we will follow
>
>
> someti
this is pulled in by the lesstif2-dev package that you do depend on.
In the near future we like to replace lesstif2 in Debian with the
relicensed (open-)motif package. Lesstif2 was originally created as an
free alternative for motif, but in the mean time became unmaintained and
buggy. Motif itself
Hi RT,
On 06-05-13 23:01, Paul Gevers wrote:
> So my question basically is, what would be the most appropriate order to
> do things?
>
> My proposal would be (with your approval) to just get motif into
> unstable/main and start converting the dependencies with the help of
>
On 7 May 2013 08:19, Paul Gevers wrote:
> Can you please document that, I mean which ones? It would be great if
> you would reply to the e-mail I sent yesterday to the release team with
> full details, so that the team knows when they make a decision.
When I get home tonight I will compose an e
On 07-05-13 07:55, Graham Inggs wrote:
> I think the testing went very well. As we suspected, most packages only
> required changing the build-depends on lesstif2-dev to libmotif-dev.
> There were a few that required the addition of libxt-dev and one or two
> that required libxext-dev and libxp-d
d not have been able to continue building
against libmotif-dev without making changes anyway.
Regards
Graham
On 7 May 2013 07:14, Paul Gevers wrote:
> Hi Graham,
>
> On 06-05-13 23:01, Paul Gevers wrote:
> > My proposal would be (with your approval) to just get motif into
> &g
Hi Graham,
On 06-05-13 23:01, Paul Gevers wrote:
> My proposal would be (with your approval) to just get motif into
> unstable/main and start converting the dependencies with the help of
> their maintainers (the libraries can coexist). Because the -dev package
> name has to chan
Hi release team,
I like to get your opinion and advise on the following.
Motif has been released with a free license last year, and I would like
to move it from non-free (called openmotif) to Debian main. Its former
free replacement lesstif2 is unsupported upstream and should be retired
(in
2013/5/5 Paul Gevers :
> As the release of wheezy has happened this weekend. Is it now a good
> time to follow up on the actions above?
It should, yes.
Feel free to upload motif to unstable, then I'll take care of removing
openmotif from the archive just before processing motif from NE
Hi Luca,
On 06-04-13 00:59, Luca Falavigna wrote:
> There's a nasty bug in dak, which prevents accepting a package if
> components are already available in a different section, as happened
> with motif, which shares libmotif-dev and libmotif4 with openmotif
> package.
>
>
Hi,
On 06-04-13 14:30, Graham Inggs wrote:
> I think it is very late now to try and get motif into Raring with it not
> being in Debian.
Get it, and thought so.
> Paul: when you re-upload motif in NEW, will you go straight to 2.3.4-2,
> or upload 2.3.4-1 again?
> (or just t
Hi all,
I am sorry to read it, but it seems we won't have motif in experimental
before the release of Wheezy. If we want to get the package in Ubuntu
Raring, it needs to go on it's own. Graham, do you still want to do that?
Paul
Original Message
Subject: Motif
Date:
y how it was done, but see the changelog entry for new
package in raring, python-cffi [1].
That package is also waiting in Debian NEW, about one week behind motif.
> So if that is possible, you are talking to an ftp-master, right? Then we
> could just make an Ubuntu version of the package i
as 2.3.4-1 (with the
> appropriate changes to the changelog and libxm4.symbols)?
> It may then be possible to get Ubuntu to sync motif from Debian's NEW
> queue and still make it into Raring (final beta freeze is March 28 [1]).
Are you sure? I believe the NEW queue is ONLY accessib
Hi Paul
You wrote that you wouldn't upload 2.3.4-2 until 2.3.4-1 had been reviewed.
Is it possible to re-upload our current effort as 2.3.4-1 (with the
appropriate changes to the changelog and libxm4.symbols)?
It may then be possible to get Ubuntu to sync motif from Debian's NEW queue
On 17 March 2013 12:10, Paul Gevers wrote:
> The one in d/copyright. Please see below. (Don't forget to add the GPL3
> required text to the file.) (And are you sure it is not GPL3 or later?)
>
Yes, from d/copyright in unity-greeter:
Format: http://www.debian.org/doc/packaging-manuals/copyright-
Hi Paul
On 17 March 2013 10:58, Paul Gevers wrote:
> If this is true, we do have an (small) issue. You can not just relicense
> this file without permission of the copyright owner. So, you have no
> choice other than state the license of this file as GPL-3 or ask
> Canonical to relicense.
>
I u
Hi Graham,
Maybe I was unclear. See what I mean below.
On 17-03-13 10:54, Graham Inggs wrote:
> I understood that this was OK since the new license was 2+.
> Or is the problem more about changing from GPL to LGPL?
The latter.
> By the way, you really should add Canonical to the copyright ho
ou have no
choice other than state the license of this file as GPL-3 or ask
Canonical to relicense.
I don't think it is a problem to have the icon licensed under GPL-3,
although most of motif is less strict licensed under LGPL, etc, as it is
not part of the binary (library) so packages linking
On 03/14/13 07:29, Graham Inggs wrote:
> After asking that question I tried to do more reading up symbols, but
> I found the information very vague, especially about (optional)
> symbols. Out of interest, why are there so many other (optional)
> symbols? How did you determine they were optional?
uess Canonical might have the copyright on the white circle image, I'll
check in the sources of unity-greeter. I'm not sure about the four
squares, I based that on the look of the icon for Xterm that is displayed
in MWM [1].
> I saw you dropped them in the mean time. Fine. However, from
nd_xft.m4 should be totally reworked, and we should probably
> consult upstream before doing that.
Sure, although by now I think you nearly know as much about the motif
code as the current upstream maintainer. I think he was just paid for a
while to work on it.
> Is there any harm in lea
ce for now?
We could create a motif-demos package and copy the demos directory to
/usr/share/doc/motif-demos, similar to what is done in gtk2.0-examples and
gtk-3-examples.
What do you think?
Paul, if you think my recent changes to:
05-multiarch-specialcase-libdir-X11.patch
13-fix_hardcoded_x11rgb_path.patch
and
14-fix_ac_find_xft.patch
are sane, then I'll send those patches upstream.
I've been looking at the motif packaging for Fedora 19 [1]. I see they
also renamed their openmotif package to motif.
The only changes we don't have now are in the man pages relating to
relocated files.
There are still many references to X11R6.
Regarding my patch 14:
Including ft2bui
On 8 March 2013 21:50, Paul Gevers wrote:
> Where did you get this file? What is the copyright? Is this file created
> as png or is it actually created in a program and does that program
> store the file in a different format so that you can edit it? In the
> later case, we also need that source
On 8 March 2013 21:38, Paul Gevers wrote:
> Can you please elaborate why you find this nicer? You didn't need the
> clean up before, and now you do. So, why?
>
Previously, we had to create a directory and then copy to debian/tmp/etc...
which I always thought was a bit of a hack.
I believe this
On 8 March 2013 21:09, Paul Gevers wrote:
> I prefer to do this by adding that file to a file called debian/clean.
> That way you don't have to override dh_clean.
>
>
Thanks, I'll look into that.
On 08-03-13 12:48, Graham Inggs wrote:
> Include custom Unity Greeter badge for MWM
> diff --git a/debian/custom_mwm_badge.png b/debian/custom_mwm_badge.png
> new file mode 100644
> index 000..cfc1703
> Binary files /dev/null and b/debian/custom_mwm_badge.png differ
Where did you get this
On 08-03-13 12:48, Graham Inggs wrote:
> +++ b/debian/mwm.install
> -/etc/X11/mwm/system.mwmrc-menu
> +debian/system.mwmrc-menu /etc/X11/mwm
> +++ b/debian/rules
> - cp -a clients/mwm/system.mwmrc debian/tmp/etc/X11/mwm/system.mwmrc-menu
> + cp clients/mwm/system.mwmrc debian/system.mwmrc-
1 - 100 of 148 matches
Mail list logo
