Processed: bug 933623 is forwarded to https://release.debian.org/transitions/html/auto-petsc.html
Processing commands for cont...@bugs.debian.org: > forwarded 933623 https://release.debian.org/transitions/html/auto-petsc.html Bug #933623 [release.debian.org] transition: petsc Set Bug forwarded-to-address to 'https://release.debian.org/transitions/html/auto-petsc.html'. > thanks Stopping processing here. Please contact me if you need assistance. -- 933623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933623 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#933623: transition: petsc
Control: forwarded -1 https://release.debian.org/transitions/html/auto-petsc.html Control: tags -1 pending Hi Drew, On 01-08-2019 05:45, Drew Parsons wrote: > The hypre 2.16.0 upgrade revealed an incompatibility between petsc 3.10 > and hypre 2.16.0. PETSc upstream has dealt with the issue with a > couple of recent patches. The best way to stabilise hypre and petsc > is to proceed with the petsc 3.11 transition. > > The slepc 3.11 transition should be considered part of this > transition. I'm also upgrading dolfin to 2019.1.0 (which is really a > just a fenics upgrade rather than a library transition). > > A mumps 5.2.0 transition is waiting, but I'll wait for this one to > clear before starting that. > > Ben file: > > title = "petsc"; > is_affected = .depends ~ > /\b(libpetsc\-complex3\.11|libpetsc\-complex3\.11\-dbg|libpetsc\-complex3\.11\-dev|libpetsc\-real3\.11|libpetsc\-real3\.11\-dbg|libpetsc\-real3\.11\-dev|libpetsc3\.11\-dev\-common|libpetsc3\.11\-dev\-examples|petsc3\.11\-doc|libpetsc\-complex3\.10|libpetsc\-complex3\.10\-dbg|libpetsc\-complex3\.10\-dev|libpetsc\-real3\.10|libpetsc\-real3\.10\-dbg|libpetsc\-real3\.10\-dev|libpetsc3\.10\-dev\-common|libpetsc3\.10\-dev\-examples|petsc3\.10\-doc)\b/; > is_good = .depends ~ > /\b(libpetsc\-complex3\.11|libpetsc\-complex3\.11\-dbg|libpetsc\-complex3\.11\-dev|libpetsc\-real3\.11|libpetsc\-real3\.11\-dbg|libpetsc\-real3\.11\-dev|libpetsc3\.11\-dev\-common|libpetsc3\.11\-dev\-examples|petsc3\.11\-doc)\b/; > is_bad = .depends ~ > /\b(libpetsc\-complex3\.10|libpetsc\-complex3\.10\-dbg|libpetsc\-complex3\.10\-dev|libpetsc\-real3\.10|libpetsc\-real3\.10\-dbg|libpetsc\-real3\.10\-dev|libpetsc3\.10\-dev\-common|libpetsc3\.10\-dev\-examples|petsc3\.10\-doc)\b/; This looks like (haven't checked 100%) the auto-generated one, so I set the forwarded tag. I'll trigger the two remaining binNMU's shortly. Paul signature.asc Description: OpenPGP digital signature
Processed (with 1 error): Re: Bug#933623: transition: petsc
Processing control commands: > forwarded -1 Unknown command or malformed arguments to command. > tags -1 pending Bug #933623 [release.debian.org] transition: petsc Added tag(s) pending. -- 933623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933623 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 934183 to buster-pu: package open-vm-tools/2:10.3.10-1+deb10u1
Processing commands for cont...@bugs.debian.org: > retitle 934183 buster-pu: package open-vm-tools/2:10.3.10-1+deb10u1 Bug #934183 [release.debian.org] stretch-pu: package open-vm-tools/2:10.3.10-1+deb10u1 Changed Bug title to 'buster-pu: package open-vm-tools/2:10.3.10-1+deb10u1' from 'stretch-pu: package open-vm-tools/2:10.3.10-1+deb10u1'. > thanks Stopping processing here. Please contact me if you need assistance. -- 934183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934183 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#934183: stretch-pu: package open-vm-tools/2:10.3.10-1+deb10u1
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu
Hi release-team,
I'd like to upload a fix for open-vm-tools to proposed-updates which
actually allows to recognize buster.
`lsb_release -sd` currently prints
Debian GNU/Linux 10 (buster)
but the current implementation in open-vm-tools expects 10. in the
output.
I'd assume that this issue will be fixed with the pointrelease anyway,
as the lsb_release output should change to 10.1, but I think it makes
sense to fix it, just in case people do partial upgrades.
Diff is attached.
Thanks,
Bernd
--
Bernd ZeimetzDebian GNU/Linux Developer
http://bzed.dehttp://www.debian.org
GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F
diff --git a/debian/changelog b/debian/changelog
index fdd98af2..316bfa27 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,17 @@
+open-vm-tools (2:10.3.10-1+deb10u1) buster; urgency=medium
+
+ * [efb4df1] Fix guest OS reporting for Debian/Buster.
+Without this fix, open-vm-tools report other4xLinux64Guest instead of
+Debian/Buster.
+Reason is the output of lsb_release, which outputs:
+$ lsb_release -sd
+Debian GNU/Linux 10 (buster)
+But the code in open-vm-tools expects '10.'.
+Thanks to Oliver Kurth (Closes: #934005)
+ * [2308b74] Updating gbp.conf for buster.
+
+ -- Bernd Zeimetz Wed, 07 Aug 2019 21:09:29 +0200
+
open-vm-tools (2:10.3.10-1) unstable; urgency=high
* [122e511] Update upstream source from tag 'upstream/10.3.10'
diff --git a/debian/gbp.conf b/debian/gbp.conf
index bf4163e8..9a54689e 100644
--- a/debian/gbp.conf
+++ b/debian/gbp.conf
@@ -1,3 +1,6 @@
+[DEFAULT]
+debian-branch = buster
+
[buildpackage]
sign-tags = True
posttag = git push && git push --tags
diff --git a/debian/patches/fix-buster-OS-reporting
b/debian/patches/fix-buster-OS-reporting
new file mode 100644
index ..eb9b2159
--- /dev/null
+++ b/debian/patches/fix-buster-OS-reporting
@@ -0,0 +1,11 @@
+--- a/open-vm-tools/lib/misc/hostinfoPosix.c
b/open-vm-tools/lib/misc/hostinfoPosix.c
+@@ -814,7 +814,7 @@ HostinfoGetOSShortName(char *distro,
+ Str_Strcpy(distroShort, STR_OS_DEBIAN_8, distroShortSize);
+ } else if (strstr(distroLower, "9.")) {
+ Str_Strcpy(distroShort, STR_OS_DEBIAN_9, distroShortSize);
+- } else if (strstr(distroLower, "10.")) {
++ } else if (strstr(distroLower, "10")) {
+ Str_Strcpy(distroShort, STR_OS_DEBIAN_10, distroShortSize);
+ }
+} else if (StrUtil_StartsWith(distroLower, "enterprise linux") ||
diff --git a/debian/patches/series b/debian/patches/series
index 8140b204..39debc1e 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,3 +1,4 @@
debian/pam-use-common-auth-account
debian/max_nic_count
debian/scsi-udev-rule
+fix-buster-OS-reporting
Bug#914404: marked as done (transition: libmng)
Your message dated Wed, 7 Aug 2019 20:21:27 +0100
with message-id <20190807192127.ga2...@powdarrmonkey.net>
and subject line Re: Bug#914404: transition: libmng
has caused the Debian Bug report #914404,
regarding transition: libmng
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 ow...@bugs.debian.org
immediately.)
--
914404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914404
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Hi Release Team,
I plan to upload new version of libmng (already in experimental and
updating it again).
Direct reverse dependencies are:
tuxonice-userui
libxine2-misc-plugins
libsynfig0a
qt5-image-formats-plugins
libqtgui4
libdevil1c2
gimp
Thanks and let me know how to proceed.
--
Kartik Mistry | IRC: kart_
{0x1f1f, kartikm}.wordpress.com
--- End Message ---
--- Begin Message ---
On Wed, Jan 09, 2019 at 11:24:43AM +0100, Emilio Pozuelo Monfort wrote:
> On 28/11/2018 19:03, Emilio Pozuelo Monfort wrote:
> > On 23/11/2018 08:15, Kartik Mistry wrote:
> >> Package: release.debian.org
> >> Severity: normal
> >> User: release.debian@packages.debian.org
> >> Usertags: transition
> >>
> >> Hi Release Team,
> >>
> >> I plan to upload new version of libmng (already in experimental and
> >> updating it again).
> >>
> >> Direct reverse dependencies are:
> >>
> >> tuxonice-userui
> >> libxine2-misc-plugins
> >> libsynfig0a
> >> qt5-image-formats-plugins
> >> libqtgui4
> >> libdevil1c2
> >> gimp
> >>
> >> Thanks and let me know how to proceed.
> >
> > Do the rdeps build against the new libmng?
>
> Did you test the rdeps? Note the transition freeze is just around the corner,
> so
> I guess this will have to wait for after buster.
Closing until the maintainer has time to attend to this.
--
Jonathan Wiltshire j...@debian.org
Debian Developer http://people.debian.org/~jmw
4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51--- End Message ---
Processed: closing 917289, closing 918308, closing 918341, closing 918539, closing 918677, closing 918687 ...
Processing commands for cont...@bugs.debian.org: > close 917289 Bug #917289 [release.debian.org] transition: ntfs-3g Marked Bug as done > close 918308 Bug #918308 [release.debian.org] transition: botan Marked Bug as done > close 918341 Bug #918341 [release.debian.org] transition: jemalloc Marked Bug as done > close 918539 Bug #918539 [release.debian.org] mini-transition: libnfs Marked Bug as done > close 918677 Bug #918677 [release.debian.org] transition: pacemaker Marked Bug as done > close 918687 Bug #918687 [release.debian.org] transition: exempi Marked Bug as done > close 918750 Bug #918750 [release.debian.org] transition: simbody Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 917289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917289 918308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918308 918341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918341 918539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918539 918677: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918677 918687: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918687 918750: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918750 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 913210, closing 913299, closing 913768, closing 913837, closing 914131, closing 914392 ...
Processing commands for cont...@bugs.debian.org: > close 913210 Bug #913210 [release.debian.org] transition: libqalculate Marked Bug as done > close 913299 Bug #913299 [release.debian.org] transition: glew Marked Bug as done > close 913768 Bug #913768 [release.debian.org] transition: glibc Marked Bug as done > close 913837 Bug #913837 [release.debian.org] transition: hdf5 Marked Bug as done > close 914131 Bug #914131 [release.debian.org] transition: openvdb Marked Bug as done > close 914392 Bug #914392 [release.debian.org] transition: coin3 Marked Bug as done > close 914416 Bug #914416 [release.debian.org] transition: libnftnl Marked Bug as done > close 914516 Bug #914516 [release.debian.org] transition: hunspell Marked Bug as done > close 914563 Bug #914563 [release.debian.org] transition: alglib Marked Bug as done > close 914662 Bug #914662 [release.debian.org] transition: hypre Marked Bug as done > close 915790 Bug #915790 [release.debian.org] transition: lm-sensors Marked Bug as done > close 917255 Bug #917255 [release.debian.org] transition: yaml-cpp Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 913210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913210 913299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913299 913768: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913768 913837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913837 914131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914131 914392: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914392 914416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914416 914516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914516 914563: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914563 914662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914662 915790: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915790 917255: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917255 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 903370, closing 903589, closing 905889, closing 906758, closing 907771, closing 909288 ...
Processing commands for cont...@bugs.debian.org: > close 903370 Bug #903370 [release.debian.org] transition: petsc Marked Bug as done > close 903589 Bug #903589 [release.debian.org] transition: uwsgi Marked Bug as done > close 905889 Bug #905889 [release.debian.org] transition: gdbm Marked Bug as done > close 906758 Bug #906758 [release.debian.org] transition: cfitsio Marked Bug as done > close 907771 Bug #907771 [release.debian.org] transition: qcustomplot Marked Bug as done > close 909288 Bug #909288 [release.debian.org] transition: kdepim 18.08 Marked Bug as done > close 910977 Bug #910977 [release.debian.org] transition: atlas-cpp Marked Bug as done > close 911388 Bug #911388 [release.debian.org] transition: superlu-dist Marked Bug as done > close 911445 Bug #911445 [release.debian.org] transition: libtirpc Marked Bug as done > close 912164 Bug #912164 [release.debian.org] transition: llvm-defaults Marked Bug as done > close 912853 Bug #912853 [release.debian.org] transition: icu Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 903370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903370 903589: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903589 905889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905889 906758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906758 907771: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907771 909288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909288 910977: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910977 911388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911388 911445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911445 912164: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912164 912853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912853 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#934176: RM: python-axiom -- ROM; no Python 3 support and no reverse deps
Package: ftp.debian.org Severity: normal Upstream Python 3 support is only proposed: https://github.com/twisted/axiom/issues/106 Reverse deps checked by dak rm -Rnb python-axiom
Bug#934175: RM: moksha.hub -- ROM; dead upstream; no Python 2 support and no reverse deps
Package: ftp.debian.org Severity: normal The source doesn't support Python 2, http://mokshaproject.net/ redirects to https://reactdom.com/graphql and I couldn't find a new upstream location. Reverse deps checked with dak rm -Rnb python-moksha.hub
Bug#904418: transition: json-c
Control: tag -1 confirmed On Tue, Jul 30, 2019 at 11:17:56AM +0200, Gianfranco Costamagna wrote: > Hello, > On Mon, 8 Jul 2019 08:47:19 +0200 Gianfranco Costamagna > wrote: > > Hello all, > > > > > > So yeah 0.12.1-2 should be alright for sid/buster, and 0.13 will have > > > > to wait > > > > for bullseye after the freeze. > > > > > > Thank you very much Boyuan <3 > > > > > > I will have a look in a moment. > > > > > > > Hello, I fixed all the failing reverse-dependencies in Ubuntu, and > > completed the transition > > successfully there (and posted patches on BTS). > > The only remaining issue is syslog-ng on i386 and s390x, but the maintainer > > is already working on (and we fixed with a patch in Ubuntu) > > I would like to do this one before gcc changes default or something else > > entangles, it should be a trivial one, > > I plan to NMU as needed. > > > > > syslog-ng is now fine. > > Can we go ahead? Please go ahead in unstable. -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51
Processed: Re: Bug#904418: transition: json-c
Processing control commands: > tag -1 confirmed Bug #904418 [release.debian.org] transition: json-c Added tag(s) confirmed. -- 904418: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904418 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 882658, closing 894159, closing 894342, closing 895006, closing 895022, closing 895193 ...
Processing commands for cont...@bugs.debian.org: > close 882658 Bug #882658 [release.debian.org] transition: cgal Marked Bug as done > close 894159 Bug #894159 [release.debian.org] transition: icu Marked Bug as done > close 894342 Bug #894342 [release.debian.org] transition: kdepim Marked Bug as done > close 895006 Bug #895006 [release.debian.org] transition: poco Marked Bug as done > close 895022 Bug #895022 [release.debian.org] transition: hypre Marked Bug as done > close 895193 Bug #895193 [release.debian.org] transition: openmpi Marked Bug as done > close 895571 Bug #895571 [release.debian.org] transition: http-parser Marked Bug as done > close 897165 Bug #897165 [release.debian.org] transition: botan Marked Bug as done > close 897270 Bug #897270 [release.debian.org] transition: libonig Marked Bug as done > close 897772 Bug #897772 [release.debian.org] transition: miniupnpc Marked Bug as done > close 898044 Bug #898044 [release.debian.org] transition: orocos-kdl Marked Bug as done > close 898934 Bug #898934 [release.debian.org] transition: libmygpo-qt Marked Bug as done > close 901546 Bug #901546 [release.debian.org] transition: libcdio Marked Bug as done > close 901880 Bug #901880 [release.debian.org] transition: libantlr3c Marked Bug as done > close 902558 Bug #902558 [release.debian.org] transition: imagemagick Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 882658: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882658 894159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894159 894342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894342 895006: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895006 895022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895022 895193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895193 895571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895571 897165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897165 897270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897270 897772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897772 898044: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898044 898934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898934 901546: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901546 901880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901880 902558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902558 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: block 933685 with 933684
Processing commands for cont...@bugs.debian.org: > block 933685 with 933684 Bug #933685 [release.debian.org] transition: http-parser 933685 was not blocked by any bugs. 933685 was not blocking any bugs. Added blocking bug(s) of 933685: 933684 > thanks Stopping processing here. Please contact me if you need assistance. -- 933685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933685 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#933685: transition: http-parser
Jonathan Wiltshire wrote... > On Mon, Aug 05, 2019 at 12:12:46AM +0200, Christoph Biedl wrote: > > Thanks, now uploaded to unstable. > > Just one failure, in python-httptools > https://buildd.debian.org/status/package.php?p=python-httptools Yep, Bug report with upstream fix filed as #933684 My plan is to NMU at the weekend. Christoph signature.asc Description: PGP signature
Bug#933685: transition: http-parser
On Mon, Aug 05, 2019 at 12:12:46AM +0200, Christoph Biedl wrote: > Jonathan Wiltshire wrote... > > > Control: tag -1 confirmed > > > > On Thu, Aug 01, 2019 at 10:12:08PM +0200, Christoph Biedl wrote: > > > following the procedures as written in the Debian wiki, I am requesting > > > a transition slot for the http-parser library 2.9.2, accepted in > > > experimental earlier today. > > > > Please go ahead in unstable. > > Thanks, now uploaded to unstable. Just one failure, in python-httptools https://buildd.debian.org/status/package.php?p=python-httptools Thanks, -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51
Processed: closing 932618
Processing commands for cont...@bugs.debian.org: > close 932618 Bug #932618 [release.debian.org] transition: librsync Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 932618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932618 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 933645
Processing commands for cont...@bugs.debian.org: > tags 933645 + pending Bug #933645 [release.debian.org] transition: libvpx Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 933645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933645 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#934163: buster-pu: package ncurses/6.1+20181013-2+deb10u1
Package: release.debian.org Severity: normal Tags: buster d-i User: release.debian@packages.debian.org Usertags: pu I have just uploaded ncurses 6.1+20181013-2+deb10u1 to Buster which contains a one-line fix for bug #933053[1], the same as in version 6.1+20190713-2 which is now in testing. Some background: for about 20 years, xterm has support for a special escape sequence which causes characters to be repeated. In ncurses 6.1-1 and later, an entry was added to the xterm* terminfo descriptions announcing this feature. The ncurses library makes use of it for line drawing characters. Now there are many terminal emulators out there who set TERM to xterm or xterm-256color, and they did generally not actually support this escape sequence, leading to the line drawing characters not repeated which looks then very bad. You can see a few screenshots in bug #933053. Most popular terminal emulators in Buster have already been fixed, so desktop systems are largely unaffected. However, if people connect to a Buster server from an older system, say Debian 9 or Ubuntu 16.04, they may experience this issue. The solution is to drop the particular entry from the xterm* terminfo entries, so that the ncurses library no longer uses it. I have tested the fix with the Stretch versions of konsole and gnome-terminal and a Buster chroot. Since ncurses builds a udeb I need a d-i ack, debian-boot@ and kibi@ are already in X-Debbugs-CC. The libraries are not touched by the patch and are identical with and without it. The xterm terminfo file is used by src:debian-installer-utils to build di-utils-terminfo.udeb, but only on kfreebsd. 1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933053 diff -Nru ncurses-6.1+20181013/debian/changelog ncurses-6.1+20181013/debian/changelog --- ncurses-6.1+20181013/debian/changelog 2019-02-11 18:17:20.0 +0100 +++ ncurses-6.1+20181013/debian/changelog 2019-08-05 20:03:21.0 +0200 @@ -1,3 +1,10 @@ +ncurses (6.1+20181013-2+deb10u1) buster; urgency=medium + + * Drop "rep" from xterm-new and derived terminfo descriptions +(Closes: #933053). + + -- Sven Joachim Mon, 05 Aug 2019 20:03:21 +0200 + ncurses (6.1+20181013-2) unstable; urgency=medium * Add Breaks against libmono-corlib4.5-cil (<< 4.6.2.7+dfsg-2) diff -Nru ncurses-6.1+20181013/debian/xterm.ti ncurses-6.1+20181013/debian/xterm.ti --- ncurses-6.1+20181013/debian/xterm.ti 2019-02-11 18:16:04.0 +0100 +++ ncurses-6.1+20181013/debian/xterm.ti 2019-08-05 20:02:15.0 +0200 @@ -136,7 +136,7 @@ kcbt=\E[Z, kent=\EOM, rin=\E[%p1%dT, - use=ansi+rep, +# use=ansi+rep, use=ecma+strikeout, use=xterm+pcfkeys, use=xterm+tmux, signature.asc Description: PGP signature
Re: Bits from the Release Team: ride like the wind, Bullseye!
Lisandro Damián Nicanor Pérez Meyer writes ("Re: Bits from the Release Team:
ride like the wind, Bullseye!"):
> No, what I have been perceiving (and pretty please note that this is my
> personal "feeling") is that maintainers, specially library maintainers, have
> even more and more "stuff to care for".
I can see why you feel that way.
I think maybe we need to make it easier for the maintainer of a
widely-used library to push some of this out to depending packages.
(And I speak as a maintainer of a leaf package with a thorough
autopkgtest suite which often blocks the migration of my
dependencies.)
Lisandro, would it meet your needs if you had free licence to file RC
bugs against all packages which were blocking your migration, before
you had done the investigation yourself ?
I think the effect would be that a maintainer of a dependent package
would have to engage with the situation and if they did nothing for
long enough, the autoremoval would kick in. Then your library would
be able to migrate.
This seems similar to the approach we take with (say) new compilers,
which trigger FTBFS bugs in depending packages. The compiler
maintainers do not investigate the issues - they file bugs, which
eventually become RC, and then the depending packages must either be
fixed our autoremoved.
(Of course some library maintainers would prefer to do some
investigation first.)
Ian.
Bug#934132: unblock: elogind/241.3-1+debian1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Dear Release Team, Further to recent discussions on #debian-release and at the suggestion of jmw I request unblocking of the testing transition of elogind. Transition of elogind to testing was blocked on 16 July after a discussion on irc. As far as I understand, the objections raised on irc have been:- 1) To Conflicts/Provides/Replaces libsystemd0 is too dangerous. 2) What prevents this getting installed where it shouldn't. 3) Claims to provide libsystemd ABI, but does not. 4) libelogind0 breaks the example program in sd_journal_next. So far there have been no reports of breakages relating to 1). We are currently early in the release cycle. It seems to me that this is precisely the time to be testing this more widely. 2) is prevented in most situations by libelogind0 also conflicting with systemd. You cannot coinstall systemd and libelogind0. It is possible to replace libsystemd0 with libelogind0 in chroots and initless containers. However, my testing of such environments demonstrates no breakage. In such a scenario the functions in both libsystemd0 and libelogind0 return non fatal errors. 3) is open to interpretation depending on your definition of ABI compatibility. Certainly libelogind.so exports the same symbols as libsystemd.so with identical binary interface. This was the agreed solution to #923244 so that policykit-1 works with libelogind without recompilation. However, there are functional differences betweent he two libraries and libelogind0 only provides a subset of libsystemd0 functionality. The libelogind0 package description describes these limitations fully although I am happy to reword or make that more explicit if you feel it could be improved. 4) In the light of the libelogind0 package description saying "The sd-login(3), sd-bus(3) and sd-id128(3) APIs are implemented in full, sd-journal(3) is only implemented by redirecting sd_journal_print* and sd_journal_send* calls to syslog(3) with other functions returning -ENOSYS and sd-hwdb(3) contains stubs returning -ENOSYS." the example program in sd_journal_next behaves as you would expect by exiting with 'Function not implemented' in response to sd_journal_open() returning -ENOSYS. I agree wholeheartedly that Debian's elogind should not break systemd. To date there have been no reports of any such breakage and I will be happy to receive and resolve bug reports in any such eventuality. Elogind provides choice and makes it possible to install many current desktop environments on non-systemd init systems: I have successfully tested xfce, cinnamon, mate and budgie and there are reports of gnome working too. Thank you for your consideration. Mark
Bug#934112: transition: poco
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Hey release team, I would like to transition Poco to the new ABI version. Cheers Jochen Ben file: title = "poco"; is_affected = .depends ~ /\b(libpococrypto60|libpocodata60|libpocodatamysql60|libpocodataodbc60|libpocodatasqlite60|libpocoencodings60|libpocofoundation60|libpocojson60|libpocomongodb60|libpoconet60|libpoconetssl60|libpocoredis60|libpocoutil60|libpocoxml60|libpocozip60)\b/ | .depends ~ /\b(libpococrypto62|libpocodata62|libpocodatamysql62|libpocodataodbc62|libpocodatasqlite62|libpocoencodings62|libpocofoundation62|libpocojson62|libpocomongodb62|libpoconet62|libpoconetssl62|libpocoredis62|libpocoutil62|libpocoxml62|libpocozip62)\b/; is_good = .depends ~ /\b(libpococrypto62|libpocodata62|libpocodatamysql62|libpocodataodbc62|libpocodatasqlite62|libpocoencodings62|libpocofoundation62|libpocojson62|libpocomongodb62|libpoconet62|libpoconetssl62|libpocoredis62|libpocoutil62|libpocoxml62|libpocozip62)\b/; is_bad = .depends ~ /\b(libpococrypto60|libpocodata60|libpocodatamysql60|libpocodataodbc60|libpocodatasqlite60|libpocoencodings60|libpocofoundation60|libpocojson60|libpocomongodb60|libpoconet60|libpoconetssl60|libpocoredis60|libpocoutil60|libpocoxml60|libpocozip60)\b/; -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: armhf (armv7l) Kernel: Linux 4.19.0-5-armmp (SMP w/8 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
