[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#884109: marked as done (stretch-pu: package mariadb-10.1/10.1.29-0+deb9u1)

Your message dated Thu, 18 Apr 2019 17:49:32 +0100
with message-id <1555606172.2777.12.camel@adam-barratt.org.uk>
and subject line Re: Bug#884109: stretch-pu: package mariadb-10.1/10.1.29-0+deb9u1
has caused the Debian Bug report #884109,
regarding stretch-pu: package mariadb-10.1/10.1.29-0+deb9u1
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 owner@bugs.debian.org
immediately.)


-- 
884109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884109
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian.org@packages.debian.org
Usertags: pu

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hi,

this is stretch-pu for mariadb-10.1.29 upstream release and couple of
fixes that creeped in stretch version just before freeze.

Fixes:

* #875708 - Add libconfig-inifiles-perl to mariadb-client-10.1 depends to fix mytop

* Failing non-release archs were added to the list of architectures that are allowed
  to fail test

* mips64el was added to a list of other mips* platforms allowed to fail the tests

* I reverted upstream decision to use embedded pcre3 library as we
  need to fix #878107 and #876299 in jessie and stretch too

Upstream:

* There's couple of minor security fixes that doesn't warrant security
  update, but it should be updated nevertheless (this this pu request).

I'll send the debdiff in a reply to this email, so this message reaches the list.

Ondrej

- -- System Information:
Debian Release: buster/sid
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-3-amd64 (SMP w/6 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_DK.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-----BEGIN PGP SIGNATURE-----

iQKTBAEBCgB9FiEEw2Gx4wKVQ+vGJel9g3Kkd++uWcIFAloulIpfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEMz
NjFCMUUzMDI5NTQzRUJDNjI1RTk3RDgzNzJBNDc3RUZBRTU5QzIACgkQg3Kkd++u
WcKpxg/+MylyvOm6JEzVr6O7AEZzRAuKYgfB3ULZtHMGZnDdl47ddwCyRoqEckLE
UycZQnttMb/FZIF8GKibr+hoFWl8Va791aWtnsGziMsu9a7v3yplbjrsmjji0smZ
b9B56mLvN97BDVPgeMIj7G6HQRe2xM8+RZQ020zPIzy9hNN4LKb5egzohHAq0h8W
vnIrB8gc0wm5AckAvJ3aWCKBUkh4tdHvJO36vJMbjgbxw2FZxK4hOD9WYaFo3RxO
yr2fsLSGkpxN+Y1wG2uleSMEPUwp/grHMUS388qbZy1+Crqz/9ULBvKFkKAHAj73
ym80GC8Y1479sO+vQuR92YOxPO/h2U3sGd/KThEc1FmvKfL7B31NMq4m49nfSHPF
vvh4gO9IxcDFfs5B/USV44Zb+9NFBL3yD+xDH1lYsAKmH7yJ541453YmJsFYXS9X
ZkHgLziUhxK41smAqlwFvT4GluQXU2hTXtwFi3AZclI4kq+iQckNYa8Ek/XSY1Bw
R63tHGoAPnbDz8S7Cah++FRimVm17eJNZwVxESTOR9mvewxpVZp2Hyv2+d6TgQfa
o0l4Csx77JthKtStjGjfI7XlWNVwi08RTk2INQcrLEdEGXwJ3XNBsy/AYGmzeuWF
v8KIBBPC5n4urStCrGou7klOsPavIywMA3K2tQgFDUjPru1wZYg=
=+7ql
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message --- 
This has been superseded by #927223.

Regards,

Adam


On Mon, 2018-02-12 at 13:28 +0100, Ondřej Surý wrote:
> Hi KiBI,
> 
> > On 10 Feb 2018, at 10:52, Julien Cristau <jcristau@debian.org>
> > wrote:
> > 
> > Control: tag -1 moreinfo
> > 
> > Hi Ondřej,
> > 
> > On Mon, Dec 11, 2017 at 14:22:03 +0000, Ondřej Surý wrote:
> > 
> > > this is stretch-pu for mariadb-10.1.29 upstream release and
> > > couple of
> > > fixes that creeped in stretch version just before freeze.
> > > 
> > > Fixes:
> > > 
> > > * #875708 - Add libconfig-inifiles-perl to mariadb-client-10.1
> > > depends to fix mytop
> > > 
> > 
> > ok
> > 
> > > * Failing non-release archs were added to the list of
> > > architectures that are allowed
> > >  to fail test
> > > 
> > 
> > that doesn't sound necessary in stable?  harmless though, so
> > probably
> > ok.
> > 
> > > * mips64el was added to a list of other mips* platforms allowed
> > > to fail the tests
> > > 
> > 
> > That's a bit confusing, where did the mips64el binaries we do have
> > come
> > from if tests are expected to fail?
> 
> mips and mipsel has been on this list since 2015 (10.0.23-1 debian
> release) as upstream doesn’t guarantee that the tests will pass on
> this platform, so the change just rectifies the situation after
> mips64el was added to the release architecture list.
> 
> As a side note: There has been recent work to move the whole suite to
> the autopkgtest suite instead of running it as a part of build
> process, and fix any failing tests on non-major platforms in
> asynchronous manner.
> 
> > > * I reverted upstream decision to use embedded pcre3 library as
> > > we
> > >  need to fix #878107 and #876299 in jessie and stretch too
> > > 
> > 
> > Is there a plan for doing this?  I'm not seeing a pu request for
> > pcre3.
> 
> I already offered Matthew Vernon help with pcre3, but it’s not my
> place to request pu for other people packages. As far as I remember
> this affects only edge cases on edge architectures, but it was broken
> before anyway, so we are basically just keeping status quo.
> 
> > > Upstream:
> > > 
> > > * There's couple of minor security fixes that doesn't warrant
> > > security
> > >  update, but it should be updated nevertheless (this this pu
> > > request).
> > > 
> > > I'll send the debdiff in a reply to this email, so this message
> > > reaches the list.
> > > 
> > 
> > I'm seeing quite a bunch of patch noise, including dropping patch
> > descriptions (and authorship), which seems less than helpful.  Can
> > we
> > please not?
> 
> I switched to gbp pq for patch management as it makes it easier for
> me to manage
> the patches, but I can revert the most intrusive changes. Dropping
> the descriptions
> and authorship was not intended.
> 
> Ondřej
> --
> Ondřej Surý
> ondrej@sury.org
> 
>

--- End Message ---
Reply to: