Bug#677788: multi-arch for lesstif2

[Michael Gilbert]

This package has not been updated in 3 years, so it is a prime
candidate for nmu'ing. In fact, it's perfectly appropriate to nmu
without advance permission of the maintainer in general.

I noticed later that the new empty/dummy ia32-libs is not in wheezy, so
that makes this bug much less urgent than I had thought.

Anyway, I'll see if I can find time to do an NMU; if not, go ahead of
course.

Peter


To UNSUBSCRIBE, email to
with a subject of "unsubscribe". Trouble? Contact

On Sun, Jul 15, 2012 at 8:13 PM, Peter Samuelson wrote:

[Michael Gilbert]

This package has not been updated in 3 years, so it is a prime
candidate for nmu'ing. In fact, it's perfectly appropriate to nmu
without advance permission of the maintainer in general.

I noticed later that the new empty/dummy ia32-libs is not in wheezy, so
that makes this bug much less urgent than I had thought.

Anyway, I'll see if I can find time to do an NMU; if not, go ahead of
course.

If you wouldn't mind. Please go ahead with this. I'm already causing
too much trouble for the release team with my efforts on the multiarch
release goal.

Best wishes,
Mike


To UNSUBSCRIBE, email to
with a subject of "unsubscribe". Trouble? Contact

[Michael Gilbert]

If you wouldn't mind. Please go ahead with this. I'm already
causing too much trouble for the release team with my efforts on the
multiarch release goal.

I saw your thread on debian-release. It looks like they aren't very
interested in fixing this (and the new ia32-libs) for wheezy. That
being the case, should we fix this in unstable now? It means that if
any other RC bugs crop up in lesstif2, you have to use t-p-u, which is
a bit of a pain.

Peter


To UNSUBSCRIBE, email to
with a subject of "unsubscribe". Trouble? Contact

On Thu, Jul 19, 2012 at 6:05 PM, Peter Samuelson wrote:

[Michael Gilbert]

If you wouldn't mind. Please go ahead with this. I'm already
causing too much trouble for the release team with my efforts on the
multiarch release goal.

I saw your thread on debian-release. It looks like they aren't very
interested in fixing this (and the new ia32-libs) for wheezy. That
being the case, should we fix this in unstable now? It means that if
any other RC bugs crop up in lesstif2, you have to use t-p-u, which is
a bit of a pain.

I'm not so sure that they're entirely opposed to it, so I think its
worth it to try. If the package is already in unstable and tested,
and working, I think they may still be willing to consider it.

Since the package hasn't been updated in an entire release cycle (i.e.
this version is the same one thats been in squeeze for 2 years), I
don't think there are likely to be any rc bugs in the current version,
so I don't think the tpu situation is likely to come up.

Best wishes,
Mike


To UNSUBSCRIBE, email to
with a subject of "unsubscribe". Trouble? Contact

On Wed, Jul 25, 2012 at 1:39 PM, Peter Samuelson wrote:

[Michael Gilbert]

Since the package hasn't been updated in an entire release cycle (i.e.
this version is the same one thats been in squeeze for 2 years), I
don't think there are likely to be any rc bugs in the current version,
so I don't think the tpu situation is likely to come up.

That's a good point. OK, I finally got around to uploading lesstif2
1:0.95.2-1.1.

Awesome!

Btw, I found a bug in my original NMU patch: 'lesstif2-dbg' cannot be
Multi-Arch after all, as it includes debug symbols for lesstif-bin as
well as the library.

I've run into that as well. Make sure to file an unblock request bug
for the release team to review.

Best wishes,
Mike


To UNSUBSCRIBE, email to
with a subject of "unsubscribe". Trouble? Contact