Bug#949267: transition: netcdf
On 1/27/20 3:59 PM, Sebastiaan Couwenberg wrote: > On 1/26/20 11:34 AM, Sebastiaan Couwenberg wrote: >> On 1/25/20 11:34 AM, Sebastiaan Couwenberg wrote: >>> On 1/24/20 12:54 PM, Sebastiaan Couwenberg wrote: On 1/23/20 8:40 AM, Sebastiaan Couwenberg wrote: > netcdf (1:4.7.3-1) is built & installed on all release architectures, > please schedule the binNMUs except netcdf-fortan which is currently > building on the buildds. The binNMUs that were scheduled have finished, please schedule the remainder of Dependency level 2. >>> >>> ferret-vis is done on all release architectures, please schedule the >>> pyferret. >> >> magics++ is done too, cdo & metview can be schedule as well. > > grass is done, qgis can be scheduled. vtk7 is done too, lammps can be scheduled. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#949921: buster-pu: package uim_1.8.8-4+deb10u3
On Mon, 27 Jan 2020 15:18:15 +0900 NOKUBI Takatsugu wrote:
> We uim maintainers had an another probrem #945344.
> The last update registers unusable uim modules.
The last diff lacks some commits, here is a new diff.
https://salsa.debian.org/debian/uim/snippets/386
diff --git a/debian/changelog b/debian/changelog
index 9b9b64b..74ffc2c 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,20 @@
+uim (1:1.8.8-4+deb10u3) buster; urgency=medium
+
+ * Non-maintainer upload.
+
+ [ NOKUBI Takatsugu ]
+ * d/libuim-data.postint: add uim-mozc (See #939588)
+
+ [ HIGUCHI Daisuke (VDR dai) ]
+ * d/libuim-data.postint: add uim-chewing
+
+ [ YOSHINO Yoshihito ]
+ * d/libuim-data.postinst: unregister not-installed modules (Closes: #945344).
+The previous upload to fix #939588 caused regression, which has
+accidentally registered some not-installed modules.
+
+ -- YOSHINO Yoshihito Sun, 12 Jan 2020 19:42:26 +0900
+
uim (1:1.8.8-4+deb10u2) buster; urgency=medium
[ HIGUCHI Daisuke (VDR dai) ]
diff --git a/debian/libuim-data.postinst b/debian/libuim-data.postinst
index b0480fd..fd3891e 100755
--- a/debian/libuim-data.postinst
+++ b/debian/libuim-data.postinst
@@ -1,9 +1,19 @@
#!/bin/sh
+register_module_was_broken=false
+
register_module() {
PKGNAME=$1
MODNAME=$2
-dpkg-query -W -f='${Status}\n' $PKGNAME 2>/dev/null | grep
"not-installed" > /dev/null
+QSTRING=$(dpkg-query -W -f='${Status}\n' $PKGNAME 2>/dev/null)
+if [ $? = "1" ]
+then
+if $register_module_was_broken; then
+uim-module-manager --unregister $MODNAME --path /var/lib/uim
+fi
+return 0
+fi
+echo $QSTRING | grep "not-installed" > /dev/null
if [ $? = "1" ]
then
uim-module-manager --register $MODNAME --path /var/lib/uim
@@ -12,6 +22,17 @@ register_module() {
case "$1" in
configure)
+if dpkg --compare-versions "$2" lt-nl "1:1.8.8-4+deb10u2.1" && \
+ dpkg --compare-versions "$2" gt "1:1.8.8-4"; then
+# buster
+register_module_was_broken=true
+fi
+if dpkg --compare-versions "$2" lt-nl "1:1.8.8-6.1~" && \
+ dpkg --compare-versions "$2" gt "1:1.8.8-5~"; then
+# bullseye/sid
+register_module_was_broken=true
+fi
+
if which uim-module-manager >/dev/null 2>&1; then
register_module uim-anthy anthy-utf8
register_module uim-byeoru byeoru
@@ -24,6 +45,8 @@ case "$1" in
register_module uim-skk skk
register_module uim-tcode tutcode
register_module uim-viqr viqr
+register_module uim-mozc mozc
+register_module uim-chewing chewing
fi
;;
@@ -37,4 +60,4 @@ case "$1" in
;;
esac
-exit 0
\ No newline at end of file
+exit 0
Processed: Re: Bug#948855: buster-pu: package iputils/3:20180629-2
Processing control commands: > tags -1 - moreinfo Bug #948855 [release.debian.org] buster-pu: package iputils/3:20180629-2 Removed tag(s) moreinfo. -- 948855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948855 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#948855: buster-pu: package iputils/3:20180629-2
Control: tags -1 - moreinfo On Fri, Jan 24, 2020 at 10:11:38PM +, Adam D. Barratt wrote: > > I'd like to fix > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947921 in > > buster. Ping has some issues coping with explicitly specified source > > interfaces when pinging DNS names and DNS returns multiple addresses > > via getaddrinfo(). Please see the commit messages and the bug report > > for in-depth explanation of what's going on. > > The metadata for that bug report suggests that it affects the iputils > package in unstable, and is not currently fixed there. Is that correct? That's correct. Upstream has not yet made a release containing the fix, nor have I backported it to the version currently in testing (there are enough changes to make that nontrivial). I am making my request based on the patch author's report that it does, indeed, fix the problem in buster, and the fact that the fix has been accepted upstream. If you'd prefer, we can wait until the next buster point release, by which time we'll presumably have more testing of these patches. noah
Bug#948205: buster-pu: package sogo-connector/60.0.2-1
Hi again, On Sat, Jan 25, 2020 at 07:34:20PM +, Adam D. Barratt wrote: > The delights of mozilla-related packages and stable. :-( Please go > ahead. thanks! Also in NEW due the new binary package. Regards Carsten
Bug#948203: buster-pu: package compactheader/2.1.6-1
Hello Adam, On Sat, Jan 25, 2020 at 07:36:03PM +, Adam D. Barratt wrote: > It's obviously not an ideal situation, but please go ahead. yes, hopefully Mozilla wont change their AddOn API again within the next ESR cycle of TB. Uploaded minutes ago, it's in NEW due the new binary package. Hopefully the FTP-Master can act in time. :) Regards Carsten
Bug#948477: transition: openbabel
Hi Andrius, On 16-01-2020 11:48, mer...@debian.org wrote: > Thanks a lot, I will wait a week before working on the transition. I see you went ahead *and* you added an autopkgtest to openbabel. Obviously I love autopkgtests, however, the test fails and times out on arm64. In case you don't know how to fix the test for arm64, I suggest you mark the test with the skippable restriction and exit 77 at the start of the test if it detects it runs on arm64. Obviously, fixing the test is better. Paul signature.asc Description: OpenPGP digital signature
Bug#949893: marked as done (nmu: gsequencer_3.0.3-1)
Your message dated Mon, 27 Jan 2020 20:55:46 +0100 with message-id <503319b0-2792-f408-bae7-2a34d6bdd...@debian.org> and subject line Re: Bug#949893: nmu: gsequencer_3.0.3-1 has caused the Debian Bug report #949893, regarding nmu: gsequencer_3.0.3-1 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.) -- 949893: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949893 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: binnmu libinstpatch bumped its SONAME. Please binNMU gsequencer: nmu gsequencer_3.0.3-1 . ANY . unstable . -m "Rebuild against libinstpatch-1.0-2" dw gsequencer_3.0.3-1 . ANY . -m "libinstpatch-dev (>= 1.1.2)" Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Hi Sebastian, On 26-01-2020 20:30, Sebastian Ramacher wrote: > libinstpatch bumped its SONAME. Please binNMU gsequencer: > > nmu gsequencer_3.0.3-1 . ANY . unstable . -m "Rebuild against > libinstpatch-1.0-2" > dw gsequencer_3.0.3-1 . ANY . -m "libinstpatch-dev (>= 1.1.2)" Scheduled, thanks. Paul signature.asc Description: OpenPGP digital signature --- End Message ---
Bug#949838: stretch-pu: package perl/5.24.1-3+deb9u6
On Sat, Jan 25, 2020 at 07:21:48PM +, Adam D. Barratt wrote: > Control: tags -1 + confirmed > > On Sat, 2020-01-25 at 20:21 +0200, Niko Tyni wrote: > > Hi, I'd like to fix src:perl #915209 (FTBFS in 2020) in stretch with > > the attached debdiff. This is a build time test-only change with no > > run time effects. > > > > IIRC source only uploads are OK for stretch, is that correct? > > > > Please go ahead. Source-only is fine. Thanks, uploaded. -- Niko
Bug#949957: buster-pu: package freetds/1.00.104-1+deb10u1
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu
Hi
freetds in buster is affected by CVE-2019-13508 (cf. #944012). The
issue was fixed in unstable. This update is to address the issue as
well for buster.
Can you accept this update as well for the next buster point release?
Regards,
Salvatore
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-6-amd64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
diff -u freetds-1.00.104/debian/changelog freetds-1.00.104/debian/changelog
--- freetds-1.00.104/debian/changelog
+++ freetds-1.00.104/debian/changelog
@@ -1,3 +1,10 @@
+freetds (1.00.104-1+deb10u1) buster; urgency=medium
+
+ * Non-maintainer upload.
+ * tds: Make sure UDT has varint set to 8 (CVE-2019-13508) (Closes: #944012)
+
+ -- Salvatore Bonaccorso Mon, 27 Jan 2020 17:28:42 +0100
+
freetds (1.00.104-1) unstable; urgency=medium
* New upstream release.
diff -u freetds-1.00.104/src/tds/data.c freetds-1.00.104/src/tds/data.c
--- freetds-1.00.104/src/tds/data.c
+++ freetds-1.00.104/src/tds/data.c
@@ -1418,6 +1418,7 @@
tds_get_string(tds, tds_get_usmallint(tds), NULL, 0);
col->column_size = 0x7ffflu;
+ col->column_varint_size = 8;
return TDS_SUCCESS;
}
@@ -1425,6 +1426,7 @@
TDS_INT
tds_clrudt_row_len(TDSCOLUMN *col)
{
+ col->column_varint_size = 8;
/* TODO save other fields */
return sizeof(TDSBLOB);
}
Bug#949267: transition: netcdf
On 1/26/20 11:34 AM, Sebastiaan Couwenberg wrote: > On 1/25/20 11:34 AM, Sebastiaan Couwenberg wrote: >> On 1/24/20 12:54 PM, Sebastiaan Couwenberg wrote: >>> On 1/23/20 8:40 AM, Sebastiaan Couwenberg wrote: netcdf (1:4.7.3-1) is built & installed on all release architectures, please schedule the binNMUs except netcdf-fortan which is currently building on the buildds. >>> >>> The binNMUs that were scheduled have finished, please schedule the >>> remainder of Dependency level 2. >> >> ferret-vis is done on all release architectures, please schedule the >> pyferret. > > magics++ is done too, cdo & metview can be schedule as well. grass is done, qgis can be scheduled. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#948991: buster-pu: package schleuder/3.4.0-2+deb10u2
Hi Adam, On 20-01-24 21:59:41, Adam D. Barratt wrote: > Please go ahead. Thanks, that is done, with a small addition to never ask for a passphrase, in case Schleuder is given a symmetrically encrypted mail. This was happening sometimes if people were running the test suite. Cheers, Georg
Processed: retitle 948899 buster-pu: package libspreadsheet-wright-perl/0.105-1+deb10u1
Processing commands for cont...@bugs.debian.org: > retitle 948899 buster-pu: package libspreadsheet-wright-perl/0.105-1+deb10u1 Bug #948899 [release.debian.org] buster-pu: package libspreadsheet-wright-perl/0.105-1~deb10u1 Changed Bug title to 'buster-pu: package libspreadsheet-wright-perl/0.105-1+deb10u1' from 'buster-pu: package libspreadsheet-wright-perl/0.105-1~deb10u1'. > thanks Stopping processing here. Please contact me if you need assistance. -- 948899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948899 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#948899: buster-pu: package libspreadsheet-wright-perl/0.105-1~deb10u1
On 2020-01-25 00:05, Adam D. Barratt wrote: > Does that imply that no-one actually uses the package, or are these > simply not commonly used areas? I think the latter. Just one of the total ~10 plugins was unusable, and another one did not process an optional set of parameters. > The changelog entries here would probably benefit from being more > similar to your descriptions in this report, given that they will be > displayed to users. Indeed - I'll make them more readable. > Please go ahead. Thanks. Best, Andrius signature.asc Description: OpenPGP digital signature
Bug#949925: stretch-pu: package cram/0.7-1+deb9u1
Package: release.debian.org Severity: normal Tags: stretch User: release.debian@packages.debian.org Usertags: pu https://tests.reproducible-builds.org/debian/rb-pkg/stretch/amd64/cram.html * Accept any test result to work around build failures. Same workaround as in buster/bullseye/sid. diff -Nru cram-0.7/debian/changelog cram-0.7/debian/changelog --- cram-0.7/debian/changelog 2016-03-04 21:37:27.0 +0200 +++ cram-0.7/debian/changelog 2020-01-27 11:02:31.0 +0200 @@ -1,3 +1,10 @@ +cram (0.7-1+deb9u1) stretch; urgency=medium + + * Non-maintainer upload. + * Accept any test result to work around build failures. + + -- Adrian Bunk Mon, 27 Jan 2020 11:02:31 +0200 + cram (0.7-1) unstable; urgency=low * New upstream release. diff -Nru cram-0.7/debian/rules cram-0.7/debian/rules --- cram-0.7/debian/rules 2016-03-04 21:43:04.0 +0200 +++ cram-0.7/debian/rules 2020-01-27 11:02:31.0 +0200 @@ -26,8 +26,10 @@ override_dh_auto_test: dh_auto_test - PYTHON=python COVERAGE=python-coverage $(MAKE) test - PYTHON=python3 COVERAGE=python3-coverage $(MAKE) test + # accept any test result until the relation between cram and coverage is clarified + # see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897516#53 + PYTHON=python COVERAGE=python-coverage $(MAKE) test || true + PYTHON=python3 COVERAGE=python3-coverage $(MAKE) test || true override_dh_clean: dh_clean -O--buildsystem=python_distutils
