Please block kdevplatform/5.1.1-1
Hi, can you please block kdevplatform/5.1.1-1 from entering testing tonight? kdevelop is affected by #866354 on armel, and I'd like the whole kdevelop stack (kdevplatform, kdevelop, kdevelop-python, and kdevelop-php) to migrate to testing at the same time. Thanks, -- Pino Toscano signature.asc Description: This is a digitally signed message part.
Bug#866643: jessie-pu: package init-select/1.20140921+deb8u1
Control: tag -1 - moreinfo On 2017-07-01 02:32, Cyril Brulebois wrote: > Andreas Beckmann (2017-06-30): >> init-select contains a grub config snippet that unconditionally runs a >> command, which will cause failures (in update-grub and friends) if >> init-select was removed but not purged. >> This was noticed on jessie->stretch upgrades of coreboot where >> init-select was installed in jessie (but gets removed during the upgrade >> to stretch). > I accidentally noticed a thread on debian-ctte@ about this. It would be > helpful to have a summary of what was agreed on there, and to make sure > grub people are in the loop. Discussion over there has ceased. To summarize it in one sentence: grub is encouraged to claim ownership of that conffile and take the neccessary measures to fix this bug on upgrades to stretch. I havent heard of any progress on the grub side ... but since it is also reproducible in plain jessie (the neccessary sequence is just not covered by the default piuparts tests), let's fix init-select in jessie, too. Andreas
Processed: Re: Bug#866643: jessie-pu: package init-select/1.20140921+deb8u1
Processing control commands: > tag -1 - moreinfo Bug #866643 [release.debian.org] jessie-pu: package init-select/1.20140921+deb8u1 Removed tag(s) moreinfo. -- 866643: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866643 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
NEW changes in stable-new
Processing changes file: dovecot_2.2.27-3+deb9u1_mips64el.changes ACCEPT
Bug#867856: stretch-pu: package src:muse-el/3.20+dfsg-1
Package: release.debian.org Severity: normal Tags: stretch User: release.debian@packages.debian.org Usertags: pu Dear Release Team, I would like to add missing copyright information for debian/* in src:muse-el (builds elpa-muse and muse-el dummy package), along with several minor fixes; however, if you would prefer I can remove the minor fixes. These changes have been in experimental since 2017-06-17 and in testing since 2017-06-25. The changes do not affection functionality, but missing copyright for debian/* might affect our downstreams. About six months ago I sent an email to the Release Team, asking if this issue merited an unblock request, and I didn't know at that time that that I should have filed it as a bug. Here is the changelog since 3.20+dfsg-1: muse-el (3.20+dfsg-1+deb9u1) stretch; urgency=medium * debian/COPYING.emails: Add confirmation emails from all previous contributors. * debian/copyright: - Add license for debian/* - Primary GPL3+ section can finally be simplified; simplify it. * debian/control: Make dependencies comply with Debian Emacs Policy. - unversioned dh-elpa - Drop emacs-nox from Build-Depends-Indep. - Add emacsen-common to Depends. * debian/elpa-muse.install: Fix creation of redundant subdir under contrib. -- Nicholas D Steeves Sun, 09 Jul 2017 18:11:33 -0400 muse-el (3.20+dfsg-1) unstable; urgency=medium And here are the associated debdiffs: $ debdiff muse-el_3.20+dfsg-1_all.deb muse-el_3.20+dfsg-1+deb9u1_all.deb File lists identical (after any substitutions) Control files: lines which differ (wdiff format) Installed-Size: [-134-] {+135+} Version: [-3.20+dfsg-1-] {+3.20+dfsg-1+deb9u1+} $ debdiff elpa-muse_3.20+dfsg-1_all.deb elpa-muse_3.20+dfsg-1+deb9u1_all.deb [The following lists of changes regard files as different if they have different names, permissions or owners.] Files in second .deb but not in first - -rw-r--r-- root/root /usr/share/doc/elpa-muse/contrib/blosxom/getstamps.pl -rw-r--r-- root/root /usr/share/doc/elpa-muse/contrib/blosxom/metadate_0_0_3.gz -rw-r--r-- root/root /usr/share/doc/elpa-muse/contrib/pyblosxom/getstamps.py -rw-r--r-- root/root /usr/share/doc/elpa-muse/contrib/pyblosxom/hardcodedates.py -rw-r--r-- root/root /usr/share/doc/elpa-muse/contrib/pyblosxom/make-blog -rw-r--r-- root/root /usr/share/doc/elpa-muse/contrib/pyblosxom/metadate.py Files in first .deb but not in second - -rw-r--r-- root/root /usr/share/doc/elpa-muse/contrib/pyblosxom/blosxom/getstamps.pl -rw-r--r-- root/root /usr/share/doc/elpa-muse/contrib/pyblosxom/blosxom/metadate_0_0_3.gz -rw-r--r-- root/root /usr/share/doc/elpa-muse/contrib/pyblosxom/pyblosxom/getstamps.py -rw-r--r-- root/root /usr/share/doc/elpa-muse/contrib/pyblosxom/pyblosxom/hardcodedates.py -rw-r--r-- root/root /usr/share/doc/elpa-muse/contrib/pyblosxom/pyblosxom/make-blog -rw-r--r-- root/root /usr/share/doc/elpa-muse/contrib/pyblosxom/pyblosxom/metadate.py Control files: lines which differ (wdiff format) Depends: [-emacsen-common,-] {+emacsen-common (>= 2.0.8),+} emacs-goodies-el Version: [-3.20+dfsg-1-] {+3.20+dfsg-1+deb9u1+} Sincerely, Nicholas
Bug#867119: jessie-pu: package 3dchess/0.8.1-18
On Wed, Jul 05, 2017 at 09:40:45AM +0200, Markus Koschany wrote: > Am 05.07.2017 um 07:20 schrieb Cyril Brulebois: > > Control: tag -1 confirmed > > > > Markus Koschany (2017-07-04): > >> I would like to fix the 100 % CPU consumption bug in 3dchess. [1] > >> Please find attached the debdiff for Jessie. > > > > Hi Markus, > > > > This looks good to me, feel free to upload; thanks. > > Uploaded. Thank you. Flagged for acceptance. 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
NEW changes in stable-new
Processing changes file: dovecot_2.2.27-3+deb9u1_arm64.changes ACCEPT Processing changes file: dovecot_2.2.27-3+deb9u1_armel.changes ACCEPT Processing changes file: dovecot_2.2.27-3+deb9u1_armhf.changes ACCEPT Processing changes file: dovecot_2.2.27-3+deb9u1_i386.changes ACCEPT Processing changes file: dovecot_2.2.27-3+deb9u1_mips.changes ACCEPT Processing changes file: dovecot_2.2.27-3+deb9u1_mipsel.changes ACCEPT Processing changes file: dovecot_2.2.27-3+deb9u1_ppc64el.changes ACCEPT Processing changes file: dovecot_2.2.27-3+deb9u1_s390x.changes ACCEPT
Upcoming stable point release (9.1)
Hi, The first point release for "stretch" (9.1) is scheduled for Saturday, July 22nd. Processing of new uploads into stretch-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming stable point release (9.1)
Hi, The first point release for "stretch" (9.1) is scheduled for Saturday, July 22nd. Processing of new uploads into stretch-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Upcoming oldstable point release (8.9)
Hi, The next point release for "jessie" (8.9) is scheduled for Saturday, July 22nd. Processing of new uploads into jessie-proposed-updates will be frozen during the preceding weekend. Regards, Adam
Bug#867597: stretch-pu: package retext/6.0.2-2+deb9u1
Control: tag -1 confirmed On Fri, Jul 07, 2017 at 07:48:50PM +0300, Dmitry Shachnev wrote: > I would like to request a Stretch update for ReText. > > The attached debdiff fixes two issues: > > * RC bug #863640 — segfault in XSettings code. > * Syntax error in the appdata XML file. Please go ahead. 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: Re: Bug#867597: stretch-pu: package retext/6.0.2-2+deb9u1
Processing control commands: > tag -1 confirmed Bug #867597 [release.debian.org] stretch-pu: package retext/6.0.2-2+deb9u1 Added tag(s) confirmed. -- 867597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867597 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#867713: transition: gnome-panel 3.24
On Sun, Jul 09, 2017 at 09:03:07PM +0300, Dmitry Shachnev wrote: > * For gnubiff, sensors-applet and workrave you can schedule binNMUs. Scheduled. 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
NEW changes in stable-new
Processing changes file: dovecot_2.2.27-3+deb9u1_amd64.changes ACCEPT
Bug#866679: stretch-pu: package dovecot/1:2.2.27-3+deb9u1
Control: tag -1 pending On Sun, Jul 02, 2017 at 03:55:26PM +0300, Apollon Oikonomopoulos wrote: > On 21:53 Sat 01 Jul , Cyril Brulebois wrote: > > Control: tag -1 confirmed > > > > Hi, > > > > Apollon Oikonomopoulos (2017-07-01): > > > On 02:19 Sat 01 Jul , Cyril Brulebois wrote: > > > > Out of curiosity, does ci.debian.net run autopkgtest for packages > > > > from (old)stable in addition to unstable/experimental? I'm > > > > specifically interested in knowing whether it picks packages from > > > > *-proposed-updates suites. > > > > > > > > If it does, extending autopkgtest support probably makes sense; > > > > otherwise, I'm not sure it's a net win to include this change. > > > > > > AFAIK, no, it does not (although it would be a great addition!). I > > > cherry-picked the tests primarily to help me test for regressions and > > > to allow anyone wishing to re-build the package in the future to do so > > > as well. > > > > Alright. I guess it doesn't hurt to include tests along with the bugfix, > > so feel free to upload with the proposed debdiff; thanks. > > Uploaded, thanks! And flagged for acceptance. 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: Re: Bug#866679: stretch-pu: package dovecot/1:2.2.27-3+deb9u1
Processing control commands: > tag -1 pending Bug #866679 [release.debian.org] stretch-pu: package dovecot/1:2.2.27-3+deb9u1 Added tag(s) pending. -- 866679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866679 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#867713: transition: gnome-panel 3.24
Hi Jonathan, On Sun, Jul 09, 2017 at 11:51:06AM +0100, Jonathan Wiltshire wrote: > Control: tag -1 confirmed > > On Sat, Jul 08, 2017 at 11:50:04PM +0300, Dmitry Shachnev wrote: > > I would like to request a transition for my gnome-panel package, to > > switch from libpanel-applet0 to libpanel-applet3. > > Please go ahead. Thank you. * gnome-panel and gnome-applets are now in unstable. * For uim I have uploaded NMU to DELAYED/1. * For gnubiff, sensors-applet and workrave you can schedule binNMUs. -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#867817: jessie-pu: package ncurses/5.9+20140913-1+deb8u1
Package: release.debian.org Severity: normal Tags: jessie User: release.debian@packages.debian.org Usertags: pu The same problem as in #867814 for stretch and almost the same fix, except that one inapplicable hunk has been removed from the patch. Cheers, Sven diff -Nru ncurses-5.9+20140913/debian/changelog ncurses-5.9+20140913/debian/changelog --- ncurses-5.9+20140913/debian/changelog 2014-09-17 19:00:57.0 +0200 +++ ncurses-5.9+20140913/debian/changelog 2017-07-09 16:26:16.0 +0200 @@ -1,3 +1,11 @@ +ncurses (5.9+20140913-1+deb8u1) jessie; urgency=medium + + * Cherry-pick upstream fixes from the 20170701 and 20170708 patchlevels +for various crash bugs in the tic library and the tic binary +(CVE-2017-10684, CVE-2017-10685, CVE-2017-2, CVE-2017-3). + + -- Sven Joachim Sun, 09 Jul 2017 16:26:16 +0200 + ncurses (5.9+20140913-1) unstable; urgency=low * New upstream patchlevel. diff -Nru ncurses-5.9+20140913/debian/patches/cve-fixes.diff ncurses-5.9+20140913/debian/patches/cve-fixes.diff --- ncurses-5.9+20140913/debian/patches/cve-fixes.diff 1970-01-01 01:00:00.0 +0100 +++ ncurses-5.9+20140913/debian/patches/cve-fixes.diff 2017-07-09 16:26:16.0 +0200 @@ -0,0 +1,173 @@ +Author: Sven Joachim +Description: Fixes for four CVEs + Fixes for CVE 2017-10684, CVE-2017-10685, CVE-2017-2, + CVE-2017-3 cherry-picked from upstream patchlevels 20170701 and + 20170708. +Bug-RedHat: https://bugzilla.redhat.com/show_bug.cgi?id=1464684 +Bug-RedHat: https://bugzilla.redhat.com/show_bug.cgi?id=1464685 +Bug-RedHat: https://bugzilla.redhat.com/show_bug.cgi?id=1464686 +Bug-RedHat: https://bugzilla.redhat.com/show_bug.cgi?id=1464687 +Bug-RedHat: https://bugzilla.redhat.com/show_bug.cgi?id=1464691 +Bug-RedHat: https://bugzilla.redhat.com/show_bug.cgi?id=1464692 +Forwarded: not-needed +Last-Update: 2017-07-09 + +--- + ncurses/tinfo/alloc_entry.c |6 +- + ncurses/tinfo/parse_entry.c | 22 -- + progs/dump_entry.c | 30 +++--- + 3 files changed, 36 insertions(+), 22 deletions(-) + +--- a/ncurses/tinfo/alloc_entry.c b/ncurses/tinfo/alloc_entry.c +@@ -96,7 +96,11 @@ _nc_save_str(const char *const string) + { + char *result = 0; + size_t old_next_free = next_free; +-size_t len = strlen(string) + 1; ++size_t len; ++ ++if (string == 0) ++ return _nc_save_str(""); ++len = strlen(string) + 1; + + if (len == 1 && next_free != 0) { + /* +--- a/ncurses/tinfo/parse_entry.c b/ncurses/tinfo/parse_entry.c +@@ -236,13 +236,14 @@ _nc_parse_entry(struct entry *entryp, in + * implemented it. Note that the resulting terminal type was never the + * 2-character name, but was instead the first alias after that. + */ ++#define ok_TC2(s) (isgraph(UChar(s)) && (s) != '|') + ptr = _nc_curr_token.tk_name; + if (_nc_syntax == SYN_TERMCAP + #if NCURSES_XNAMES + && !_nc_user_definable + #endif + ) { +- if (ptr[2] == '|') { ++ if (ok_TC2(ptr[0]) && ok_TC2(ptr[1]) && (ptr[2] == '|')) { + ptr += 3; + _nc_curr_token.tk_name[2] = '\0'; + } +@@ -284,9 +285,11 @@ _nc_parse_entry(struct entry *entryp, in + if (is_use || is_tc) { + entryp->uses[entryp->nuses].name = _nc_save_str(_nc_curr_token.tk_valstring); + entryp->uses[entryp->nuses].line = _nc_curr_line; +- entryp->nuses++; +- if (entryp->nuses > 1 && is_tc) { +- BAD_TC_USAGE ++ if (VALID_STRING(entryp->uses[entryp->nuses].name)) { ++ entryp->nuses++; ++ if (entryp->nuses > 1 && is_tc) { ++ BAD_TC_USAGE ++ } + } + } else { + /* normal token lookup */ +@@ -571,7 +574,7 @@ append_acs0(string_desc * dst, int code, + static void + append_acs(string_desc * dst, int code, char *src) + { +-if (src != 0 && strlen(src) == 1) { ++if (VALID_STRING(src) && strlen(src) == 1) { + append_acs0(dst, code, *src); + } + } +@@ -829,15 +832,14 @@ postprocess_termcap(TERMTYPE *tp, bool h + } + + if (tp->Strings[to_ptr->nte_index]) { ++ const char *s = tp->Strings[from_ptr->nte_index]; ++ const char *t = tp->Strings[to_ptr->nte_index]; + /* There's no point in warning about it if it's the same + * string; that's just an inefficiency. + */ +- if (strcmp( +- tp->Strings[from_ptr->nte_index], +- tp->Strings[to_ptr->nte_index]) != 0) ++ if (VALID_STRING(s) && VALID_STRING(t) && strcmp(s, t) != 0) + _nc_warning("%s (%s) already has an explicit value %s, ignoring ko", +-ap->to, ap->from, +-_nc_visbuf(tp->Strings[to_ptr->nte_index])); ++ap->to, ap->from, t); + continue; + } + +--- a/progs/dump_entry.c b/progs/dump_entry.c +@@ -609,9 +609,10 @@ fmt_entry(TERMTYPE *tterm, + PredIdx num_strings = 0; + bool outcount = 0; + +-#define WRAP_CONCAT \ +- wrap_concat(buffer); \ +- outcount = TRUE ++#define WRAP_CONCAT1(s) wrap_concat(s); outcount = TRUE ++#define WRAP_CONCAT2(a,b) wrap_concat(a); WRAP_CONCAT1(b) ++#
Bug#867814: stretch-pu: package ncurses/6.0+20161126-1+deb9u1
Package: release.debian.org Severity: normal Tags: stretch User: release.debian@packages.debian.org Usertags: pu Recently a few flaws in the tic program and the tic library have been detected: null pointer dereference, buffer overflow, stack smashing, you name it. Six bugs have been reported in the Red Hat bugtracker and four CVEs assigned. Fortunately there are rather few users who would run affected programs at all, so it was decided that no DSA would be necessary. Upstream has fixed these problems in the latest patchlevels (already in sid), and I would like to address them in a stable upload. I have verified that the testcases in the reported Red Hat bugs no longer cause crashes (if anybody wants to verify that, I can send them). Cheers, Sven diff -Nru ncurses-6.0+20161126/debian/changelog ncurses-6.0+20161126/debian/changelog --- ncurses-6.0+20161126/debian/changelog 2016-11-29 21:19:08.0 +0100 +++ ncurses-6.0+20161126/debian/changelog 2017-07-09 15:32:26.0 +0200 @@ -1,3 +1,11 @@ +ncurses (6.0+20161126-1+deb9u1) stretch; urgency=medium + + * Cherry-pick upstream fixes from the 20170701 and 20170708 patchlevels +for various crash bugs in the tic library and the tic binary +(CVE-2017-10684, CVE-2017-10685, CVE-2017-2, CVE-2017-3). + + -- Sven Joachim Sun, 09 Jul 2017 15:32:26 +0200 + ncurses (6.0+20161126-1) unstable; urgency=low * New upstream patchlevel. diff -Nru ncurses-6.0+20161126/debian/patches/cve-fixes.diff ncurses-6.0+20161126/debian/patches/cve-fixes.diff --- ncurses-6.0+20161126/debian/patches/cve-fixes.diff 1970-01-01 01:00:00.0 +0100 +++ ncurses-6.0+20161126/debian/patches/cve-fixes.diff 2017-07-09 15:32:26.0 +0200 @@ -0,0 +1,185 @@ +Author: Sven Joachim +Description: Fixes for four CVEs + Fixes for CVE 2017-10684, CVE-2017-10685, CVE-2017-2, + CVE-2017-3 cherry-picked from upstream patchlevels 20170701 and + 20170708. +Bug-RedHat: https://bugzilla.redhat.com/show_bug.cgi?id=1464684 +Bug-RedHat: https://bugzilla.redhat.com/show_bug.cgi?id=1464685 +Bug-RedHat: https://bugzilla.redhat.com/show_bug.cgi?id=1464686 +Bug-RedHat: https://bugzilla.redhat.com/show_bug.cgi?id=1464687 +Bug-RedHat: https://bugzilla.redhat.com/show_bug.cgi?id=1464691 +Bug-RedHat: https://bugzilla.redhat.com/show_bug.cgi?id=1464692 +Forwarded: not-needed +Last-Update: 2017-07-09 + +--- + ncurses/tinfo/alloc_entry.c |6 +- + ncurses/tinfo/parse_entry.c | 22 -- + progs/dump_entry.c | 34 +- + 3 files changed, 38 insertions(+), 24 deletions(-) + +--- a/ncurses/tinfo/alloc_entry.c b/ncurses/tinfo/alloc_entry.c +@@ -96,7 +96,11 @@ _nc_save_str(const char *const string) + { + char *result = 0; + size_t old_next_free = next_free; +-size_t len = strlen(string) + 1; ++size_t len; ++ ++if (string == 0) ++ return _nc_save_str(""); ++len = strlen(string) + 1; + + if (len == 1 && next_free != 0) { + /* +--- a/ncurses/tinfo/parse_entry.c b/ncurses/tinfo/parse_entry.c +@@ -236,13 +236,14 @@ _nc_parse_entry(struct entry *entryp, in + * implemented it. Note that the resulting terminal type was never the + * 2-character name, but was instead the first alias after that. + */ ++#define ok_TC2(s) (isgraph(UChar(s)) && (s) != '|') + ptr = _nc_curr_token.tk_name; + if (_nc_syntax == SYN_TERMCAP + #if NCURSES_XNAMES + && !_nc_user_definable + #endif + ) { +- if (ptr[2] == '|') { ++ if (ok_TC2(ptr[0]) && ok_TC2(ptr[1]) && (ptr[2] == '|')) { + ptr += 3; + _nc_curr_token.tk_name[2] = '\0'; + } +@@ -284,9 +285,11 @@ _nc_parse_entry(struct entry *entryp, in + if (is_use || is_tc) { + entryp->uses[entryp->nuses].name = _nc_save_str(_nc_curr_token.tk_valstring); + entryp->uses[entryp->nuses].line = _nc_curr_line; +- entryp->nuses++; +- if (entryp->nuses > 1 && is_tc) { +- BAD_TC_USAGE ++ if (VALID_STRING(entryp->uses[entryp->nuses].name)) { ++ entryp->nuses++; ++ if (entryp->nuses > 1 && is_tc) { ++ BAD_TC_USAGE ++ } + } + } else { + /* normal token lookup */ +@@ -572,7 +575,7 @@ append_acs0(string_desc * dst, int code, + static void + append_acs(string_desc * dst, int code, char *src) + { +-if (src != 0 && strlen(src) == 1) { ++if (VALID_STRING(src) && strlen(src) == 1) { + append_acs0(dst, code, *src); + } + } +@@ -833,15 +836,14 @@ postprocess_termcap(TERMTYPE *tp, bool h + } + + if (tp->Strings[to_ptr->nte_index]) { ++ const char *s = tp->Strings[from_ptr->nte_index]; ++ const char *t = tp->Strings[to_ptr->nte_index]; + /* There's no point in warning about it if it's the same + * string; that's just an inefficiency. + */ +- if (strcmp( +- tp->Strings[from_ptr->nte_index], +- tp->Strings[to_ptr->nte_index]) != 0) ++ if (VALID_STRING(s) && VALID_STRING(t) && strcmp(s, t) != 0) + _nc_warning("%s (%s) already has an explicit
NEW changes in stable-new
Processing changes file: pdns-recursor_4.0.4-1+deb9u1_armhf.changes ACCEPT Processing changes file: pdns-recursor_4.0.4-1+deb9u1_mips64el.changes ACCEPT Processing changes file: pdns-recursor_4.0.4-1+deb9u1_mipsel.changes ACCEPT
NEW changes in stable-new
Processing changes file: pdns-recursor_4.0.4-1+deb9u1_armel.changes ACCEPT Processing changes file: protozero_1.5.1-1+deb9u1_armel.changes ACCEPT Processing changes file: protozero_1.5.1-1+deb9u1_armhf.changes ACCEPT Processing changes file: protozero_1.5.1-1+deb9u1_mips64el.changes ACCEPT Processing changes file: protozero_1.5.1-1+deb9u1_mipsel.changes ACCEPT
NEW changes in stable-new
Processing changes file: 3dchess_0.8.1-19+deb9u1_armhf.changes ACCEPT Processing changes file: gnome-settings-daemon_3.22.2-2+deb9u1_armel.changes ACCEPT Processing changes file: gnome-settings-daemon_3.22.2-2+deb9u1_armhf.changes ACCEPT Processing changes file: gnome-settings-daemon_3.22.2-2+deb9u1_mipsel.changes ACCEPT
NEW changes in stable-new
Processing changes file: 3dchess_0.8.1-19+deb9u1_armel.changes ACCEPT Processing changes file: fpc_3.0.0+dfsg-11+deb9u1_armel.changes ACCEPT Processing changes file: fpc_3.0.0+dfsg-11+deb9u1_armhf.changes ACCEPT Processing changes file: gnome-settings-daemon_3.22.2-2+deb9u1_mips64el.changes ACCEPT
NEW changes in oldstable-new
Processing changes file: 3dchess_0.8.1-18+deb8u1_mipsel.changes ACCEPT
NEW changes in stable-new
Processing changes file: 3dchess_0.8.1-19+deb9u1_mips64el.changes ACCEPT Processing changes file: 3dchess_0.8.1-19+deb9u1_mipsel.changes ACCEPT Processing changes file: fpc_3.0.0+dfsg-11+deb9u1_all.changes ACCEPT Processing changes file: fpc_3.0.0+dfsg-11+deb9u1_arm64.changes ACCEPT Processing changes file: pdns-recursor_4.0.4-1+deb9u1_mips.changes ACCEPT
NEW changes in oldstable-new
Processing changes file: 3dchess_0.8.1-18+deb8u1_arm64.changes ACCEPT Processing changes file: 3dchess_0.8.1-18+deb8u1_armel.changes ACCEPT Processing changes file: 3dchess_0.8.1-18+deb8u1_armhf.changes ACCEPT Processing changes file: 3dchess_0.8.1-18+deb8u1_i386.changes ACCEPT Processing changes file: 3dchess_0.8.1-18+deb8u1_mips.changes ACCEPT Processing changes file: 3dchess_0.8.1-18+deb8u1_powerpc.changes ACCEPT Processing changes file: 3dchess_0.8.1-18+deb8u1_ppc64el.changes ACCEPT Processing changes file: 3dchess_0.8.1-18+deb8u1_s390x.changes ACCEPT
NEW changes in stable-new
Processing changes file: 3dchess_0.8.1-19+deb9u1_arm64.changes ACCEPT Processing changes file: 3dchess_0.8.1-19+deb9u1_i386.changes ACCEPT Processing changes file: 3dchess_0.8.1-19+deb9u1_mips.changes ACCEPT Processing changes file: 3dchess_0.8.1-19+deb9u1_ppc64el.changes ACCEPT Processing changes file: 3dchess_0.8.1-19+deb9u1_s390x.changes ACCEPT Processing changes file: fpc_3.0.0+dfsg-11+deb9u1_amd64.changes ACCEPT Processing changes file: fpc_3.0.0+dfsg-11+deb9u1_i386.changes ACCEPT Processing changes file: gnome-settings-daemon_3.22.2-2+deb9u1_arm64.changes ACCEPT Processing changes file: gnome-settings-daemon_3.22.2-2+deb9u1_i386.changes ACCEPT Processing changes file: gnome-settings-daemon_3.22.2-2+deb9u1_mips.changes ACCEPT Processing changes file: gnome-settings-daemon_3.22.2-2+deb9u1_ppc64el.changes ACCEPT Processing changes file: gnome-settings-daemon_3.22.2-2+deb9u1_s390x.changes ACCEPT Processing changes file: pdns-recursor_4.0.4-1+deb9u1_amd64.changes ACCEPT Processing changes file: pdns-recursor_4.0.4-1+deb9u1_arm64.changes ACCEPT Processing changes file: pdns-recursor_4.0.4-1+deb9u1_i386.changes ACCEPT Processing changes file: pdns-recursor_4.0.4-1+deb9u1_ppc64el.changes ACCEPT Processing changes file: pdns-recursor_4.0.4-1+deb9u1_s390x.changes ACCEPT Processing changes file: protozero_1.5.1-1+deb9u1_arm64.changes ACCEPT Processing changes file: protozero_1.5.1-1+deb9u1_i386.changes ACCEPT Processing changes file: protozero_1.5.1-1+deb9u1_mips.changes ACCEPT Processing changes file: protozero_1.5.1-1+deb9u1_ppc64el.changes ACCEPT Processing changes file: protozero_1.5.1-1+deb9u1_s390x.changes ACCEPT Processing changes file: request-tracker4_4.4.1-3+deb9u2_all.changes ACCEPT
Bug#867190: stretch-pu: package apt/1.4.7
On Sun, Jul 09, 2017 at 03:22:12PM +0100, Adam D. Barratt wrote: > On Wed, 2017-07-05 at 09:38 +0200, Julian Andres Klode wrote: > > On Wed, Jul 05, 2017 at 07:58:11AM +0200, Cyril Brulebois wrote: > > > Control: tag -1 moreinfo > > > > > > Hi, > > > > > > Julian Andres Klode (2017-07-04): > > > > This release fixes several smaller bugs in the network connection. > > > > Apart from the changes in the changelog, there also are some changes > > > > to our travis CI integration and the test suite to make CI more > > > > reliable (by fixing coverage errors messing up our tests), more future > > > > proof (by using docker instead of mixing travis' ubuntu trusty with > > > > wily and xenial packages...), and the CI now runs on stretch, so > > > > that's good too :) > > > > > > > > All fixes are straight cherry-picks from unstable, just the travis > > > > stuff had some changes (one less variant to build and stretch isntead > > > > of testing), but that does not affect us. > > > > > > apt will need to migrate to testing before we could tentatively accept > > > anything from stretch-new; but we're not there yet. > > > > grr, why did the bits email Adam sent then say: > > > > " * The bug you want to fix in stable must be fixed in unstable > > already (and not waiting in NEW or the delayed queue)" > > > > I guess you'll see a lot more people trying to do stable updates > > only in unstable if that's what people have been told is needed > > - perhaps send a follow-up correction? > > There are two things here that I think may be getting confused. > > The requirement for accepting an update to p-u has always been that it > doesn't affect unstable - either by the affected code not being present > or (more commonly) by the bug having already been fixed in unstable. > That requirement is to ensure that the fix gets at least some exposure > before the point release, and because it's quicker and simpler to get > any required follow-up fixes applied in unstable. We do of course want > to fix to be available to users of testing asap, but that's not a > blocker for the p-u request. > > In order for the fix to then get into stable itself, the version of the > package in testing must be strictly higher than that of the p-u update. > It's preferable if that occurs due to a more recent package having > migrated to testing, but if necessary ftp-master will (at our request) > force packages into testing and/or unstable during the point release, in > order to avoid violating the archive's inter-suite version constraints. Ah yeah, sorry, I forgot that testing was still at 1.4.6 (now 1.5~beta1 seems to have migrated). > > > > > [ David Kalnischkies ] > > > > * use port from SRV record instead of initial port > > > > => Might have picked the wrong port > > > > > > > > [ Julian Andres Klode ] > > > > * Reset failure reason when connection was successful > > > > => Some failures were only treated as warnings, not errors > > > > > > No bug reports with details for those? > > [...] > > > > > > > * http: A response with Content-Length: 0 has no content > > > > > > > > => Downloading failed if server responded with Content-Length: 0, as > > > >APT was waiting for content to read. > > > > > > No bug report with details? > > > > I discovered the last two while writing the TLS support in 1.5, so I did > > not open up a bug report for each. I'm not sure how David noticed the > > first one, but all of them seem to be important bugs. > > I'm okay with the fixes, but the changelog descriptions aren't > particularly great. For instance, you've explained in this thread that > the Content-Length: bug caused apt to wait (indefinitely?) for content > that would never arrive, but that's not really clear (at least to me) > from the changelog. There are timeouts for everything, well one value, defaulting to 120s, that is, 2 minutes. So what do you suggest? A simple rewording like this: " * http: A response with Content-Length: 0 has no content." => " * http: Do not try to read content if Content-Length is 0" " * Reset failure reason when connection was successful." => " * Ignore errors from earlier connection attempts on successful connection" (What about the " use port from SRV record instead of initial port."? It's entirely clear if you know what a SRV record is, but otherwise...). Or more details? For example, we could expand all changelog entries to include (almost) the entire commit message (the changelog is generated by gbp-dch), then we end up with this monster: apt (1.4.7) unstable; urgency=medium [ David Kalnischkies ] * travis: ignore profiling warning in progress lines. On Travis CI running tests with code coverage enabled sometimes generates profiling lines, which we filter out for a while now, but that misses lines generated showing progress still causing test failures, so more sed logic is added in the hopes to ignore them. * use port from SRV record instead of in
Bug#867190: stretch-pu: package apt/1.4.7
On Wed, 2017-07-05 at 09:38 +0200, Julian Andres Klode wrote: > On Wed, Jul 05, 2017 at 07:58:11AM +0200, Cyril Brulebois wrote: > > Control: tag -1 moreinfo > > > > Hi, > > > > Julian Andres Klode (2017-07-04): > > > This release fixes several smaller bugs in the network connection. > > > Apart from the changes in the changelog, there also are some changes > > > to our travis CI integration and the test suite to make CI more > > > reliable (by fixing coverage errors messing up our tests), more future > > > proof (by using docker instead of mixing travis' ubuntu trusty with > > > wily and xenial packages...), and the CI now runs on stretch, so > > > that's good too :) > > > > > > All fixes are straight cherry-picks from unstable, just the travis > > > stuff had some changes (one less variant to build and stretch isntead > > > of testing), but that does not affect us. > > > > apt will need to migrate to testing before we could tentatively accept > > anything from stretch-new; but we're not there yet. > > grr, why did the bits email Adam sent then say: > > " * The bug you want to fix in stable must be fixed in unstable > already (and not waiting in NEW or the delayed queue)" > > I guess you'll see a lot more people trying to do stable updates > only in unstable if that's what people have been told is needed > - perhaps send a follow-up correction? There are two things here that I think may be getting confused. The requirement for accepting an update to p-u has always been that it doesn't affect unstable - either by the affected code not being present or (more commonly) by the bug having already been fixed in unstable. That requirement is to ensure that the fix gets at least some exposure before the point release, and because it's quicker and simpler to get any required follow-up fixes applied in unstable. We do of course want to fix to be available to users of testing asap, but that's not a blocker for the p-u request. In order for the fix to then get into stable itself, the version of the package in testing must be strictly higher than that of the p-u update. It's preferable if that occurs due to a more recent package having migrated to testing, but if necessary ftp-master will (at our request) force packages into testing and/or unstable during the point release, in order to avoid violating the archive's inter-suite version constraints. > > > > > Let me know if this is good to go. > > > > > > apt (1.4.7) stretch; urgency=medium > > > > I'll let Adam comment on whether it's OK for this specific case not to > > use +debXuY versioning, since you seem to be going for 1.4.x series in > > stretch. > > We also did this in jessie. dpkg also does this. > > APT now maintains stable branches matching Debian and Ubuntu > releases, and 1.4.y is the branch for stretch and artful. ACK. > > > * New microrelease fixing issues in http method (LP: #1702326) > > > => I'll also upload this to Ubuntu, that's just a tag for them, it > > >also helps summarizing the main part of the upload > > > > This isn't much informative: I have no idea what issues you're fixing, > > or how. Users won't know, either. > > That's true. I'm still figuring out the best way to keep the Ubuntu > one in sync, so I thought I'd just add the tracking bug I need for > that release there in here and then upload the whole thing there > after fiddling with changes. I'm basically just trying to keep a > single continuity of 1.4.y, and not have 1.4.y-debian and > 1.4.y-ubuntu. That won't last long however, the Ubuntu release > only has 9 months of support since April. > > We can of course make it more helpful, if you have any > suggestions :) See related comments later. > > > [ Robert Luberda ] > > > * fix a "critical" typo in old changelog entry (Closes: 866358) > > > > > > => Remove a letter, and works around a bug in apt-listchanges. > > > > Having a quick glance at the BTS, severity:minor isn't exactly what > > we're considering for proposed-updates. Having correct bug meta data > > would help (from reading the bug report, working around the issue might > > be an idea, but fixing apt-listchanges in stable as well might be > > better). > > It's not the main focus of this release, but since we are already > fixing the important bugs in the http stack, I thought we'd include > this for the ride. It's removing a single character from a changelog > file, after all. Seems ok. > > > [ David Kalnischkies ] > > > * use port from SRV record instead of initial port > > > => Might have picked the wrong port > > > > > > [ Julian Andres Klode ] > > > * Reset failure reason when connection was successful > > > => Some failures were only treated as warnings, not errors > > > > No bug reports with details for those? > [...] > > > > > * http: A response with Content-Length: 0 has no content > > > > > > => Downloading failed if server responded with Content-Length: 0, as > > >APT was waiting for content to read.
Processed: Re: Bug#866388: uim: FTBFS with gnome-panel 3.24, needs switch to in-process applet
Processing control commands: > severity -1 serious Bug #866388 [src:uim] uim: FTBFS with gnome-panel 3.24, needs switch to in-process applet Severity set to 'serious' from 'important' > block 867713 by -1 Bug #867713 [release.debian.org] transition: gnome-panel 3.24 867713 was not blocked by any bugs. 867713 was not blocking any bugs. Added blocking bug(s) of 867713: 866388 -- 866388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866388 867713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867713 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 867119
Processing commands for cont...@bugs.debian.org: > tags 867119 + pending Bug #867119 [release.debian.org] jessie-pu: package 3dchess/0.8.1-18 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 867119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867119 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#867665: transition: wmaker
On 2017-07-09 Jonathan Wiltshire wrote: > Control: tag -1 confirmed > On Sat, Jul 08, 2017 at 01:22:26PM +0200, Andreas Metzler wrote: >> wmaker 0.95.8 features a soname bump of libwraster. There are only 3 >> other packages involved (wdm, wmforecast and wmweather+) and all of them >> build fine against the libwmaker-dev in experimental. > Please go ahead. Thanks, I have just uploaded to sid. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' signature.asc Description: PGP signature
NEW changes in stable-new
Processing changes file: protozero_1.5.1-1+deb9u1_amd64.changes ACCEPT
NEW changes in stable-new
Processing changes file: gnome-settings-daemon_3.22.2-2+deb9u1_amd64.changes ACCEPT
Bug#867684: marked as done (nmu: xindy_2.5.1.20160104-2)
Your message dated Sun, 9 Jul 2017 12:20:26 +0100 with message-id <20170709112026.6vjfbcqoxd6ht...@powdarrmonkey.net> and subject line Re: Bug#867684: nmu: xindy_2.5.1.20160104-2 has caused the Debian Bug report #867684, regarding nmu: xindy_2.5.1.20160104-2 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.) -- 867684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867684 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 nmu xindy_2.5.1.20160104-2 . ANY . unstable . -m "Rebuild against clisp-fasl-loader-20100806" The clisp abi virtual package has changed from clisp-fasl-loader-20080430 xindy seems to be the only user of this. Andreas --- End Message --- --- Begin Message --- On Sat, Jul 08, 2017 at 03:52:34PM +0200, Andreas Beckmann wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: binnmu > > nmu xindy_2.5.1.20160104-2 . ANY . unstable . -m "Rebuild against > clisp-fasl-loader-20100806" > > The clisp abi virtual package has changed from > clisp-fasl-loader-20080430 > > xindy seems to be the only user of this. Scheduled. 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--- End Message ---
Processed: Re: Bug#866759: stretch-pu: package protozero/1.5.1-1+deb9u1
Processing control commands: > tag -1 pending Bug #866759 [release.debian.org] stretch-pu: package protozero/1.5.1-1+deb9u1 Added tag(s) pending. -- 866759: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866759 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#867091: stretch-pu: package gnome-settings-daemon/3.22.2-2
Processing control commands: > tag -1 pending Bug #867091 [release.debian.org] stretch-pu: package gnome-settings-daemon/3.22.2-2 Added tag(s) pending. -- 867091: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867091 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#867091: stretch-pu: package gnome-settings-daemon/3.22.2-2
Control: tag -1 pending On Wed, Jul 05, 2017 at 07:31:49AM +0200, Cyril Brulebois wrote: > Laurent Bigonville (2017-07-03): > > Today I discovered that gnome-settings-daemon was not remembering the > > numlock state between the different sessions due to a debian specific > > patch. > > > > This is particularly a problem for people using wayland. > > > > Upstream has this enabled for years, but due to an old bug (around 2012) > > this feature was disabled. This bug is fixed today. > > > > The attached debdiff reset the remember-numlock-state dconf key back to > > the upstream value. > > > > This should IMHO be fixed in stable. > > This looks good to me, feel free to upload. We'll need the package in > unstable to migrate to testing before accepting your update from > stretch-new though. Looks like it was uploaded; flagged for acceptance. -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51
Bug#866759: stretch-pu: package protozero/1.5.1-1+deb9u1
Control: tag -1 pending On Thu, Jul 06, 2017 at 07:19:46AM +0200, Sebastiaan Couwenberg wrote: > On 07/03/2017 11:36 AM, Cyril Brulebois wrote: > > Bas Couwenberg (2017-07-01): > >> protozero 1.5.1 in stretch contains a serious bug that was fixed in > >> 1.5.2. The fix has been cherry-picked and I'd like to upload this > >> proposed-update. > >> > >> >From the changelog and patch description: > >> > >> " > >> This fixes a rather embarrassing bug in the equality operator of the > >> data_view class. The equality operator is actually never used in the > >> protozero code itself, but users of protozero might use it. This is a > >> serious bug that could lead to buffer overrun type problems. > >> " > >> > >> The issue was pointed out by the upstream author in: > >> > >> https://lists.debian.org/debian-gis/2017/07/msg0.html > > > > Ah right, \0 characters are fun… > > > > This looks good to me, but we'll need to wait until 1.5.2-1 has reached > > testing before accepting this from stretch-new; either upload now, and > > ping when it's migrated; or upload when it's migrated, and ping us right > > afterwards. > Ping. protozero (1.5.2-1) migrated to testing today, and protozero > (1.5.1-1+deb9u1) was uploaded a few days ago. > Flagged for acceptance, thanks for the ping. -- 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: tagging 867190
Processing commands for cont...@bugs.debian.org: > tags 867190 - moreinfo Bug #867190 [release.debian.org] stretch-pu: package apt/1.4.7 Removed tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 867190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867190 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
NEW changes in oldstable-new
Processing changes file: 3dchess_0.8.1-18+deb8u1_amd64.changes ACCEPT Processing changes file: bind9_9.9.5.dfsg-9+deb8u12_amd64.changes ACCEPT Processing changes file: bind9_9.9.5.dfsg-9+deb8u12_arm64.changes ACCEPT Processing changes file: bind9_9.9.5.dfsg-9+deb8u12_armel.changes ACCEPT Processing changes file: bind9_9.9.5.dfsg-9+deb8u12_armhf.changes ACCEPT Processing changes file: bind9_9.9.5.dfsg-9+deb8u12_i386.changes ACCEPT Processing changes file: bind9_9.9.5.dfsg-9+deb8u12_mips.changes ACCEPT Processing changes file: bind9_9.9.5.dfsg-9+deb8u12_mipsel.changes ACCEPT Processing changes file: bind9_9.9.5.dfsg-9+deb8u12_powerpc.changes ACCEPT Processing changes file: bind9_9.9.5.dfsg-9+deb8u12_ppc64el.changes ACCEPT Processing changes file: bind9_9.9.5.dfsg-9+deb8u12_s390x.changes ACCEPT
NEW changes in stable-new
Processing changes file: fpc_3.0.0+dfsg-11+deb9u1_source.changes ACCEPT Processing changes file: jabberd2_2.4.0-3+deb9u1_sourceonly.changes ACCEPT Processing changes file: jabberd2_2.4.0-3+deb9u1_amd64.changes ACCEPT Processing changes file: jabberd2_2.4.0-3+deb9u1_arm64.changes ACCEPT Processing changes file: jabberd2_2.4.0-3+deb9u1_armel.changes ACCEPT Processing changes file: jabberd2_2.4.0-3+deb9u1_armhf.changes ACCEPT Processing changes file: jabberd2_2.4.0-3+deb9u1_i386.changes ACCEPT Processing changes file: jabberd2_2.4.0-3+deb9u1_mips.changes ACCEPT Processing changes file: jabberd2_2.4.0-3+deb9u1_mips64el.changes ACCEPT Processing changes file: jabberd2_2.4.0-3+deb9u1_mipsel.changes ACCEPT Processing changes file: jabberd2_2.4.0-3+deb9u1_ppc64el.changes ACCEPT Processing changes file: jabberd2_2.4.0-3+deb9u1_s390x.changes ACCEPT Processing changes file: pdns-recursor_4.0.4-1+deb9u1_source.changes ACCEPT Processing changes file: request-tracker4_4.4.1-3+deb9u2_source.changes ACCEPT
Processed: Re: Bug#867713: transition: gnome-panel 3.24
Processing control commands: > tag -1 confirmed Bug #867713 [release.debian.org] transition: gnome-panel 3.24 Added tag(s) confirmed. -- 867713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867713 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#867713: transition: gnome-panel 3.24
Control: tag -1 confirmed On Sat, Jul 08, 2017 at 11:50:04PM +0300, Dmitry Shachnev wrote: > I would like to request a transition for my gnome-panel package, to > switch from libpanel-applet0 to libpanel-applet3. Please go ahead. 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
Bug#867665: transition: wmaker
Control: tag -1 confirmed On Sat, Jul 08, 2017 at 01:22:26PM +0200, Andreas Metzler wrote: > wmaker 0.95.8 features a soname bump of libwraster. There are only 3 > other packages involved (wdm, wmforecast and wmweather+) and all of them > build fine against the libwmaker-dev in experimental. Please go ahead. 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: Re: Bug#867665: transition: wmaker
Processing control commands: > tag -1 confirmed Bug #867665 [release.debian.org] transition: wmaker Added tag(s) confirmed. -- 867665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867665 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#867118: stretch-pu: package 3dchess/0.8.1-19+b1
Control: tag -1 pending On Wed, Jul 05, 2017 at 09:40:20AM +0200, Markus Koschany wrote: > Am 05.07.2017 um 07:18 schrieb Cyril Brulebois: > > Control: tag -1 confirmed > > > > Hi Markus, > > > > Markus Koschany (2017-07-04): > >> I would like to fix the 100 % CPU consumption bug in 3dchess. [1] > >> Please find attached the debdiff for Stretch. > > > > This looks good to me, feel free to upload; thanks. > > Hi Kibi, > > thanks for the review. I have uploaded the package a few minutes ago. Flagged for acceptance. 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: Re: Bug#865225: stretch-pu: package request-tracker4/4.4.1-3+deb9u2
Processing control commands: > tag -1 pending Bug #865225 [release.debian.org] stretch-pu: package request-tracker4/4.4.1-3+deb9u2 Added tag(s) pending. -- 865225: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865225 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#865225: stretch-pu: package request-tracker4/4.4.1-3+deb9u2
Control: tag -1 pending On Thu, Jul 06, 2017 at 07:26:30PM +0100, Dominic Hargreaves wrote: > On Sun, Jul 02, 2017 at 11:18:43PM +0200, Cyril Brulebois wrote: > > Hi, > > > > Dominic Hargreaves (2017-06-27): > > > Sorry, this is not yet uploaded. I somehow got this and the anope > > > bug mixed up. > > > > Alright, no worries; for the avoidance of doubt, I can't spot any > > uploads of the request-tracker4 package to stretch at the moment. > > Should be there now :) Flagged for acceptance. 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: Re: Bug#867159: stretch-pu: package pdns-recursor/4.0.4-1
Processing control commands: > tag -1 pending Bug #867159 [release.debian.org] stretch-pu: package pdns-recursor/4.0.4-1 Added tag(s) pending. -- 867159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867159 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 865997
Processing commands for cont...@bugs.debian.org: > tags 865997 + pending Bug #865997 [release.debian.org] [release.debian.org] stretch-pu: Fix Local time / UTC conversion in Free Pascal Run Time Library Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 865997: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865997 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#867118: stretch-pu: package 3dchess/0.8.1-19+b1
Processing control commands: > tag -1 pending Bug #867118 [release.debian.org] stretch-pu: package 3dchess/0.8.1-19+b1 Added tag(s) pending. -- 867118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867118 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#867159: stretch-pu: package pdns-recursor/4.0.4-1
Control: tag -1 pending On Wed, Jul 05, 2017 at 01:54:47PM +0200, Christian Hofstaedtler wrote: > Hi, > > * Cyril Brulebois [170705 07:13]: > > Control: tag -1 confirmed > > > > Christian Hofstaedtler (2017-07-04): > > > pdns-recursor has an embedded copy of the DNS root (".") zone public > > > signing key ("KSK"), for DNSSEC verification purposes. ICANN has > > > created a new key and expects it to use starting from October 11, > > > 2017, in place of the old key. > > > > > > [..] > > > > This looks good to me, feel free to upload. > > Done, should be in proposed-updates by now. Flagged for acceptance. 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
Bug#865997: [Pkg-pascal-devel] Bug#865997: [release.debian.org] stretch-pu: Fix Local time / UTC conversion in Free Pascal Run Time Library
On Sun, Jul 02, 2017 at 11:20:59PM +0200, Cyril Brulebois wrote: > Control: tag -1 - moreinfo + confirmed > > Abou Al Montacir (2017-06-28): > > On Mon, 2017-06-26 at 14:04 +0100, Jonathan Wiltshire wrote:... > > > > > The patch alone is not enough to decide this; please prepare a source > > > debdiff (i.e. between the .dsc files) of your proposed upload relative > > > to stretch. The upload target should be 'stretch', not 'stable'. > > Please find attached the debdiff. > > This looks good to me, feel free to upload; thanks. Looks like it was uploaded; flagged for acceptance. -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51
NEW changes in stable-new
Processing changes file: 3dchess_0.8.1-19+deb9u1_amd64.changes ACCEPT