Bug#961053: transition: mumps petsc slepc
No please enlighten me on my part in this please sir On Thu, May 21, 2020, 9:45 AM Sebastian Ramacher wrote: > Control: tags -1 + moreinfo > > Hi Drew > > On 2020-05-20 00:48:48 +0800, Drew Parsons wrote: > > Package: release.debian.org > > Severity: normal > > User: release.debian@packages.debian.org > > Usertags: transition > > > > I think the joint mumps 5.3.1 / petsc 3.13 / slepc 3.13 transition is > > ready to proceed. Packages seem well behaved in experimental. > > Did you test if the reverse dependencies build with the new mumps, petsc > and slepc stack? > > Cheers > -- > Sebastian Ramacher >
Bug#961514: buster-pu: package lirc/0.10.1-6.2~deb10u1
Call me 5045038792 On Mon, May 25, 2020, 7:45 AM Andreas Beckmann wrote: > Package: release.debian.org > Severity: normal > Tags: buster > User: release.debian@packages.debian.org > Usertags: pu > > Hi, > > I'd like to update lirc in buster to fix the conffile management > (conffiles were installed in dummy locations but not copied to the > proper locations). Now they are handled as proper conffiles. > I've tested several upgrade scenarios before uploading these changes to > sid. > This may cause dpkg prompting due to modified conffiles on upgrades, but > only if there are actually user modifications (i.e. the existing > configuration files (if any) do not match anything known to be shipped > in the past). > In order to get a clean upgrade path to bullseye, we need to be careful > with the version numbers (in .preinst and .maintscript). Therefore this > is a rebuild of the package in sid, but the two patches added in > unrelated uploads to sid are not relevant for Debian buster and are > disabled in the series file. > > The package is already uploaded. > > > Andreas >
Bug#961020: Updated debdiff for libexif/0.6.21-2+deb9u2
Call me 5045038792 On Mon, May 25, 2020, 6:21 AM Hugh McMaster wrote: > I've updated the debdiff for this release to include the changelog > entries for the sponsored upload. >
Bug#961019: Updated debdiff for libexif/0.6.21-5.1+deb10u2
Call me 5045038792 On Mon, May 25, 2020, 6:21 AM Hugh McMaster wrote: > I've updated the debdiff for this release to include the changelog > entries for the sponsored upload. > >
Bug#955211: release.debian.org: Transition r-base for 4.0.0
Call me 5045038792 On Sat, Mar 28, 2020, 7:57 AM Dirk Eddelbuettel wrote: > > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > X-Debbugs-Cc: debia...@lists.debian.org > > R 4.0.0 will be released on April 24. The upstream team always follows a > well-publicised scheduled which started yesterday with the first 'alpha' > release candidate, which I uploaded to experimental [1] > > R does change internals every now and then with the annual releases; this > is > a major one which will require rebuilds of all packages. > > The transition will be managed jointly by R package maintainer (myself) and > the Debian R Packages Team. Using the 'debian-r' list (as in the CC above) > is > an efficient way to reach everybody. We have managed similar transitions > before with R 3.4.0 and R 3.5.0. Note that last year's main release, R > 3.6.0, > did *not* require a rebuild hence the r-api-3.5 entry in the ben file > below. > > Ben file: > > > - > title = "r-base"; > is_affected = .depends ~ "r-api-3.5" | .depends ~ "r-api-4.0"; > is_good = .depends ~ "r-api-4.0"; > is_bad = .depends ~ "r-api-3.5"; > > - > > Special shoutout to Dylan and especially Graham for double-checking > required > steps here. > > Cheers, Dirk > > [1] https://packages.debian.org/source/experimental/r-base > > -- > http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org > >
Bug#961514: Info received (Bug#961514: buster-pu: package lirc/0.10.1-6.2~deb10u1)
Call me 5045038792
Bug#961019: Updated debdiff for libexif/0.6.21-5.1+deb10u2
Call me 5045038792 On Mon, May 25, 2020, 6:21 AM Hugh McMaster I've updated the debdiff for this release to include the changelog > entries for the sponsored upload. > >
Bug#894049: marked as done (transition: ncurses)
What stretch-pu ftp Masters to download the On Sun, May 31, 2020, 1:45 PM Debian Bug Tracking System < ow...@bugs.debian.org> wrote: > Your message dated Sun, 31 May 2020 20:29:18 +0200 > with message-id <7f60b78d-6907-a4f4-ce15-85a5ba234...@debian.org> > and subject line Re: Bug#894049: transition: ncurses > has caused the Debian Bug report #894049, > regarding transition: ncurses > 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.) > > > -- > 894049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894049 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > > > > -- Forwarded message -- > From: Sven Joachim > To: Debian Bug Tracking System > Cc: > Bcc: > Date: Sun, 25 Mar 2018 21:51:37 +0200 > Subject: transition: ncurses > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > > I would like to start a transition for ncurses, changing the soname of > the libraries from 5 to 6. This affects a large number of packages > (about 600 of them), but should be doable almost exclusively via > binNMUs, with two exceptions: > > - libcdk5 needs a sourceful upload and a rename of the library package, > neither this package nor its three reverse dependencies should be > rebuilt before that. Please see https://bugs.debian.org/892280 and > https://release.debian.org/transitions/html/auto-libcdk5.html. > > - cwidget also needs a sourceful upload and either a package rename or a > shlibs bump + versioned Breaks against aptitude, please see > https://bugs.debian.org/891161 for details. Fortunately both cwidget > and aptitude currently FTBFS with libncursesw6, so there is no danger > of incompatible combinations after binNMUs. > > The packages libtinfo5, libncurses5 and libncursesw5 are still built, so > only packages depending on the multilib packages and the udeb become > uninstallable and need to be rebuilt right away: grub, readline and > screen. > > Apart from cwidget/aptitude, I have not noticed any ncurses related > FTBFS bugs, and the API is unchanged. However, there will certainly be > quite a few unrelated FTBFS problems, such as the recent switch to > openjdk-9 and the python3.6/python3-distutils breakage. > > Suggested ben file (please check if it is correct): > > title = "ncurses"; > is_affected = .depends ~ > /\b(lib32ncurses6|lib32ncursesw6|lib32tinfo6|lib64ncurses6|lib64ncursesw6|lib64tinfo6|libncurses6|libncursesw6|libtinfo6|libtinfo6\-udeb|lib32ncurses5|lib32ncursesw5|lib32tinfo5|lib64ncurses5|lib64tinfo5|libncurses5|libncursesw5|libtinfo5|libtinfo5\-udeb)\b/; > is_good = .depends ~ > /\b(lib32ncurses6|lib32ncursesw6|lib32tinfo6|lib64ncurses6|lib64ncursesw6|lib64tinfo6|libncurses6|libncursesw6|libtinfo6|libtinfo6\-udeb)\b/; > is_bad = .depends ~ > /\b(lib32ncurses5|lib32ncursesw5|lib32tinfo5|lib64ncurses5|lib64tinfo5|libncurses5|libncursesw5|libtinfo5|libtinfo5\-udeb)\b/ > & ! .package ~ /\b(libncursesw5|libncurses5)\b/; > > Thanks for your consideration, > Sven > > > > -- Forwarded message -- > From: Paul Gevers > To: 894049-d...@bugs.debian.org, Sven Joachim > Cc: > Bcc: > Date: Sun, 31 May 2020 20:29:18 +0200 > Subject: Re: Bug#894049: transition: ncurses > Hi, > > On 12-09-2019 11:18, Paul Gevers wrote: > > Let's move this report a bit out of the way, but not close it as it > > isn't really finished. > > I think it's all done now. The last pieces of *this* transition are gone. > > Paul > >
Bug#962059: buster-pu: package python-markdown2/2.3.7-2
I need a company hand to reach out to me or if someone can point me in that direction ID aprecciated , Mark On Tue, Jun 2, 2020, 1:33 PM Pierre-Elliott Bécue wrote: > Package: release.debian.org > Severity: normal > Tags: buster > User: release.debian@packages.debian.org > Usertags: pu > > Dear Release Managers, > > I'd like to have python-markdown2 updated in Buster, due to a CVE: > CVE-2020-11888. > > I attached a debdiff with the bug report, and the update is the > simple adding of debian/patches/0001. > > I've also added a gbp.conf to have gbp stop complaining when I don't > give it the proper branch to build, this addition doesn't change the > binary packages. > > Note that I've uploaded python-markdown2 2.3.9-1 to unstable 15 minutes > ago. It ships the CVE fix, and should be visible in the archive soon. > > Thanks a lot for your work! :) > > -- System Information: > Debian Release: 10.4 > APT prefers stable > APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'unstable') > Architecture: amd64 (x86_64) > > Kernel: Linux 4.19.0-8-amd64 (SMP w/8 CPU cores) > Kernel taint flags: TAINT_USER > Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) (ignored: > LC_ALL set to fr_FR.UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) (ignored: > LC_ALL set to fr_FR.UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled >
Re: Processed: Re: Bug#962155: stretch-pu: package ca-certificates/20200601~deb9u1
Supposely supposed to be so called Debian Package Managers , telling me I'm on this Bug List from getting Debianized. If you know who I can get in touch with to get this straightened out. Id Appreciate it if you help me out. On Thu, Jun 4, 2020, 9:51 AM Debian Bug Tracking System < ow...@bugs.debian.org> wrote: > Processing control commands: > > > tags -1 + confirmed > Bug #962155 [release.debian.org] stretch-pu: package > ca-certificates/20200601~deb9u1 > Added tag(s) confirmed. > > -- > 962155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962155 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > >
Bug#963272: transition: ace
What transition? On Sun, Jun 21, 2020, 1:48 PM Sudip Mukherjee wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > > Hi, > > Small transition with only two affected packages: diagnostics, ivtools, > Both of them builds fine with ace 6.5.8+dfsg-1 version in experimental. > > The autogenerated ben tracker looks good. Please consider 'ace' for > transition. > Thanks in advance. > > -- > Regards > Sudip > >
Bug#947351: buster-pu: package cloud-init/20.2-2+deb10u1
Adam I'm not sure what's going on or whats my role role in Debian. Please if someone could tell me what is happening I deciphered Pubian on March 5 2020 I tried to send you a message from rhetoricb...@gmail.com and the profile says Pete Y. My emails are being erased so if you don't get this I'm not surprised but if you could you send a text or call 5045038792. Thank you, Mark Reddin On Wed, Jul 1, 2020 at 7:00 AM Adam D. Barratt wrote: > On Tue, 2020-06-30 at 17:45 -0700, Noah Meyerhans wrote: > > Control: retitile -1 buster-pu: package cloud-init/20.2-2+deb10u1 > > Control: tags + > > patch > > I'm not sure that tagging pu bugs "patch" makes much sense, fwiw. Any > pu bug that doesn't have a patch attached is by definition incomplete. > > > Let's try to finally get something done with this cloud-init update. > > The request is to update to upstream version 20.2 in buster. This > > version is currently in both testing and buster-backports. It has > > been tested by the cloud team and others in common cloud environments > > including Microsoft Azure, AWS, and OpenStack. It contains fixes for > > bugs including #936030, and implements support for the IMDSv2 API in > > Amazon EC2. > > > > It backports cleanly from testing to buster, with no changes beyond > > the debian/changelog update. > > Have the changes been tested on buster using this proposed package, or > just with the unstable/testing/backports versions? > > What does a binary debdiff between the current stable package and the > proposed package look like? > > > Full debdiff against buster's 18.3-6 is attached. > > fwiw, that debdiff was large enough (even compressed) that the mail > didn't make it to debian-release. > > +cloud-init (20.2-2+deb10u1) buster; urgency=medium > > The version needs to be /lower/ than the package in unstable, so a > backported version is 20.2-2~deb10u1, similarly to bpo. > > Regards, > > Adam > >
Bug#961843: buster-pu: package lighttpd/1.4.53-4
Will the team be able to make a apk Pubbian app for andriod . On Thu, Jul 2, 2020, 2:51 PM Adam D. Barratt wrote: > Control: tags -1 + moreinfo > > On Tue, 2020-06-02 at 09:16 +0200, Helmut Grohne wrote: > > Hi SRMs and Glenn, > > > > On Sat, May 30, 2020 at 04:44:34AM -0400, Glenn Strauss wrote: > > > Greetings! I am an upstream maintainer of lighttpd. > > > > > > Please accept this backport of important patches from > > > lighttpd 1.4.54 (released 2019.05.27) > > > lighttpd 1.4.55 (released 2020.01.31) > [...] > > Glenn, this is not a debdiff. What you attached the diff containing > > the > > debian directory. What was asked for is the output of the debdiff > > command for two source packages: > > > > debdiff lighttpd_1.4.53-4.dsc lighttpd_1.4.53-4+deb10u1.dsc > > > lighttpd_1.4.53-4+deb10u1.debdiff > [...] > > I'm attaching the correct debdiff now. > > There doesn't appear to have actually been an attachment here. > > Regards, > > Adam > >
Bug#961843: buster-pu: package lighttpd/1.4.53-4
&qf wzfr÷$aX111@×111XZRê pppxER Get Outlook for Android<https://aka.ms/ghei36> ____ From: R hertoric Sent: Friday, July 3, 2020 12:45:53 AM To: Adam D. Barratt ; 961...@bugs.debian.org <961...@bugs.debian.org> Cc: Helmut Grohne ; Glenn Strauss ; team+light...@tracker.debian.org Subject: Re: Bug#961843: buster-pu: package lighttpd/1.4.53-4 Will the team be able to make a apk Pubbian app for andriod . On Thu, Jul 2, 2020, 2:51 PM Adam D. Barratt mailto:a...@adam-barratt.org.uk>> wrote: Control: tags -1 + moreinfo On Tue, 2020-06-02 at 09:16 +0200, Helmut Grohne wrote: > Hi SRMs and Glenn, > > On Sat, May 30, 2020 at 04:44:34AM -0400, Glenn Strauss wrote: > > Greetings! I am an upstream maintainer of lighttpd. > > > > Please accept this backport of important patches from > > lighttpd 1.4.54 (released 2019.05.27) > > lighttpd 1.4.55 (released 2020.01.31) [...] > Glenn, this is not a debdiff. What you attached the diff containing > the > debian directory. What was asked for is the output of the debdiff > command for two source packages: > > debdiff lighttpd_1.4.53-4.dsc lighttpd_1.4.53-4+deb10u1.dsc > > lighttpd_1.4.53-4+deb10u1.debdiff [...] > I'm attaching the correct debdiff now. There doesn't appear to have actually been an attachment here. Regards, Adam
Bug#963792: transition: ros-*
Lilly kill all On Sat, Jun 27, 2020, 4:54 AM Jochen Sprickerhof wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > > Hi release team, > > I would like to transition these packages to unstable: > > ros-roscpp-core > ros-ros-comm > ros-geometric-shapes > ros-urdf > ros-interactive-markers > ros-actionlib > ros-geometry2 > ros-vision-opencv > > Would you be ok with doing all of them at the same time? > (Otherwise I would start with ros-roscpp-core.) > > The generated Ben files are ok. > > Cheers Jochen > > -- System Information: > Debian Release: bullseye/sid > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 5.7.0-1-amd64 (SMP w/8 CPU cores) > Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), > LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > >
Bug#964350: buster-pu: package intel-microcode/3.20200616.1~deb10u1
3.202006016.1~deb{9,10}u1{ፈርeeዝ}
On Sun, Jul 5, 2020, 3:48 PM Henrique de Moraes Holschuh
wrote:
> Package: release.debian.org
> Severity: normal
> Tags: buster
> User: release.debian@packages.debian.org
> Usertags: pu
>
> I'd like to update the intel-microcode packages in buster and stretch to
> 3.202006016.1~deb{9,10}u1.
>
> This is basically the same packages already in buster and stretch via
> buster/strech-security, with one extra microcode revert. It effectively
> fixes a regression introduced by the security updates for a single
> processor model (Xeon E3 with signature 0x506e3).
>
> The upload via s-p-u/os-p-u was suggested by the security team: we
> agreed the revert of microcode 0x506e3 did not really deserve a DSA and
> could be handled through the upcoming point releases (it affects only
> *some* motherboards with such processors).
>
> The git diff is attached. Unfortunately, stable debdiff gets mightly
> confused by a directory rename that only has binary files inside, so git
> diff does a much better job here.
>
> diffstat:
> changelog | 8 ++
> debian/changelog | 19
> intel-ucode/06-4e-03 | Bin 104448 -> 101376
> bytes
> intel-ucode/06-5e-03 | Bin 104448 -> 101376
> bytes
> microcode-20200609.d => microcode-20200616.d | 0
> releasenote| 32
> -
> s000406E3_m00C0_r00D6.fw | Bin 101376 -> 0 bytes
> bin => supplementary-ucode-20200616_BDX-ML.bin | 0
> 8 files changed, 32 insertions(+), 27 deletions(-)
>
> --
> Henrique Holschuh
>
Bug#964351: stretch-pu: package intel-microcode/3.20200616.1~deb9u1
Package intel-microcode} freeze{3.20200616.1~deb9u1
On Sun, Jul 5, 2020, 4:03 PM Adam D. Barratt
wrote:
> Control: tags -1 + confirmed
>
> On Sun, 2020-07-05 at 17:46 -0300, Henrique de Moraes Holschuh wrote:
> > I'd like to update the intel-microcode packages in buster and stretch
> > to 3.202006016.1~deb{9,10}u1.
> >
> > This is basically the same packages already in buster and stretch via
> > buster/strech-security, with one extra microcode revert. It
> > effectively fixes a regression introduced by the security updates for
> > a single processor model (Xeon E3 with signature 0x506e3).
> >
>
> Please go ahead.
>
> Regards,
>
> Adam
>
>
Re: Processed: Re: Bug#964350: buster-pu: package intel-microcode/3.20200616.1~deb10u1
Adam.D Barratt HAULT messages to > tags -1 + confirmed Bug #964350 [release.debian.org] buster-pu: package intel-microcode/3.20200616.1~deb10u1 Added tag(s) confirmed. On Sun, Jul 5, 2020, 4:03 PM Debian Bug Tracking System < ow...@bugs.debian.org> wrote: > Processing control commands: > > > tags -1 + confirmed > Bug #964350 [release.debian.org] buster-pu: package > intel-microcode/3.20200616.1~deb10u1 > Added tag(s) confirmed. > > -- > 964350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964350 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > >
Bug#964346: buster-pu: package wav2cdr/2.3.4-2+deb10u1
* Use C99 fixed-size integer types to fix runtime assertion on 64bit architectures other than amd64 and alpha. (Closes: #956927) * Stop linking to the dead Homepage Stop sending all packages thru broken 🔑 security needs to update tty On Sun, Jul 5, 2020, 3:24 PM Adrian Bunk wrote: > Package: release.debian.org > Severity: normal > Tags: buster > User: release.debian@packages.debian.org > Usertags: pu > > * Use C99 fixed-size integer types to fix runtime assertion on > 64bit architectures other than amd64 and alpha. (Closes: #956927) > * Stop linking to the dead Homepage. >
Re: Processed: Re: Bug#964350: buster-pu: package intel-microcode/3.20200616.1~deb10u1
On Sun, Jul 5, 2020, 4:03 PM Debian Bug Tracking System < ow...@bugs.debian.org> wrote: > Processing control commands: > > > tags -1 + confirmed > Bug #964350 [release.debian.org] buster-pu: package > intel-microcode/3.20200616.1~deb10u1 > Added tag(s) confirmed. > > -- > 964350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964350 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > >
Re: Processed: Re: Bug#962067: buster-pu: package dbus/1.12.20-0+deb10u1
On Sun, Jul 5, 2020, 7:27 AM Debian Bug Tracking System < ow...@bugs.debian.org> wrote: > Processing control commands: > > > retitle -1 buster-pu: package dbus/1.12.20-0+deb10u1 > Bug #962067 [release.debian.org] buster-pu: package dbus/1.12.18-0+deb10u1 > Changed Bug title to 'buster-pu: package dbus/1.12.20-0+deb10u1' from > 'buster-pu: package dbus/1.12.18-0+deb10u1'. > > -- > 962067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962067 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > >
Bug#963267: buster-pu: package multipath-tools/0.7.9-3+deb10u1
Id rather talk about call me 5045038792
On Sun, Jun 21, 2020, 11:57 AM Chris Hofstaedtler wrote:
> Package: release.debian.org
> Severity: normal
> Tags: buster
> User: release.debian@packages.debian.org
> Usertags: pu
>
> Dear Stable Release Managers,
>
> I'd like to push a fix for #959727 to buster. The bug causes us some
> trouble with block devices that are -sometimes- missing. I've tested
> the fix a while ago (on buster), and it seemed to help.
>
> Please consider this.
>
> Thanks,
> Chris
>
> diff -Nru multipath-tools-0.7.9/debian/changelog
> multipath-tools-0.7.9/debian/changelog
> --- multipath-tools-0.7.9/debian/changelog 2019-03-18
> 15:26:38.0 +
> +++ multipath-tools-0.7.9/debian/changelog 2020-06-21
> 16:41:48.0 +
> @@ -1,3 +1,9 @@
> +multipath-tools (0.7.9-3+deb10u1) buster; urgency=medium
> +
> + * [775fe68] kpartx: use correct path to partx in udev rule (Closes:
> #959727)
> +
> + -- Chris Hofstaedtler Sun, 21 Jun 2020 16:41:48 +
> +
> multipath-tools (0.7.9-3) unstable; urgency=medium
>
>* [51a7724] Reliably extract the running systemd version
> diff -Nru multipath-tools-0.7.9/debian/patches/partx-path.patch
> multipath-tools-0.7.9/debian/patches/partx-path.patch
> --- multipath-tools-0.7.9/debian/patches/partx-path.patch 1970-01-01
> 00:00:00.0 +
> +++ multipath-tools-0.7.9/debian/patches/partx-path.patch 2020-06-21
> 16:41:48.0 +
> @@ -0,0 +1,14 @@
> +Use Debian-specific path for partx (from util-linux).
> +
> +Index: multipath-tools/kpartx/del-part-nodes.rules
> +===
> +--- multipath-tools.orig/kpartx/del-part-nodes.rules
> multipath-tools/kpartx/del-part-nodes.rules
> +@@ -28,6 +28,6 @@ GOTO="end_del_part_nodes"
> + LABEL="del_part_nodes"
> + IMPORT{db}="DM_DEL_PART_NODES"
> + ENV{DM_DEL_PART_NODES}!="1", ENV{DM_DEL_PART_NODES}="1", \
> +- RUN+="/usr/sbin/partx -d --nr 1-1024 $env{DEVNAME}"
> ++ RUN+="/usr/bin/partx -d --nr 1-1024 $env{DEVNAME}"
> +
> + LABEL="end_del_part_nodes"
> diff -Nru multipath-tools-0.7.9/debian/patches/series
> multipath-tools-0.7.9/debian/patches/series
> --- multipath-tools-0.7.9/debian/patches/series 2019-02-08
> 13:38:26.0 +
> +++ multipath-tools-0.7.9/debian/patches/series 2020-06-21
> 16:41:48.0 +
> @@ -6,3 +6,4 @@
> fix-usrmerge-paths.patch
> 11-dm-mpath-fix-DM_UDEV_RULES_VSN-check.patch
> enable-cross-build.patch
> +partx-path.patch
>
>
Bug#964228: buster-pu: package nmap/7.70+dfsg1-6+deb10u1
> tags -1 + confirmed Bug #964350 [release.debian.org] buster-pu: package intel-microcode/3.20200616.1~deb10u1 Added tag(s) confirmed. On Fri, Jul 3, 2020, 4:24 PM Samuel Henrique wrote: > Package: release.debian.org > Severity: normal > Tags: buster > User: release.debian@packages.debian.org > Usertags: pu > > A backported upstream patch [0] is required to fix #940284 [1] on nmap; > Bug title: autogeneration of ssl key in ssl server mode of ncat is broken > > The issue itself is well described in both BTS [1] and the upstream > bug report [2], but the summary of it is that the openssl shipped with > Buster requires a key with minimum size of 2048b, while nmap 7.70 > generates one sized 1024b. This has been fixed in 7.80 (which is the > version on Testing right now). > > The debdiff is attached to this email, > > Thanks, > > [0] > https://github.com/nmap/nmap/commit/25db5fbb0d8fb88b6e7f4f298c862cd05ed0f8b1 > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940284 > [2] https://github.com/nmap/nmap/pull/1310 > > -- > Samuel Henrique >
Bug#964228: buster-pu: package nmap/7.70+dfsg1-6+deb10u1
Yes, it is correct. On Sun, Jul 5, 2020, 7:00 PM Samuel Henrique wrote: > Hello, I believe you picked the wrong bug id, could you double check that, > please? > > Thanks >
Bug#963267: buster-pu: package multipath-tools/0.7.9-3+deb10u1
Send reply to edre...@gmail.com
On Sun, Jun 21, 2020, 11:57 AM Chris Hofstaedtler wrote:
> Package: release.debian.org
> Severity: normal
> Tags: buster
> User: release.debian@packages.debian.org
> Usertags: pu
>
> Dear Stable Release Managers,
>
> I'd like to push a fix for #959727 to buster. The bug causes us some
> trouble with block devices that are -sometimes- missing. I've tested
> the fix a while ago (on buster), and it seemed to help.
>
> Please consider this.
>
> Thanks,
> Chris
>
> diff -Nru multipath-tools-0.7.9/debian/changelog
> multipath-tools-0.7.9/debian/changelog
> --- multipath-tools-0.7.9/debian/changelog 2019-03-18
> 15:26:38.0 +
> +++ multipath-tools-0.7.9/debian/changelog 2020-06-21
> 16:41:48.0 +
> @@ -1,3 +1,9 @@
> +multipath-tools (0.7.9-3+deb10u1) buster; urgency=medium
> +
> + * [775fe68] kpartx: use correct path to partx in udev rule (Closes:
> #959727)
> +
> + -- Chris Hofstaedtler Sun, 21 Jun 2020 16:41:48 +
> +
> multipath-tools (0.7.9-3) unstable; urgency=medium
>
>* [51a7724] Reliably extract the running systemd version
> diff -Nru multipath-tools-0.7.9/debian/patches/partx-path.patch
> multipath-tools-0.7.9/debian/patches/partx-path.patch
> --- multipath-tools-0.7.9/debian/patches/partx-path.patch 1970-01-01
> 00:00:00.0 +
> +++ multipath-tools-0.7.9/debian/patches/partx-path.patch 2020-06-21
> 16:41:48.0 +
> @@ -0,0 +1,14 @@
> +Use Debian-specific path for partx (from util-linux).
> +
> +Index: multipath-tools/kpartx/del-part-nodes.rules
> +===
> +--- multipath-tools.orig/kpartx/del-part-nodes.rules
> multipath-tools/kpartx/del-part-nodes.rules
> +@@ -28,6 +28,6 @@ GOTO="end_del_part_nodes"
> + LABEL="del_part_nodes"
> + IMPORT{db}="DM_DEL_PART_NODES"
> + ENV{DM_DEL_PART_NODES}!="1", ENV{DM_DEL_PART_NODES}="1", \
> +- RUN+="/usr/sbin/partx -d --nr 1-1024 $env{DEVNAME}"
> ++ RUN+="/usr/bin/partx -d --nr 1-1024 $env{DEVNAME}"
> +
> + LABEL="end_del_part_nodes"
> diff -Nru multipath-tools-0.7.9/debian/patches/series
> multipath-tools-0.7.9/debian/patches/series
> --- multipath-tools-0.7.9/debian/patches/series 2019-02-08
> 13:38:26.0 +
> +++ multipath-tools-0.7.9/debian/patches/series 2020-06-21
> 16:41:48.0 +
> @@ -6,3 +6,4 @@
> fix-usrmerge-paths.patch
> 11-dm-mpath-fix-DM_UDEV_RULES_VSN-check.patch
> enable-cross-build.patch
> +partx-path.patch
>
>
Bug#964351: stretch-pu: package intel-microcode/3.20200616.1~deb9u1
Freeze {diffstat:
changelog | 8 ++
debian/changelog | 19
intel-ucode/06-4e-03 | Bin 104448 -> 101376
bytes
intel-ucode/06-5e-03 | Bin 104448 -> 101376
bytes
microcode-20200609.d => microcode-20200616.d | 0
releasenote| 32
-
s000406E3_m00C0_r00D6.fw | Bin 101376 -> 0 bytes
bin => supplementary-ucode-20200616_BDX-ML.bin | 0
8 files changed, 32 insertions(+), 27 deletions(-)
On Sun, Jul 5, 2020, 3:51 PM Henrique de Moraes Holschuh
wrote:
> Package: release.debian.org
> Severity: normal
> Tags: stretch
> User: release.debian@packages.debian.org
> Usertags: pu
>
> I'd like to update the intel-microcode packages in buster and stretch to
> 3.202006016.1~deb{9,10}u1.
>
> This is basically the same packages already in buster and stretch via
> buster/strech-security, with one extra microcode revert. It effectively
> fixes a regression introduced by the security updates for a single
> processor model (Xeon E3 with signature 0x506e3).
>
> The upload via s-p-u/os-p-u was suggested by the security team: we
> agreed the revert of microcode 0x506e3 did not really deserve a DSA and
> could be handled through the upcoming point releases (it affects only
> *some* motherboards with such processors).
>
> The git diff is attached. Unfortunately, stable debdiff gets mightly
> confused by a directory rename that only has binary files inside, so git
> diff does a much better job here.
>
> diffstat:
> changelog | 8 ++
> debian/changelog | 19
> intel-ucode/06-4e-03 | Bin 104448 -> 101376
> bytes
> intel-ucode/06-5e-03 | Bin 104448 -> 101376
> bytes
> microcode-20200609.d => microcode-20200616.d | 0
> releasenote| 32
> -
> s000406E3_m00C0_r00D6.fw | Bin 101376 -> 0 bytes
> bin => supplementary-ucode-20200616_BDX-ML.bin | 0
> 8 files changed, 32 insertions(+), 27 deletions(-)
>
> --
> Henrique Holschuh
>
Bug#963703: 963703: gnutls28 3.5.8-5+deb9u5 flagged for acceptance
-- *From:* Adam D Barratt *Sent:* Friday, July 3, 2020 1:55:08 PM *To:* 963...@bugs.debian.org <963...@bugs.debian.org> *Cc:* 963703-submit...@bugs.debian.org <963703-submit...@bugs.debian.org> *Subject:* Bug#963703: gnutls28 3.5.8-5+deb9u5 flagged for acceptance package nnn.d...@debian.org tags 963703 = stretch pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: gnutls28 Version: 3.5.8-5+deb9u5 Explanation: fix memory corruption issue [CVE-2019-3829]; fix memory leak; add support for zero length session tickets, fix connection errors on TLS1.2 sessions to some hosting providers
Bug#963267: buster-pu: package multipath-tools/0.7.9-3+deb10u1
Control: tags -1 + confirmed d-i
On Sun, Jun 21, 2020, 11:57 AM Chris Hofstaedtler wrote:
> Package: release.debian.org
> Severity: normal
> Tags: buster
> User: release.debian@packages.debian.org
> Usertags: pu
>
> Dear Stable Release Managers,
>
> I'd like to push a fix for #959727 to buster. The bug causes us some
> trouble with block devices that are -sometimes- missing. I've tested
> the fix a while ago (on buster), and it seemed to help.
>
> Please consider this.
>
> Thanks,
> Chris
>
> diff -Nru multipath-tools-0.7.9/debian/changelog
> multipath-tools-0.7.9/debian/changelog
> --- multipath-tools-0.7.9/debian/changelog 2019-03-18
> 15:26:38.0 +
> +++ multipath-tools-0.7.9/debian/changelog 2020-06-21
> 16:41:48.0 +
> @@ -1,3 +1,9 @@
> +multipath-tools (0.7.9-3+deb10u1) buster; urgency=medium
> +
> + * [775fe68] kpartx: use correct path to partx in udev rule (Closes:
> #959727)
> +
> + -- Chris Hofstaedtler Sun, 21 Jun 2020 16:41:48 +
> +
> multipath-tools (0.7.9-3) unstable; urgency=medium
>
>* [51a7724] Reliably extract the running systemd version
> diff -Nru multipath-tools-0.7.9/debian/patches/partx-path.patch
> multipath-tools-0.7.9/debian/patches/partx-path.patch
> --- multipath-tools-0.7.9/debian/patches/partx-path.patch 1970-01-01
> 00:00:00.0 +
> +++ multipath-tools-0.7.9/debian/patches/partx-path.patch 2020-06-21
> 16:41:48.0 +
> @@ -0,0 +1,14 @@
> +Use Debian-specific path for partx (from util-linux).
> +
> +Index: multipath-tools/kpartx/del-part-nodes.rules
> +===
> +--- multipath-tools.orig/kpartx/del-part-nodes.rules
> multipath-tools/kpartx/del-part-nodes.rules
> +@@ -28,6 +28,6 @@ GOTO="end_del_part_nodes"
> + LABEL="del_part_nodes"
> + IMPORT{db}="DM_DEL_PART_NODES"
> + ENV{DM_DEL_PART_NODES}!="1", ENV{DM_DEL_PART_NODES}="1", \
> +- RUN+="/usr/sbin/partx -d --nr 1-1024 $env{DEVNAME}"
> ++ RUN+="/usr/bin/partx -d --nr 1-1024 $env{DEVNAME}"
> +
> + LABEL="end_del_part_nodes"
> diff -Nru multipath-tools-0.7.9/debian/patches/series
> multipath-tools-0.7.9/debian/patches/series
> --- multipath-tools-0.7.9/debian/patches/series 2019-02-08
> 13:38:26.0 +
> +++ multipath-tools-0.7.9/debian/patches/series 2020-06-21
> 16:41:48.0 +
> @@ -6,3 +6,4 @@
> fix-usrmerge-paths.patch
> 11-dm-mpath-fix-DM_UDEV_RULES_VSN-check.patch
> enable-cross-build.patch
> +partx-path.patch
>
>
Bug#964228: buster-pu: package nmap/7.70+dfsg1-6+deb10u1
Samuel Henrique do you know where backdoor is I believe you don't On Fri, Jul 3, 2020, 4:24 PM Samuel Henrique wrote: > Package: release.debian.org > Severity: normal > Tags: buster > User: release.debian@packages.debian.org > Usertags: pu > > A backported upstream patch [0] is required to fix #940284 [1] on nmap; > Bug title: autogeneration of ssl key in ssl server mode of ncat is broken > > The issue itself is well described in both BTS [1] and the upstream > bug report [2], but the summary of it is that the openssl shipped with > Buster requires a key with minimum size of 2048b, while nmap 7.70 > generates one sized 1024b. This has been fixed in 7.80 (which is the > version on Testing right now). > > The debdiff is attached to this email, > > Thanks, > > [0] > https://github.com/nmap/nmap/commit/25db5fbb0d8fb88b6e7f4f298c862cd05ed0f8b1 > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940284 > [2] https://github.com/nmap/nmap/pull/1310 > > -- > Samuel Henrique >
Re: Bug#964228: buster-pu: package nmap/7.70+dfsg1-6+deb10u1
Thank you On Tue, Jul 7, 2020, 1:24 PM Samuel Henrique wrote: > > Please go ahead. > > Thank you Adam, > > nmap_7.70+dfsg1-6+deb10u1_source.changes ACCEPTED into > proposed-updates->stable-new > > Regards, > > -- > Samuel Henrique > >
