[Git][xorg-team/lib/libglvnd][debian-unstable] control: Add libopengl-dev to libglvnd-dev depends, since it used to carry the .so.

[Timo Aaltonen]

Timo Aaltonen pushed to branch debian-unstable at X Strike Force / lib / 
libglvnd


Commits:
20ecc130 by Timo Aaltonen at 2020-01-09T12:24:16+02:00
control: Add libopengl-dev to libglvnd-dev depends, since it used to carry the 
.so.

- - - - -


2 changed files:

- debian/changelog
- debian/control


Changes:

=
debian/changelog
=
@@ -1,3 +1,10 @@
+libglvnd (1.3.0-8) UNRELEASED; urgency=medium
+
+  * control: Add libopengl-dev to libglvnd-dev depends, since it used to
+carry the .so.
+
+ -- Timo Aaltonen   Thu, 09 Jan 2020 12:23:54 +0200
+
 libglvnd (1.3.0-7) unstable; urgency=medium
 
   * control: Add libglx-dev to libgl-dev Depends.


=
debian/control
=
@@ -29,6 +29,7 @@ Depends:
  libgl-dev (>= 1.3.0-1),
  libgles-dev (>= 1.3.0-1),
  libglx-dev (>= 1.3.0-1),
+ libopengl-dev (>= 1.3.0-1),
 Breaks:
  libglvnd-core-dev (<< 1.3.0-1),
 Replaces:



View it on GitLab: 
https://salsa.debian.org/xorg-team/lib/libglvnd/commit/20ecc130fda79dd2d64d1acb1f5ed2a3238adce3

-- 
View it on GitLab: 
https://salsa.debian.org/xorg-team/lib/libglvnd/commit/20ecc130fda79dd2d64d1acb1f5ed2a3238adce3
You're receiving this email because of your account on salsa.debian.org.

Re: Problems with libgl1-mesa-dev, libgl and so on

[Timo Aaltonen]

On 9.1.2020 12.08, Leopold Palomo-Avellaneda wrote:
> Hi Timo,
> 
> 
> yesterday I wrote an email to debian-devel [1], but I think that it's better 
> to
> write you directly because some changes you have done during the last month in
> the mesa and libglnd packages have made me crazy in the last hours.

better to use debian-x@

> I have been working with the coin3 [2] package and I found yesterday some
> curious situation. I built the package in my pbuilder without
> any problem. Then I have tested the ci so:
> 
> - at Jan 8, 2020 3:08 PM I have pushed to salsa and the ci was activated
> building the sources but failing _only_ reprotest. [3]
> - at Jan 8, 2020 3:08 PM I have pushed a modified version (d/changelog,
> d/watch) and the sources doesn't build.
> 
> It seems that some OpenGL test failed, but it was working so I don't
> know which package have entered in unstable in that period that could
> modified that test.
> 
> That was that I wrote yesterday to debian-devel, however, today, maybe with
> sunlight and after updating my local mirror and my pbuilder I found the 
> error. I
> thought that it was because CMake deals with OpenGL with GLVND or something, 
> but
> not.
> 
> coin(3 o 2) is an old package. It entered by Steve M. Robbins 
> 
> in 5 Apr 2003. Since some time ago it's maintained by Debian-science and I one
> of the maintainers that take care of it.
> 
> As far I can remember we have never changed the OpenGL build dependency stuff.
> We relay on the libgl1-mesa-dev and last year I added freeglut3-dev. However,
> all began to fail yesterday. I'm not an expert, neither DD, but in buster we
> have libOpenGL.so in libglvnd-dev and in sid it's in libopengl-dev. IMHO it's
> not a good idea this kind of changes, at least without a transition, or some
> kind of warning. But I have to admit that maybe I didn't notice if someone 
> did it.

Looks like libglvnd-dev should indeed depend on libopengl-dev, and it
does now in git.

> I know that you modified libgl1-mesa-dev as transitional dummy package but, 
> just
> curiosity, did you check all the packages that depends on that package in 
> build
> depends? Because I'm afraid that maybe many of them will fail in a rebuild.

No I didn't, there have been some failures but things are more or less
fine now.

> In coin3, changing libgl1-mesa-dev by libgl-dev + libopengl-dev + libglew-dev
> the package is built. But libcoin-dev depends on (libgl1-mesa-dev | libgl-dev)
> and I'm not sure if it's the better option.
> 
> Anyway, please, could you recommend me which are the more appropriate
> dependencies in my case for the coin3 package or any package that use OpenGL 
> in
> Debian?

drop libgl1-mesa-dev from it, since it's transitional and libgl-dev
ships gl.pc now.


-- 
t



signature.asc
Description: OpenPGP digital signature

Re: Problems with libgl1-mesa-dev, libgl and so on

[Leopold Palomo-Avellaneda]

El 9/1/20 a les 11:29, Timo Aaltonen ha escrit:
[...]

> 
> better to use debian-x@

ok

[...]

> Looks like libglvnd-dev should indeed depend on libopengl-dev, and it
> does now in git.

ok, libglvnd (1.3.0-8) in on the kitchen. But, then, what is your
recommendation?. Put both as build dependency? Because the description of
libopengl-dev and libglvnd-dev are almost identical.

>> I know that you modified libgl1-mesa-dev as transitional dummy package but, 
>> just
>> curiosity, did you check all the packages that depends on that package in 
>> build
>> depends? Because I'm afraid that maybe many of them will fail in a rebuild.
> 
> No I didn't, there have been some failures but things are more or less
> fine now.

IMHO, with -7 no, maybe with -8 but it's on git, not pushed.
> 
>> In coin3, changing libgl1-mesa-dev by libgl-dev + libopengl-dev + libglew-dev
>> the package is built. But libcoin-dev depends on (libgl1-mesa-dev | 
>> libgl-dev)
>> and I'm not sure if it's the better option.
>>
>> Anyway, please, could you recommend me which are the more appropriate
>> dependencies in my case for the coin3 package or any package that use OpenGL 
>> in
>> Debian?
> 
> drop libgl1-mesa-dev from it, since it's transitional and libgl-dev
> ships gl.pc now.

ok, I will try.

Thanks,


Leopold


-- 
--
Linux User 152692 GPG: 05F4A7A949A2D9AA
Catalonia
-
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?



signature.asc
Description: OpenPGP digital signature

Re: Problems with libgl1-mesa-dev, libgl and so on

[Timo Aaltonen]

On 9.1.2020 13.35, Leopold Palomo-Avellaneda wrote:
> El 9/1/20 a les 11:29, Timo Aaltonen ha escrit:
>> Looks like libglvnd-dev should indeed depend on libopengl-dev, and it
>> does now in git.
> 
> ok, libglvnd (1.3.0-8) in on the kitchen. But, then, what is your
> recommendation?. Put both as build dependency? Because the description of
> libopengl-dev and libglvnd-dev are almost identical.

So? If you need both to build, then you install both.

>>> I know that you modified libgl1-mesa-dev as transitional dummy package but, 
>>> just
>>> curiosity, did you check all the packages that depends on that package in 
>>> build
>>> depends? Because I'm afraid that maybe many of them will fail in a rebuild.
>>
>> No I didn't, there have been some failures but things are more or less
>> fine now.
> 
> IMHO, with -7 no, maybe with -8 but it's on git, not pushed.

We'd have heard about them by now, libglvnd 1.3.0-4 was uploaded before
xmas.


-- 
t



signature.asc
Description: OpenPGP digital signature

Bug#948516: xterm: displays incorrect text when one scrolls backward while output is ongoing

[Thomas Dickey]

On Thu, Jan 09, 2020 at 06:05:37PM +0100, Vincent Lefevre wrote:
> Package: xterm
> Version: 351-1
> Severity: normal
> 
> With scrollTtyOutput set to "false", when one scrolls backward while
> output is ongoing, xterm displays incorrect text. This is reproducible
> with the xterm Debian package in the following versions (at least):
> 337-1, 341-1, 344-1, 348-2, 349-1, 351-1. It seems that xterm does not
> fully erase the previous line when scrolling.

maybe - but without a typescript which would show me what went to the
terminal, I'm missing most of the information needed to investigate it.

-- 
Thomas E. Dickey 
https://invisible-island.net
ftp://ftp.invisible-island.net


signature.asc
Description: PGP signature

Bug#948516: xterm: displays incorrect text when one scrolls backward while output is ongoing

[Vincent Lefevre]

On 2020-01-09 20:54:15 -0500, Thomas Dickey wrote:
> maybe - but without a typescript which would show me what went to the
> terminal, I'm missing most of the information needed to investigate it.

What do you mean exactly?

Note that the bug is reproducible with almost anything that
generates output (but not too fast). Running a "./configure"
is a good practical example.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#948516: xterm: displays incorrect text when one scrolls backward while output is ongoing

[Vincent Lefevre]

On 2020-01-10 03:22:05 +0100, Vincent Lefevre wrote:
> On 2020-01-09 20:54:15 -0500, Thomas Dickey wrote:
> > maybe - but without a typescript which would show me what went to the
> > terminal, I'm missing most of the information needed to investigate it.
> 
> What do you mean exactly?
> 
> Note that the bug is reproducible with almost anything that
> generates output (but not too fast). Running a "./configure"
> is a good practical example.

And this is reproducible with the default X resources, except
scrollTtyOutput (which I had mentioned), e.g.

  unset XAPPLRESDIR
  /usr/bin/xterm -xrm "*scrollTtyOutput: false"

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)