Plus one to this initiative!
I also wanted to share the tip to use libfaketime as the easiest way
to test if a build or test suite works on an arbitrary future date. I
am currently testing that the MariaDB upstream test suite passes in
2037 and 2028 using libfaketime like this:
Hi!
So just to clarify, are you saying that a copy of
https://security.debian.org/debian-security/dists/buster/ will never
be archived at https://archive.debian.org/debian-security/dists/ like
previous releases have been so far?
This is not about getting *new security updates*, but purely a
Hi!
On Sun, 19 May 2024 at 20:48, Don Armstrong wrote:
>
> On Sun, 19 May 2024, Bill Allombert wrote:
> > Also debbugs is a special case:
> > The debbugs Debian package (as opposed to the debbugs software) have never
> > been
> > really maintained. I am actually one of the very few users of
Hi Simon!
> > A better approach would not treat Debian metadata as git data. Even the
> > most vocal advocate of switching everything to Salsa writes in his MR
> > that the changelog should not be touched in a commit, because it creates
> > conflicts, and instead a manual step will need to be
Hi!
> > If I am successful, then lintian can specialize its efforts into issues only
> > visible in packaged artifacts and thereby reduce it scope a bit.
>
> Perfect. I'd love to have some policy checking at "the right point in
> time". I'd love to support this but as far as I understand even
> > Ideally debbugs should be made non-native so that some else could
> > maintain the Debian package.
>
> I'm happy to review patches that get the 2.6 branch of debbugs in shape
> where it can be released into Debian again if someone wants to take that
> effort. I've just assumed that anyone
On Sat, 23 Mar 2024 at 01:32, Ansgar wrote:
>
> Hi,
>
> Debian 10 "buster" has moved to archive.debian.org in order to free
> space on the main mirror network. We plan to start removing files for
> non-LTS architectures in about two weeks; the existing Release files
> will then refer to no
Thanks for reply Jonas,
> > You could go to
> > https://salsa.debian.org/debbugs-team/debbugs/-/merge_requests/19 and
> > conduct a code review?
> >
> > You might discover that GitLab is useful and is not duplicating
> > Debbugs or anything else in Debian - it is currently the only platform
> >
> > My concern about Gitlab is not its *additions* to existing services, but
> > its *duplications* of core services already in Debian.
>
> I agree, that's the key problem.
I agree that duplication is bad - but I disagree that use of version
control duplicates the use of the Debian archive for
Hi Bill and Wookey!
In a recent long thread on debian-devel you had somewhat negative
sentiments towards the usefulness of Salsa. I do see you doing good
technical work for Debian and recently a MR from Bill too, so I was
thinking that maybe you will change your mind when you read more
in-depth
Hi!
ti 7. toukok. 2024 klo 23.01 Charles Plessy kirjoitti:
> Le Tue, May 07, 2024 at 08:17:31PM -0700, Otto Kekäläinen a écrit :
> >
> > Can you give me an example of a package you want to build and what is
> > the starting point, and I can tell you what command
Hi!
On Tue, 7 May 2024 at 15:27, Charles Plessy wrote:
..
> I want to leverage our cluster to automate as much of the rebuilds as I
> can, but could not find the right tool. I tried to run sbuild in a
> Singularity image and this failed. However, I do not need the whole
> power of engines like
Hi!
On Sat, 30 Mar 2024 at 14:32, Andrey Rakhmatullin wrote:
> On Sat, Mar 30, 2024 at 10:49:33AM +0200, Jonathan Carter wrote:
> > Another big question for me is whether I should really still
> > package/upload/etc from an unstable machine. It seems that it may be prudent
> > to consider it
Hi!
While reviewing xz-utils commits I noticed that a bunch of old
copyright holder names were removed in
https://salsa.debian.org/debian/xz-utils/-/commit/d1b67558cbc06c449a0ae7b7c1694e277aef4a78.
Is this OK to do so? Having source code in the public domain means
that there is no copyright, so
Hi!
pe 15. maalisk. 2024 klo 6.56 Fabian Grünbichler
kirjoitti:
> On Thu, Mar 14, 2024 at 10:03:57PM -0700, Otto Kekäläinen wrote:
> > Hi!
> >
> > Is anyone perhaps planning to fix cargo?
> >
> > For example curl isn't building on armel/armhf now and numerous
Hi!
Is anyone perhaps planning to fix cargo?
For example curl isn't building on armel/armhf now and numerous packages
that depend of curl are not building on armel/armhf.
Thanks in advance to the person who steps up.
Hi Benjamin!
You recently uploaded openssl 3.1.5-1.1.
Are you tracking the effect it had on reverse dependencies?
Do you have plans to do any follow-up uploads or +b1 rebuilds of other packages?
For example curl is unable to satisfy build dependencies on
armhf/armel at the moment:
Thanks Steve for uploading a fixed curl on Saturday. Just checking did you
notice amel/armhf are still not building due to secondary issues and n
dependencies?
https://buildd.debian.org/status/package.php?p=curl
> $ grep mariadb results/*
> results/results_dumped.txt:libmariadb-dev
> results/results_failed.txt:libmariadbd-dev
> results/results_none.txt:libmariadb-dev
> $
>
> There was nothing unintentional here. libmariadb-dev is clean wrt time_t.
> libmariadbd-dev failed to be analyzed because it has
> Re: Steve Langasek
> > Christoph Berg
> >postgresql-16 (U)
>
> Please do not upload postgresql-16 before I ack the diff.
>
> I'll also note that *ALL* nmu diffs I've seen so far are using the
> wrong version number in debian/changelog, missing the "~exp1" upload
> from the actual upload.
Hi!
> > It would be nice though if the version in Debian was newer :)
>
> I probably won't update it until it is suitable for inclusion in a
> stable release. This means at minimum being relatively safe to run in
> an untrusted source tree, probably by using debvm to generate a VM
> containing
Hi!
> Thats beginning to look like the history of check-all-the-things.
Yeah, I remember looking into cats some years back as a place to learn
what commands exist. Similarly I also occasionally browse
https://pre-commit.com/hooks.html.
The challenge with having all possible checkers is that they
> I looked into better tooling/editor support in general for Debian
> languages in general. I think the industry answer is that "someone"
> ought to build a "language (LSP) server" for the Debian languages, which
> would enable editors with LSP support[1] to get the same basic features.
True -
Hi!
Thanks for the tip, Niels!
It would be cool if dh_assistant had some kind of generic command like
"dh_assistant validate" which would attempt to introspect all
information silently and emit output only if it fails to parse
something. Additionally it could emit a non-zero exit code on errors.
Hi!
What editors and extensions are you using to augment your productivity
and minimize mistakes when editing debian/* files?
I am aware of dpkg-dev-el for Emacs mentioned in the DD reference[1].
I am a big fan of Pulsar[2] and recently found a 'language-debian'
plugin for Pulsar[3], but didn't
Package: wnpp
Severity: wishlist
Owner: Otto Kekäläinen
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: pulsar-edit
Version : 1.112.1
Upstream Contact: ad...@pulsar-edit.dev
* URL : https://pulsar-edit.dev/
* License : MIT
Programming Lang
Hi!
Is anybody aware if there is some kind of static analyzer for the
`debian/rules` file?
I can do very basic syntax checking with `make --dry-run
--makefile=debian/rules` which will error on serious syntax errors
(which I already implemented in my CI workflow[1]).
However, that or a general
Hi!
I've noticed that the most recent LLMs are actually very good at
finding information, summarizing and giving code examples about Debian
already without extra training. One just needs to double check that
the answer was correct to not fall for when they are simply making up
plausible sounding
Hi Abou!
I can't help with the issue at hand, but as general advice for the
future: if you had Salsa-CI enabled at
https://salsa.debian.org/pascal-team/fpc/-/pipelines the build-all and
build-any jobs would have probably caught this before upload.
Just open
> Paul already answered the lintian part, so I will skip that. But I also
> wanted to suggest looking into integrated spell-checking in your editor
> if possible. Having integrated spell-check will enable a much faster
> feedback loop.
Thanks the reply, but basic spell checking is pretty much
Hi!
Currently Lintian requires a (source or binary) package to check[1].
However, many of the Lintian source package checks (e.g. spelling of
debian/changelog entries) don't strictly depend on anything being built.
Is anyone aware of a way to run lintian directly on a debian/ directory
contents
> >> I finally fixed this. Sorry for the delay.
> >>
> >> https://udd.debian.org/lintian?packages=entr has a link for each lintian
> >> tag, that points to (e.g.)
> >> https://udd.debian.org/lintian-tag.cgi?tag=superfluous-file-pattern
> >> That page includes a description of the tag as well as
> > This issue still exists. I would now have the need to send the url
> > https://lintian.debian.org/tags/service-file-is-not-a-file to upstream
> > developers to learn about this Lintian issue, but the URL does not
> > serve any contents nor does it redirect to a new location.
> >
> > I am still
Hi!
On Wed, 27 Sept 2023 at 13:27, Lucas Nussbaum wrote:
>
> Hi,
>
> #1042428 is the bug for "no explanation for lintian tags on UDD"
>
> On 26/09/23 at 21:35 -0700, Otto Kekäläinen wrote:
> > I know Lintian tag info is available via command line, but I
> &
Hi!
Thanks for the context - so there is no need technical incompatibility
at play, but mostly a matter of having resources and time to do it.
..
> Regarding the 301 redirection I'll see with the interested parties (DSA
> and Lintian maintainers) if this option is fine with everyone.
I could
> > > > Host lintian.debian.org not found: 3(NXDOMAIN)
> > > >
> > > > is this expected ?
> > >
> > > Yes, it is replaced by the UDD interface:
> > >
> > > https://wiki.debian.org/Services/lintian.debian.org
The page above links to two bug reports but I can't find any actual
information about
Hi all!
I just wanted to share that the story about Salsa-CI was featured a
couple days ago at
https://about.gitlab.com/blog/2023/09/19/debian-customizes-ci-tooling-with-gitlab/
Personally I think Salsa-CI is extremely useful and pleasant to use
and understand, and it surely helped make Debian
> > > Host lintian.debian.org not found: 3(NXDOMAIN)
> > >
> > > is this expected ?
> >
> > Yes, it is replaced by the UDD interface:
> >
> > https://wiki.debian.org/Services/lintian.debian.org
> > https://udd.debian.org/lintian/
Could we please have a HTTP 301 redirect from lintian.debian.org to
(re-posting one more call for help as so far I am doing most the
packaging fixes alone)
Hi!
I just uploaded mariadb 1:10.11.2-2~exp1 into experimental. If nothing
surfaces, I will upload this to Debian unstable next weekend and it
will be the final version of MariaDB in Debian Bookworm.
If you
Hi!
On Thu, 23 Feb 2023 at 08:22, Otto Kekäläinen wrote:
>
> Hello!
>
> (Stop reading if you don't use MariaDB)
>
> I am currently preparing the upload of MariaDB 10.11.2-2 to Debian
> unstable and aim for the highest possible quality. I am currently
> doing the bulk of t
Hello!
(Stop reading if you don't use MariaDB)
I am currently preparing the upload of MariaDB 10.11.2-2 to Debian
unstable and aim for the highest possible quality. I am currently
doing the bulk of the testing and packaging alone and to make sure
that the quality is top notch, I would be glad to
> > About the execution of this change repository-wide:
> >
> > Is anyone working on feeding
> > https://salsa.debian.org/lintian/lintian/-/blob/master/data/fields/obsolete-packages
> > to https://janitor.debian.net/scrub-obsolete/ so that at least
> > Salsa-maintained packages would swiftly get
Hi!
On Wed, 18 Jan 2023 at 09:00, Andreas Metzler wrote:
>
> On 2023-01-18 Otto Kekäläinen wrote:
> > Lintian just started erroring on 'depends-on-obsolete-package
> > lsb-base' on many of my packages yesterday. There are no new uploads
> [...]
> > Does
Hi!
Lintian just started erroring on 'depends-on-obsolete-package
lsb-base' on many of my packages yesterday. There are no new uploads
of lsb-base recently and I did not find any news about this topic. The
Lintian page https://lintian.debian.org/tags/depends-on-obsolete-package
is only about the
Hi!
On Wed, 9 Nov 2022 at 01:08, Santiago Ruano Rincón
wrote:
> Aiming to reduce the space used in the salsa infrastructure by the
> salsa-ci artifacts, and to avoid exceeding the size limit in build jobs,
> we (Salsa CI Team) are planning to stop building dbgsym packages:
>
> > I think the answer to this should probably be established by the
> > libpam-tmpdir maintainer and documented first, for fear of someone else
> > later coming along and saying that the maintainer script incorrectly
> > ignores TMPDIR because we started ignoring it to resolve this bug. So I
> >
On Sat, Nov 27, 2021 at 5:30 AM Simon McVittie wrote:
>
> On Fri, 26 Nov 2021 at 22:10:45 -0800, Otto Kekäläinen wrote:
> > Lintian in Debian unstable has a new test that my package is failing on:
> > https://lintian.debian.org/tags/no-code-sections
>
> As with any Lintia
Hello!
Lintian in Debian unstable has a new test that my package is failing on:
https://lintian.debian.org/tags/no-code-sections
Can somebody who recently fixed this in their own package give some
advice how I should fix it for mariadb-10.6?
See example of Lintian error about libmariadbd.a in
Hello!
I noticed that Lintian has recently started erroring on
https://lintian.debian.org/tags/systemd-service-in-odd-location
I can't find this requirement anywhere in the Debian Policy, e.g.
https://www.debian.org/doc/debian-policy/ch-opersys.html#starting-system-services
does not mention
Hello!
The MariaDB Foundation is seeking to get a Debian expert to work for
them (plus if you are a DD). This is a great opportunity for Debian
people to land a job/contract where they can work full-time on open
source and with a big part of it related to Debian.
Check out:
Hello!
> For me, this whole situation seems wrong though. Why do you have
> versioned package names (mariadb-server-*) when they are all mutually
> exclusive with one another due to all shipping the same binary?
This is how the MySQL packaging has been structured for the past 10
years or so.
Hell!
On Sun, Apr 4, 2021 at 4:54 AM Andreas Metzler wrote:
>
> On 2021-04-03 Otto Kekäläinen wrote:
> > Hello!
>
> > In MariaDB we have over the years moved files around. A file that was first
> > in e.g. mariadb-server-10.3 might have been moved to
> > mariad
Hello!
In MariaDB we have over the years moved files around. A file that was first
in e.g. mariadb-server-10.3 might have been moved to
mariadb-server-core-10.3 and some years later to mariadb-client-core-10.5.
The result is a massive debian/control file with a lot of
Conflicts/Breaks/Replaces
Thanks David, using --with-sources is exactly what I needed.
As a starting point I have the *.deb I've built. In the same directory
I create a Packages file with:
apt-ftparchive packages . > ./Packages
Then I install using it:
apt install --with-source ./Packages -s mariadb-server mariadb-client
Hello!
I've noticed I've spent quite a lot of time debugging various
situations where the debian/control definitions for
depends/breaks/replaces/conflicts/provides are not optimal.
The waste of time is two-fold:
1) apt is not verbose enough
2) the cycle to rebuild/tests is too slow
As an
On Fri, 8 Jan 2021 at 04:01, Seth Arnold wrote:
>
> On Thu, Jan 07, 2021 at 11:02:24PM +0200, Otto Kekäläinen wrote:
> > Do you have any tips about generic command-line coloring programs?
>
> The bat package provides a batcat program that'll add colour to a lot of
> d
Hello!
Colorizing the command-line is an efficient way to make various output
more readable. In particular when browsing log files it helps hugely
if columns or certain key values are colorized.
For this type of use case there is ccze packaged in Debian[1].
Lesspipe[2] is also somewhat known. I
> So, if I understand well, if I have 3 MariaDB Buster nodes in a cluster,
> I just need to dist-upgrade them to Bullseye, and it will automagically
> just work and upgrade to Galera 4? If so, that's just great, because
> during our last discussion in Brazil, you told me about something a way
>
to 26. marrask. 2020 klo 18.45 Thomas Goirand kirjoitti:
> Hi Otto,
>
> On 11/26/20 4:44 PM, Otto Kekäläinen wrote:
> > Hello!
> >
> > MariaDB 10.5 release 1:10.5.8-3 finally entered Debian testing
> > today[1]. It has been in unstable since early September,
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%
Hello!
ma 8. kesäk. 2020 klo 12.04 Arturo Borrero Gonzalez
(art...@debian.org) kirjoitti:
>
> On 5/27/20 9:06 PM, Otto Kekäläinen wrote:
> > Hello!
> >
> > Do we have Debian devs here who have pimped their shell heavily with custom
> > prompts, colors, command line f
Hello!
Finalizing and publishing DEP-14 would be nice.
I have been using git-buildpackage for all of my packages for many years
already, and thus been automatically following these guidelines as they are
followed by git-buildpackage.
There are only two diversions I've noted:
- in
Hello!
> > Imagemagick in Debian is extremely outdated (6.9.10.23 vs 7.0.10-21),
> > causing some FTBFS on packages that depend on it.
..
> It doesn't need a one time NMU, but an additional 1-3 active maintainers.
> Failing that, we should rather drop it for bullseye.
Personally I prefer the
Hello!
Just my 2 cents: I hope Debian would not rush to any changes here.
Lets just stay neutral for now. The subject seems very US-centric and
there is a risk that it is creating division among people forcing them
to take sides on issues that previously were not political at all.
Here is some
Hi!
Thanks for all the tips! I have a long todo of programs to test out now.
One additional source of great Debian Developer wisdom about
command-line terminal app / interpreter / productivity is Jonathan
Carter's Debian Package of the Day YouTube videos:
Hello!
Do we have Debian devs here who have pimped their shell heavily with custom
prompts, colors, command line fonts, shell window title hacks, perhaps
using zsh etc? Have you written blogs about you experiences, can you share
some good reads (with screenshots) of what you have done?
I've read
>From
>https://janitor.debian.net/lintian-fixes/#i-dont-find-this-useful-how-do-i-stop-it
>I don’t find this useful. How do I stop it?
>If you ignore or close the first merge proposal, there won't be any more for
>the same maintainer.
>You can also just comment on the merge proposal that you
Hello!
Currently the project where I am closest to this goal is in
rdiff-backup. The upstream debian/ is almost 1:1 to the downstream
debian/. I've made a dh_gencontrol override to ensure the upstream CI
always builds binaries with the correct version number inherited from
a git tag in upstream:
Hello!
Thanks for all the examples (LXQt [where I looked at the sources of
lxqt-panel], git-remote-gcrypt, nbd, review, glibc).
Most interesting was perhaps Seans git-remote-gcrypt. You even have a
rpm spec file included which helps illustrate this is a true upstream
and not a fully native
Hi!
Thanks for the example. I see you even maintain the changelog in upstream:
https://git.notmuchmail.org/git?p=notmuch;a=blob;f=debian/changelog;h=4f7457cd7f588e6d3a821bf1530cc1f8742c8d6f;hb=refs/heads/master
But apparently "upstream" releases are decoupled from also bumping the
Debian
Hello!
I've ended up in being both the maintainer in Debian and an upstream
developer for a couple of packages and I have been fantasizing about
how to optimize my workflow so that I primarily fix all bugs and do QA
directly on the upstream development version (=upstream git master)
and then have
-cracklib-password-check mariadb-test mariadb-test-data
Architecture: source
Version: 1:10.3.22-1
Distribution: unstable
Urgency: medium
Maintainer: Debian MySQL Maintainers
Changed-By: Otto Kekäläinen
Description:
libmariadb-dev - MariaDB database development files
libmariadb-dev-compat - MariaDB
-cracklib-password-check mariadb-test mariadb-test-data
Architecture: source
Version: 1:10.3.21-2
Distribution: unstable
Urgency: medium
Maintainer: Debian MySQL Maintainers
Changed-By: Otto Kekäläinen
Description:
libmariadb-dev - MariaDB database development files
libmariadb-dev-compat - MariaDB
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 02 Jan 2020 10:20:27 +0200
Source: galera-4
Binary: galera-4 galera-arbitrator-4
Architecture: source
Version: 26.4.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian MySQL Maintainers
Changed-By: Otto Kekäläinen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 30 Dec 2019 11:56:34 +0200
Source: galera-4
Binary: galera-4 galera-arbitrator-4
Architecture: source amd64
Version: 26.4.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian MySQL Maintainers
Changed-By: Otto
Hello!
ti 31. jouluk. 2019 klo 14.55 Alexander Wirt (formo...@debian.org) kirjoitti:
> On Mon, 30 Dec 2019, Bernd Zeimetz wrote:
> > Also, if resources are an issue: I've offered several times to see if I
> > can get some k8s resources for gitlab runners, but never got a reply.
> > Not even a no.
Hello!
I've seen many times before statements like these so I'd like to raise
some discussion around the topic:
pe 13. syysk. 2019 klo 16.36 Bastian Blank (wa...@debian.org) kirjoitti:
> On Sun, Sep 08, 2019 at 05:35:10PM -0400, Sam Hartman wrote:
> > The Salsa CA pipeline is recommended.
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 22 Dec 2019 12:06:07 +0200
Source: galera-4
Binary: galera-4 galera-arbitrator-3
Architecture: source amd64
Version: 26.4.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian MySQL Maintainers
Changed-By: Otto
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 16 Dec 2019 21:32:17 +0200
Source: galera-3
Binary: galera-3 galera-arbitrator-3
Architecture: source
Version: 25.3.28-2
Distribution: unstable
Urgency: low
Maintainer: Debian MySQL Maintainers
Changed-By: Otto Kekäläinen
-cracklib-password-check mariadb-test mariadb-test-data
Architecture: source
Version: 1:10.3.21-1
Distribution: unstable
Urgency: low
Maintainer: Debian MySQL Maintainers
Changed-By: Otto Kekäläinen
Description:
libmariadb-dev - MariaDB database development files
libmariadb-dev-compat - MariaDB
-cracklib-password-check mariadb-test mariadb-test-data
Architecture: source
Version: 1:10.3.20-1
Distribution: unstable
Urgency: high
Maintainer: Debian MySQL Maintainers
Changed-By: Otto Kekäläinen
Description:
libmariadb-dev - MariaDB database development files
libmariadb-dev-compat - MariaDB
-cracklib-password-check mariadb-test mariadb-test-data
Architecture: source
Version: 1:10.3.19-1
Distribution: unstable
Urgency: high
Maintainer: Debian MySQL Maintainers
Changed-By: Otto Kekäläinen
Description:
libmariadb-dev - MariaDB database development files
libmariadb-dev-compat - MariaDB
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 26 Oct 2019 19:09:56 +0300
Source: entr
Binary: entr
Architecture: source
Version: 4.3-1
Distribution: unstable
Urgency: low
Maintainer: Yuri D'Elia
Changed-By: Otto Kekäläinen
Description:
entr - Run arbitrary
Hello!
It seems devscripts cannot be installed in Sid at the moment. I was
not able to find a bug report about this on bugs.debian.org and I
cannot follow up the dependencies on what package actually is stopping
it.
Anybody else experiencing this as well?
$ docker run -it debian:sid bash
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 16 Sep 2019 19:17:31 +0300
Source: galera-3
Binary: galera-3 galera-arbitrator-3
Architecture: source
Version: 25.3.28-1
Distribution: unstable
Urgency: medium
Maintainer: Debian MySQL Maintainers
Changed-By: Otto Kekäläinen
-cracklib-password-check mariadb-test mariadb-test-data
Architecture: source
Version: 1:10.3.18-1
Distribution: unstable
Urgency: medium
Maintainer: Debian MySQL Maintainers
Changed-By: Otto Kekäläinen
Description:
libmariadb-dev - MariaDB database development files
libmariadb-dev-compat - MariaDB
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 02 Aug 2019 21:01:40 +0100
Source: rdiff-backup
Binary: rdiff-backup
Architecture: source
Version: 1.3.3-1
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team
Changed-By: Otto Kekäläinen
-cracklib-password-check mariadb-test mariadb-test-data
Architecture: source
Version: 1:10.3.17-1
Distribution: unstable
Urgency: high
Maintainer: Debian MySQL Maintainers
Changed-By: Otto Kekäläinen
Description:
libmariadb-dev - MariaDB database development files
libmariadb-dev-compat - MariaDB
-Python-Version field
.
[ Otto Kekäläinen ]
* Add Salsa-CI for quality assurance
* Allow gbp to build from any branch so that merge requests etc can be built
* Organize control file with wrap-and-sort -a
* Mark Otto Kekäläinen as new Debian maintainer and developer
* Install bash
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 27 Jul 2019 16:33:43 -0300
Source: galera-3
Binary: galera-3 galera-arbitrator-3
Architecture: source
Version: 25.3.27-1
Distribution: unstable
Urgency: medium
Maintainer: Debian MySQL Maintainers
Changed-By: Otto Kekäläinen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 25 Jul 2019 14:11:56 -0300
Source: galera-3
Binary: galera-3 galera-arbitrator-3
Architecture: source
Version: 25.3.27-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian MySQL Maintainers
Changed-By: Otto
-cracklib-password-check mariadb-test mariadb-test-data
Architecture: source
Version: 1:10.3.16-1
Distribution: unstable
Urgency: medium
Maintainer: Debian MySQL Maintainers
Changed-By: Otto Kekäläinen
Description:
libmariadb-dev - MariaDB database development files
libmariadb-dev-compat - MariaDB
-cracklib-password-check mariadb-test mariadb-test-data
Architecture: source
Version: 1:10.3.15-2
Distribution: unstable
Urgency: medium
Maintainer: Debian MySQL Maintainers
Changed-By: Otto Kekäläinen
Description:
libmariadb-dev - MariaDB database development files
libmariadb-dev-compat - MariaDB
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 07 Jun 2019 09:49:57 +0300
Source: galera-3
Binary: galera-3 galera-arbitrator-3
Architecture: source
Version: 25.3.26-2~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian MySQL Maintainers
Changed-By: Otto
-cracklib-password-check mariadb-test mariadb-test-data
Architecture: source
Version: 1:10.3.15-1
Distribution: unstable
Urgency: high
Maintainer: Debian MySQL Maintainers
Changed-By: Otto Kekäläinen
Description:
libmariadb-dev - MariaDB database development files
libmariadb-dev-compat - MariaDB
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 23 Apr 2019 13:23:35 +0300
Source: galera-3
Binary: galera-3 galera-arbitrator-3
Architecture: source
Version: 25.3.26-1
Distribution: unstable
Urgency: medium
Maintainer: Debian MySQL Maintainers
Changed-By: Otto Kekäläinen
-cracklib-password-check mariadb-test mariadb-test-data
Architecture: source
Version: 1:10.3.14-1
Distribution: unstable
Urgency: medium
Maintainer: Debian MySQL Maintainers
Changed-By: Otto Kekäläinen
Description:
libmariadb-dev - MariaDB database development files
libmariadb-dev-compat - MariaDB
Hello!
Thanks everybody for the pointers. I fixed it now with:
Subject: [PATCH] Ensure cmake builds also apply CPPFLAGS flags for hardening
to fully work
---
debian/rules | 5 +
1 file changed, 5 insertions(+)
diff --git a/debian/rules b/debian/rules
index 3a16f8bfa..2e7536b9c 100755
---
So apparently the 'D_FORTIFY_SOURCE=2' is in CPPFLAGS (not read by
cmake) but not in CXXFLAGS (read by cmake)[1].
So maybe I should define?
CXXFLAGS=$(CXXFLAGS) $(CPPFLAGS)
This is the current state of mysqld, should I be happy with this or is
it relevant that all functions are protected?
Hello!
> > Is there any hardening flag / cmake expert around who could help me
> > get the hardening flags perfect in MariaDB 10.3?
> Start with https://wiki.debian.org/Hardening#Notes_for_packages_using_CMake
I've read this section many times over but I don't get it. A
workaround is presented
1 - 100 of 235 matches
Mail list logo
