[bts-link] source package src:glibc

2021-11-11 Thread debian-bts-link
#
# bts-link upstream status pull for source package src:glibc
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
# https://bts-link-team.pages.debian.net/bts-link/
#

user debian-bts-l...@lists.debian.org

# remote status report for #998622 (http://bugs.debian.org/998622)
# Bug title: glibc: CVE-2021-43396: Conversion from ISO-2022-JP-3 with iconv 
may emit spurious NUL character on state reset
#  * http://sourceware.org/bugzilla/show_bug.cgi?id=28524
#  * remote status changed: (?) -> RESOLVED
#  * remote resolution changed: (?) -> FIXED
#  * closed upstream
tags 998622 + fixed-upstream
usertags 998622 + status-RESOLVED resolution-FIXED

thanks



Processed: [bts-link] source package src:glibc

2021-11-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package src:glibc
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #998622 (http://bugs.debian.org/998622)
> # Bug title: glibc: CVE-2021-43396: Conversion from ISO-2022-JP-3 with iconv 
> may emit spurious NUL character on state reset
> #  * http://sourceware.org/bugzilla/show_bug.cgi?id=28524
> #  * remote status changed: (?) -> RESOLVED
> #  * remote resolution changed: (?) -> FIXED
> #  * closed upstream
> tags 998622 + fixed-upstream
Bug #998622 [src:glibc] glibc: CVE-2021-43396: Conversion from ISO-2022-JP-3 
with iconv may emit spurious NUL character on state reset
Added tag(s) fixed-upstream.
> usertags 998622 + status-RESOLVED resolution-FIXED
There were no usertags set.
Usertags are now: status-RESOLVED resolution-FIXED.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
998622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998622
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#999465: tzdata: asks debconf question tzdata/Areas twice

2021-11-11 Thread Andreas Beckmann
Package: tzdata
Version: 2021e-1
Severity: normal

Hi,

when (manually) installing tzdata in my minimal pbuilder chroots, the
debconf question tzdata/Areas gets asked twice: once in the
pre-configuration step, once during package configuration:

# apt-get install tzdata
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
  tzdata
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/291 kB of archives.
After this operation, 3431 kB of additional disk space will be used.
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based 
frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 
78, <> line 1.)
debconf: falling back to frontend: Readline
Preconfiguring packages ...
Configuring tzdata
--

Please select the geographic area in which you live. Subsequent configuration 
questions will narrow this down by presenting a list of cities, representing 
the time zones in which they are located.

  1. Africa  2. America  3. Antarctica  4. Australia  5. Arctic  6. Asia  7. 
Atlantic  8. Europe  9. Indian  10. Pacific  11. US  12. Etc
Geographic area: 8

Please select the city or region corresponding to your time zone.

  1. Amsterdam  5. Belfast 9. Brussels13. Chisinau17. Guernsey 
21. Jersey   25. Lisbon  29. Madrid 33. Monaco   37. Paris  41. 
Rome45. Saratov 49. Stockholm  53. Ulyanovsk  57. Vienna 61. 
Zagreb
  2. Andorra6. Belgrade10. Bucharest  14. Copenhagen  18. Helsinki 
22. Kaliningrad  26. Ljubljana   30. Malta  34. Moscow   38. Podgorica  42. 
Samara  46. Simferopol  50. Tallinn54. Uzhgorod   58. Vilnius62. 
Zaporozhye
  3. Astrakhan  7. Berlin  11. Budapest   15. Dublin  19. Isle_of_Man  
23. Kiev 27. London  31. Mariehamn  35. Nicosia  39. Prague 43. 
San_Marino  47. Skopje  51. Tirane 55. Vaduz  59. Volgograd  63. 
Zurich
  4. Athens 8. Bratislava  12. Busingen   16. Gibraltar   20. Istanbul 
24. Kirov28. Luxembourg  32. Minsk  36. Oslo 40. Riga   44. 
Sarajevo48. Sofia   52. Tiraspol   56. Vatican60. Warsaw
Time zone: 7

Selecting previously unselected package tzdata.
(Reading database ... 14597 files and directories currently installed.)
Preparing to unpack .../tzdata_2021e-1_all.deb ...
Unpacking tzdata (2021e-1) ...
Setting up tzdata (2021e-1) ...
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based 
frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 
78.)
debconf: falling back to frontend: Readline
Configuring tzdata
--

Please select the geographic area in which you live. Subsequent configuration 
questions will narrow this down by presenting a list of cities, representing 
the time zones in which they are located.

  1. Africa  2. America  3. Antarctica  4. Australia  5. Arctic  6. Asia  7. 
Atlantic  8. Europe  9. Indian  10. Pacific  11. US  12. Etc
Geographic area: 8


Current default time zone: 'Europe/Berlin'
Local time is now:  Thu Nov 11 13:40:48 CET 2021.
Universal Time is now:  Thu Nov 11 12:40:48 UTC 2021.
Run 'dpkg-reconfigure tzdata' if you wish to change it.


The minimal chroot has a pre-existing /etc/timezone containing Etc/UTC,
but even if I delete that before installing tzdata that question is
repeated. There are no pre-existing "*tzdata*" entries in the debconf
database.


Andreas

PS: tzdata gets usually installed as a dependency when manually
entering the pbuilder environment and doing apt-get build-dep $pkg
to do some interactive build testing ...