[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1038872: marked as done (qt6-shadertools-dev: Installs private headers when it shouldn't)

Your message dated Sun, 27 Apr 2025 19:59:08 +0200
with message-id <5078740.0VBMTVartN@treadstone-71>
and subject line 
has caused the Debian Bug report #1038872,
regarding qt6-shadertools-dev: Installs private headers when it shouldn't
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1038872: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038872
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: qt6-shadertools-dev
Version: 6.4.2-1
Severity: normal
X-Debbugs-Cc: lisandro@debian.org

Hi! I just noticed the package is installing private headers when it
shouldn't.


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: arm64

Kernel: Linux 6.1.0-9-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages qt6-shadertools-dev depends on:
ii  libqt6shadertools6  6.4.2-1
ii  qt6-shader-baker    6.4.2-1

qt6-shadertools-dev recommends no packages.

qt6-shadertools-dev suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
Hi,

mixing public and private headers is actually intentional in this case.
qt6-shadertools does not expose any public API at this stage. If that 
changes, we can still split the package.


-- 
Med vänliga hälsningar

Patrick Franz

--- End Message ---
Reply to: