Processed: Re: Bug#929776: unblock: rrdtool/1.7.1-2
Processing control commands: > tags -1 moreinfo confirmed Bug #929776 [release.debian.org] unblock: rrdtool/1.7.1-2 Added tag(s) moreinfo and confirmed. -- 929776: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929776 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#929776: unblock: rrdtool/1.7.1-2
Control: tags -1 moreinfo confirmed Jean-Michel Vourgère: > Package: release.debian.org > User: release.debian@packages.debian.org > Usertags: unblock > Severity: normal > > Please allow me to add an upstream patch in order to fix segfaults in rrdtool > daemon, that occurs when xport'ing an non-existent RRD file. > > unblock rrdtool/1.7.1-2 > Please go ahead with the upload and remove the moreinfo tag when it is ready to be unblocked. Thanks, ~Niels
Bug#929321: Update for SQLAlchemy to address CVE-2019-7164 CVE-2019-7548
Dear package maintainer, We're about to upgrade SQLAlchemy in Buster to address an SQL injection issue. The fixed package is in unstable, under the version 1.2.18+ds1-2. In some rare cases, this update may break reverse depenencies, leading to non-working SQL queries. This is why I'm writing this email to you today: to ask you to please test your application with SQLAlchemy 1.2.18+ds1-2 ASAP, to address any potential unforecast issue before the Buster release. Details about the discussion can be seen here in the Debian bug #929321. Best regards, Thomas Goirand (zigo)
Bug#929776: unblock: rrdtool/1.7.1-2
Package: release.debian.org User: release.debian@packages.debian.org Usertags: unblock Severity: normal Please allow me to add an upstream patch in order to fix segfaults in rrdtool daemon, that occurs when xport'ing an non-existent RRD file. unblock rrdtool/1.7.1-2 diff -Nru rrdtool-1.7.1/debian/changelog rrdtool-1.7.1/debian/changelog --- rrdtool-1.7.1/debian/changelog 2019-02-07 17:08:22.0 +0100 +++ rrdtool-1.7.1/debian/changelog 2019-05-30 22:28:06.0 +0200 @@ -1,3 +1,9 @@ +rrdtool (1.7.1-2) unstable; urgency=medium + + * Cherry pick commit from 1.7.2 to prevent daemon segfault. + + -- Jean-Michel Vourgère Thu, 30 May 2019 22:28:06 +0200 + rrdtool (1.7.1-1) unstable; urgency=medium * New upstream version (Closes: #891491, #898184): diff -Nru rrdtool-1.7.1/debian/patches/segfault-xport rrdtool-1.7.1/debian/patches/segfault-xport --- rrdtool-1.7.1/debian/patches/segfault-xport 1970-01-01 01:00:00.0 +0100 +++ rrdtool-1.7.1/debian/patches/segfault-xport 2019-05-30 22:28:06.0 +0200 @@ -0,0 +1,21 @@ +From: themylogin +Subject: fix segfault on non-existent RRD file when using rrdcached + fix segfault on non-existent RRD file when using rrdcached + rrdtool xport + (like 814ca69 does for rrdtool graph) +Applied-Upstream: https://github.com/oetiker/rrdtool-1.x/commit/24b922a2eae193d5d44c01a75786aca4b277a4db +Date: Wed, 27 Mar 2019 18:09:55 +0100 +Reviewed-by: Tobias Oetiker + +Index: rrdtool/src/rrd_xport.c +=== +--- rrdtool.orig/src/rrd_xport.c rrdtool/src/rrd_xport.c +@@ -231,7 +231,7 @@ static int rrd_xport_fn( + + + /* pull the data from the rrd files ... */ +-if (data_fetch(im) == -1) ++if (data_fetch(im) != 0) + return -1; + + /* evaluate CDEF operations ... */ diff -Nru rrdtool-1.7.1/debian/patches/series rrdtool-1.7.1/debian/patches/series --- rrdtool-1.7.1/debian/patches/series 2019-02-07 16:21:22.0 +0100 +++ rrdtool-1.7.1/debian/patches/series 2019-05-30 22:28:06.0 +0200 @@ -1,2 +1,3 @@ no-rpath-for-ruby breaks-long-man-lines +segfault-xport signature.asc Description: This is a digitally signed message part.
Bug#927856: unblock: python-jwcrypto/0.6.0-1
Hi Timo, On 30-05-2019 13:18, Timo Aaltonen wrote: > Hi, I don't know how much would have to be backported, but it's probably > better to just unblock freeipa 4.7.2-3 instead, because python-jwcrypto > is a dep of freeipa-server (which isn't built on sid/buster). Do I understand correctly that the code is present to build it, you just don't do that in Debian? Do you suggest to change this bug to "unblock: freeipa/4.7.2-3" instead then? (I would be willing to unblock it, but then python-jwcrypto would go). > That way > current client-only freeipa would remain on buster. Custodia is another > package which depends on -jwcrypto, but it's again a server thing so can > be removed from buster. These package are all from the same team, I guess the team agrees? Paul
Bug#928807: unblock: mesa/18.3.6-2
Control: tags -1 moreinfo Hi Andreas, On Sat, 11 May 2019 16:43:45 +0200 Andreas Boll wrote: > This unblock request contains a stable upstream release with lots of > bug fixes for mesa's graphics drivers including fixes for driver > crashes and visual corruption. It fixes two RC bugs (#922346, > #926857). How would a targeted fix look like? New upstream releases don't meet the freeze policy and the diff is way to big to properly review. Paul signature.asc Description: OpenPGP digital signature
Processed: Re: unblock: mesa/18.3.6-2
Processing control commands: > tags -1 moreinfo Bug #928807 [release.debian.org] unblock: mesa/18.3.6-2 Added tag(s) moreinfo. -- 928807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928807 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: unblock: zfs-linux/0.7.13-1
Processing control commands: > tags -1 moreinfo Bug #928746 [release.debian.org] unblock: zfs-linux/0.7.13-1 Added tag(s) moreinfo. -- 928746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928746 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#928746: unblock: zfs-linux/0.7.13-1
Control: tags -1 moreinfo Hi Mo, On Thu, 09 May 2019 22:09:18 -0700 Mo Zhou wrote: > zfs-linux (= 0.7.13-1) is 66 days in unstable and there is no new bug > for it. > Compared to (0.7.12-2), the (0.7.13-1) version in unstable only > introduces > bug fixes. Aron has already applied for an unblock but it was rejected. > Here I'm requesting for unblock again. I checked bug #923770 again (it was filed by you by the way). As I said in that bug, I didn't spot anything that was at the level of important or more severe in Debian BTS terms. I may have been wrong, but then please point me to the changes so important that you want them in buster. Please also be prepared to undo the new upstream release and just fix the bugs that are so important to you. Be aware that requests like this one are draining energy from the release team. It isn't nice to turn a maintainer down on a request, repeating the process is worse. Your changes are huge (your explanation is appreciated), we get several unblock requests per day and we have a freeze policy in place to manage it. Please don't push your pet project so hard if it doesn't meet the policy that you are driving the volunteers in the release team away. Thanks for also considering our time. Paul signature.asc Description: OpenPGP digital signature
Processed: Re: [pre-a] unblock: julia/1.0.4+dfsg-1
Processing control commands: > tags -1 moreinfo Bug #928741 [release.debian.org] [pre-a] unblock: julia/1.0.4+dfsg-1 Added tag(s) moreinfo. > retitle -1 unblock: julia/1.0.4+dfsg-1 Bug #928741 [release.debian.org] [pre-a] unblock: julia/1.0.4+dfsg-1 Changed Bug title to 'unblock: julia/1.0.4+dfsg-1' from '[pre-a] unblock: julia/1.0.4+dfsg-1'. -- 928741: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928741 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#928741: [pre-a] unblock: julia/1.0.4+dfsg-1
Control: tags -1 moreinfo Control: retitle -1 unblock: julia/1.0.4+dfsg-1 Hi Mo, On Thu, 09 May 2019 19:26:06 -0700 Mo Zhou wrote: > The current version in testing is 1.0.3, I'm requesting > unblock for 1.0.4 (not-yet-released) because Julia's > 1.0.X series is strictly a bug-fix-only branch. As per > upstream's call-for-community-testing announcement: I appreciate you want the latest you can get for you package into buster. However, a new upstream (even for only bug fixes branches) does not meet the freeze policy. Can you please indicate which bugs in the changelog you consider important or more severe (in Debian BTS terms)? How much of the changes would fall in that category? Paul signature.asc Description: OpenPGP digital signature
Bug#926778: marked as done (unblock: python3.7 3.7.3 packages)
Your message dated Thu, 30 May 2019 21:16:46 +0200 with message-id <88b5c7fe-a3bd-dcca-3ac1-35ce70a34...@debian.org> and subject line Re: Bug#926778: unblock: python3.7 3.7.3 packages has caused the Debian Bug report #926778, regarding unblock: python3.7 3.7.3 packages 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.) -- 926778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926778 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: unblock Please unblock python3.7, python3-stdlib-extensions and python3-defaults, bumping the version to the final 3.7.3 release, and fixing a bus error on armhf, and avoiding unaligned memory accesses on arm64. --- End Message --- --- Begin Message --- Hi doko, On 27-05-2019 16:22, Matthias Klose wrote: > On 11.05.19 18:56, Paul Gevers wrote: >> On Wed, 10 Apr 2019 10:23:15 +0200 Matthias Klose wrote: >>> Please unblock python3.7, python3-stdlib-extensions and python3-defaults, >>> bumping the version to the final 3.7.3 release, and fixing a bus error on >>> armhf, >>> and avoiding unaligned memory accesses on arm64. >> >> This looks mostly OK (albeit a new upstream release, which we try to >> avoid unblocking), > > The update beyond 3.7.2 with the goal of 3.7.3 was communicated and approved > by > Emilio (pochu) even before doing the first upload from the 3.7 branch to > unstable. Please let me know if there is anything I can do to avoid confusion > for future uploads. Just mentioning it would have helped. Even if it would have been me that approved this, there is so much going on with different packages that it is easy to loose track of stuff. A word (or even better, a link) would go a long way. >> Please make sure that during the release, you document *all* packaging >> changes in the changelog and if needed, elaborate in the unblock request. > > will do for future uploads. Much appreciated. I unblocked the three packages, thanks for your work on Python. Paul signature.asc Description: OpenPGP digital signature --- End Message ---
Bug#928381: unblock: stunnel4/3:5.54~b3-1
Hi Peter, On 30-05-2019 11:24, Peter Pentchev wrote: > Just for my information, is there a chance that this upgrade could be > allowed later on during the buster lifecycle as a stable update? If it would be suitable for a stable release point update, it would be suitable now. We're close to releasing, but not that close yet. Paul signature.asc Description: OpenPGP digital signature
Bug#929132: unblock (pre-approval): dbus/1.12.14-1
Hello, Simon McVittie, le jeu. 30 mai 2019 19:04:49 +0100, a ecrit: > The only change that I think could possibly cause regressions > for d-i's use case (AT-SPI) d-i doesn't use AT-SPI yet actually. Samuel
Bug#929132: unblock (pre-approval): dbus/1.12.14-1
On Sun, 19 May 2019 at 15:35:00 +, Niels Thykier wrote: > Ok. I have added an unblock and age-days 8 hint. Also CC'ing KiBi for a > d-i ack before adding an unblock-udeb hint. This is now only waiting for a d-i ack, and I haven't had any regression reports. Any opinions? Full details: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929132#5 The only change that I think could possibly cause regressions for d-i's use case (AT-SPI) is that the tighter validation in bus/desktop-file.c could break AT-SPI if it ships syntactically invalid .service files, but /usr/share/dbus-1/services/org.a11y.Bus.service and /usr/share/dbus-1/accessibility-services/org.a11y.atspi.Registry.service both seem valid, so that shouldn't be an issue. smcv
Bug#924948: unblock: onedrive/2.2.6-2
Dear Niels, Please remove onedrive from buster. Thanks Norbert -- PREINING Norbert http://www.preining.info Accelia Inc. + JAIST + TeX Live + Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Bug#924948: unblock: onedrive/2.2.6-2
Norbert Preining: > Hi Paul, > > On Thu, 30 May 2019, Paul Gevers wrote: >> On Tue, 19 Mar 2019 07:50:10 +0900 Norbert Preining > > What a time lag for a release related bug, impressive. > Hi Nobert, I can understand that the delay in the reply is unsatisfying to you - personally, I am not happy about such delays either. However, I find remarks like the above unhelpful and uncalled for at best - not to mention draining energy- and motivation-wise. Please keep future communication professional. A much better approach would have been to ask us an update (in a friendly/professional manner) in case we had forgotten about the request. This might have gotten you a reply much earlier. Thanks, ~Niels
Bug#929321: unblock: sqlalchemy/1.2.18+ds1-2 (CVE-2019-7164 CVE-2019-7548)
On 5/30/19 5:23 AM, Paul Gevers wrote: Hi Mike, zigo, Thanks for your replies, I very much think it's safer to just allow SQLAchemy to migrate right now, to fix the potential SQL insertion vulnerability, rather than waiting for any (potential, but likely rare) issue in the above reverse dependencies. I do think a gentle ping to the maintainers of the above packages would be nice, but probably mass-filling of bugs isn't needed. How can I easily gather the list of maintainer? Is there a script somewhere to do this, or should I write it myself (which shouldn't be hard with some apt-cache show in a loop...)? Piotr, Mike, is what I wrote above accurate? I can confirm Openstack is likely OK, most packages are likely OK, and if a package is not OK, it's a trivial fix for them. But as long as they are not fixed, how severe do you expect those issues to be? I suggest to proceed with contacting them, just so maintainers can check their package if they care. severe because they will have queries that won't run. @zigo, if you have the package name, you can contact the maintainers by sending to @packages.debian.org. I'm not 100% sure if this only works for source package names. Paul
Bug#924948: unblock: onedrive/2.2.6-2
Hi Paul, On Thu, 30 May 2019, Paul Gevers wrote: > On Tue, 19 Mar 2019 07:50:10 +0900 Norbert Preining What a time lag for a release related bug, impressive. > I fear this request hasn't received a response because it is very > daunting to review (35 files changed, 1565 insertions(+), 747 As far as I remember, there have been other full version upgrades after that date, but anyway. > fixes). Hence the I am seriously wondering if it wouldn't be better to > remove onedrive from buster and make sure the package is in better shape > during the bullseye cycle. What do you think? Feel free to do whatever you think is good. I have no particular opinion. The version that is in buster now is usable, but does not catch errors in a good way but crashes. Manual syncing should be fine in most cases, while background sync / monitor mode might be sub-optimal or crash rather soon. Best Norbert -- PREINING Norbert http://www.preining.info Accelia Inc. +JAIST +TeX Live +Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Bug#929676: unblock: lintian/2.15.0
On Thu, 30 May 2019, Chris Lamb wrote: > Hi Ivo, > > > > Please consider unblocking lintian 2.15.0 for buster (from 2.9.1). This > > > was specifically requested in #929577 by Mattia Rizzollo: > > > > This really should have been discussed in advance. > > I completely agree. The problems simply did not occur to me as — as > #929577 implies — it affects infrastructure that I am not involved > with and thus I was not experiencing any issue. > > >If you want to maintain the correct version ordering between > > testing and backports, I suggest you don't do any new uploads to backports > > before you get confirmation that the corresponding version will be accepted > > in > > buster. > > 100% noted. Just for the record, lintian has an exception for backports. So please upload whenever you like. Alex - Backports ftpmaster signature.asc Description: PGP signature
Bug#926412: marked as done (unblock: gnutls28/3.6.7-2)
Your message dated Thu, 30 May 2019 12:07:00 + with message-id <10f1ba2b-fce1-fdca-0a1b-ac942f61e...@thykier.net> and subject line Re: Bug#926412: unblock: gnutls28/3.6.7-2 has caused the Debian Bug report #926412, regarding unblock: gnutls28/3.6.7-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.) -- 926412: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926412 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: unblock Please unblock package gnutls28. This is a upstream bugfix release featuring two security fixes + Fixes a memory corruption (double free) vulnerability in the certificate verification API. https://gitlab.com/gnutls/gnutls/issues/694 CVE-2019-3829 GNUTLS-SA-2019-03-27 + Fixes an invalid pointer access via malformed TLS1.3 async messages; https://gitlab.com/gnutls/gnutls/issues/704 CVE-2019-3836 GNUTLS-SA-2019-03-27 One of these is fixed by a hardening measure (gnutls_free() will automatically set the free'd pointer to NULL.) It also unbreaks vlc (#922879) and has some TLS1.3 related changes. The straight debdiff is huge, because of a) usual release updates of autogenerated files and b) because it includes a global 's/http:/https:/'. Stripped down debdiff is attached. unblock gnutls28/3.6.7-2 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' smaller.debdiff.diff.xz Description: application/xz signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Andreas Metzler: > On 2019-05-20 Paul Gevers wrote: >> On 19-05-2019 10:33, Andreas Metzler wrote: >>> I probably could try to pick the CVE related changes and other important >>> bug-fixes, however I do not think it is the right choice. The changes >>> will be smaller but the risk of breakage is higher. > >> Can you explain why do you believe that? > >>> Also 3.6.7 now has >>> been tested in sid for almost two months now. > >> Ack. > > Hello Paul, > > well, apart from the two CVE fixes there are many bugfixes in this > release that we probably want, e.g. > https://gitlab.com/gnutls/gnutls/issues/690 > https://gitlab.com/gnutls/gnutls/issues/689 > https://gitlab.com/gnutls/gnutls/issues/713 > https://gitlab.com/gnutls/gnutls/issues/698 > etc. > > Most of these are related to TLS 1.3. - They might not show up as bug > reports now because it TLS1.3 is not that common yet but will propably > cause issues later in buster's lifetime. And the more fixes there the > more error-prone complicated cherry-picking s going to be. > You bumped the debhelper compat level. That isn't a change we find acceptable during the freeze. >>> >>> I will immediately revert this if it helps. > >> I don't have enough experience yet with reviewing unblocks, that I feel >> comfortable reviewing and unblocking the current package, so if your >> insisting on the whole, somebody else will have to do the review. I am >> sure this revert will be a requirement though. > > The revert has been in sid for a week now. > > cu Andreas > Unblocked. The upload had a poor signal-to-noise ratio (most of the diff being version bumps in manpages, etc.). A selective filterdiff *might* have made this go quicker - as a suggestion for next time. Thanks, ~Niels--- End Message ---
Bug#927856: unblock: python-jwcrypto/0.6.0-1
On 30.5.2019 10.59, Paul Gevers wrote: > Control: tags -1 moreinfo > > Hi Timo, > > On Wed, 24 Apr 2019 11:06:36 +0300 Timo Aaltonen > wrote: >> Please unblock package python-jwcrypto >> >> The new upstream release is needed to fix: >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925457 > > Can't we have a targeted fix for that issue? New upstream releases are > typically not appropriate at this stage of the release. If not, I expect > we'll just let the package be autoremoved from buster. > > Paul > Hi, I don't know how much would have to be backported, but it's probably better to just unblock freeipa 4.7.2-3 instead, because python-jwcrypto is a dep of freeipa-server (which isn't built on sid/buster). That way current client-only freeipa would remain on buster. Custodia is another package which depends on -jwcrypto, but it's again a server thing so can be removed from buster. -- t
Bug#929676: unblock: lintian/2.15.0
Hi Ivo, > > Please consider unblocking lintian 2.15.0 for buster (from 2.9.1). This > > was specifically requested in #929577 by Mattia Rizzollo: > > This really should have been discussed in advance. I completely agree. The problems simply did not occur to me as — as #929577 implies — it affects infrastructure that I am not involved with and thus I was not experiencing any issue. >If you want to maintain the correct version ordering between > testing and backports, I suggest you don't do any new uploads to backports > before you get confirmation that the corresponding version will be accepted in > buster. 100% noted. Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org 🍥 chris-lamb.co.uk `-
Bug#928381: unblock: stunnel4/3:5.54~b3-1
On Thu, May 30, 2019 at 11:08:02AM +0200, Paul Gevers wrote:
> tags 928381 wontfix
> thanks
>
> Hi Peter,
>
> On Fri, 3 May 2019 13:48:43 +0300 Peter Pentchev wrote:
> > I am aware that new upstream versions are not usually allowed in during
> > a release freeze; however, the upstream author has said that the changes
> > in the stunnel internal operation to fix the thread interlock problem
> > are too extensive to be easily backported :(
>
> We're too uncomfortable with all the changes (they are too big to
> properly review). I recognize that the bug isn't pretty, but introducing
> new ones at this stage is even less so (that's why we have the freeze).
Thanks for considering this and for the reply; I cannot say that
I didn't expect such a resolution at all.
Just for my information, is there a chance that this upgrade could be
allowed later on during the buster lifecycle as a stable update?
Thanks for everything you are doing for Debian!
G'luck,
Peter
--
Peter Pentchev roam@{ringlet.net,debian.org,FreeBSD.org} p...@storpool.com
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13
signature.asc
Description: PGP signature
Bug#929321: unblock: sqlalchemy/1.2.18+ds1-2 (CVE-2019-7164 CVE-2019-7548)
Hi Mike, zigo, Thanks for your replies, >> I very much think it's safer to just allow SQLAchemy to migrate right >> now, to fix the potential SQL insertion vulnerability, rather than >> waiting for any (potential, but likely rare) issue in the above reverse >> dependencies. >> >> I do think a gentle ping to the maintainers of the above packages would >> be nice, but probably mass-filling of bugs isn't needed. How can I >> easily gather the list of maintainer? Is there a script somewhere to do >> this, or should I write it myself (which shouldn't be hard with some >> apt-cache show in a loop...)? >> >> Piotr, Mike, is what I wrote above accurate? > > I can confirm Openstack is likely OK, most packages are likely OK, and > if a package is not OK, it's a trivial fix for them. But as long as they are not fixed, how severe do you expect those issues to be? I suggest to proceed with contacting them, just so maintainers can check their package if they care. @zigo, if you have the package name, you can contact the maintainers by sending to @packages.debian.org. I'm not 100% sure if this only works for source package names. Paul signature.asc Description: OpenPGP digital signature
Processed: tagging 929215
Processing commands for cont...@bugs.debian.org: > tags 929215 - moreinfo Bug #929215 [release.debian.org] unblock: systemd/241-4 Removed tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 929215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929215 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Re: [pcp] pcp is marked for autoremoval from testing
Hi Nathan, On 30-05-2019 06:55, Nathan Scott wrote: > The issues below no longer affect pcp-4.3.2, which has been in > unstable for some time. > According to https://tracker.debian.org/pkg/pcp this version is blocked ... > > "Not touching package due to block request by freeze (please contact > debian-release if update is needed)" > > Please consider unblocking pcp-4.3.2 to resolve this. That's a new upstream version which is not appropriate during the freeze. Please make sure you have a targeted fix for RC issues. Also, e-mail tends to get lost regularly, the volume is big on our list. Please file unblock bugs against the release.debian.org pseudo package next time or if you have an acceptable solution. Paul signature.asc Description: OpenPGP digital signature
Bug#929320: marked as done (unblock: libpfm4/4.10.1+git10-gd2a5b56-1)
Your message dated Thu, 30 May 2019 09:10:00 +
with message-id
and subject line Re: Bug#929320: unblock: libpfm4/4.10.1+git10-gd2a5b56-1
has caused the Debian Bug report #929320,
regarding unblock: libpfm4/4.10.1+git10-gd2a5b56-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.)
--
929320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929320
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: unblock
Please unblock package libpfm4
This is a new upstream snapshot updating the event definitions for some
CPU models.
unblock libpfm4/4.10.1+git10-gd2a5b56-1
Andreas
diff --git a/Makefile b/Makefile
index 440249f..c928088 100644
--- a/Makefile
+++ b/Makefile
@@ -65,11 +65,14 @@ tar: clean
ln -s $$PWD ../$(PKG) && cd .. && $(TAR) -zcf $(TARBALL) $(PKG)/. &&
rm $(PKG)
@echo generated ../$(TARBALL)
-install:
- @echo installing in $(DESTDIR)
- @set -e ; for d in $(DIRS) ; do $(MAKE) -C $$d $@ ; done
-
-install_examples:
+install-lib:
+ @echo installing in $(DESTDIR)$(PREFIX)
+ @$(MAKE) -C lib install
+install install-all:
+ @echo installing in $(DESTDIR)$(PREFIX)
+ @set -e ; for d in $(DIRS) ; do $(MAKE) -C $$d install ; done
+install-examples install_examples:
+ @echo installing in $(DESTDIR)$(PREFIX)
@set -e ; for d in $(EXAMPLE_DIRS) ; do $(MAKE) -C $$d $@ ; done
tags:
@@ -79,6 +82,6 @@ tags:
static:
make all CONFIG_PFMLIB_SHARED=n
-.PHONY: all clean distclean depend tar install install_examples lib static
+.PHONY: all clean distclean depend tar install install-all install-lib
install-examples lib static install_examples
# DO NOT DELETE
diff --git a/config.mk b/config.mk
index cc9a6d9..daa982e 100644
--- a/config.mk
+++ b/config.mk
@@ -116,7 +116,7 @@ AGE=1
#
# Where should things (lib, headers, man) go in the end.
#
-PREFIX=/usr/local
+PREFIX?=/usr/local
LIBDIR=$(PREFIX)/lib
INCDIR=$(PREFIX)/include
MANDIR=$(PREFIX)/share/man
diff --git a/debian/changelog b/debian/changelog
index fed9f51..bae0b83 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,17 @@
+libpfm4 (4.10.1+git10-gd2a5b56-1) unstable; urgency=medium
+
+ * New upstream GIT snapshot.
+- Update SKX and CLX event tables.
+
+ -- Andreas Beckmann Sat, 18 May 2019 15:13:01 +0200
+
+libpfm4 (4.10.1+git9-gac95d19-1) unstable; urgency=medium
+
+ * New upstream GIT snapshot.
+- Remove MERGE event from AMD Fam17h table.
+
+ -- Andreas Beckmann Tue, 30 Apr 2019 01:46:05 +0200
+
libpfm4 (4.10.1+git6-g8f2208a-1) unstable; urgency=medium
* New upstream GIT snapshot.
diff --git a/debian/snapshot.sh b/debian/snapshot.sh
index 4c68d61..4d15f21 100755
--- a/debian/snapshot.sh
+++ b/debian/snapshot.sh
@@ -5,7 +5,8 @@ set -e
commit=${1:-libpfm4/master}
-gitver=$(git describe --tags ${commit})
+upsver=$(git describe --tags ${commit})
+gitver=$(git describe --match ${upsver%+git*} --tags ${commit})
gitver=${gitver#v}
tagver=${gitver%%-*}
gitver=${gitver#${tagver}-}
diff --git a/debian/source/lintian-overrides b/debian/source/lintian-overrides
new file mode 100644
index 000..53fb7f6
--- /dev/null
+++ b/debian/source/lintian-overrides
@@ -0,0 +1,2 @@
+# this is a git snapshot
+hyphen-in-upstream-part-of-debian-changelog-version
diff --git a/docs/man3/pfm_get_os_event_encoding.3
b/docs/man3/pfm_get_os_event_encoding.3
index 6ec57be..c9cab18 100644
--- a/docs/man3/pfm_get_os_event_encoding.3
+++ b/docs/man3/pfm_get_os_event_encoding.3
@@ -64,7 +64,7 @@ in this field. The typical calling sequence looks as follows:
PFM_OS_NONE,
&e);
if (ret == PFM_SUCCESS) {
- printf("fstr=%s\n", fstr);
+ printf("fstr=%s\\n", fstr);
free(fstr);
}
.fi
diff --git a/examples/Makefile b/examples/Makefile
index 68d1081..fc5677a 100644
--- a/examples/Makefile
+++ b/examples/Makefile
@@ -51,7 +51,7 @@ clean:
distclean: clean
-install_examples: $(TARGETS)
+install-examples install_examples: $(TARGETS)
@echo installing: $(TARGETS)
-mkdir -p $(EXAMPLESDIR)
$(INSTALL) -m 755 $(TARGETS) $(EXAMPLESDIR)
@@ -59,4 +59,4 @@ install_examples: $(TARGETS)
#
# examples are installed as part of the RPM install, typically in
/usr/share/doc/libpfm-X.Y/
#
-.PHONY: install depend install_examples
+.PHONY: install depend install-example install_examples
diff --git a/lib/events/amd64_events_fam17h.h b/lib/events/amd64_events_fam17h.h
i
Bug#929625: marked as done (unblock: bird/1.6.6-1)
Your message dated Thu, 30 May 2019 09:05:00 + with message-id and subject line Re: Bug#929625: unblock: bird/1.6.6-1 has caused the Debian Bug report #929625, regarding unblock: bird/1.6.6-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.) -- 929625: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929625 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: unblock Please unblock the bird package because the version in testing has some serious bugs about routes propagation, better explained in the attached diff. This was discussed in #928141, where one of the upstream maintainers recommended that 1.6.6 should get into testing. The version currently in unstable has been in unstable for three months without any issues, and is the one that I am using in production (while the one currently in testing was toxic in my environment). I am not the bird maintainer, but Ondřej looks busy and I am sure that he will not mind me requesting this. I am attaching a debdiff from which I removed the generated files and some documentation/example changes not relevant for the Debian package. unblock bird/1.6.6-1 -- ciao, Marco diff -Nru bird-1.6.5/ChangeLog bird-1.6.6/ChangeLog --- bird-1.6.5/ChangeLog 2019-01-07 16:29:04.0 +0100 +++ bird-1.6.6/ChangeLog 2019-03-01 00:13:32.0 +0100 @@ -1,3 +1,86 @@ +commit b5d1903bf6ce454716e97828e6e4062bf17ac000 +Author: Ondrej Zajicek (work) +Date: Tue Feb 26 18:10:04 2019 +0100 + +NEWS and version update + +commit 2e7ee1c9d3158603c3b01bbef8559092ae46ae84 +Author: Ondrej Zajicek (work) +Date: Fri Feb 22 02:33:01 2019 +0100 + +Nest: Do not compare rte.flags during rte_update() + +Route flags are mosty internal state of rtable, they are not significant +to whether a route has changed. With the old code, all routes received as +a part of enhanced route refresh are always re-announced to other peers +due to change in REF_STALE. + +commit 797969983d38149f4a0ea1f960becfac88fc2b8e +Author: Ondrej Zajicek (work) +Date: Tue Feb 19 18:32:45 2019 +0100 + +Doc: Detect SP/OpenSP automatically + +commit b3fceeba30bd6a685de0aa17dbe6bcfd77d1ca29 +Author: Ondrej Zajicek (work) +Date: Tue Feb 19 16:21:52 2019 +0100 + +Nest: Prevent withdraws from propagation back to source protocol (for accepted mode) + +Update for one of previous patches, handles the the issue for +first-accepted mode of route propagation. + +commit 2dd9800ab51a309add1c56aa9659c41f30481299 +Author: Ondrej Zajicek (work) +Date: Tue Feb 19 16:00:30 2019 +0100 + +Nest: Improve export counter handling + +One of previous workarounds for phantom route avoidance breaks export +counters by expanding sending of spurious withdraws, which are send when +we are not sure whether we have advertised that routes in the past. +If not, then export counter is decreased, but it was not increased +before, so it overflows under zero. + +The patch fixes that by sending spurious withdraws, but not counting them +on export counter. That may lead to error in the other direction, but +that happens only as a race condition (i.e., in normal operation filters +return proper values about old route export state). + +commit b4438e40efa498325f38f0bf4681ecb2bbba4da7 +Author: Ondrej Zajicek (work) +Date: Wed Jan 30 17:03:30 2019 +0100 + +Nest: Prevent withdraws from propagation back to source protocol + +The earlier fix loosen conditions for not running filters on old +route when deciding about route propagation to a protocol to avoid +issues with ghost routes in some race conditions. + +Unfortunately, the fix also caused back-propagation of withdraws. For +regular updates, back-propagation is prevented in import_control hooks, +but these are not called on withdraws. For them, import_control hooks +are called on old routes instead, changing (old, NULL) notification +to (NULL, NULL), which is ignored. By not calling export processing +in some cases, the withdraw is not ignored and is back-propagated. + +This patch fixes that by contract conditions so the earlier fix is not +applied to back-propagated updates. + +commit ccb37330d062712935b3f3b9c236322d20c177f6 +Author: Ondrej Zajicek (work) +Date: Sat Jan 26 21:03:36 2019 +0100 + +Doc: Add documentation for OSPF retransmit delay option + +Thanks to Igor Podlesny for notification. + +commit e99e7d
Bug#929419: marked as done (unblock: tasksel/3.53)
Your message dated Thu, 30 May 2019 09:06:00 + with message-id <7fe59c50-2658-b89e-60a3-f3d1306c0...@thykier.net> and subject line Re: Bug#929419: unblock: tasksel/3.53 has caused the Debian Bug report #929419, regarding unblock: tasksel/3.53 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.) -- 929419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929419 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Usertags: unblock I would like to request an unblock for version 3.53 of tasksel. The changings contain: - Remove bubulle from uploaders. - Translation update for Korean - Trivial syntax fixes in changelog file. A corresponding debdiff is attached. Thanks Holger -- Holger Wansing PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076 diff -Nru tasksel-3.52/debian/changelog tasksel-3.53/debian/changelog --- tasksel-3.52/debian/changelog 2019-04-02 22:48:50.0 +0200 +++ tasksel-3.53/debian/changelog 2019-05-23 05:57:05.0 +0200 @@ -1,4 +1,18 @@ +tasksel (3.53) unstable; urgency=medium + + * Team upload. + + [ Cyril Brulebois ] + * Remove Christian Perrier from Uploaders, with many thanks for all +his contributions over the years! (Closes: #927489) + + [ Updated debconf translations ] + * Korean (ko.po) by Changwoo Ryu. + + -- Holger Wansing Thu, 23 May 2019 05:57:05 +0200 + tasksel (3.52) unstable; urgency=medium + * Team upload. [ Updated translations ] @@ -7,6 +21,7 @@ -- Holger Wansing Tue, 02 Apr 2019 22:48:50 +0200 tasksel (3.51) unstable; urgency=medium + * Team upload. * Add firefox-l10n-ne-np to task-nepali-desktop. Closes: #922123 @@ -32,6 +47,7 @@ -- Holger Wansing Sun, 10 Mar 2019 23:12:54 +0100 tasksel (3.50) unstable; urgency=medium + * Team upload. [ Yves-Alexis Perez ] @@ -49,6 +65,7 @@ -- Holger Wansing Fri, 08 Feb 2019 22:28:45 +0100 tasksel (3.49) unstable; urgency=medium + * Team upload [ Tetsutaro KAWADA ] diff -Nru tasksel-3.52/debian/control tasksel-3.53/debian/control --- tasksel-3.52/debian/control 2019-03-10 23:11:31.0 +0100 +++ tasksel-3.53/debian/control 2019-04-22 09:13:13.0 +0200 @@ -2,8 +2,7 @@ Section: tasks Priority: optional Maintainer: Debian Install System Team -Uploaders: Christian Perrier , - Nicolas Braud-Santoni +Uploaders: Nicolas Braud-Santoni Standards-Version: 4.1.4 Build-Depends: po-debconf, debhelper (>= 9), gettext, dpkg-dev (>= 1.9.0) Vcs-Browser: https://salsa.debian.org/installer-team/tasksel diff -Nru tasksel-3.52/debian/po/ko.po tasksel-3.53/debian/po/ko.po --- tasksel-3.52/debian/po/ko.po 2018-08-10 21:25:13.0 +0200 +++ tasksel-3.53/debian/po/ko.po 2019-05-23 05:42:53.0 +0200 @@ -1,13 +1,13 @@ # Sunjae Park , 2005 -# Changwoo Ryu , 2005. +# Changwoo Ryu , 2005, 2019. # msgid "" msgstr "" "Project-Id-Version: tasksel_debian\n" "Report-Msgid-Bugs-To: task...@packages.debian.org\n" "POT-Creation-Date: 2018-05-23 01:37+0200\n" -"PO-Revision-Date: 2007-12-30 07:11+0900\n" -"Last-Translator: Sunjae Park \n" +"PO-Revision-Date: 2019-05-20 08:09+0900\n" +"Last-Translator: Changwoo Ryu \n" "Language-Team: Korean \n" "Language: ko\n" "MIME-Version: 1.0\n" @@ -47,7 +47,7 @@ #. Description #: ../templates:3001 msgid "This can be preseeded to override the default desktop." -msgstr "" +msgstr "ì´ ì¤ì ì ëí´ ë¯¸ë¦¬ ì¤ì 기ë¥ì ì´ì©í´ 기본 ë°ì¤í¬í±ì ë°ê¿ ì ììµëë¤." #. Type: title #. Description --- End Message --- --- Begin Message --- Holger Wansing: > Package: release.debian.org > Usertags: unblock > > > I would like to request an unblock for version 3.53 of tasksel. > > > The changings contain: > > - Remove bubulle from uploaders. > - Translation update for Korean > - Trivial syntax fixes in changelog file. > > > A corresponding debdiff is attached. > > > > Thanks > Holger > Unblocked, thanks. ~Niels--- End Message ---
Processed: Re: unblock: stunnel4/3:5.54~b3-1
Processing commands for cont...@bugs.debian.org: > tags 928381 wontfix Bug #928381 [release.debian.org] unblock: stunnel4/3:5.54~b3-1 Added tag(s) wontfix. > thanks Stopping processing here. Please contact me if you need assistance. -- 928381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928381 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: unblock: onedrive/2.2.6-2
Processing control commands: > tags -1 moreinfo Bug #924948 [release.debian.org] unblock: onedrive/2.2.6-2 Added tag(s) moreinfo. -- 924948: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924948 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#924948: unblock: onedrive/2.2.6-2
Control: tags -1 moreinfo Hi Norbert, On Tue, 19 Mar 2019 07:50:10 +0900 Norbert Preining wrote: > I am asking to unblock onedrive 2.2.6-2 for buster. This is a new > upstream release that fixes a considerable amount of (critical) bugs, > most of which not reported in Debian, but still present. Here are the > release notes from the CHANGELOG.md file: > > ## 2.2.6 - 2019-03-12 > ### Fixed > * Resolve application crash when unable to delete remote folders when > business retention policies are enabled > * Resolve deprecation warning: loop index implicitly converted from size_t > to int > * Resolve warnings regarding 'bashisms' > * Resolve handling of notification failure is dbus server has not started > or available > * Resolve handling of response JSON to ensure that 'id' key element is > always checked for > * Resolve excessive & needless logging in monitor mode > * Resolve compiling with LDC on Alpine as musl lacks some standard > interfaces > * Resolve notification issues when offline and cannot act on changes > * Resolve Docker entrypoint.sh to accept command line arguments > * Resolve to create a new upload session on reinit > * Resolve where on OneDrive query failure, default root and drive id is > used if a response is not returned > * Resolve Key not found: nextExpectedRanges when attempting session uploads > and incorrect response is returned > * Resolve application crash when re-using an authentication URI twice after > previous --logout > * Resolve creating a folder on a shared personal folder appears successful > but returns a JSON error > * Resolve to treat mv of new file as upload of mv target > * Update Debian i386 build dependencies > * Update handling of --get-O365-drive-id to print out all 'site names' that > match the explicit search entry rather than just the last match > * Update Docker readme & documentation > * Update handling of validating local file permissions for new file uploads > ### Added > * Add support for install & uninstall on RHEL / CentOS 6.x > * Add support for when notifications are enabled, display the number of > OneDrive changes to process if any are found > * Add 'config' option 'min_notif_changes' for minimum number of changes to > notify on, default = 5 > * Add additional Docker container builds utilising a smaller OS footprint > * Add configurable interval of logging in monitor mode > * Implement new CLI option --skip-dot-files to skip .files and .folders if > option is used > * Implement new CLI option --check-for-nosync to ignore folder when special > file (.nosync) present > * Implement new CLI option --dry-run > > > The Debian related diffs are trivial, see attached debdiff, where I > excluded the actual code changes in the onedrive sources. > > Having 2.2.5 with all the hitherto found bugs in buster would be > unfortunate. I fear this request hasn't received a response because it is very daunting to review (35 files changed, 1565 insertions(+), 747 deletions(-)) and it doesn't comply with the freeze policy (targeted fixes). Hence the I am seriously wondering if it wouldn't be better to remove onedrive from buster and make sure the package is in better shape during the bullseye cycle. What do you think? Paul signature.asc Description: OpenPGP digital signature
Bug#929571: marked as done (unblock: dgit/8.5)
Your message dated Thu, 30 May 2019 08:15:00 +
with message-id <8e02b68b-e05b-c529-28ab-d12a7f434...@thykier.net>
and subject line Re: Bug#929571: unblock: dgit/8.5
has caused the Debian Bug report #929571,
regarding unblock: dgit/8.5
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.)
--
929571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929571
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: unblock
Please unblock package dgit
I have discovered an annoying bug in a common error handling pattern
in dgit, which results in it not printing errno when it is crashing
for an unexpected reason.
I would like to fix it in buster for two reasons:
* It makes some kinds of failure much harder to diagnose.
* The fix, while conceptually extremely simple, and extremely
formulaic, is textually very large. I would like to avoid such a
big textual divergence between buster and future development;
primarily to avoid textual conflicts when back-porting /
forward-porting any future bugfixes to the stable branch.
I attach the git commit which explains the details. Assuming you give
the go-ahead, I will upload this with an appropriate changelog update.
unblock dgit/8.5
-- System Information:
Debian Release: 9.9
APT prefers stable-debug
APT policy: (500, 'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-0.bpo.2-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
>From d28467db161d0590469b5f8e1115f84858d66e06 Mon Sep 17 00:00:00 2001
From: Ian Jackson
Date: Sun, 26 May 2019 10:50:23 +0100
Subject: [PATCH] Replace `confess $!' with `confess "$!"', to actually print
errno
$ perl -e 'use Carp; open X, ">/dev/eacces" or die $!'
Permission denied at -e line 1.
$ perl -e 'use Carp; open X, ">/dev/eacces" or confess $!'
at -e line 1.
$ perl -e 'use Carp; open X, ">/dev/eacces" or confess "$!"'
Permission denied at -e line 1.
$
confess will get references to its arguments in @_. Its documentation
says it saves/restores $!. I conjecture that these interact as we see
here:
$ perl -e '$!=1; sub x { print ">@_<\n"; } x $!;'
>Operation not permitted<
$ perl -e '$!=1; sub x { local $!; print ">@_<\n"; } x $!;'
><
Quoting "$!" averts the reference (and it will also ensure that we
get the string value of $!, in case confess were to do anything in the
future which would mess that up).
This commit was made like this:
perl -i -pe 's/confess \$!/confess "\$!"/g' dgit
perl -i -pe 's/confess \$!/confess "\$!"/g' git-debrebase
perl -i -pe 's/confess \$!/confess "\$!"/g' Debian/Dgit.pm
I have manually reviewed each hunk and it all looks good to me.
Closes: #929549
Signed-off-by: Ian Jackson
---
Debian/Dgit.pm | 56 +++---
dgit | 240 -
git-debrebase | 42 +-
3 files changed, 169 insertions(+), 169 deletions(-)
diff --git a/Debian/Dgit.pm b/Debian/Dgit.pm
index 2ef32f32..61476d9f 100644
--- a/Debian/Dgit.pm
+++ b/Debian/Dgit.pm
@@ -148,11 +148,11 @@ sub setup_sigwarn () {
sub initdebug ($) {
($debugprefix) = @_;
-open DEBUG, ">/dev/null" or confess $!;
+open DEBUG, ">/dev/null" or confess "$!";
}
sub enabledebug () {
-open DEBUG, ">&STDERR" or confess $!;
+open DEBUG, ">&STDERR" or confess "$!";
DEBUG->autoflush(1);
$debuglevel ||= 1;
}
@@ -181,7 +181,7 @@ sub printdebug {
print DEBUG $debugprefix unless $printdebug_noprefix;
pop @_ while @_ and !length $_[-1];
return unless @_;
-print DEBUG @_ or confess $!;
+print DEBUG @_ or confess "$!";
$printdebug_noprefix = $_[-1] !~ m{\n$};
}
@@ -214,9 +214,9 @@ sub shellquote {
sub printcmd {
my $fh = shift @_;
my $intro = shift @_;
-print $fh $intro," " or confess $!;
-print $fh shellquote @_ or confess $!;
-print $fh "\n" or confess $!;
+print $fh $intro," " or confess "$!";
+print $fh shellquote @_ or confess "$!";
+print $fh "\n" or confess "$!";
}
sub debugcmd {
@@ -347,7 +347,7 @@ sub waitstatusmsg () {
sub failedcmd_report_cmd {
my $intro = shift @_;
$intro //= __ "failed command";
-{ local ($!); printcmd \*STDERR, _us().": $intro:", @_ or confess $!; };
+{ local ($!); printcmd \*STDERR, _us().": $intro:", @_ or
Bug#929108: marked as done (unblock: gmsh/4.1.5+really4.1.3+ds1-1)
Your message dated Thu, 30 May 2019 08:13:00 +
with message-id <0161f264-befc-6e18-5983-7af12ed01...@thykier.net>
and subject line Re: Bug#929108: unblock: gmsh/4.1.5+really4.1.3+ds1-1
has caused the Debian Bug report #929108,
regarding unblock: gmsh/4.1.5+really4.1.3+ds1-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.)
--
929108: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929108
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: unblock
gmsh has an old path to OpenCASCADE include files (#927808); this is
easy to fix (see attached diff).
Rebuilding the package also changes a dependency on amd64 (libgmsh4.1
depends on `libhdf5-openmpi-103 (>= 1.8.13)` instead of `libhdf5-103`
after the rebuild); however this matches the dependency on i386.
However gmsh was updated to a new upstream release in unstable on
2019-03-02 with a small fix on 2019-03-04; this missed the freeze date
slightly.
Do you prefer an upload via t-p-u or should I prepare a gmsh
4.1.5+really4.1.3+ds1-1 upload for unstable?
Ansgar
diff -Nru gmsh-4.1.3+ds1/debian/changelog gmsh-4.1.3+ds1/debian/changelog
--- gmsh-4.1.3+ds1/debian/changelog 2019-01-27 12:22:01.0 +0100
+++ gmsh-4.1.3+ds1/debian/changelog 2019-05-17 10:41:56.0 +0200
@@ -1,3 +1,10 @@
+gmsh (4.1.3+ds1-2) buster; urgency=medium
+
+ * Team upload.
+ * debian/rules: Do not pass `-DOCC_INC=...` to cmake (Closes: #927808)
+
+ -- Ansgar Burchardt Fri, 17 May 2019 10:41:56 +0200
+
gmsh (4.1.3+ds1-1) unstable; urgency=medium
* [dbbbe82] New upstream version 4.1.3+ds1
diff -Nru gmsh-4.1.3+ds1/debian/rules gmsh-4.1.3+ds1/debian/rules
--- gmsh-4.1.3+ds1/debian/rules 2019-01-27 12:22:01.0 +0100
+++ gmsh-4.1.3+ds1/debian/rules 2019-05-17 10:39:57.0 +0200
@@ -32,7 +32,6 @@
-DENABLE_ONELAB:BOOL=ON \
-DCMAKE_SKIP_RPATH:BOOL=ON \
-DCMAKE_INCLUDE_PATH:STRING="/usr/include/mpi" \
--DOCC_INC:STRING="/usr/include/occt" \
-DOCC_LIB:STRING="/usr/lib/${DEB_HOST_MULTIARCH}"
│
--- End Message ---
--- Begin Message ---
Ansgar:
> Control: tags -1 - moreinfo
> Control: retitle -1 unblock: gmsh/4.1.5+really4.1.3+ds1-1
>
> Ivo De Decker writes:
>> On Fri, May 17, 2019 at 11:12:59AM +0200, Ansgar Burchardt wrote:
>>> Do you prefer an upload via t-p-u or should I prepare a gmsh
>>> 4.1.5+really4.1.3+ds1-1 upload for unstable?
>>
>> An upload to unstable would be preferred. So please go ahead with that and
>> remove the moreinfo tag from this bug once it is in unstable.
>
> gmsh_4.1.5+really4.1.3+ds1-1 was uploaded to unstable yesterday.
>
> Ansgar
>
And unblocked now, thanks. :)
~Niels--- End Message ---
Bug#929731: marked as done (unblock: flash-kernel/3.99)
Your message dated Thu, 30 May 2019 08:09:00 + with message-id <53d2c79f-92d3-859c-13fd-b79aac4a2...@thykier.net> and subject line Re: Bug#929731: unblock: flash-kernel/3.99 has caused the Debian Bug report #929731, regarding unblock: flash-kernel/3.99 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.) -- 929731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929731 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: unblock X-Debbugs-Cc: vagr...@debian.org, debian-b...@lists.debian.org Please unblock package flash-kernel This upload adds support for two additional boards, one additional name for another board, and updates the Uploaders list. The changes should be very low risk to existing platforms, and really appreciated by people with the added boards. diff -Nru flash-kernel-3.98/db/all.db flash-kernel-3.99/db/all.db --- flash-kernel-3.98/db/all.db 2019-04-04 14:37:13.0 -0700 +++ flash-kernel-3.99/db/all.db 2019-05-23 09:54:49.0 -0700 @@ -481,6 +481,13 @@ U-Boot-Script-Name: bootscr.sunxi Required-Packages: u-boot-tools +Machine: FriendlyARM NanoPi NEO 2 +Kernel-Flavors: arm64 +Boot-Script-Path: /boot/boot.scr +DTB-Id: allwinner/sun50i-h5-nanopi-neo2.dtb +U-Boot-Script-Name: bootscr.uboot-generic +Required-Packages: u-boot-tools + Machine: Gemei G9 Tablet Kernel-Flavors: armmp Boot-Script-Path: /boot/boot.scr @@ -945,12 +952,20 @@ Required-Packages: u-boot-tools Machine: Marvell 8040 MACCHIATOBin +Machine: Marvell 8040 MACCHIATOBin Double-shot Machine: Marvell 8040 MACHIATOBin Kernel-Flavors: arm64 DTB-Id: marvell/armada-8040-mcbin.dtb Boot-Script-Path: /boot/boot.scr U-Boot-Script-Name: bootscr.uboot-generic Required-Packages: u-boot-tools + +Machine: Marvell 8040 MACCHIATOBin Single-shot +Kernel-Flavors: arm64 +DTB-Id: marvell/armada-8040-mcbin-singleshot.dtb +Boot-Script-Path: /boot/boot.scr +U-Boot-Script-Name: bootscr.uboot-generic +Required-Packages: u-boot-tools # Marvell dev board has different names depending on how it's booted, # via DTB or older ATAGS diff -Nru flash-kernel-3.98/debian/changelog flash-kernel-3.99/debian/changelog --- flash-kernel-3.98/debian/changelog 2019-04-04 14:38:42.0 -0700 +++ flash-kernel-3.99/debian/changelog 2019-05-24 18:36:25.0 -0700 @@ -1,3 +1,18 @@ +flash-kernel (3.99) unstable; urgency=medium + + [ Domenico Andreoli ] + * Add support for NanoPi NEO2 (Closes: #928861). + + [ Cyril Brulebois ] + * Remove Christian Perrier from Uploaders, with many thanks for all +his contributions over the years! (Closes: #927488) + + [ Heinrich Schuchardt ] + * Add Marvell 8040 MACCHIATOBin Double-shot and Single-shot. +(Closes: #928951) + + -- Vagrant Cascadian Fri, 24 May 2019 18:36:25 -0700 + flash-kernel (3.98) unstable; urgency=medium [ Vagrant Cascadian ] diff -Nru flash-kernel-3.98/debian/control flash-kernel-3.99/debian/control --- flash-kernel-3.98/debian/control2019-02-27 22:52:45.0 -0800 +++ flash-kernel-3.99/debian/control2019-05-12 14:42:39.0 -0700 @@ -2,8 +2,7 @@ Section: utils Priority: optional Maintainer: Debian Install System Team -Uploaders: Christian Perrier , - Vagrant Cascadian , +Uploaders: Vagrant Cascadian , Karsten Merker Build-Depends: debhelper (>= 9), devio, linux-base (>= 3.2), dash Standards-Version: 3.9.6 unblock flash-kernel/3.99 Thanks for considering! live well, vagrant signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Cyril Brulebois: > Hi, > > [...] >>> >>> unblock flash-kernel/3.99 > > No objections, thanks. > > > Cheers, > Unblocked, thanks. ~Niels--- End Message ---
Processed: Re: unblock: appstream/0.12.6-1
Processing commands for cont...@bugs.debian.org: > tags 924742 wontfix Bug #924742 [release.debian.org] unblock: appstream/0.12.6-1 Added tag(s) wontfix. > thanks Stopping processing here. Please contact me if you need assistance. -- 924742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924742 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#924742: marked as done (unblock: appstream/0.12.6-1)
Your message dated Thu, 30 May 2019 10:05:34 +0200 with message-id <08eb8014-d81c-7bed-b19c-2bfe6269f...@debian.org> and subject line Re: unblock: appstream/0.12.6-1 has caused the Debian Bug report #924742, regarding unblock: appstream/0.12.6-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.) -- 924742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924742 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org User: release.debian@packages.debian.org Usertags: unblock Dear Release Team, please consider unblocking appstream 0.12.6-1. This minor release contains just two changes[1], one adds a few new XML/YAML tags to the AppStream specification which allow releases to denote the location of source code as well as binaries for the respective release. The risk of breakage due to this feature is minimal. The other improves the search functionality of libappstream, which is the change I would really like to see in Buster. A full revamp of AppStream's fulltext search is planned for a future post-Buster release, but the changes in this release are already a major improvement and will help users find the things they are looking for in software centers included in Debian. Thank you for considering! Matthias Klumpp [1]: https://github.com/ximion/appstream/blob/master/NEWS#L5 unblock appstream/0.12.6-1 --- End Message --- --- Begin Message --- tags 924742 wontfix thanks Hi Matthias, On Sat, 16 Mar 2019 20:13:01 +0100 Matthias Klumpp wrote: > please consider unblocking appstream 0.12.6-1. > > This minor release contains just two changes[1], one adds a few new > XML/YAML tags to the AppStream specification which allow releases to > denote the location of source code as well as binaries for the > respective release. The risk of breakage due to this feature is > minimal. > The other improves the search functionality of libappstream, which is > the change I would really like to see in Buster. A full revamp of > AppStream's fulltext search is planned for a future post-Buster > release, but the changes in this release are already a major > improvement and will help users find the things they are looking for > in software centers included in Debian. > > Thank you for considering! > Matthias Klumpp I think it is fair to say that we won't be unblocking this for buster. The changes just came too late, don't meet the freeze policy and are too large to do a proper review for an exception. Paul signature.asc Description: OpenPGP digital signature --- End Message ---
Processed: Re: unblock: python-jwcrypto/0.6.0-1
Processing control commands: > tags -1 moreinfo Bug #927856 [release.debian.org] unblock: python-jwcrypto/0.6.0-1 Added tag(s) moreinfo. -- 927856: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927856 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#927856: unblock: python-jwcrypto/0.6.0-1
Control: tags -1 moreinfo Hi Timo, On Wed, 24 Apr 2019 11:06:36 +0300 Timo Aaltonen wrote: > Please unblock package python-jwcrypto > > The new upstream release is needed to fix: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925457 Can't we have a targeted fix for that issue? New upstream releases are typically not appropriate at this stage of the release. If not, I expect we'll just let the package be autoremoved from buster. Paul
Bug#929603: marked as done (unblock: webkit2gtk/2.24.2-1)
Your message dated Thu, 30 May 2019 09:51:42 +0200 with message-id <5f83019c-fbbc-fabe-d632-dcf757751...@debian.org> and subject line Re: Bug#929603: unblock: webkit2gtk/2.24.2-1 has caused the Debian Bug report #929603, regarding unblock: webkit2gtk/2.24.2-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.) -- 929603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929603 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: unblock Please unblock package webkit2gtk The new upstream stable release contains (among others) fixes for these three security bugs: CVE-2019-8595, CVE-2019-8607 and CVE-2019-8615. unblock webkit2gtk/2.24.2-1 -- System Information: Debian Release: 9.9 APT prefers stable-debug APT policy: (500, 'stable-debug'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-9-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Hi, On 30-05-2019 09:13, Moritz Muehlenhoff wrote: > On Thu, May 30, 2019 at 08:42:42AM +0200, Paul Gevers wrote: >> Just to get it clear, the security support of webkit2gtk in buster will >> be done by following upstream releases? Does this involve specific >> stable release branches? And this upload/unblock is the same what the >> security team would accept if we would already have released? > > Yep, that's the case. Thanks for confirming, unblocked. Paul signature.asc Description: OpenPGP digital signature --- End Message ---
Processed: Re: Bug#929108: unblock: gmsh/4.1.5+really4.1.3+ds1-1
Processing control commands: > tags -1 - moreinfo Bug #929108 [release.debian.org] unblock / tpu approval: gmsh/4.1.3+ds1-2 Removed tag(s) moreinfo. > retitle -1 unblock: gmsh/4.1.5+really4.1.3+ds1-1 Bug #929108 [release.debian.org] unblock / tpu approval: gmsh/4.1.3+ds1-2 Changed Bug title to 'unblock: gmsh/4.1.5+really4.1.3+ds1-1' from 'unblock / tpu approval: gmsh/4.1.3+ds1-2'. -- 929108: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929108 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#929108: unblock: gmsh/4.1.5+really4.1.3+ds1-1
Control: tags -1 - moreinfo Control: retitle -1 unblock: gmsh/4.1.5+really4.1.3+ds1-1 Ivo De Decker writes: > On Fri, May 17, 2019 at 11:12:59AM +0200, Ansgar Burchardt wrote: >> Do you prefer an upload via t-p-u or should I prepare a gmsh >> 4.1.5+really4.1.3+ds1-1 upload for unstable? > > An upload to unstable would be preferred. So please go ahead with that and > remove the moreinfo tag from this bug once it is in unstable. gmsh_4.1.5+really4.1.3+ds1-1 was uploaded to unstable yesterday. Ansgar
Bug#929603: unblock: webkit2gtk/2.24.2-1
On Thu, May 30, 2019 at 08:42:42AM +0200, Paul Gevers wrote: > Control: tags -1 moreinfo > > Hi Alberto, > > On Sun, 26 May 2019 23:08:03 +0200 Alberto Garcia wrote: > > Please unblock package webkit2gtk > > > > The new upstream stable release contains (among others) fixes > > for these three security bugs: CVE-2019-8595, CVE-2019-8607 and > > CVE-2019-8615. > > Just to get it clear, the security support of webkit2gtk in buster will > be done by following upstream releases? Does this involve specific > stable release branches? And this upload/unblock is the same what the > security team would accept if we would already have released? Yep, that's the case. Cheers, Moritz
