Hello, what is this? Kimberly Thompson, kathompson4...@gmail.com

On Nov 19, 2017 11:45 AM, "final notice" <p...@debian.org> wrote:

important information

<http://shineslim.com/cl/r-S5K5SI2NHJPS13I2CS1E3O5SE3NS0S0S0S15S2SBSCCS21FS21OSA>

<http://shineslim.com/cl/ua-S5K5SI2NHJPS13I2CS1E3O5SE3NS0S0S0S15S2SBSCCS21FS21OSA>

<http://shineslim.com/cl/op-S5K5SI2NHJPS13I2CS1E3O5SE3NS0S0S0S15S2SBSCCS21FS21OSA>
















































































Package: release.debian.org Severity: normal User:
release.debian....@packages.debian.org Usertags: binnmu debhelper 10.10.7
fixed a regression in debhelper 10.10.6 that prevented dbgsym packages from
being generated. There are probably several packages affected but I am not
aware of any easy mechanism to determine which packages were built against
debhelper 10.10.6 so I've just included a binNMU request for the two
packages I'm aware of that were definitely affected by this. debhelper
(10.10.7) unstable; urgency=medium * dh_strip: Fix a regression that caused
debug symbols for executables to be discarded instead of included into
debug packages. nmu xdg-desktop-portal_0.8-3 . amd64 arm64 i386 mips64el
mips powerpc ppc64el s390x . unstable . -m "Rebuild to include dbgsym
packages after debhelper 10.10.7 fix" nmu xdg-desktop-portal-gtk_0.7-3 .
amd64 arm64 i386 mips64el mips powerpc ppc64el s390x . unstable . -m
"Rebuild to include dbgsym packages after debhelper 10.10.7 fix" -- bye,
pabs https://wiki.debian.org/PaulWise

Reply via email to