I uploaded now with 'dput --delayed=7 ftp-master *.changes' as it is
unlikely this will get any further review, nor need it as it is just a
regular new minor upstream release.
There is no tentative date at https://release.debian.org/ yet but at
least this will be in -proposed after this.
I uploaded now with 'dput --delayed=7 ftp-master *.changes' as it is
unlikely this will get any further review, nor need it as it is just a
regular new minor upstream release.
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: mari...@packages.debian.org
Control: affects -1 + src:galera-4
I propose that the latest minor maintenance version of Galera be included in the
oldstable release
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: mari...@packages.debian.org
Control: affects -1 + src:galera-4
I propose that the latest minor maintenance version of Galera be included in the
stable release update
Hi oldstable release managers,
I got email after my upload 11 days ago that 10.5.23 was accepted in
oldstable-proposed-updates but I don't see any updates under 'News' at
https://tracker.debian.org/pkg/mariadb-10.5 yet.
Is the update progressing automatically somewhere?
Package: release.debian.org
Followup-For: Bug #1057180
Control: retitle -1 bullseye-pu: package mariadb-10.5/1:10.5.23-0+deb11u1
Control: tags -1 -moreinfo
The MR at
https://salsa.debian.org/mariadb-team/mariadb-10.5/-/merge_requests/16
has been merged and is ready to proceed to upload.
##
As it is very unlikely to get changes anymore after 4+ weeks of
pending review, I uploaded it in the delayed 7 days queue.
Hi Debian security team!
MariaDB 1:10.11.6-1 entered Trixie only today after being stuck in
pending migration since Nov 28th from unstable. This
1:10.11.6-0+deb12u1 missed the point update window.
Are you OK if we proceed with this as a security upload?
Changes visible at
Uploading 10.11.6 to Bookworm should be done today but since autopkgtests
(mostly misc unrelated fails in LibreOffice) have been blocking the
migration from unstable to testing for past 10 days, uploading latest to
Bookworm would lead to a situation where Trixie has and older version
(10.11.5)
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
I propose that the latest version of MariaDB 10.5.23 be included in
the oldstable release update of Debian.
According to https://release.debian.org/ there is no planned point
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
I propose that the latest version of MariaDB 10.11.6 be included in
the stable release update of Debian.
I am filing this bug report for tracking purposes. The final version
and
Sure. Let me polish a bit the latest upload in unstable, and then I will
prepare suitable versions of latest Galera for both Bookworm, Bullseye and
others
Hi!
> That is the correct interpretation, but you missed the second half:
>
> > > You have the wrong version there though.
>
> That is a reference to:
>
> On Mon, Jul 24, 2023 at 10:09:30AM -0700, Otto Kekäläinen wrote:
> > On Mon, 24 Jul 2023 at 09:33, Jonatha
Hi!
> > I am ready to upload mariadb/1:10.11.4-0+deb12u2 as a source-only
> > upload with the requested changes[1] but I guess the previous
> > upload[2] needs to clear the NEW queue first, right?
>
> No, don't worry about that. You have the wrong version there though.
I interpreted this to mean
Release managers, please advise what you want me to do at this point.
On Tue, 25 Jul 2023 at 14:43, Otto Kekäläinen wrote:
>
> I am ready to upload mariadb/1:10.11.4-0+deb12u2 as a source-only
> upload with the requested changes[1] but I guess the previous
> upload[2] needs to c
I am ready to upload mariadb/1:10.11.4-0+deb12u2 as a source-only
upload with the requested changes[1] but I guess the previous
upload[2] needs to clear the NEW queue first, right?
[1]
Changes done and pending CI to validate that there are no unintended
side effects:
https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/52
On Mon, 24 Jul 2023 at 09:33, Jonathan Wiltshire wrote:
>
> There are two lintian warnings:
>
> W: debhelper-but-no-misc-depends mariadb-server-10.5
> W: transitional-package-not-oldlibs-optional database/optional
The version in unstable has intentionally no changes to ensure maximum
time of
OK, package pending approval in NEW now:
https://ftp-master.debian.org/new/mariadb_1:10.11.4-0+deb12u1.html
Hi!
I updated the changelog, tagged as
https://salsa.debian.org/mariadb-team/mariadb-server/-/commits/debian/1%2510.11.4-0+deb12u1
and uploaded binary packages as this will need to go via NEW queue.
However, it was rejected in NEW queue with error message:
mariadb_10.11.4-0+deb12u1.dsc:
Control: tag -1 moreinfo
Right, I will add this missing line to changelog:
* New upstream version 10.11.4. Includes fixes for several severe regressions,
see details at https://mariadb.com/kb/en/mariadb-10-11-4-release-notes/
(Same as unstable version in
Hi Jonathan!
Am I allowed to upload this?
On Thu, 13 Jul 2023 at 23:02, Otto Kekäläinen wrote:
>
> I propose that the latest version of MariaDB 10.11.4 be included in
> the upcoming stable release update of Debian. Package ready at
> https://salsa.debian.org/mariadb-team/ma
Beckmann ]
* Introduce transitional mariadb-server-10.5 (Closes: #1035949)
[ Otto Kekäläinen ]
* Duplicate selected Lintian overrides in old Lintian syntax for NEW queue
(this might strictly not be needed for bookworm but does not hurt either)
-- Otto Kekäläinen Thu, 13 Jul 2023 21
Hi!
Can you please grant permission to upload this to oldstable-proposed-updates?
Hi!
> That MR looks sane; please prepare a backport of 1:10.11.4-1 and send a
> confirmation source debdiff, and it can most likely be waved through.
Thanks for confirmation/guidance.
This is now on my TODO to be done immediately when I return from a
vacation trip in about a week.
Hi Adam!
Do you plan to still do a 11.8 release? (Mentioned on
https://release.debian.org/)
Should I abandon this or upload this to oldstable-proposed-updates?
- Otto
Hi!
Note that upstream released 10.11.4 today. Import preparation in
progress at
https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/50.
I plan to upload this to experimental tomorrow and eventually into
bookworm-pu if the release team approves.
- Otto
Package: release.debian.org
Severity: serious
Tags. bookworm
User: release.debian@packages.debian.org
Usertags: unblock
Control: affects -1 src:mariadb
This pre-unblock request is to get a decision from the Bookworm
release team if you prefer to have this Bug#1035949 fix:
a) in Bookworm in a
Status: I've sent requests for comments about
https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/45
this week to maintainer team mailing list and recent contributors and DDs
who have reported bugs in 2023.
I will wait for 6h more for opinions and then finalize the next upload
Hi!
> On 15-05-2023 07:55, Otto Kekäläinen wrote:
> > This pre-unblock request is to get a decision from the Bookworm
> > release team if you prefer to accept this 10.11.3 into Bookworm, or if
> > you wish it to be postponed to a stable update in Bookworm some time
> >
To summarize, the request is to revert these bugfixes:
* Upgrades from MySQL 5.7 to MariaDB 10.11 (MDEV-30483) (Closes: #866751)
* Add patch to fix cross-compilation failure on uca-dump (Closes: #1029165)
* Limit check of running mysqld/mariadbd to system users (Closes: #1032047)
* Fix man pages
, --workdir and
WORK_DIR in garb.conf which can be used to set the working
directory for garbd process, which helps to fix long standing
issue from 2015 (https://github.com/codership/galera/issues/313).
-- Otto Kekäläinen Sat, 15 Apr 2023 12:22:52 -0700
Debdiff attached
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Control: affects -1 src:mariadb
A new MariaDB 10.11 upstream minor maintenance 10.11.3 is pending at
https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/46
This
Thanks for the review. Can you please also look at commit log as it has
additional information and also commit-by-commit is easier to read?
I would argue that all the work done in Feb-March was targeted for Bookworm
and appropriate and low risk. As you can see in the Salsa project all
improvement
654)
-- Otto Kekäläinen Sat, 15 Apr 2023 12:50:35 -0700
± git diff --stat debian/1%10.5.19-0+deb11u1..bullseye
debian/changelog | 6 ++
debian/patches/mariadb-client-version-id.patch | 53
+
debian/patc
Hi!
Can you please list the commits you do not accept so I can revert them and
upload a 10.11.2-3 which you are then willing to approve?
I think it would be a huge miss if none of a month worth of bugfix work
would make into the release.
> I hope you realize that you're stretching it:
> 68 files changed, 11039 insertions(+), 404 deletions(-)
Yes, there are a lot of fixes. There was an extensive push to test and
polish everything from Feb to mid-March, resulting in 39 git commits.
However everything is purely about bug fixes,
parameters -w, --workdir and
WORK_DIR in garb.conf which can be used to set the working
directory for garbd process, which helps to fix long standing
issue from 2015 (https://github.com/codership/galera/issues/313).
-- Otto Kekäläinen Sat, 15 Apr 2023 12:14:05 -0700
Debdiff
mariadb (1:10.11.2-2) unstable; urgency=medium
.
[ Otto Kekäläinen ]
* SUMMARY: This version has a lot of bug fixes, quality fixes, documentation
and translation updates and it is tailored for the Debian 12 "Bookworm"
release and all potentially functional change
Hi!
Based on
https://packages.debian.org/search?keywords=mariadb-server=names=all=all
this 10.5.19-0+deb11u1 is still pending and a stable update of Debian
11 "Bullseye" has not yet been made in March 2023?
Is it OK if I merge in one regression fix and upload a new version?
> On Fri, 2023-02-17 at 08:00 -0800, Otto Kekäläinen wrote:
> > Can I proceed to upload MariaDB 10.5.19 to proposed stable updates?
>
> A week's a little early for a personal poke...
Page https://release.debian.org/ said mid-February so I was worried I
would miss the window if th
> On my daily updated system, I today saw this:
> The following NEW packages will be installed:
>libdbd-mariadb-perl
> The following packages have been kept back:
>mariadb-server
> The following packages will be upgraded:
>chromium chromium-common chromium-driver chromium-sandbox
>
Control: retitle -1 unblock: mariadb/1:10.11.2-1
MariaDB Foundation just announced 10.11.2 GA, so I uploaded 10.11.2 so
that Bookworm users will get the latest version. The old version
10.11.1-5 had been in unstable for only 1-2 days, so this move delayed
the process by 1-2 days as 'days in
Can I proceed to upload MariaDB 10.5.19 to proposed stable updates?
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Control: affects -1 + src:mariadb
Please unblock package mariadb (=10.11), so it can be included in
Debian Bookworm instead of previous mariadb-10.6 (=10.6).
[ Reason ]
MariaDB 10.11 is
On Mon, 5 Dec 2022 at 01:18, Utkarsh Gupta wrote:
>
> Hi Otto,
>
> On Mon, Dec 5, 2022 at 5:33 AM Otto Kekäläinen wrote:
> > I didn't get a reply to this, so asking again.
>
> I could take care of the upload but if you'd like to do that, please
> feel free t
> I assume there are no other changes in the new releases that might be
> relevant / interesting to users (and thus worthy of mentioning in the
> changelog)?
Misc bugfixes but nothing special to highlight, and nothing that is
known to fix any of the 5 bugs tracked at bugs.debian.org for
Hi Emilio!
I didn't get a reply to this, so asking again.
On Sun, 20 Nov 2022 at 17:57, Otto Kekäläinen wrote:
>
> Hello Emilio!
>
> MariaDB 1:10.3.37-0+deb10u1 is ready for upload at
> https://salsa.debian.org/mariadb-team/mariadb-10.3/-/commits/buster
>
> Do
Page https://release.debian.org/ says next stable update is mid-late
November. Are you OK if I upload this to bullseye?
- Otto
version 10.3.37.
-- Otto Kekäläinen Fri, 11 Nov 2022 20:54:48 -0800
This release does not (at least not yet) have any CVE tracked vulnerabilities.
I realize you might not be interested to include this in a LTS release
if there are no critical fixes to point out, but I decided to file
-27449
- CVE-2022-27451
- CVE-2022-27452
- CVE-2022-27455
- CVE-2022-27456
- CVE-2022-27457
- CVE-2022-27458
- CVE-2022-32083
- CVE-2022-32085
- CVE-2022-32086
- CVE-2022-32087
- CVE-2022-32088
-- Otto Kekäläinen Fri, 11 Nov 2022 18:33:01 -0800
Hi!
On Thu, Mar 17, 2022 at 4:09 AM Paul Gevers wrote:
..
> 2023-01-12 - Milestone 1 - Transition and toolchain freeze
> 2023-02-12 - Milestone 2 - Soft Freeze
> 2023-03-12 - Milestone 3 - Hard Freeze - for key packages and
> packages without
Hi Adam!
Could you please also approve upload of galera-4 and galera-3 to
Bullseye stable updates?
Thanks
/codership/documentation/blob/master/release-notes/release-notes-galera-26.4.10.txt
-- Otto Kekäläinen Wed, 02 Mar 2022 21:26:00 -0800
Debdiff attached. Created with commands:
git diff --stat debian/26.4.9-0+deb11u1..bullseye | xz >
26.4.11-0+deb11u1.debdiff.stat.xz
git diff debian/26.4.
/codership/documentation/blob/master/release-notes/release-notes-galera-25.3.35.txt
-- Otto Kekäläinen Wed, 02 Mar 2022 21:39:54 -0800
Debdiff attached. Created with commands:
git diff --stat debian/25.3.34-0+deb11u1..bullseye | xz >
25.3.36-0+deb11u1.debdiff.stat.xz
git diff debian/25.3.3
> > According to https://release.debian.org/ the next stable update is
> > due
> > in February. Please include this update to MariaDB.
> >
>
> That was the plan, yes. As you probably noticed, we're a little behind
> schedule
That's fine as long as it is just about a couple of weeks, and not
long
Package: release.debian.org
Currently mariadb-10.6 is blocked from migrating to testing due to
test failure in ruby-mysql2/0.5.3-3
Please consider adding a migration hint[1, 2] like:
force-skiptest ruby-mysql2/0.5.3-3
We are currently waiting for upstream ruby-mysql2 to make a new
release 0.5.4
Hi!
> Yes, please fix the situation in unstable/testing. It looks like 10.6
> isn't migrating because your reverse depends need fixing first (did you
> report that to the maintainers?); having 10.6 migrate would ease the
> situation a bit because then we can just remove 10.5. I think it would
Hey,
Next MariaDB for Bullseye release tracked in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000342
Status: the stable release team decided not to release the latest
MariaDB 10.5.13 even though it was prepared and uploaded for Bullseye.
Apparently on the grounds that Debian testing does
> When we were faced with a similar situation for 10.3 last year, we
> decided to proceed anyway as 10.5 was about to become the default
> version and 10.3 was then removed from unstable shortly afterwards.
True
> Looking at the current status of the 10.6 packages in unstable, it
> doesn't seem
MariaDB 10.6.5 has been uploaded to Sid and will replace 10.5 as soon as it
has the initial bugs weeded out and is same or better overall quality as
10.5.
> On Fri, 2021-11-26 at 22:32 -0800, Otto Kekäläinen wrote:
> > Thanks Paul for the schedule update. Maybe link those emails from
> > release.debian.org so that they are easy to find in the future..?
> >
The current text on https://release.debian.org/ is good, helps a lot
in
> > Before I submit the final debdiff and changelog I will wait for the
> > release date to show up at https://release.debian.org/
>
> Why? The longer you wait, the fewer changes you have to actually get the
> update
> into the next point release. It'd be better to send those debdiffs early and
>
> > mariadb-10.5 (1:10.5.13-0+deb11u1) bullseye; urgency=medium
> >
> >* New upstream version 10.5.13. Includes security fixes for:
> > - CVE-2021-35604
> >* Drop MIPS and libatomic patches applied now upstream
> >
> > -- Otto Kekäläinen
-35604
* Drop MIPS and libatomic patches applied now upstream
-- Otto Kekäläinen Sat, 20 Nov 2021 12:53:28 -0800
* Drop MIPS and libatomic patches applied now upstream
* Upstream issue MDEV-25114 about Galera WSREP invalid state
fixed (Closes: #989898)
-- Otto Kekäläinen Thu, 18 Nov 2021 20:26:21 -0800
Hello!
I uploaded this now: mariadb-10.3_10.3.31-0+deb10u1_source.changes
ACCEPTED into oldstable-proposed-updates->oldstable-new
Uploading without prior permissions is allowed according to
https://lists.debian.org/debian-devel-announce/2018/04/msg7.html
I will do the same for MariaDB 10.5
the latest version to Bullseye is important as the upstream
bugs might cause data loss or data to drift in the Galera cluster.
Changelog:
galera-4 (26.4.9-0+deb11u1) bullseye; urgency=medium
[ Otto Kekäläinen ]
* New upstream release 26.4.9. Includes multiple bug fixes, see
https://github.com
Control: retitle -1 buster-pu: package mariadb-10.3 10.3.31-0+deb10u1
New MariaDB 10.3.31 is out and it is also a security update. I'll take
this with the sec team since stable updates are not on the horizon
according to release.debian.org.
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package mariadb-10.5 to allow new upstream maintenance
release into Bullseye.
[ Motivation ]
The new upstream version 10.5.11 is a maintenance release that only
fixes bugs.
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package galera-3 to allow new upstream maintenance
release into Bullseye.
unblock: galera-3/25.3.33-1
[ Motivation ]
The new upstream version 25.3.33 is a maintenance
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu
I propose that the latest version of MariaDB 10.3.30 would be included
in the upcoming stable release update of Debian. Package is ready at
Hello!
> > Please unblock package galera-4 to fix MariaDB upgrade as reported in
> > #988089.
>
> I appreciate a fix for that bug, but did you really have to do that by
> uploading a new upstream release too? How is the new upstream release
> related to that bug?
Yes, the upstream package is a
There hasn't been any responses from release team to
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988255 in the past
week nor is there a release date for Debian 10.10 at
https://release.debian.org/
If the security team wants I can also target this as a security update
for Debian Buster?
-
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu
I propose that the latest version of MariaDB 10.3 (includes security
fixes) would be included in the upcoming stable release update of
Debian. Package is almost ready at
Ok, uploaded.
I don't guarantee that a machine currently running mariadb-server-10.3
and mariadb-server-10.3 binary packages in testing or unstable can
upgrade to the latest in Buster, since the Buster has been maintained
with upstream changes only, and the 10.3.x version in unstable has
also had
> As previously discussed, as things stand, in order to include this
> update in the point release we will also need to copy it to testing and
> unstable either during, or before, the point release, to avoid version
> skew.
This is outside the domain of my expertise, but just to be sure: there
adb-10.5
commits : 197
authors :
187 Otto Kekäläinen 94.9%
2 Christian Göttsche 1.0%
2 Helmut Grohne 1.0%
1 Aurelien Jarno 0.5%
1 Bastian Germann 0.5%
1 Christian Ehrhardt 0.5%
1 Daniel Black0.5%
1 Faustin Lammler 0.5%
> Well, my point was more that we already have buster > unstable, and
> that I was assuming you'd fix that by uploading a package to unstable,
> rather than an even newer package to buster. :-)
As MariaDB 10.5 is already in unstable, it is in practice impossible
to do any 10.3 uploads to unstable
Hello!
On Tue, 24 Nov 2020 at 21:08, Adam D. Barratt wrote:
..
> I see there's a mariadb-10.3 update in experimental (for 10.3.27).
> Based on the above, I assume that an upload to unstable is also
> planned?
No, that was an experiment which turned out to be a very stupid one
and I will no
> If you want to keep src:mariadb-10.3 around, one or the other. Or you
> could upload a new version of mariadb-10.3 which drops the package.
Ok, I will upload a new 10.3. I want it to stay around for a bit more
until the transition of 10.5 is fully completed and verified to
replace 10.3 in full.
> https://release.debian.org/britney/update_output.txt.gz says this;
>
> trying: mariadb-10.5
> skipped: mariadb-10.5 (1, 0, 30)
> got: 31+0: a-1:a-27:a-1:a-0:i-0:m-0:m-0:p-0:s-2
> * s390x: libmariadbclient-dev
>
> So, migrating mariadb-10.5 to testing would make libmariadbclient-dev
>
Hello!
> Could you please add some whitelist/override for debci so that at
> least the issue of "autopkgtest for mariadb-10.3/1:10.3.24-2" failing
> would go away [...]
I see you did this in https://release.debian.org/britney/hints/elbrus, thanks!
We also found a hack to get around the amrhf
Hello!
> To start with item 2:
>
> > 2) autopkgtest for mariadb-10.3/1:10.3.24-2 fail on i386 (and armhf
> > when it build earlier this month). The test is installing
> > "mariadb-server" which in unstable pulls in mariadb-10.5. I silenced
> > this false positive (or indifferent failure of access
Hello!
> > 1) Builds on armhf stopped working earlier this month due to compiler
> > bug #972564, perhaps in cmake or gcc. Upstream gcc has confirmed at
> > least one issue. There is no schedule on when it will be fixed and
> > there is nothing to my knowledge that I could reasonably do about
> >
Hello!
I kindly ask assistance from the Debian release team what to do about
MariaDB 10.5.
I have been working on MariaDB 10.5 packaging since August[1] and I've
had it in unstable since early September[2]. It is currently however
stuck on two migration excuses:
1) Builds on armhf stopped
.
-- Otto Kekäläinen Sat, 04 Jul 2020 15:31:51 +0300
Since the amendment is so small I will not attach a new debdiff.
Latest source always visible at
https://salsa.debian.org/mariadb-team/mariadb-10.3/-/tree/buster
Hi!
su 5. heinäk. 2020 klo 14.24 Adam D. Barratt
kirjoitti:
> On Sun, 2020-07-05 at 11:00 +0300, Otto Kekäläinen wrote:
> > For unstable the plan is to upload MariaDB 10.5 soon, and therefore
> > uploads of MariaDB 10.3 are already discontinued.
>
> How soon is "soon&q
For unstable the plan is to upload MariaDB 10.5 soon, and therefore
uploads of MariaDB 10.3 are already discontinued. Since we already
have MariaDB 10.4 in Debian experimental, it is not even possible to
do any uploads of MariaDB 10.3 because of triggering the NEW queue and
version
Control: tags -1 -moreinfo
> Tagging your bug "moreinfo" means that it's not ready for processing by
> SRM. Is that what you intended?
Thanks for a quick response. I just copied the previous stable update
email I've sent without realizing that it wasn't directly suited.
Sorry for the mistakes.
> tail: cannot open '/home/debci/.kodi/temp/kodi.log' for reading: No such file
> or directory
> tail: no files remaining
This is the only output in the test log, otherwise it is installing
packages and everything else seemed to go fine.
Test source says it just starts the app, but now it does
Ok, I will amend the changelog and re-upload today 1:10.3.22-0... to buster
updates.
Thanks for pointing out this mistake.
Unfortunately it was already uploaded. There are frequently releases to
unstable/testing so I don't expect this to cause any bigger problems.
Past and future changelog entries will not have this mistake.
Control: tags -1 -moreinfo
Control: severity -1 normal
Based on #950309 security updates don't seem to warrant 'serious', so
dropping to 'normal'.
Also removing tag moreinfo that was inherited from a stable update bug
report template. apparently it is not part of the process.
Hello!
MariaDB 10.3.20 is already out and I am in the process of preparing it..
> Some poking around on Github suggests that the fix is
> https://github.com/MariaDB/server/commit/47f8a18fec604983e47fdf7c822d94b26d85cade
>
> If this is actively breaking systems, couldn't we simply apply that
> patch to the current versions in stretch and buster, as a least-change
> option?
We
> [For reference, X-Debbugs-Cc is generally better than your mail client's
> CC when submitting bugs, as it means the recipient gets the mail from
> the BTS with the bug number included]
[rant] I'll try to remember, but this UI that is based on me
remembering all the option names and syntaxes (or
la 14. syysk. 2019 klo 16.57 Adam D. Barratt
(a...@adam-barratt.org.uk) kirjoitti:
>
> On Fri, 2019-09-13 at 21:10 +0300, Otto Kekäläinen wrote:
> > To clarify, 10.3.18 has been uploaded to Debian unstable. Issue is
> > still open for Buster and Stretch.
>
> Is the
> The cross-build changes aren't really appropriate for stable, but I'm
> going to ACK the whole and hope it works out.
Thanks!
All fixes are related to critical bugs or build failures, but true,
cross-build problems are not actually that relevant build problems. It
would be a pity to not have
commit b7529cdcab61f416e3fc003e42c50153475f1bd1 (HEAD -> buster, origin/buster)
Author: Otto Kekäläinen
Date: Tue Aug 27 23:52:54 2019 +0200
Amend changelog to surely include all changes since 1:10.3.15-1
diff --git a/debian/changelog b/debian/changelog
index 80556fc88..c0dfdf308 100
1 - 100 of 165 matches
Mail list logo
