Re: Salsa - best thing in Debian in recent years? (Re: finally end single-person maintainership)
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 this package > > and I tried several times to get the maintainers to do a new upload but they > > were clearly not interested. > > It's more that I'm prioritizing spending my (very) limited Debian time > on keeping bugs.debian.org and debbugs itself working (and [very slowly] > developing a new version of Debbugs with a more modern design in the > hopes that others will contribute.) Everyone else has very limited time to contribute to Debian as well. Therefore we all need to think about what is the most efficient workflow. Perhaps you could consider how you can be a force multiplier and scale your work? You could for example add some of the recent contributors as developers or maintainers at https://salsa.debian.org/groups/debbugs-team/-/group_members so they can review/merge/push code, and you could review all submissions at https://salsa.debian.org/debbugs-team/debbugs/-/merge_requests and grow those contributors into co-maintainers instead of just ignoring them? Perhaps you can also consider optimizing your git workflows? For example in the case of https://salsa.debian.org/debbugs-team/debbugs/-/merge_requests/19 you could have simply pressed "Merge" and everything would be good. Now you decided to not use any of the support Salsa/Salsa-CI provides, you did extra work to cherry-pick some commits (but not all), added your extra commit to break the build and now there is new follow-up work to be done for lapses that could have been easily avoided if Salsa-CI was enabled.. (I did submit MR!20 though, you can just merge it) I started this thread "Salsa - best thing in Debian in recent years?" by asking people who resist Salsa to at least try using it for a while before criticizing it so much. What happened in this episode is a case in point. You sit in a "local optima" of your current workflow and are not willing to invest a bit extra effort to get to a place where Salsa+Salsa-CI can benefit and decrease your extra work burden. Now both you and me ended up having to do extra work that could easily have been avoided.. Personally I like Salsa a lot, and collaboration with maintainers who embrace Salsa is a breeze, and I feel that my limited Debian time is relatively productive. That is all thanks to Salsa. I wish those who are not yet using it would give it a sincere try.
Re: finally end single-person maintainership
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 performed later. Not exactly, I said it is unnecessary work and doing it will just cause more work. Exact quote: "These commits have intentionally no debian/changelog updates as it causes every single rebase or cherry-pick of a commit to always have a merge conflict. It is much better to have all commits as-is, and then right before upload just run gbp-dch --auto to automatically generate the changelog." Thus better not to inject debian/changelog changes in every single patch and instead.. > > At the very least, GitLab integration would allow me to automate such a > > simple thing as changelog handling in a more comfortable way than > > displaying instructions how to download the conflicting branch into > > local git, resolve the conflicts manually, and force-push the branch to > > solve the problem. > > gbp dch --commit --release ..just let automation handle it, like Luca and many others already know. Personally I prefer the variant `gbp dch --verbose --auto --release` but essentially it does the same thing. Anyway, thanks Simon for doing a review on https://salsa.debian.org/debbugs-team/debbugs/-/merge_requests/19, at least I know you have tried using Salsa and are speaking from a point of some experience when criticising it (unlike apparently many others). Back on-topic of single-person maintainership - has anyone made a list of which packages have only *one* maintainer/git committer and are in the set of top-1000 or top-5000 Debian packages? We should perhaps ask those people why they don't have co-maintainership, and why they resist sharing the development work. Debbugs is one example - it has multiple open MRs and patches in the bug tracker but somehow the sole active maintainer does not see value in granting more people commit permissions. If we learn how these maintainers think, perhaps we can come up with a model to facilitate having more co-maintenance that can apply to the exact cases where co-maintenance is missing. - Otto
Re: Any volunteers for lintian co-maintenance?
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 your > suggestion does not spare the work of fixing lintian itself. The problem > that motivated me to my initial mail to ask for help on lintian was about > packaged artifacts and we need to keep an eye on this - no matter how nifty > things we do before. As somebody who has contributed to a bunch of Debian packaging tooling (Lintian, Deputy, git-buildpackage, Salsa-CI) I think Niels' approach makes a lot of sense. Deputy is great for static analysis of Debian packaging (i.e. are the files in debian/* syntactically and semantically correct). Lintian could over time remove those checks and focus only on analysing the build artifacts (as anyway Lintian can be run only _after_ the build was done). Yes, Lintian needs to continue to be maintained, but the maintenance work could be slightly less if Lintian adopts the strategy/architecture of focusing only on post-build artifact analysis. Regarding this discussion in general, I get the sense that participants haven't actually tried Debputy and are not aware of its capabilities. If you have Podman/Docker you can effortlessly run this little check to get some experience: cd my-package podman run --interactive --tty --rm --volume=$PWD:/tmp/my-package --workdir=/tmp/my-package debian:sid bash apt update && apt install -y dh-debputy python3-lsprotocol debputy lint Examples of output: pedantic: File: ./debian/changelog:944:82:944:89: Line exceeds 82 characters 944: - runtime-test-file-uses-supported-python-versions-without-python-all-build-depends informational: File: ./debian/control:64:19:64:24: Latest Standards-Version is 4.7.0 64: Standards-Version: 4.6.2
Re: Salsa - best thing in Debian in recent years? (Re: finally end single-person maintainership)
> > 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 using that package was running > unstable or running debbugs out of git. I did not notice the release_2.6 branch before. What is the intent with that branch? Do you want people to submit patches targeting 'master' or 'release_2.6'? How often do you plan to merge it to or from 'master'? The 'master' branch is still the default branch. The https://salsa.debian.org/debbugs-team/debbugs/-/blob/master/README.md does not mention anything about release_2.6. Should it? I am a big fan of READMEs and recommend using them to convey guidance to contributors (assuming you want to have contributors).
Re: Debian 10 "buster" moved to archive.debian.org
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 longer existing files on the main mirror network. > > An exception is the security archive (which already has no non-LTS > architectures): we will only archive it after LTS support ended. Would it be feasible to mirror the security section to archive.debian.org as well? As of today for example if one uses Buster on armhf one needs to have the repos pointing to archive.debian.org but security still pointing to deb.debian.org, which is confusing. It would be simpler for systems that still have Buster could switch to archive.debian.org in one go and not have to do it twice (once for main, and later for security). Err:3 http://archive.debian.org/debian-security buster/updates Release 404 Not Found [IP: 151.101.194.132 80] Err:4 http://deb.debian.org/debian buster/main armel Packages 404 Not Found [IP: 151.101.162.132 80] Err:5 http://deb.debian.org/debian buster-updates/main armel Packages 404 Not Found [IP: 151.101.162.132 80]
Re: Salsa - best thing in Debian in recent years? (Re: finally end single-person maintainership)
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 > > to conduct code reviews on in a way that has automatic testing and > > comment-response-resolved -tracking. Doing code reviews patches > > attached in email does not have that. > > > > If you try it out, and still think Salsa is bad for Debian, then I am > > more willing to accept your stanze. > > But it *is* duplicating Debbugs: None of your valuable contributions > posted as part of your code review appears on Debbugs. Actually some of them are in Debbugs as patches, but hard to find as there are 200+ open bugs. However, the bugs.debian.org system does not offer code testing or review facilitation. Again, I invite you to test out https://salsa.debian.org/debbugs-team/debbugs/-/merge_requests/19 for _code review_ for the same reason I stated above.
Re: Salsa - best thing in Debian in recent years? (Re: finally end single-person maintainership)
> > 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 source code storage, or that use of GitLab for code reviews would duplicate Debbugs. > > ...instead of lumping all those discussions into a discussion of ease of > > user interface for a single catch-all code forge that maybe make all those > > other complications go away by affecting all those questions and that way > > implicitly provides *some* answer to them all. > > Also, there is a difference between ease of use and intuitivity. GitLab > does not provide any tools that really make packaging easier. It is > initially more accessible to non-maintainers, because of familiarity, > but actual work happens outside of it. Would you be kind and try to understand the opposing viewpoint by trying it for one day? 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 to conduct code reviews on in a way that has automatic testing and comment-response-resolved -tracking. Doing code reviews patches attached in email does not have that. If you try it out, and still think Salsa is bad for Debian, then I am more willing to accept your stanze. - Otto
Salsa - best thing in Debian in recent years? (Re: finally end single-person maintainership)
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 arguments. This is my attempt to have you think about Salsa in a new light: On Tue, 9 Apr 2024 at 11:41, Bill Allombert wrote: > Having a repository on salsa or even "packaging team" does not prevent > a lack of maintainer, so this is not relevant. > Without a maintainer, no contribution will be merged in any case. Consider this Merge Request to fix debbugs builds immediately, and to include Salsa-CI to keep the build from regressing again: https://salsa.debian.org/debbugs-team/debbugs/-/merge_requests/19 1. If the package was not on git and Salsa, I would have no way to see what the maintainers have been doing in the years 2018-2023 (Debian repos had last upload in 2018) 2. If the package was not on Salsa, and had the MR feature active, I would not be able to submit a MR to fix the issues. Now the MR is up there, and anybody can review and comment it - thus we are not even dependent on the original maintainers alone. 3. The UI is easy and useful. I invite you to read my MR and add your review. I made have some extra instructions to make this very welcoming for people who do not "like" Salsa/GitLab and might feel that something is unintuitive 4. If you don't want to use the web UI, you can also download my patch https://salsa.debian.org/debbugs-team/debbugs/-/merge_requests/19.patch and review by email. Or you can click in the UI once to subscribe the MR and then continue review/comments by email. Personally I fully agree with the people stating that "Salsa is the best thing in Debian in the past 20 years". So far everyone I talked to who initially had reservations regarding using Salsa have started liking it after they learned a bit more how it works, and have seen things like Salsa-CI in action saving the Debian archive from needless widespread failures. Thanks, Otto
Re: Tool to build Debian packages not requiring root in containers ?
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 to issue to > > https://salsa.debian.org/otto/debcraft to achieve it? > > > > It supports running Podman in user mode (=no root permissions needed), > > Hi Otto, > > it looks really great! > > Do you think you can make it work with Singularity/Apptainer instead of > Podman? Our cluster runs only singularity 3.5.2 > (https://docs.sylabs.io/guides/3.5/user-guide/). Debian has version > 4.1.2 in the singularity-container package. > > The conversion of a Docker container to the Singularity format is > simple, and Singularity already mounts most of the local storage to make > it visible and writable from within the container. > I read the docs on how Singularity is able to pull Docker images of Debian Sid and build on top of them, and run and exec just like Docker/Podman. Unfortunately it has its own Containerfile format ( https://docs.sylabs.io/guides/3.5/user-guide/quick_start.html#singularity-definition-files) and the commands have their own syntax. I guess Debcraft could be extended to support it, but that would require at least one Singularity user as frequent contributor to test and develop Singularity-compatibility. The entire code base is shell code. Perhaps you want to take a look if it looks hackable for you?
Re: Tool to build Debian packages not requiring root in containers ?
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 sbuild, as none of the packages involved require > root priviledges to build. > > Do you have a suggestion for a tool can run in user mode in a container > image having access to local storage on the host, and that given a > Debian source control file will download the dependencies and build the > package ? 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 to issue to https://salsa.debian.org/otto/debcraft to achieve it? It supports running Podman in user mode (=no root permissions needed), it loop-mounts a local directory (local storage), creates clean build containers on the fly similar to sbuild but is much easier and faster to use. Example of how to build one of your packages with just pointing it at the source git repo: $ debcraft build https://salsa.debian.org/med-team/altree.git Building container 'debcraft-debian-sid' in '/tmp/tmp.brCZRhn2lL/debcraft-container' for downloader use mkdir: created directory '/tmp/tmp.brCZRhn2lL/debcraft-container' STEP 1/10: FROM debian:sid ... $ ls -1 debcraft-build-altree-1715137513.a8c999a+master altree_1.3.2-2_amd64.build altree_1.3.2-2_amd64.buildinfo altree_1.3.2-2_amd64.changes altree_1.3.2-2_amd64.deb altree-dbgsym_1.3.2-2_amd64.deb altree-examples_1.3.2-2_all.deb control.log filelist.log lintian.log First build is a bit slow as it needs to download all the dependencies and create a container, but the second run of 'debcraft build' inside the source directory will be very fast as all container cache is reused.
Re: xz backdoor
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 best practice to work from stable machines where any private > > keys are involved. For me it's just been so convenient to use unstable > > because it helps track changes that affect my users by the time it hits > > stable and also find bugs early that I care about, but perhaps I just need > > to make that adjustment and find more efficient ways to track unstable > > (perhaps on additional machines / VMs / etc). Not sure how other DDs think > > about this, but I'm also curious how they will deal with this, because > > there's near to no filter between unstable and the outside world, and this > > is probably not the last time someone will try something like this. > For me it's simple: if I'm forced to run my tools not on the host but in > some kind of inconvenient VM/chroot/whatever, I'll just stop contributing. I am doing all my builds inside a (Podman) container with the sources loop-mounted. Thus I can use git and visual code editor directly on sources with full access, but when the build runs, it is fully inside a container that has no host access nor even network access. To achieve this I wrote a tool which you might want to check out: https://salsa.debian.org/otto/debcraft
Is it allowed to remove attribution in public domain "licensed" source code? (and pondering about ftp-level reviews)
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 no attribution required either? But if copyright attribution is done, each name should have a year next to it at least, right? Is it so that the debian/copyright file is reviewed by ftp-masters only for packages in NEW queue, and there is probably no automation in place to flag subsequent copyright changes for re-review? Pondering off-topic: I don't expect ftp-masters to have bandwidth to do manually anything more, so I am specifically keen to understand what automation is in place. Some improvements can be done in Salsa-CI for things that the maintainer is likely to be interested in fixing themselves (e.g. [1], [2]) but the most critical checks for copyright changes and supply-chain changes related to who is the uploader or what is the upstream homepage/repository address could perhaps have some mechanism at ftp-level that requires review/sign-off by additional Debian Developers, perhaps via a new review tool. - Otto [1] https://salsa.debian.org/salsa-ci-team/pipeline/-/issues/342 (missing git tags after upload) [2] https://salsa.debian.org/salsa-ci-team/pipeline/-/issues/343 (misconfigured upstream git branches)
Re: 64-bit time_t transition: cargo needs manual intervention
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 packages > > that depend of curl are not building on armel/armhf. > > > > Thanks in advance to the person who steps up. > > see the (linked) t64 transition bug: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036884#197 That link doesn't answer my question. The link is to bug report summarizing that cargo is broken and suggesting it needs to be re-bootstrapped. Currently we haven't seen anybody step up to do it. I would be very grateful if somebody with enough expertise would be available to do it and thus help resolve the whole chain of broken builds. > >
Re: 64-bit time_t transition: cargo needs manual intervention
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.
openssl 3.1.5-1.1 effect on reverse dependencies
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: https://buildd.debian.org/status/package.php?p=curl=sid curl build-depends on: - libssl-dev:armhf libssl-dev depends on: - libssl3t64:armhf (= 3.1.5-1.1) curl build-depends on: - libssl-dev:armhf libssl-dev depends on: - libssl3t64:armhf (= 3.1.5-1.1) libssl3t64 depends on: - libssl3t64 conflicts with: - libssl3:armhf (< 3.1.5-1.1)
Re: time_t transition and bugs
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
Re: postgresql-16; wrong NMU versions (Re: 64-bit time_t transition in progress)
> $ 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 header ordering > requirements which did not get resolved. > > https://adrien.dcln.fr/misc/armhf-time_t/2024-02-03T09:18:00/logs/libmariadbd-dev/base/log.txt > > Much better that there be a library transition only for the lesser-used > library! Ok, good. Thanks for the clarification!
Re: postgresql-16; wrong NMU versions (Re: 64-bit time_t transition in progress)
> 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. I've imported some nmu diffs into the > packaging gits, and now everything is wrong. +1 for MariaDB for the above. Also I think the package name change was done for the wrong package, it should probably have been done for libmariadb3 and not for libmariabd19. apt-cache rdepends --no-recommends --no-suggests libmariadb3 = 120 packages vs zero packages using libmariadbd (that library is useful mostly for embedded systems doing custom binaries) I am ready to update/finalize the name change myself (draft at https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/68) if I get a reply from Graham on how you wish to proceed with this.
Re: Editor extensions to help editing debian/* files?
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 the relevant tools and running the tools in the VM. As it happens, I have been writing this tool[1] that runs all builds and tests inside a container, and check-all-the-things would be a perfect match to be wrapped by the command 'debcraft validate' that mounts sources inside a throwaway container.. ;) https://salsa.debian.org/otto/debcraft
Re: Editor extensions to help editing debian/* files?
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 create a lot of noise and managing the false positives end up being a lot of work. Not suitable for daily use, but I will probably use cats for "annual checkups" on stuff I maintain. It would be nice though if the version in Debian was newer :) Since https://tracker.debian.org/pkg/check-all-the-things lacks a working git and homepage link, you guys should probably do a new upload to Debian. By the way, I submitted some small fixes at https://github.com/collab-qa/check-all-the-things/pulls.
Re: Editor extensions to help editing debian/* files?
> 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 - LSPs is the common API into linters (and more) nowadays, but I was ready to settle with something simpler, as building a LSP for Debian I imagine is a lot of work.. .. > I might have a stab at writing a prototype for a LSP for Debian formats. ..however, if you start doing a minimal prototype it would be a great! Who knows if the LSP some day in the future would forward snippets to a Debian-specific LLM that would give hints on what needs to be changed to conform to the Debian policy :)
Re: Editor extensions to help editing debian/* files?
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.
I tested your latest command and it works as you expected, though it
does not use exit code.
# dh_assistant detect-unknown-hook-targets
The hook target override_dh_car_configure in debian/rules does not
seem to match any known commands.
# echo $?
0
Also if the JSON included the filename and line number of the finding
it would be handy:
{
"unknown-hook-targets": [
{
"candidates": [],
"filename": "debian/rules",
"target-name": "override_dh_car_configure"
}
]
}
I don't know how much ambition you have for expanding the scope of
dh_assistant. We already have Lintian which has a massive amount of
checks, including ones related to debian/rules. It is just a pity
Lintian does not support checking a single file or the debian/
directory contents without building the package.. [1]
[1] https://bugs.debian.org/262783
Editor extensions to help editing debian/* files?
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 get it to emit any errors/messages.
I would be interested to learn what editors and integrations others
use specifically for debian/* files. I've witnessed several old DDs
stop their Debian work, and many aspiring ones give up on becoming a
DD, because the Debian packaging work is so laboursome. One small
thing that could ease the burden could be better editor integrations
that help people write and maintain the debian/* files with less
effort.
- Otto
[1]
https://www.debian.org/doc/manuals/developers-reference/developers-reference.en.html
[2] https://optimizedbyotto.com/post/pulsar-best-text-file-and-code-editor/
[3] https://web.pulsar-edit.dev/packages/language-debian
PS. Related, these are commands I frequently run manually but don't
have any editor integration for:
wrap-and-sort --wrap-always --verbose
make --dry-run --makefile=debian/rules
codespell --write --check-filenames --check-hidden debian/
find debian/ -type f | xargs spellintian --picky
aspell --mode=debctrl -c debian/control
duck -v --color=always
find -name *.pot -exec i18nspector "{}" +; find -name *.po -exec
i18nspector "{}" +;
shellcheck -x --shell=bash $(shell grep -Irnw -e '^#!.*/bash' | sort
-u |cut -d ':' -f 1 | xargs)
shellcheck -x --shell=sh $(shell grep -Irnw -e '^#!.*/sh' | sort -u
|cut -d ':' -f 1 | xargs)
if [ "$(find debian/patches/ -type f -not -name series | wc -l)" !=
"$(wc -l < debian/patches/series)" ]
then
echo "Contents of debian/patches/series does not match number of
patches in debian/patches"
fi
Bug#1060778: ITP: pulsar-edit -- A Community-led Hyper-Hackable Text Editor (formerly Atom)
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: JavaScript Description : A Community-led Hyper-Hackable Text Editor Anyone can test the app using upstream package https://download.pulsar-edit.dev/?os=linux=linux_deb which installs everything in /opt/Pulsar/. This is an Electron app and I am looking for advice from other NodeJS and Electron app maintainers on how to package this properly in Debian.
Static analyzer / linter for debian/rules?
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 Makefile tool such as checkmake[2] or unmake[3] do not help much as the debian/rules is very Debian specific. Lintian has some checks for debian/rules contents, but it can't be run on a single debian/rules file or even the debian/ directory directly.[4] I occasionally come across simple syntax issues which a static analyzer / linter could easily pick up so I was wondering if it could be automated. For example in one case[5] exporting DPKG_GENSYMBOLS_CHECK_LEVEL did not take effect due to easily detectable incorrect (but not fatal) syntax. - Otto [1] https://salsa.debian.org/mariadb-team/mariadb-server/-/commit/b1f1640d414e2c7631cdccbb7f5445a4b8ad56e4 [2] https://github.com/mrtazz/checkmake [3] https://github.com/mcandre/unmake [4] https://bugs.debian.org/262783 [5] https://salsa.debian.org/mariadb-team/mariadb-server/-/commit/f2fe8d8300642c373ce325f19d1100d79adeed45
Re: DebGPT: how LLM can help debian development? demo available.
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 stuff. However, checking if an answer is correct is much faster than figuring it out something from scratch. Anyone can test it for themselves at https://chat.lmsys.org/ - no registration required, just participate in the research by reading the replies from two LLMs and telling the leaderboard which reply you think was better. Knowing there is so much repetitive petty work involved in Debian package maintenance that drains a of energy both from current and aspiring maintainers I have been skimming the README at https://salsa.debian.org/deeplearning-team/debgpt with high hopes for DebGPT to evolve over time. It would be great if there was a LLM with enough logic and context that it could do things like Lintian-brush (or even go all the way like Janitor and start filing MRs on Salsa for humans to review/finalize).
Re: [Pkg-pascal-devel] Issue with fpc_3.2.2+dfsg-24 in Sid.
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 https://salsa.debian.org/pascal-team/fpc/-/settings/ci_cd and under "General pipelines" in box "CI/CD configuration file" put "recipes/debian.yml@salsa-ci-team/pipeline" to activate it. It is super easy. More at https://salsa.debian.org/salsa-ci-team/pipeline/-/blob/master/README.md Hopefully more and more DDs adopt Salsa-CI, it is such a time saver! :)
Re: Running Lintian against a debian/ directory?
> 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 already solved (ignoring the fact that we have hunspell, nuspell and aspell trying to solve the same problem but none of them doing it perfectly - that is another story). I use Pulsar and have in it https://web.pulsar-edit.dev/packages/spell-check with hunspell as backend. Additionally I occasionally run these spell checkers from the command-line manually (sharing in case others want to try them out): codespell --write --check-filenames --check-hidden debian/ find debian/ -type f | xargs spellintian --picky aspell --mode=debctrl -c debian/control
Running Lintian against a debian/ directory?
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 as-is without doing a source build first? I am exploring this in order to get my text editor to nag about findings immediately without separate source build steps. Otto [1] https://manpages.debian.org/bookworm/lintian/lintian.1.en.html
Re: Bug#1042428: lintian.debian.org off ?
> >> 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 all packages > >> affected by the tag. > > > >Thanks! > > > >Could you consider setting up also redirects from old url, as it seems > >that search engines had it indexed pretty well and tend to offer links > >to lintian.debian.org as the primary result on searches for various > >Lintian errors? > > > >https://lintian.debian.org/tags/([a-z-]*)/?$ > >-> > >https://udd.debian.org/lintian-tag.cgi?tag=$1 I noticed today that Google is returning results from http://lintian.debathena.org/tags/bad-distribution-in-changes-file.html instead of old lintian.debian.org, so we have this functionality now back online but not hosted by Debian officially.
Re: Bug#1042428: lintian.debian.org off ?
> > 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 willing to contribute the Apache/Nginx rewrite rules if > > somebody can point me to a code repository where I can read/contribute > > at like I announced on September 27th in this thread. > > 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 all packages > affected by the tag. Thanks! Could you consider setting up also redirects from old url, as it seems that search engines had it indexed pretty well and tend to offer links to lintian.debian.org as the primary result on on searches for various Lintian errors? https://lintian.debian.org/tags/([a-z-]*)/?$ -> https://udd.debian.org/lintian-tag.cgi?tag=$1
Re: lintian.debian.org off ?
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 > > frequently need to educate upstreams about Lintian rules, and thus > > really also need a URL to share to them. Perhaps I could implement > > that later in the year. > > That's indeed a good rationale for adding a web interface to lintian > tags explanations. Thanks. > > I still plan to work on adding that eventually. 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 willing to contribute the Apache/Nginx rewrite rules if somebody can point me to a code repository where I can read/contribute at like I announced on September 27th in this thread. - Otto
Re: lintian.debian.org off ?
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 easily write Ansible code to maintain a simple Nginx server, with 302 redirects https://lintian.debian.org/tags/(.*)/?$ -> https://udd.debian.org/lintian-tag.cgi?tag=$1, use same Ansible style as salsa.debian.org is maintained on (https://salsa.debian.org/salsa/salsa-ansible), and also donate a tiny virtual machine for Debian project if needed. Is there some special bureaucracy on top of that work to do to be able to contribute with this? I know Lintian tag info is available via command line, but I frequently need to educate upstreams about Lintian rules, and thus really also need a URL to share to them. Perhaps I could implement that later in the year. - Otto
Re: lintian.debian.org off ?
> > > > 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 *why* the site https://lintian.debian.org/ was shut down? The site https://udd.debian.org/lintian-tag.cgi?tag=wrong-name-for-upstream-changelog only lists packages with the issue, while the old site had full explanations of the issue and felt quite friendly and easy to consume (non-CSS styled version still visible in Google cache, eg. https://webcache.googleusercontent.com/search?q=cache:AKmDGNJEIaAJ:https://lintian.debian.org/tags/wrong-name-for-upstream-changelog).
Salsa-CI featured on GitLab.com blog
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 12 a very solid and high quality release. Nice to see this getting more visibility! If you want to help boost the visibility, please vote on HackerNews: https://news.ycombinator.com/item?id=37635937 Thanks to Alexander and Joerg for maintaining Salsa itself, and to Santiago, Iñaki and Agustin for being the main drivers of https://salsa.debian.org/salsa-ci-team/pipeline since 2018. - Otto
Re: lintian.debian.org off ?
> > > 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 https://udd.debian.org/lintian/ so people will automatically find the new location? And perhaps a separate redirect from URL https://lintian.debian.org/manual to the new location, wherever the guide now is to be read. I used the old website frequently, and also shared links to the Lintian error explanations there frequently. Currently all links from all HTML reports from Lintian are broken, see https://mariadb-team.pages.debian.net/-/galera-4/-/jobs/4709137/artifacts/debian/output/lintian.html for example. Maybe they should now be updated to be links to UDD instead? Thanks for everyone maintaining our infra and working towards resolving this. > > There is no web based location for the description of each tag yet. > > I don't know if it is just me, but even udd gives me a 500 > when I try to check lintian output for any (existing) package. > > For example: https://udd.debian.org/lintian/?packages=nim I also just get error 500 when trying to look up LIntian errors for my own packages..
Re: MariaDB 10.11 in Bookworm - call for contributions
(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 want to help polish MariaDB in Bookworm, please help by (in order of importance): 1. Review past commits in https://salsa.debian.org/mariadb-team/mariadb-server/-/commits/debian/latest?ref_type=heads and post feedback/improvement suggestions on the maintainermailing list (pkg-mysql-maint at lists.alioth.debian.org) so people can see how many reviews happened and what they commented on. 2. Review open MRs at https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests about improvements that might still go into next upload, or a future one. 3. Review general QA system feedback at https://tracker.debian.org/pkg/mariadb and post MRs to fix whatever you found and want to fix yourself. 4. Review and triage/close open bug reports at https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no=mariadb=mariadb-10.6=mariadb-10.5=mariadb-10.3=mariadb-10.1 - Otto
Re: MariaDB 10.11 in Bookworm - call for contributions
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 the testing and packaging alone and to make sure > that the quality is top notch, I would be glad to see more people > contribute. > > If you have time to help, please consider these (in order of importance): > > 1. Review current open MRs at > https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests > > 2. Review items highlighted by Debian QA systems (Lintian, builds etc) > and submit a fix to improve the quality: > https://tracker.debian.org/pkg/mariadb > > 3. Review what testing we have at > https://salsa.debian.org/mariadb-team/mariadb-server/-/pipelines and > think about potential gaps - CI is very important as it is the only > way we can prevent regressions in a scalable way > > 4. Review/follow-up on existing bugs that currently need more > information: > https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no=mariadb=mariadb-10.6=mariadb-10.5=mariadb-10.3=mariadb-10.1 > > MariaDB and C++ skills are useful, but not required. For example > reviewing the NEWS for 10.11 requires no coding skills: > https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/37 One more items I am requesting help with: 5. If you know C/C++ compatibility on armhf and care about e.g. Raspberry PI your help would be very useful. Upstream does not test/target armhf and there are many minor places in upstream code that would need some armhf tweaks. You could for example install the mariadb-test package and run the full upstream test suite with 7227 tests and see which ones currently break on armhf (details in https://optimizedbyotto.com/post/grokking-mariadb-test-run-mtr/). - Otto
MariaDB 10.11 in Bookworm - call for contributions
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 see more people contribute. If you have time to help, please consider these (in order of importance): 1. Review current open MRs at https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests 2. Review items highlighted by Debian QA systems (Lintian, builds etc) and submit a fix to improve the quality: https://tracker.debian.org/pkg/mariadb 3. Review what testing we have at https://salsa.debian.org/mariadb-team/mariadb-server/-/pipelines and think about potential gaps - CI is very important as it is the only way we can prevent regressions in a scalable way 4. Review/follow-up on existing bugs that currently need more information: https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no=mariadb=mariadb-10.6=mariadb-10.5=mariadb-10.3=mariadb-10.1 MariaDB and C++ skills are useful, but not required. For example reviewing the NEWS for 10.11 requires no coding skills: https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/37 - Otto
Re: depends-on-obsolete-package lsb-base
> > 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 on path to get this
> > dependency removed (and Salsa-CI failures stopped on this Lintian
> > error)?
>
> That's an interesting idea. The current format
> https://salsa.debian.org/lintian/lintian/-/blob/master/data/fields/obsolete-packages
> isn't super machine-readable. Perhaps it could be split into one file
> with human-readable hints, and one with straightforward replacements
> (e.g. "libtinfo-dev => libncurses-dev" )?
Related, current lintian-brush actually adds lsb-base back if it was removed:
$ lintian-brush --version
lintian-brush 0.145
$ lintian-brush --allow-reformatting --uncertain --yolo --modern
$ git show
commit a0a2bf5d6972348114b6d6d489619353c539bd74 (HEAD -> dev-otto)
Add missing dependency on lsb-base.
Changes-By: lintian-brush
Fixes: lintian: init.d-script-needs-depends-on-lsb-base
See-also:
https://lintian.debian.org/tags/init.d-script-needs-depends-on-lsb-base.html
diff --git a/debian/control b/debian/control
index 80edd7be401..240d74914d3 100644
--- a/debian/control
+++ b/debian/control
@@ -454,7 +454,8 @@ Depends: galera-4 (>= 26.4),
- ${shlibs:Depends}
+ ${shlibs:Depends},
+ lsb-base
I have only ever found two bugs in lintian-brush, otherwise it works
perfectly. I wish those who drive changes to Lintian rules would take
one extra step and also collaborate with lintian-brush to automate
fixing the issues instead of relying on all human maintainers to read
Lintian reports and address them manually.
Re: depends-on-obsolete-package lsb-base
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 somebody know what is going on? > > > Example: > > E: mariadb-server: depends-on-obsolete-package Depends: lsb-base (>= 3.0-10) > > That is this change > * Remove init.d-script-needs-depends-on-lsb-base and add lsb-base to > obsolete-packages. (Closes: #1019851) > > from this commit: > > commit 97f742b00553a4dd7ba681aefa4cc164ea263f71 > Remove init.d-script-needs-depends-on-lsb-base and add lsb-base to > obsolete-packages > > The functionality of lsb-base is in the Essential:yes set since > Bullseye. The package itself is now an empty transitional package > (because debootstrap doesn't understand the Provides relationship) which > depends on the new provider of the functionality, sysvinit-utils, which > is also in the Essential:yes set. > > Closes: #1019851 Thanks for an exact reply! 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 on path to get this dependency removed (and Salsa-CI failures stopped on this Lintian error)? As a side note, it would be cool if the Janitor could also mass add brackets to Lintian overrides (like done manually in https://salsa.debian.org/lintian/lintian/-/commit/6e8c0487a186e1640fe69e2409544b28e6f26164 on Lintian itself) now after that not backwards compatible change was introduced last summer so that we get it executed repository-wide.
depends-on-obsolete-package lsb-base
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 error in general, not any mention of lsb-base specific changes. Does somebody know what is going on? Example: E: mariadb-server: depends-on-obsolete-package Depends: lsb-base (>= 3.0-10)
Re: [Salsa CI] stop building dbgsym packages by default?
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: > https://salsa.debian.org/salsa-ci-team/pipeline/-/merge_requests/382 +1 > We are aware some fellows have pipelines based on salsa-ci's, and we > would like to avoid breaking their stuff, in case something depends on > the dbgsym packages. > The question is: should `DEB_BUILD_OPTIONS=noautodbgsym` be opt-in > or enabled by default? The proposal to make it opt-in makes sense to me. - Otto
Re: TMPDIR behaviour in maintainer scripts [was: Re: Bug#1023778: mysql-server-8.0: fails to restart on upgrade with libpam-tmpdir]
> > 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 > > copied debian-devel@ for comment. > > I'm not sure this is libpam-tmpdir specific, but rather a bit more > general: what are the expectations that maintainer scripts can have > about the environment they're running in, and how do we make those > expectations hold? This should probably then be documented in policy. This MySQL 8.0 in Sid tmpdir issue is identical to MariaDB 10.6 in Sid tmpdir issue, as they are based on historically the same maintainer script. MariaDB duplicate of this has been filed as https://jira.mariadb.org/browse/MDEV-29910 and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022994 The suggested solution in https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/23 to set an empty TMPDIR does not seem to work - or at least CI shows that even a basic install fails after that. Instead of manually trying to manage TMPDIR env variable in various places, we should have a standardized way to run maintainer scripts in clean shell sessions that have all env variables set automatically correctly. More proposals on how to handle this are welcome at https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests :) - Otto
Re: How to fix Lintian 'no-code-sections'?
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 Lintian tag, I would recommend doing your own assessment > of whether this is a real error before assuming there is a bug that you > need to fix. I tried, but clearly reading the Lintian page linked above and the bug report linked from it didn't really convey what it was actually trying to achieve. Now when you explained it, I got it, and also see why it is fine to ignore. > This particular one looks like it's a Lintian bug: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000469 (fixed in git) Thanks for pointing this out!
How to fix Lintian 'no-code-sections'?
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 context at
https://salsa.debian.org/mariadb-team/mariadb-server/-/jobs/2203726
in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977596 there is a
shell example how to test for no-code-sections, but it does not return
anything for me locally:
readelf -W --section-headers
./debian/tmp/usr/lib/x86_64-linux-gnu/libmariadbd.a | sed -n '/^ *\[[
0-9]*\]/s/ *\[[ 0-9]*\] *//p' | awk 'BEGIN {rv=1} /^NULL/ {next} $1
~/^.(text|data|(preinit|init|fini)_array$)/ {if ($5 !~ /^0+$/) rv=0}
END { exit rv}'
readelf: Warning: unable to apply unsupported reloc type 21 to section
.debug_info
(or https://paste.debian.net/1220493/ with no line breaks)
Any suggestions how to debug this locally so I can validate if various
changes in debian/rules fixes it or not?
- Otto
New systemd service file path?
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 anything about systemd paths. Seems dh_systemd_enable still installs files into /lib/systemd/system/ and I find it confusing that apparently Lintian errors on what debhelper does by default. Please enlighten me on what I have missed. So, which one of these paths should be used and why? - /lib/systemd/system/ - /usr/lib/systemd/system/ Thanks!
MariaDB Foundation looking to hire/contract Debian packaging expert
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: https://mariadb.org/debian-ubuntu-packaging-expert/ I got MariaDB 5.5 into Debian unstable back in 2013 and have been the main maintainer ever since. At one point I also worked for the MariaDB Foundation, but left a couple of years ago. I still maintain all my commitments to Debian, but only on a best-effort level. There is no crisis in MariaDB packaging. The Foundation is simply now investing in the area as one volunteer (me) is not enough, and I will continue to stay around. Current state of MariaDB, Galera and related packages in Debian and Ubuntu is very good. Despite it being a very large package and installed on about 10% of all Debian systems (according to popcon) it has a surprisingly low number of bugs (mariadb-10.3 in stable has _4_ and mariadb-10.5 in unstable has 35). It is a nice situation to start contributing to the work. The package is well documented with good commit history for the past 10 years, up-to-date README files for both maintainers and contributors and probably the most extensive Salsa-CI pipeline in all of Debian to ensure new commits don't regress anything (check out https://salsa.debian.org/mariadb-team/mariadb-10.5/-/pipelines/266998). The Debian packaging is also almost fully in sync with the upstream packaging in mariadb.org repositories, so this is a nice piece of software to work with, promise! Note that MariaDB Foundation is not looking for simply a maintainer, but that the work includes a lot of new development as well. MariaDB is constantly shipping new interesting features and you could have your say in them. If you are at all keen to do FOSS and MariaDB full-time, or if you have friends who might be interested, please check out https://mariadb.org/debian-ubuntu-packaging-expert/ or reach out to dan...@mariadb.org for more info. - Otto PS. I am a long-time entrepreneur in the open source scene, and everybody who works for me gets to spend a big share of their working time contributing to open source. If MariaDB Foundation turns you down, you can also ping me and ask for work opportunities.
Re: Tips for debugging/testing debian/control Depends/Breaks etc changes?
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. There was probably some use case that users wanted to stick to a certain major release by installing e.g. 'mysql-server-5.1' while installing 'mysql-server' would just auto-upgrade the major version on dist-upgrade. I don't know for sure, this predates me by years. I'd rather not start changing it now due to the potential unknown and hard to revert consequences it could have to users. I did however a couple years ago remove the versions from the plugin package names, so the issue is at least limited to server and client packages. For the record, I solved the original issue already using the 'apt install --with-source ./Packages -s' technique.
Re: File moved from one package to another - use Conflicts/Replaces or Breaks/Replaces?
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 > > 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 [1] > > > While trying to clean up and simplify I started wondering, when should one > > use Conflicts/Replaces and when Breaks/Replaces? > [...] > > The rough guideline is to use Breaks together with an earlier than (<<, > <=) condition. Which seems to be what mariadb does. OK > I do not think there is a lot to improve here. Did you you see David's > recent message, <20210331164012.gevwmagm63q2yc54@crossbow>? Yes, and I solved the original issue already using the 'apt install --with-source ./Packages -s' technique.
File moved from one package to another - use Conflicts/Replaces or Breaks/Replaces?
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 [1] While trying to clean up and simplify I started wondering, when should one use Conflicts/Replaces and when Breaks/Replaces? Policy [2] says: "Breaks should be used when moving a file from one package to another" Man page [3] says: "Conflicts: Lists packages that conflict with this one, for example by containing files with the same names." Wiki page [4] implies to use Breaks/Replaces in the "ReOrg" scenario, but it does not directly apply here as it discusses changes to two packages, not only one as in the MariaDB case. Looking at the MariaDB control file [1], how do you suggest I clean it up? Examples of file moves and control file updates over the years: [5], [6] [1] https://salsa.debian.org/mariadb-team/mariadb-10.5/-/blob/master/debian/control [2] https://www.debian.org/doc/debian-policy/ch-relationships.html#s-conflicts [3] https://manpages.debian.org/buster/dpkg-dev/deb-control.5.en.html [4] https://wiki.debian.org/PackageTransition [5] https://salsa.debian.org/mariadb-team/mariadb-10.5/-/commit/7bda76751754145a66239c8f9fd343d47fd1c1b0 [6] https://salsa.debian.org/mariadb-team/mariadb-10.5/-/commit/49ecd78307e0ddc65ccb7464321e612e423ddce3
Re: Tips for debugging/testing debian/control Depends/Breaks etc changes?
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 libmariadbclient18 Between each attempt I can edit the Packages file and it immediately takes effect. While the Packages file does not have the exact same format as the debian/control file, it is close enough so I can simulate small depends/breaks/replaces changes without having to rebuild anything, just editing this one file directly. Nice! The debugging options produce a ton of output which I did not yet learn to ready, but I'll paste it here below for reference for others to see what the resolver debug output looks like: # apt install --with-source ./Packages -s mariadb-server mariadb-client libmariadbclient18 -o Debug::pkgDepCache::Marker=1 -o Debug::pkgDepCache::AutoInstall=1 -o Debug::pkgProblemResolver=1 Reading package lists... Done Building dependency tree Reading state information... Done MarkInstall mariadb-server:amd64 < none -> 1:10.5.10+maria~bionic @un puN Ib > FU=1 Installing mariadb-server-10.5 as Depends of mariadb-server MarkInstall mariadb-server-10.5:amd64 < none -> 1:10.5.10+maria~bionic @un uN Ib > FU=0 Installing mariadb-common as PreDepends of mariadb-server-10.5 MarkInstall mariadb-common:amd64 < none -> 1:10.5.10+maria~bionic @un uN > FU=0 Installing galera-4 as Depends of mariadb-server-10.5 MarkInstall galera-4:amd64 < none -> 26.4.5~ubuntu18.04.1~153342.189a33e7+4.x.debian.packaging.update @un uN > FU=0 Installing gawk as Depends of mariadb-server-10.5 MarkInstall gawk:amd64 < none -> 1:4.1.4+dfsg-1build1 @un uN Ib > FU=0 Installing libmpfr6 as PreDepends of gawk MarkInstall libmpfr6:amd64 < none -> 4.0.1-1 @un uN > FU=0 Installing libreadline7 as PreDepends of gawk MarkInstall libreadline7:amd64 < none -> 7.0-3 @un uN Ib > FU=0 Installing readline-common as Depends of libreadline7 MarkInstall readline-common:amd64 < none -> 7.0-3 @un uN > FU=0 Installing libsigsegv2 as PreDepends of gawk MarkInstall libsigsegv2:amd64 < none -> 2.12-1 @un uN > FU=0 Installing iproute2 as Depends of mariadb-server-10.5 MarkInstall iproute2:amd64 < none -> 4.15.0-2ubuntu1.3 @un uN Ib > FU=0 Installing libelf1 as Depends of iproute2 MarkInstall libelf1:amd64 < none -> 0.170-0.4ubuntu0.1 @un uN > FU=0 Installing libmnl0 as Depends of iproute2 MarkInstall libmnl0:amd64 < none -> 1.0.4-2 @un uN > FU=0 Installing libatm1 as Recommends of iproute2 MarkInstall libatm1:amd64 < none -> 1:2.5.1-2build1 @un uN > FU=0 Installing libxtables12 as Recommends of iproute2 MarkInstall libxtables12:amd64 < none -> 1.6.1-2ubuntu2 @un uN > FU=0 Installing libdbi-perl as Depends of mariadb-server-10.5 MarkInstall libdbi-perl:amd64 < none -> 1.640-1ubuntu0.2 @un uN > FU=0 Installing lsof as Depends of mariadb-server-10.5 MarkInstall lsof:amd64 < none -> 4.89+dfsg-0.1 @un uN > FU=0 Installing mariadb-client-10.5 as Depends of mariadb-server-10.5 MarkInstall mariadb-client-10.5:amd64 < none -> 1:10.5.10+maria~bionic @un uN Ib > FU=0 Installing mariadb-client-core-10.5 as Depends of mariadb-client-10.5 MarkInstall mariadb-client-core-10.5:amd64 < none -> 1:10.5.10+maria~bionic @un uN Ib > FU=0 Installing libmariadb3 as Depends of mariadb-client-core-10.5 MarkInstall libmariadb3:amd64 < none -> 1:10.5.10+maria~bionic @un uN > FU=0 Installing libreadline5 as Depends of mariadb-client-core-10.5 MarkInstall libreadline5:amd64 < none -> 5.2+dfsg-3build1 @un uN > FU=0 Removing: mysql-client-core-5.7 MarkDelete mysql-client-core-5.7:amd64 < 5.7.30-0ubuntu0.18.04.1 | 5.7.33-0ubuntu0.18.04.1 @ii umH Ib > FU=0 Removing: mysql-client-5.7 MarkDelete mysql-client-5.7:amd64 < 5.7.30-0ubuntu0.18.04.1 | 5.7.33-0ubuntu0.18.04.1 @ii umH Ib > FU=0 Installing libdbd-mysql-perl as Recommends of mariadb-client-10.5 MarkInstall libdbd-mysql-perl:amd64 < none -> 4.046-1 @un uN Ib > FU=0 Installing libmysqlclient20 as Depends of libdbd-mysql-perl MarkInstall libmysqlclient20:amd64 < none -> 5.7.33-0ubuntu0.18.04.1 @un uN > FU=0 Installing libterm-readkey-perl as Recommends of mariadb-client-10.5 MarkInstall libterm-readkey-perl:amd64 < none -> 2.37-1build1 @un uN > FU=0 Installing mariadb-server-core-10.5 as Depends of mariadb-server-10.5 MarkInstall mariadb-server-core-10.5:amd64 < none -> 1:10.5.10+maria~bionic @un uN Ib > FU=0 Installing libpcre2-8-0 as Depends of mariadb-server-core-10.5 MarkInstall libpcre2-8-0:amd64 < none -> 10.31-2 @un uN > FU=0 Removing: mysql-server-core-5.7
Tips for debugging/testing debian/control Depends/Breaks etc changes?
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 example of 1, sometimes I see this: apt install mariadb-client The following packages have unmet dependencies: mariadb-client : Depends: mariadb-client-10.5 (>= 1:10.5.10) but it is not going to be installed apt install mariadb-client-10.5 Installing.. Done! When this happens I have no idea why apt did not resolve the dependency by itself automatically, as there was no real conflict in installing it. Do you have tips on how to debug the root cause of situations like these? For the problem 2, I hate to rebuild all of the packages (and binaries) just because there was a change in debian/control and go through the hassle of updating a test repo etc. I wonder if there is some other "lighter" way to just edit the debian/control and produce new binary packages with them updated without having to actually build new binary packages (and no, editing the .deb files manually and repackaging them with 'ar' is not an option that would make life easier). Thanks for any tips you have on the topic! - Otto
Re: Tools to better colorize the command-line experience?
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 > different file formats. There's some screenshots on the github page: > https://github.com/sharkdp/bat Thanks, bat is great. It has now become my standard replacement for 'cat'. I recently also switched to fzf[1] for my 'cd' and Ctrl+R use. Thanks to this Debian-devel list I've learnt about both Liquid Prompt and the fuzzy-finder for the bash prompt, which both are very useful and solid (and not overly complex or incompatible like all those zsh extensions many Mac users rely on). I didn't expect that the command-line efficiency can still increase this much in 2021 and I am a bit surprised the standard tools shipped in all Linux distros are still the same as in the past 30 years or so. There is a lot of productivity improvements people are missing out with the standard tools.. [1] https://linuxnatives.net/2021/save-time-command-line-fuzzy-finder
Tools to better colorize the command-line experience?
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 looked into packaging hl[3] as it is easier to use than ccze, It also worries me that ccze has no upstream commits in 10 years. However I stopped working on hl as it does not seem to be as powerful and generic as ccze. Do you have any tips about generic command-line coloring programs? I am in particular interested in generic from the point of view that they would work well in different shells and terminal connections, and support a wide array of log file formats or program outputs, and thus would best serve an average Linux distro user. - Otto [1] https://tracker.debian.org/pkg/ccze [2] https://github.com/wofr06/lesspipe [3] https://github.com/mbornet-hl/hl
Re: MariaDB 10.5 has entered Debian testing (will be in Bullseye)
> 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 > more risky (ie: turn off 2 nodes, upgrade the 3rd one, then upgrade node > 1 and 2). Yes, after we spoke 1,5 years ago Galera has started to support rolling upgrades from 3->4. I have personal experience that it works. So keep all 3 nodes on. Upgrade fully one node, wait until it joins and syncs and cluster is PRIMARY again, then proceed with the 2nd node etc.
Re: MariaDB 10.5 has entered Debian testing (will be in Bullseye)
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, and the work > > on the successor of 10.3 in Debian started already in January (with > > 10.4 which then turned into 10.5 as upstream released it this spring). > > Thanks for maintaining MariaDB in Debian. > > Do you happen to know the procedure for upgrading a Galera cluster of 3 > MariaDB nodes from 10.3 to 10.5? Is this formalized in some doc anywhere? > You can do a live rolling upgrade. New hosts with Galera 4 can join a running Galera 3 cluster one by one, but once upgrade starts no new old hosts can join anymore, only leave. https://www.slideshare.net/ottokekalainen/debconf-2020-whats-new-in-mariadb-server-105-and-galera-4#34 https://galeracluster.com/library/documentation/upgrading.html MariaDB 10.4 intoduced Galera 4, so this applies for MariaDB 10.3 (Galera 3) -> 10.5 ((Galera 4) upgrades as well: https://mariadb.com/kb/en/upgrading-from-mariadb-103-to-mariadb-104-with-galera-cluster/ >
MariaDB 10.5 has entered Debian testing (will be in Bullseye)
Hello! MariaDB 10.5 release 1:10.5.8-3 finally entered Debian testing today[1]. It has been in unstable since early September, and the work on the successor of 10.3 in Debian started already in January (with 10.4 which then turned into 10.5 as upstream released it this spring). This also means that MariaDB 10.3 will be removed (or the remaining traces of it to be exact) in the following weeks. MariaDB 10.5 has a rather massive 45 step CI pipeline just for Debian[2] and we hope the number of bugs is small, but still it is always expected that in a major upgrade like 10.3 -> 10.5 users might experience some issues. If you encounter issues 1) file a high quality bug report at bugs.debian.org, and consider filing one in parallel at upstream at jira.mariadb.org if the issue does not seem to be packaging related 2) send a merge request on Salsa following guidelines at https://wiki.debian.org/Teams/MySQL/patches MariaDB in Debian is quite heavily on my shoulders right now. I would be very glad to see more merge requests, even small ones are nice and show that people contribute. Some git stats for the post-10.3 cycle in Debian: git summary 7bf99ca66..HEAD project : mariadb-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% 1 Miroslav Kure 0.5% Thanks to all contributors! [3] Also a big thanks those who sent patches as files and very helpful hints, in particular jrtc27 and the porter folks! [1] https://tracker.debian.org/pkg/mariadb-10.5 [2] https://salsa.debian.org/mariadb-team/mariadb-10.5/-/pipelines/200608 [3] https://salsa.debian.org/mariadb-team/mariadb-10.5/-/graphs/master
Re: Pimp your shell - Debian developer tips?
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 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 a bit on zsh and powerline and the like, but I am annoyed that all > > those blog posts are quite superficial and do not mention security, > > interoperability or performance aspects. Frankly any blog post that > > recommends > > cloning random repos or even worse, running wget | sh something gives me > > chills. ... > Take a look at liquidprompt(1). > > Is what I use everywhere! This turned out to be my favourite tip. I've written about my experiences and why I love it so much at https://linuxnatives.net/2020/liquid-prompt in case others are interested. And thanks to Arturo for packaging it and for recently uploading the latest version of it to Debian unstable! - Otto
Re: Accepting / adopting DEP-14
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 git-buildpackage default master is 'master', not DEP-14 'debian/master' - git-buildpackage in my use has the branch 'pristine-tar' which DEP-14 does not cover
Re: NMU for Imagemagick?
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 drop-in replacement GraphicsMagick, which is also more recent in Debian. Maybe you should migrate your ImageMagick needs to GraphicsMagic? - https://tracker.debian.org/pkg/graphicsmagick - https://tracker.debian.org/pkg/imagemagick
Re: DEP-14: renaming master to main?
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 background of what philosophical meaning the term had in git: https://public-inbox.org/git/20200618152300.cw7teo2jmxyfsl2l@chatter.i7.local/ > This is actually an important philosophical point with software like > git. There is no such thing as master.kernel.org for the very specific > reason that we position kernel.org to be merely a convenient place where > to get a *copy* of Linux. The "master copy" of the mainline tree exists > only in one place -- on Linus's computer. Let's wait and see if upstream Git changes the default, then others will naturally follow next time they run 'git init'. So far upstream git has removed a couple of mentions of slavs: - https://github.com/git/git/commit/f33b5bddaf7ac1535c6c37fde168597e252872b3 - https://github.com/git/git/commit/08dc26061f3ff9ee79e6cfda88f0c825b8730e54 Python had a similar discussion in 2018 and they concluded that the term 'master' does not have any political undertone when used in git master, postmaster or hostmaster: https://bugs.python.org/issue34605
Re: Pimp your shell - Debian developer tips?
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: https://www.youtube.com/watch?v=v9iwVsV50nk=PLIbuTLE8Wih4pBd8S9UjGDGQQXG4-a6Yw=11 I highly recommend it. The best part with those tips is that they are all just one apt install away :) I also found this post about a handful of new Rust based command-line tools interesting, although none of them are in Debian yet: https://towardsdatascience.com/rust-powered-command-line-utilities-to-increase-your-productivity-eea03a4cf83a - Otto
Pimp your shell - Debian developer tips?
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 a bit on zsh and powerline and the like, but I am annoyed that all those blog posts are quite superficial and do not mention security, interoperability or performance aspects. Frankly any blog post that recommends cloning random repos or even worse, running wget | sh something gives me chills. Some above average posts are https://linuxhint.com/install_zsh_shell_ubuntu_1804/ and https://www.hildeberto.com/2018/02/oh-my-zsh.html I'd very much want to read about some more knowledgeable experiences. Tips? Some might react that bells and whistles is useless and real unix beards only run plain bash, but I think that good text prompts have a potential to increase productivity. And anyway I don't want those MacOS users to claim that their shells would be in any way better than what I can have in Debian ;)
Re: Is there any way to refuse Janitor changes in team git?
>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 don't want any >automated merge proposals. >It would be great if you can also give us an idea of what specifically you >don’t appreciate about these merge proposals, and if there’s anything that can >be done to improve them. >Alternatively, propose a change to the policy on Salsa.
Re: Best practices for Debian developers who are also upstreams?
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: https://github.com/rdiff-backup/rdiff-backup/blob/master/debian/rules What remains is to decide what to do to the debian/changelog. The version there still leaks the source package version number that ends up in *.changes and *.dsc.. Otherwise it is rolling pretty well. The upstream .travis-ci.yml builds the .eb just like Debian will eventually do (apart from some version and changelog differences) and all bugs I encounter in Debian or elsewhere can be fixed directly on upstream for everybody's benefit. My work on the quality of the software is directly beneficial at upstream and "globally" and not just for Debian. I still have a separate Debian repo on salsa.debian.org but in future I think I'll have a debian/master branch directly in upstream repository and configure to git-buildpackage the upstream branch as 'master'. One of the best inspirations for this was https://vincent.bernat.ch/en/blog/2019-pragmatic-debian-packaging and examples at https://github.com/vincentbernat/pragmatic-debian-packages/tree/master but I am still looking to optimize the process as a whole. I don't feel there is any problem with "two hats". Pretty much everything the Debian policy states about software quality applies universally to any open source project. The things that are very Debian specific will only be expressed in code under debian/ and not affect other distros. If this works out well I'll expand to become upstream in all projects I maintain in Debian if the upstreams trust me enough to give write access. The closer a maintainer is to the upstream, the better everything will be I reason. - Otto
Re: Best practices for Debian developers who are also upstreams?
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 Debian package. There does not seem to be any automation around release numbering — currently the repo tags, debian/changelog and redhat spec file all bumped manually and independently. https://github.com/spwhitton/git-remote-gcrypt/commit/069f6ea33149fbaa8bd83423b7a7b591fcfed43b In the other cases I did not see a real feedback loop where upstream developers would be exposed to Debian policy requirements or Debian QA. Seems many misunderstood my list of goals. My emphasis is not on the git branch layout or patch handling. So let me rephrase my goals from a quality assurance perspective: - Build .deb directly at upstream for every upstream commit: allow upstream developers to notice if they break Debian packaging to the level that it stops building. Upstream PRs (or MRs) should not be accepted if they make changes without considering if they break .deb (or .rpm if that is also included in the upstream repository). Effectively this requires that upstream git master branch has a debian/ directory. - Since there will be a debian/ directory, upstream might as well run full Debian QA on every commit. This will help detect if upstream developes make grave mistakes, like try to run curl/git fetches duringthe build stage, introduce library symbols in a wrong way or embed in the build something that stops from being a reproducible build anymore. Lintian even complains about spelling mistakes. Such QA items are not Debian specific – all code everywhere should be without spelling mistakes, all programs should stay reproducible if they now are so etc. Now some ask, if it reasonable to require all upstream developers to follow Debian QA? No, I don't think so. If the CI runs automatically and the QA is automatic, then developers will be served with in-context errors and warnings at the time they are changing some code. For everybody to know the Debian Policy by heart and so on is naturally unreasonable, but reading a Lintian warning about a spelling error or broken multi-arch is not hard or unreasonable, and when those things are addressed the upstream code base benefits and all distributions benefit. The contrary is in my opinion unreasonable: to expect the Debian maintainer to fix tens of upstream issues at Debian import time that can be anything ranging like fixing a failing test suite or tracking down why the build is no longer reproducible. Yes, the maintainer could file N upstream bugs, but upstreams are less likely to fix them (as they might have switched context and don't want to revisit something they coded several months back) and even if upstreams fix them, the maintainer would need to wait some weeks, then manually cherry-pick and patch the Debian version, and then do extra work following up on all those patches and dropping or refreshing them on next upstream release. Having a debian/ in upstream, having deb building as part of the upstream CI, and keeping the delta of Debian debian/ and upstream debian/ as small as possible makes life much easier for the Debian maintainer, and in general all distros and the whole upstream code base benefits of the extra QA. - Otto
Re: Best practices for Debian developers who are also upstreams?
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 version? https://git.notmuchmail.org/git?p=notmuch;a=commit;h=3efa2ad72c8ffd8183fab2cd6592f35e72fbb7d7 This means debian/changelog shows "wrong" version at least for one commit and that would not work in the CI pipelines I use as build products would end up with inaccurate version strings. This is something I seek to find an elegant solution for.. - Otto
Best practices for Debian developers who are also upstreams?
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 only a very small overhead work then importing and uploading new upstream releases in Debian. Is somebody else already doing something similar like this? Any tips, blogs, examples on the topic? I find it annoying to carry Debian patches for bugs that could be fixed globally at upstream, and it is also annoying when something Debian QA catches is broken at upstream and I find it out only at the time I am preparing an upload to Debian. My goals would be: - have debian/ in upstream repository, and a CI that does the bulk of Debian QA on every upstream commit and immediately gives feedback to upstream devs that "break" something from Debian QA point of view - have the delta of Debian debian/ an upstream debian/ as small as possible - fix all bugs detected in Debian directly at upstream when possible - when not possible, fix them "locally" first in Debian and eventually have it upstreamed - have it easy to compare Debian and upstream debian/ contents - bonus: import upstream releases as git operations without having to export and import tar.gz packages I have in rdiff-backup pretty much this setup already in place but I have some challenges on how to handle the debian/changelog file and a couple of other details. I would be very keen to learn from others before inventing too much of new. - Otto
Accepted mariadb-10.3 1:10.3.22-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 28 Jan 2020 22:12:28 +0200 Source: mariadb-10.3 Binary: libmariadb-dev libmariadbclient-dev libmariadb-dev-compat libmariadb3 libmariadbd19 libmariadbd-dev mariadb-common mariadb-client-core-10.3 mariadb-client-10.3 mariadb-server-core-10.3 mariadb-server-10.3 mariadb-server mariadb-client mariadb-backup mariadb-plugin-connect mariadb-plugin-rocksdb mariadb-plugin-oqgraph mariadb-plugin-tokudb mariadb-plugin-mroonga mariadb-plugin-spider mariadb-plugin-gssapi-server mariadb-plugin-gssapi-client mariadb-plugin-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 Connector/C, compatibility symlinks libmariadb3 - MariaDB database client library libmariadbclient-dev - MariaDB database development files (transitional package) libmariadbd-dev - MariaDB embedded database, development files libmariadbd19 - MariaDB embedded database, shared library mariadb-backup - Backup tool for MariaDB server mariadb-client - MariaDB database client (metapackage depending on the latest vers mariadb-client-10.3 - MariaDB database client binaries mariadb-client-core-10.3 - MariaDB database core client binaries mariadb-common - MariaDB common metapackage mariadb-plugin-connect - Connect storage engine for MariaDB mariadb-plugin-cracklib-password-check - CrackLib Password Validation Plugin for MariaDB mariadb-plugin-gssapi-client - GSSAPI authentication plugin for MariaDB client mariadb-plugin-gssapi-server - GSSAPI authentication plugin for MariaDB server mariadb-plugin-mroonga - Mroonga storage engine for MariaDB mariadb-plugin-oqgraph - OQGraph storage engine for MariaDB mariadb-plugin-rocksdb - RocksDB storage engine for MariaDB mariadb-plugin-spider - Spider storage engine for MariaDB mariadb-plugin-tokudb - TokuDB storage engine for MariaDB mariadb-server - MariaDB database server (metapackage depending on the latest vers mariadb-server-10.3 - MariaDB database server binaries mariadb-server-core-10.3 - MariaDB database core server files mariadb-test - MariaDB database regression test suite mariadb-test-data - MariaDB database regression test suite - data files Closes: 948424 Changes: mariadb-10.3 (1:10.3.22-1) unstable; urgency=medium . [ Otto Kekäläinen ] * New upstream version 10.3.22. Includes security fixes for: - CVE-2020-2574 * Update conflicts/breaks/replaces for MySQL 8.0 * Add Rules-Requires-Root definition to control file * Activate NO_UPDATE_BUILD_VERSION to make RocksDB build reproducible * Strip path from Mroonga to make the build reproducible * Update Debian Policy version * Simplify and extend Gitlab-CI testing by using more of Salsa-CI features * Prefer salsa-ci.yml naming over gitlab-ci.yml since we inherit Salsa-CI * Add Breaks/Replaces for mysql-client-5.7 that ships myisam_ftdump . [ Christian Göttsche ] * Set correct SELinux contexts on package installation (Closes: #948424) Checksums-Sha1: bf0cdea4e99c12b81ba238af960e43b47d87ddb4 4780 mariadb-10.3_10.3.22-1.dsc f92f517fc2ea893ffb3d599ade219bf0a0045265 72050820 mariadb-10.3_10.3.22.orig.tar.gz 7a46b0a13588b834b0cfa378fa5e3a6e108f459b 195 mariadb-10.3_10.3.22.orig.tar.gz.asc 9e6f7b4a47aeca013800570084e096418345710b 216264 mariadb-10.3_10.3.22-1.debian.tar.xz 7935e70328ddcb5ad3ec143902e99b115acb4b3f 9252 mariadb-10.3_10.3.22-1_source.buildinfo Checksums-Sha256: 395d56066fbd4a35e9ff9e4b1619e41857b412a47387fcf16c34265b93d67dd0 4780 mariadb-10.3_10.3.22-1.dsc 3200055dbdc27746981b3bb4bc182e2cb79dcf28ea88014b641a5b81280ccec7 72050820 mariadb-10.3_10.3.22.orig.tar.gz 1ede70600162de2876f875984a1f719665d257334612bae00583ebe658b67ea7 195 mariadb-10.3_10.3.22.orig.tar.gz.asc 1b56b2d3dc406c84d6e2d5cd6c3abaf3cb7459d0974285178b81c2bdfb308927 216264 mariadb-10.3_10.3.22-1.debian.tar.xz ea5f697ef9cf5a7d02ce1023baad812084befc293c3c4f5b60811008ee4af5c8 9252 mariadb-10.3_10.3.22-1_source.buildinfo Files: 56a08f575423de574fcac95edf902025 4780 database optional mariadb-10.3_10.3.22-1.dsc f712a5e6fde038d0c9c6d2a2cd88b84e 72050820 database optional mariadb-10.3_10.3.22.orig.tar.gz 1b596ebaf171191ed000640d1dddc573 195 database optional mariadb-10.3_10.3.22.orig.tar.gz.asc 08bd99cb35e4bb2252d34f4a92800321 216264 database optional mariadb-10.3_10.3.22-1.debian.tar.xz b4ed8ee8d0f39a45fe53d8da9ebaaa56 9252 database optional mariadb-10.3_10.3.22-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEmbRSsR88dMO0U+RvvthEn87o2ogFAl4wlxAACgkQvthEn87o 2ogjbA/+OiQen7+h8j6EMvXlyFq6TKouf/E9KL+bqLVJ7nprJKxfWHO1b3l/SJKq awIo8n72GsRqeFNGVx6fMUGTThoIfQu7jzvkrA/NtXRN0Kivqqm9Qc2FU+waw0x+ hgZElYdnC93EVlDgokj8B5XSXX752D6detAmrDVC/xhzAulS1ZxeOGhvgH+IW+TQ
Accepted mariadb-10.3 1:10.3.21-2 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 07 Jan 2020 09:01:10 +0200 Source: mariadb-10.3 Binary: libmariadb-dev libmariadbclient-dev libmariadb-dev-compat libmariadb3 libmariadbd19 libmariadbd-dev mariadb-common mariadb-client-core-10.3 mariadb-client-10.3 mariadb-server-core-10.3 mariadb-server-10.3 mariadb-server mariadb-client mariadb-backup mariadb-plugin-connect mariadb-plugin-rocksdb mariadb-plugin-oqgraph mariadb-plugin-tokudb mariadb-plugin-mroonga mariadb-plugin-spider mariadb-plugin-gssapi-server mariadb-plugin-gssapi-client mariadb-plugin-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 Connector/C, compatibility symlinks libmariadb3 - MariaDB database client library libmariadbclient-dev - MariaDB database development files (transitional package) libmariadbd-dev - MariaDB embedded database, development files libmariadbd19 - MariaDB embedded database, shared library mariadb-backup - Backup tool for MariaDB server mariadb-client - MariaDB database client (metapackage depending on the latest vers mariadb-client-10.3 - MariaDB database client binaries mariadb-client-core-10.3 - MariaDB database core client binaries mariadb-common - MariaDB common metapackage mariadb-plugin-connect - Connect storage engine for MariaDB mariadb-plugin-cracklib-password-check - CrackLib Password Validation Plugin for MariaDB mariadb-plugin-gssapi-client - GSSAPI authentication plugin for MariaDB client mariadb-plugin-gssapi-server - GSSAPI authentication plugin for MariaDB server mariadb-plugin-mroonga - Mroonga storage engine for MariaDB mariadb-plugin-oqgraph - OQGraph storage engine for MariaDB mariadb-plugin-rocksdb - RocksDB storage engine for MariaDB mariadb-plugin-spider - Spider storage engine for MariaDB mariadb-plugin-tokudb - TokuDB storage engine for MariaDB mariadb-server - MariaDB database server (metapackage depending on the latest vers mariadb-server-10.3 - MariaDB database server binaries mariadb-server-core-10.3 - MariaDB database core server files mariadb-test - MariaDB database regression test suite mariadb-test-data - MariaDB database regression test suite - data files Closes: 920994 945697 947553 Changes: mariadb-10.3 (1:10.3.21-2) unstable; urgency=medium . [ Otto Kekäläinen ] * Update Python dependencies and recommends to Python 3 (Closes: #945697) * Remove deprecated basedir config from debian.cnf (Closes: #947553) . [ James Clarke ] * Fix RocksDB on GNU/kFreeBSD (Closes: #920994) * Use versioned symbols on GNU/kFreeBSD Checksums-Sha1: b857f56b8ea25a694ce651afbb5430525abb0296 4780 mariadb-10.3_10.3.21-2.dsc 172cac94a39dc739191449ce51da536defb867e4 215824 mariadb-10.3_10.3.21-2.debian.tar.xz cda35a4749b3c420f35c4cd65a319f6e0fdffcab 9252 mariadb-10.3_10.3.21-2_source.buildinfo Checksums-Sha256: e48cfd77089397110380d9b69c3fb860c90490a293797986f864130dbc171cda 4780 mariadb-10.3_10.3.21-2.dsc 19f08f3dccd9aea68a1ca4fe083f93dbe06b6348392fdc7d4492675590fa8485 215824 mariadb-10.3_10.3.21-2.debian.tar.xz ecd10039eeb1b183cf83c3a250711adb188869c33ab17d7a2fe6a7c43f2cdc10 9252 mariadb-10.3_10.3.21-2_source.buildinfo Files: 62b375ed08db16a6b3b1214978f344e9 4780 database optional mariadb-10.3_10.3.21-2.dsc 2f0b144c006127b4bda0718713e10823 215824 database optional mariadb-10.3_10.3.21-2.debian.tar.xz badbf2a10f909f4b48a8f2193a757191 9252 database optional mariadb-10.3_10.3.21-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEmbRSsR88dMO0U+RvvthEn87o2ogFAl4ULx8ACgkQvthEn87o 2oiAQw/9Gew9zKUK0KOqRDfDeVtcLmbbh97nrHAO/CtApxGlz7gYO5t55Pt9Kn1S Cn+9zICsTQXjtxxeP2yYiK7qYjA0fuK4CL4Z4mk4oF8ME5jzkXJ1L4l03CaNmHov oTrGibrwSO6R+F5pbmMatBkKseD/PgnK45HYVe0XE0p0Bv9P82mSXdT0UHMlcMNa bBj2voWj8YfHsN3qcDa30xEZQ4eSz4+SwM4caKUQiFh0gp2NXnQ0u8Zt1IMjtO3C KNeve6hncO3kKPTQjwBtPmCRlh4oaa8hRoR5DtErCAQR/QXr0I1/kKk0BZXix8My C/bQviNisFOTSO/Ty+58iSwuxk95DmLgqq7ce8W3H2cb5+RRMMaVFRKRQ355CN+W iUChrrOGXQ1DfV2bvfNVowuouCYDT5nNGABSOvEuqGOHHFfbRbReM+FsnjfvRmSD EWegeyC9UVj8nOus3/KlbUD+RGHCmzPp68f432nmttPe0szmh4DRAgve0p8nZj8Y J34M0H8pX2uXftrpYAOw3FhA1L/uomv6sEgMidMeLL70bN1AZwgbLcoxFcX0hNUx BOI0Zi1sESSHpo1gNZRIMhy696hod7VRMAiMnkulWujYUa+sf3zjGJZo4Gm4r11M 4IkBg1syoOKhV+jvGd/plcOaNJurunvCttpejek9xMw/1/jUe/Q= =w17h -END PGP SIGNATURE-
Accepted galera-4 26.4.3-3 (source) into unstable
-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 Description: galera-4 - Replication framework for transactional applications galera-arbitrator-4 - Galera arbitrator daemon Changes: galera-4 (26.4.3-3) unstable; urgency=medium . * No-change, source-only upload after previous binary upload to NEW. Checksums-Sha1: ab583d5dd224a9faaed0b274ae6c995a20594fd7 2114 galera-4_26.4.3-3.dsc 355e2c19dfb3683119b827808486df7203427d54 17388 galera-4_26.4.3-3.debian.tar.xz 201ad22c363c5d8c49f8626515a1034e65d2c629 6747 galera-4_26.4.3-3_source.buildinfo Checksums-Sha256: 8c7755f423566d6461d2ad465260a35734132e7765eccfebc692940778fb9872 2114 galera-4_26.4.3-3.dsc 3fe61297df26eec66b99366a6186e98ff706373c48ce72326161f5c844f64285 17388 galera-4_26.4.3-3.debian.tar.xz d2393a1fb1c75bc09e1d710d229b26670ad31b8a709ad6e50358aecdb191513c 6747 galera-4_26.4.3-3_source.buildinfo Files: 851e05ff04562fed3f24203e3740af98 2114 database optional galera-4_26.4.3-3.dsc f266b42428a572ee2f3020f1465ff89f 17388 database optional galera-4_26.4.3-3.debian.tar.xz 3fd91f23266e0ee14e3b611796874f24 6747 database optional galera-4_26.4.3-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEmbRSsR88dMO0U+RvvthEn87o2ogFAl4NqC8ACgkQvthEn87o 2ohReRAAlO7e+SZZIWVaGtaaVqCQN759uM1huW3wPs2UVzgbIOMVmk/qYRNvb+fH w63UimXPM7KiR4eyey4WdgL6GZXm6mrHAIJEf4u+8jC8z1h3MXvaCGs0bRs3STka ux7hdo6QFVsM1/JhUXbBz5KcNgbUrvjcQdy17guOiTweVpuqucvm5pQyf1VoDZma L9318rTzIrF/DtrpyDKA44yBM8w5a7DQoorQVas2wz63NqlH8W2RX4s3cTFAR6AG /yrGM6rHa0LVPxruMNJCO/gP+Vi4JgeukZaEfKMpkId/U7Sp1dZlib8K/uU8sz4W J2M5cq1nn9V8AdLxATz/xuqrlhcSEqQfzh/MiQqhGXPlE9e3o4e5mcNGH4OyshP3 /qbKfcNcknyMFYcwhk/7g/nRTdc8QiZ7CeJBRuCm3REVsLnO/I3Le+6DTG+zjrVH s4rF2cjIsVAduzLlphoXfKYFRUmQZBDvfYcFi2Bbz8hUdOwuOR2kWpUC3ys1kHCA lps7jlPMNa23e8pJe96L0yDn81k0ltr246jsh2AtddteoElUn0BSqMaBeGAq3Mc8 yuSyVBIu4EEfeIzwdOt4/BZuySn25POEBGzCyllIGsbmkTMDubkTt3CfNWw7Y3WB km1Kr0E4tTFNid6/019etmhNL7unWMG/J6QJOgIAHzO12DylBx8= =kLLp -END PGP SIGNATURE-
Accepted galera-4 26.4.3-2 (source amd64) into unstable, unstable
-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 Kekäläinen Description: galera-4 - Replication framework for transactional applications galera-arbitrator-4 - Galera arbitrator daemon Changes: galera-4 (26.4.3-2) unstable; urgency=medium . * Rename galera-arbitrator-4 -> -3 forgotten form previous upload * Add proper conflicts/replaces to older Galera versions * Extend Salsa-CI tests with upgrade scenarios Checksums-Sha1: 4ba9062584b528e5014621178ced37e90ca17458 2114 galera-4_26.4.3-2.dsc 25fb8b7b4dbc7c65f16745edb7e3858fe778cba8 17348 galera-4_26.4.3-2.debian.tar.xz bd3c8a93560b02d59592cd3c55b1d9efbd3a670d 6387 galera-4_26.4.3-2_amd64.buildinfo 9535ed5d935151e5e518c0ab3acb4b8f75ac441a 912896 galera-4_26.4.3-2_amd64.deb 4140a0e69cc401cf693ef8d33ae294dc79245736 611624 galera-arbitrator-4_26.4.3-2_amd64.deb Checksums-Sha256: 13d70ff6097040dc5d3fc775421785d6221f89b044afdd99594b1e9536faa50e 2114 galera-4_26.4.3-2.dsc 0ffdd20ef63b2ddb4015b5671b0d66e920e13418db56d2d246e15531c55d47b4 17348 galera-4_26.4.3-2.debian.tar.xz 07d94c5b2609167163b400268c165646f4d04defc880828e6008221f55a2b01a 6387 galera-4_26.4.3-2_amd64.buildinfo f05ec3f313083cd4b4c5e47486178b5e16e87855f29ea68642030e11c4315ef5 912896 galera-4_26.4.3-2_amd64.deb ca0763ee633dbac4e661978aee32291a269fae7c93c88e4ae9c50e5724bf4fd2 611624 galera-arbitrator-4_26.4.3-2_amd64.deb Files: 1cbebb695a3515d8199abc4dc999c4bf 2114 database optional galera-4_26.4.3-2.dsc 85b26e8d96b6c977c43a5a1c776dd28c 17348 database optional galera-4_26.4.3-2.debian.tar.xz 20e51f21af741d13f1710d217914d595 6387 database optional galera-4_26.4.3-2_amd64.buildinfo 7906d7a74b5e7cacc9d21743a51a888c 912896 libs optional galera-4_26.4.3-2_amd64.deb bf2e3c1a498ab7c07f5c35a4e0573e7d 611624 database optional galera-arbitrator-4_26.4.3-2_amd64.deb -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEmbRSsR88dMO0U+RvvthEn87o2ogFAl4KF38ACgkQvthEn87o 2ogRYA/5AfGpERxvRMCo26T6Rxp/HzjHpOLZ/8eXfJguDXXTsK4lVGfAzPrc6aQ8 KVN8tYtZ6aCmZSzGr8qeEWwKppYUKGotuQVZQSPPiqseltrT6ntzGb6Tvm48YTom L7AiKqWptr2vjJVET1KT2eYZr2NRDpRs2Ir+E3CideDxDbAeKH/Y4O41a5GEHAje kN/XaixQ6K8VLg0tKDS2G7RY4ftEu511gdwxBwwhemye7bSRilL2IVISyNs180io FLvqtB8ioVfzn1mc98gmmzZVSfhMLm+ic3xT9ljyIEZT9t2tJKe2fqVtpPfGLYLT bfUPUOgF4rGXQxLwGRne652WQcxjk3gg3I4H1Yo+M8lKbfc1Oh1toNPK54kR7Z9o ye21Gk6J2yen1dEHTitGGJqTEnJceTLQqx0zSFvRpKv3q1onDVW9tDcMubHw1Nny XGNN2ICwvadNLtzjdpzPeY0GKrjberkMQGMOGUEy/J6zPTBJ0bvo94rEMh8VpFFo PD7/dISCqDBipc1kPRkWMP9AKbFOs3NWGGzD9bHgQ7CiK0pWWI0cbDsr6oacvBIK kef9+NkUrJcXRCYIosWBt+52EKFX6GJ575qXAgk8Ct4y75Qy/psP7Xt0JX04VRlP +JQuUvAKtYymiWEDq0l6g/ZzrTo5sq3Ot7jbwaJaXoj6BjEjdJ0= =hAFs -END PGP SIGNATURE-
Re: Help needed: conflicting interests between Salsa admins and Salsa users (Re: Git Packaging Round 2: When to Salsa)
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. > It is not a problem on the runner side. > > And as said, we are working on the other problems until we can improve > something in that part. If it is not a problem on the runner side and you don't need more runner resources, what is the reason the runner is capped at 1h? MariaDB is a huge beast and building it and running all tests take 1,5h for completely valid reasons (also note we have ccache on Salsa-CI so re-builds are much faster). Could you be kind at set back the default runner time limit to 2h as it was some weeks ago? This is stopping me and our contributors from working on putting mariadb-10.4 in Debian. It you don't intend to revert the change back to how it was? Or could you please at least state the reasons at https://salsa.debian.org/salsa/support/issues/184 ? So far you have not commented anything in your own bug tracker at salsa/support.. Thanks again for everybody maintaining and developing Salsa, the CI and all that comes with them. That has been a huge boost in my motivation to continue Debian work and makes me much more productive than ever before. - Otto
Help needed: conflicting interests between Salsa admins and Salsa users (Re: Git Packaging Round 2: When to Salsa)
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. > > For this I need to use my veto as Salsa admin. With the CI people we > have to work through too much problems first. There seems to be a conflict between the Salsa admins and users of Salsa: the more Salsa is used, the bigger becomes the maintenance burden and the more computing resources Salsa needs. There is however no inherent growth feedback loop in the system that would increase maintenance commitments as usage commitments grow. In economic terms one could say that the Salsa admins don't profit from maintaining Salsa and as demand grows there is nothing that grows the supply at the moment. The reason for Salsa popularity to grow all the time is simply because it is such a brilliant service and many Debian Developers and aspiring new contributors love to use it. Personally I've had all my packages on Salsa since early 2018 and I would never want to go back to the mix of Github and Alioth I used before. Using Gitlab-CI is nowadays an inherent part of my packaging workflow to test contributions before merging them and to do QA before uploads. Any disruptions to Salsa basically grinds by packaging work to a halt[1], it is so central for me nowadays. Since Salsa was officially launched in 2018 there has not been any [2] new members to the Salsa admins group [3]. Alexander, Joerg and Bastian have done a great job maintaining our Gitlab installation. The software suite is a beast and keeping it running well is a major effort in itself. They need help going forward. The sentiment of restricting vital use of Salsa is a sign of them trying to keep things under control. But Salsa usage needs to grow, as that is good for Debian as a project. For the Debian project I think it would be a priority to find more resources to the Salsa admin team. I think that would be the ultimate solution to the current conflict. Personally I cannot commit to maintain Salsa, unfortunately. If Salsa is out of computing resources I can however help find more sponsors for public runners. But I have the understanding that Google has donated plenty of cloud computing time and the root cause is not in lack of computing resources, but in the human scalability aspects of Salsa operations. I hope somebody else on the debian-devel list would respond to this call for help. I am sure there are many ways to help the team and it is not just about Salsa/Gitlab admin stuff, but also about creating structure in the team, triaging issues, spreading best practices for users and helping the most advanced users to grow into admins of Salsa etc. Right now we don't even have any kind of salsa-related discussion list on lists.debian.org. Thus I wanted to raise discussion on debian-devel. In my opinion Salsa is becoming a very central piece of the Debian infrastructure and it should have more attention on debian-devel and from the project leader. Thanks again for current Salsa admins for the work you've done! Salsa is amazing and I hope it will get broader attention and help so it scales to support our packaging work far into the future. [1] https://salsa.debian.org/salsa/support/issues/184 [2] https://wiki.debian.org/Salsa?action=diff=37=17 [3] https://wiki.debian.org/Salsa#Maintenance
Accepted galera-4 26.4.3-1 (source amd64) into unstable, unstable
-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 Kekäläinen Description: galera-4 - Replication framework for transactional applications galera-arbitrator-3 - Galera arbitrator daemon Changes: galera-4 (26.4.3-1) unstable; urgency=medium . * New upstream version 26.4.3 * Refresh patches after 26.4.3 import * Rename galera-3 -> galera-4 after Galera 4 import Checksums-Sha1: 06433de229e1dca8ba73ba9c9e545546d3843c7d 2114 galera-4_26.4.3-1.dsc e8987f755701f287bdb2a26e2115360ba49baf2b 3507925 galera-4_26.4.3.orig.tar.gz b348a183196f4a0b6fb589da4efb964fb6813e3e 16636 galera-4_26.4.3-1.debian.tar.xz fdea0e91a3e8f0218180eacad4081d91f0d9e9a8 6387 galera-4_26.4.3-1_amd64.buildinfo 695ca78c23dca6cf27a5be0fe558afdc9e5e953c 913860 galera-4_26.4.3-1_amd64.deb bec652b4169783490b4fb57f5b04703d23fb387a 611688 galera-arbitrator-3_26.4.3-1_amd64.deb Checksums-Sha256: 15ab5842096cd33985a3517dcff5d715742e897042a8853a9fba09c6d1cf4dd9 2114 galera-4_26.4.3-1.dsc fdde14c25c206bab6c04ee9c4c63e4e1869eb337cc1ee619437c27efb364540f 3507925 galera-4_26.4.3.orig.tar.gz d32354053208ad4dde0f583e0e330e321e3f07768efa444f761ada708ab08660 16636 galera-4_26.4.3-1.debian.tar.xz 92c36d419a5834a7b5fc996a6bba63957fffdf61469e6cbf5c343d8d5456fc7b 6387 galera-4_26.4.3-1_amd64.buildinfo 9c82e55c9ffb61687cd9206f1085ed8a62c4577c41ab30463cd4718a3fb9dcb6 913860 galera-4_26.4.3-1_amd64.deb 3956140a04b8c4ff43430859d6146efbd22ff2d7359f9d1395880bbd292859c3 611688 galera-arbitrator-3_26.4.3-1_amd64.deb Files: 75647f601c38df5b5a7308566c1ea2bf 2114 database optional galera-4_26.4.3-1.dsc d443cb732360f3622ff8f67620100094 3507925 database optional galera-4_26.4.3.orig.tar.gz 09926dc323950ea0f447c061bbc1869a 16636 database optional galera-4_26.4.3-1.debian.tar.xz 1719ea9cb7cbf1e72067f779e52b109e 6387 database optional galera-4_26.4.3-1_amd64.buildinfo 42f58e98f58df205ac79458b41dc8282 913860 libs optional galera-4_26.4.3-1_amd64.deb 91232e51e4e4660543b2212a8f43334e 611688 database optional galera-arbitrator-3_26.4.3-1_amd64.deb -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEmbRSsR88dMO0U+RvvthEn87o2ogFAl3/Zc4ACgkQvthEn87o 2oi9mBAAmJcrSNRbu44eGeKsniWT43qKWBijaVg4ipVCd/ohcA+KrDgEl+WSIzuw dow2xdVfmqmw4FQYE4GIcHFLX8jyConK7o7GpQfDl/0WOoePS23CRCft0mfXHQYH rHtiPafFMe2HfwpHxs+mDND6rbOmUVtap+/U/HtovyDFh1h0AVXIkpQqa/CZAWUY w1BEpiQY2LyFWsyCH2Oa189o9JnXNMApVzlGfdaH4EmRR55DSD6UEQpIKQNdAEx8 bE5ENXR4jikL6WpZzAb3fG88zDWIaJa13gUioMVHQ/qbCZi8oLsCq3IEYp8ttgq0 WcEfoL4iCkcgRxGnTAsaLLl8cBI+xKlGqJDcLzsIyxXPDuzo9C8HOtTD1BKtIHak yUgBLdbLP545Ihuua6GSPBlmp/p9ngdDp2DKOOEqbsa+hqv1X4KFv5ERe0qJdfFu tLokLxXMVS5WbHgb+LCXWR8kfeBGmrEgBU6G4fJEYhd+gQ0HEWHCiTtIlsw3v8t4 o9kdsGwh/4dsAdMAosiwDAa4zL3ivNuqx4QLMB0aHfm76J8aBLokIeNRdO01xhBM SnrjE9fk0YaLW8gCGgYuW1W0xBQC9iDBykEtiUTM7E89JQUyrD6d7AR2j8RQpn7E fN/U2G2FC9fwi52vADWxBUqa9hkwK8zAXBt09baLN4JzBiL7k1w= =JqTs -END PGP SIGNATURE-
Accepted galera-3 25.3.28-2 (source) into unstable
-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 Description: galera-3 - Replication framework for transactional applications galera-arbitrator-3 - Galera arbitrator daemon Changes: galera-3 (25.3.28-2) unstable; urgency=low . [ Debian Janitor ] * Use secure URI in debian/watch. * Update standards version to 4.4.1, no changes needed. * Bump debhelper from old 9 to 12. * Fix field name typos in debian/copyright. * Remove obsolete fields Name, Contact from debian/upstream/metadata. Checksums-Sha1: 029a9c8527269c18a69f14bba8db6416d9f1a664 2374 galera-3_25.3.28-2.dsc d3b89354926184054521b605c3df26357bad647e 16564 galera-3_25.3.28-2.debian.tar.xz db7ce2422e6e455195141e612dd2ae9ae62c8676 6751 galera-3_25.3.28-2_source.buildinfo Checksums-Sha256: ad1e770195cc571260a966c91a97d64571535aa8043f0a45700f64675690ee21 2374 galera-3_25.3.28-2.dsc 266508847313bfda61815365f60b120e95a1753b5aec4f8d32ba7a8d676ee690 16564 galera-3_25.3.28-2.debian.tar.xz ee6c989bc5fa8ba8ba9c2bb0558a5f8158b421ae89d6dc21fa20793e3d2b67fa 6751 galera-3_25.3.28-2_source.buildinfo Files: 47e91f9347cd690e7925c41ce3a6153e 2374 database optional galera-3_25.3.28-2.dsc 37939b2e242c04c011d8f1cb7efe 16564 database optional galera-3_25.3.28-2.debian.tar.xz 79cf757c242dd8ca38c57046e6ed787e 6751 database optional galera-3_25.3.28-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEmbRSsR88dMO0U+RvvthEn87o2ogFAl333EUACgkQvthEn87o 2ogOvBAAgqMDcm8Mjl7p+U4QNh3Mlyggk4+MUsmEZf8NTm0BeOz3qkyfzyVVIOZG dNj5Dj+3WNGEG6BiMXjExCrMjRpxMqlxyrJAvqRuQPM0r3WYO4cBTgDaFEHyIy5U ljJFpfJxSjve4YiIyFo5craK1wnvfqS+suVy81zgkfYlFwudf/b9qB0nBRPoqlF8 SDD2HsLE2moGlF7kw2UvPFxHM44PzG35BgSHm+SO5QgQU0DoREXBRIBIZHIPHBzG xnvqr9wKsKmajQJh/IuALAPepFPDNt+BoQ4Lw8jyWdAE9GHx8h8t3mBuoBticbt6 oeqrQgRz1yvF4owC9kKgL9YS4Xq1bRahKfo3ScfvfTdNxG3Vx5cs8keYA5RTqqxJ 4TMR0LZqztBUvgJM515ryj0GbB5AkbaZyYbOl1A/kJraD8Br98DIRdI/usTumWT6 ZHsv3naZSCBdCFKaq2ASTRJe/OUbWl7QyysaTGcawwiNBtD6rfiHhkEYsgcDYq+3 xiknuui86aBv0eJ/lioRuNFoiJybNHfKwLMj4WblyA6eQ5WrRgKnNvHHTH+tQUwC RqyT6r3z/UzXSkHHbp1WBako3segFJ3EWcJ9DSEK1tR72NbTZuL2j7xj4TkqQFKH GCC8KIZHDNVQ+FcpyJ9qQDgUgcbJqPr/Q8p7x5fJPrERAdixB8I= =o/hj -END PGP SIGNATURE-
Accepted mariadb-10.3 1:10.3.21-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 11 Dec 2019 18:01:43 +0200 Source: mariadb-10.3 Binary: libmariadb-dev libmariadbclient-dev libmariadb-dev-compat libmariadb3 libmariadbd19 libmariadbd-dev mariadb-common mariadb-client-core-10.3 mariadb-client-10.3 mariadb-server-core-10.3 mariadb-server-10.3 mariadb-server mariadb-client mariadb-backup mariadb-plugin-connect mariadb-plugin-rocksdb mariadb-plugin-oqgraph mariadb-plugin-tokudb mariadb-plugin-mroonga mariadb-plugin-spider mariadb-plugin-gssapi-server mariadb-plugin-gssapi-client mariadb-plugin-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 Connector/C, compatibility symlinks libmariadb3 - MariaDB database client library libmariadbclient-dev - MariaDB database development files (transitional package) libmariadbd-dev - MariaDB embedded database, development files libmariadbd19 - MariaDB embedded database, shared library mariadb-backup - Backup tool for MariaDB server mariadb-client - MariaDB database client (metapackage depending on the latest vers mariadb-client-10.3 - MariaDB database client binaries mariadb-client-core-10.3 - MariaDB database core client binaries mariadb-common - MariaDB common metapackage mariadb-plugin-connect - Connect storage engine for MariaDB mariadb-plugin-cracklib-password-check - CrackLib Password Validation Plugin for MariaDB mariadb-plugin-gssapi-client - GSSAPI authentication plugin for MariaDB client mariadb-plugin-gssapi-server - GSSAPI authentication plugin for MariaDB server mariadb-plugin-mroonga - Mroonga storage engine for MariaDB mariadb-plugin-oqgraph - OQGraph storage engine for MariaDB mariadb-plugin-rocksdb - RocksDB storage engine for MariaDB mariadb-plugin-spider - Spider storage engine for MariaDB mariadb-plugin-tokudb - TokuDB storage engine for MariaDB mariadb-server - MariaDB database server (metapackage depending on the latest vers mariadb-server-10.3 - MariaDB database server binaries mariadb-server-core-10.3 - MariaDB database core server files mariadb-test - MariaDB database regression test suite mariadb-test-data - MariaDB database regression test suite - data files Changes: mariadb-10.3 (1:10.3.21-1) unstable; urgency=low . [ Faustin Lammler ] * Remove no more needed lintian overrides . [ Otto Kekäläinen ] * New upstream version 10.3.21 Checksums-Sha1: 9d55a2c4b9d520927b20cd25042333c1f3353a7e 4780 mariadb-10.3_10.3.21-1.dsc d5605b1f175e4f0b6a1a481e30ee5ef1344199a0 72005618 mariadb-10.3_10.3.21.orig.tar.gz 8d02132291ebdf86ffbbfd1f63610a3d4586a4a0 195 mariadb-10.3_10.3.21.orig.tar.gz.asc 8b4b647b6f8929024e7dabbeef1eeac498e5d5fa 214288 mariadb-10.3_10.3.21-1.debian.tar.xz f2131b52270205cc1db1d16901950b95d447a8c4 9252 mariadb-10.3_10.3.21-1_source.buildinfo Checksums-Sha256: d6b62c61246c68ee1763d7ce97fec31c918ea71aba53c737de39410e2293162f 4780 mariadb-10.3_10.3.21-1.dsc f95bd4b670fb86082d1e3f0c4299ebcd40bda856b111e3f02ab647b0e9ba5e8f 72005618 mariadb-10.3_10.3.21.orig.tar.gz f41c8ebfe7b9598edc776f271b32643aec2448ac490c36db11d7c6493e395b9f 195 mariadb-10.3_10.3.21.orig.tar.gz.asc 08b019319b938a95fa97dd090e689ef37e806fcb9f1a8d24e469de4f11daa39b 214288 mariadb-10.3_10.3.21-1.debian.tar.xz edc2d3e41cd136e15529c815ac256e90961785abc74a59ea153d22f04c7fa130 9252 mariadb-10.3_10.3.21-1_source.buildinfo Files: 4da4964151daa3daede29b89fbf006b4 4780 database optional mariadb-10.3_10.3.21-1.dsc c5b9ed98f2f57f7b809d4ec9c1515107 72005618 database optional mariadb-10.3_10.3.21.orig.tar.gz df5f1abd7590c7b12aa8145fbd017104 195 database optional mariadb-10.3_10.3.21.orig.tar.gz.asc 4c6e233380fb4cde857b31ec879f000f 214288 database optional mariadb-10.3_10.3.21-1.debian.tar.xz a3ec498db0dc8dbed3e953b913bf73f3 9252 database optional mariadb-10.3_10.3.21-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEmbRSsR88dMO0U+RvvthEn87o2ogFAl33az8ACgkQvthEn87o 2oiyMg//aH+62p18A41rQxzX2RhbsLXRUyX4dHivXPo/Y5BHA/hg6LAawvFeCI5F ynalVOeuxwgFXoNZEvAERlVBlBQaZf9wlqsgmLZuFYocJbBh8MALLi1+zX6dFElU cVI64YTqmDYR11rP5VMjjMb4tZq2BMIftEkbhrDYaDExaSSrAy/zNE2vjfJPo/ck y5blZFV5+GehBLDrzEdlb+lzXiumvAwp0CdbeZYFE5/T6r4fE+MlLim8PKOYapS1 6HXuY/WYtEm+Ld9ESlOeyxLYo0xOzCyAKRri/9v5fyF65NzQzj/VI5kMaN2HJ5UO ivx3gPnhFWGQmRFYpbgOoQB8O8BF6BqXjuFcUERZvtPtbo0r2nnOxMxzwYk4QKux PCMFZzk25I685ISHAojsL2eO4hk5Po8h4PQOXnFBmAbADB/JRRjt3KVAogb7/OGy iixYhD7ulPXkuBuDbLRgLFd9vkcZyKk40OMqlnI5zzFTu/vVDFtDvyto2nqKnNn2 x8nhenCHGDZdeOffXdi1jGs4AQu+C+2c+vMp0M+Dz23HF0HiSmtfe+EZLAqaBMwz gXOTZuAGiWQUQ7KiLI4N4O+2nTzJZW6bc2gll1IdRq5AHu2UXBgs4xZRSLMRBPb2 Ztivv0QsC0BmyyhkgykSvS7XBV5on23auUTPnwAsLB57/UTIX/g= =AmZG -END PGP SIGNATURE-
Accepted mariadb-10.3 1:10.3.20-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 11 Nov 2019 23:55:37 +0200 Source: mariadb-10.3 Binary: libmariadb-dev libmariadbclient-dev libmariadb-dev-compat libmariadb3 libmariadbd19 libmariadbd-dev mariadb-common mariadb-client-core-10.3 mariadb-client-10.3 mariadb-server-core-10.3 mariadb-server-10.3 mariadb-server mariadb-client mariadb-backup mariadb-plugin-connect mariadb-plugin-rocksdb mariadb-plugin-oqgraph mariadb-plugin-tokudb mariadb-plugin-mroonga mariadb-plugin-spider mariadb-plugin-gssapi-server mariadb-plugin-gssapi-client mariadb-plugin-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 Connector/C, compatibility symlinks libmariadb3 - MariaDB database client library libmariadbclient-dev - MariaDB database development files (transitional package) libmariadbd-dev - MariaDB embedded database, development files libmariadbd19 - MariaDB embedded database, shared library mariadb-backup - Backup tool for MariaDB server mariadb-client - MariaDB database client (metapackage depending on the latest vers mariadb-client-10.3 - MariaDB database client binaries mariadb-client-core-10.3 - MariaDB database core client binaries mariadb-common - MariaDB common metapackage mariadb-plugin-connect - Connect storage engine for MariaDB mariadb-plugin-cracklib-password-check - CrackLib Password Validation Plugin for MariaDB mariadb-plugin-gssapi-client - GSSAPI authentication plugin for MariaDB client mariadb-plugin-gssapi-server - GSSAPI authentication plugin for MariaDB server mariadb-plugin-mroonga - Mroonga storage engine for MariaDB mariadb-plugin-oqgraph - OQGraph storage engine for MariaDB mariadb-plugin-rocksdb - RocksDB storage engine for MariaDB mariadb-plugin-spider - Spider storage engine for MariaDB mariadb-plugin-tokudb - TokuDB storage engine for MariaDB mariadb-server - MariaDB database server (metapackage depending on the latest vers mariadb-server-10.3 - MariaDB database server binaries mariadb-server-core-10.3 - MariaDB database core server files mariadb-test - MariaDB database regression test suite mariadb-test-data - MariaDB database regression test suite - data files Changes: mariadb-10.3 (1:10.3.20-1) unstable; urgency=high . * New upstream version 10.3.20. Includes fix for regression: - MDEV-20987: InnoDB fails to start when FTS table has FK relation * Remove obsolete fields Name, Contact from debian/upstream/metadata * Gitlab-CI: Print artifact sizes to ensure it stays under 100 MB * Gitlab-CI: Adapt CI jobs for Debian Sid work * Update README.Maintainer with current Debian and Ubuntu release statuses Checksums-Sha1: 3e87c24d1aef18d820e26bd0663808c9a33a9115 4780 mariadb-10.3_10.3.20-1.dsc 169a9e158a32c98443a375f265fac55ba30c94f4 71990355 mariadb-10.3_10.3.20.orig.tar.gz 8afafa8bd01b29f58ed517c053db636143be4507 195 mariadb-10.3_10.3.20.orig.tar.gz.asc b0b7d301693d39e3f1cb15ea7975f82d7aab9b7a 214472 mariadb-10.3_10.3.20-1.debian.tar.xz 47b3416d4517302aedaba7e4c6994f503064f781 9262 mariadb-10.3_10.3.20-1_source.buildinfo Checksums-Sha256: 8c14aea4aa0fa5a65c4c6401275239d84cfbc2205ca228e0e3f6d7c9b9263c85 4780 mariadb-10.3_10.3.20-1.dsc 53818f2d684e060143b4d8293da44c7f09cc676d71959405f84e6dc8affbc492 71990355 mariadb-10.3_10.3.20.orig.tar.gz 4d401a96d48db10680c0f939d24b33b37a1a632d376c6be811ff30bfc60f31f6 195 mariadb-10.3_10.3.20.orig.tar.gz.asc e6268c3994de2063cd75cbcc934b6ea085a2b947300c9e1217a5bd1957dcaf62 214472 mariadb-10.3_10.3.20-1.debian.tar.xz b971439263edff283bd11d945c20e3f1affee05b3ed26a9bc6b385c0c0868569 9262 mariadb-10.3_10.3.20-1_source.buildinfo Files: 6ae94b6c1107730f06108a0b8f5b8099 4780 database optional mariadb-10.3_10.3.20-1.dsc a87a9532568c0ed50d25ce7e7c60d67d 71990355 database optional mariadb-10.3_10.3.20.orig.tar.gz b0147a579cc64093b1e49a4c92dd1ff5 195 database optional mariadb-10.3_10.3.20.orig.tar.gz.asc b1f643042e74e86c368172a54d93f881 214472 database optional mariadb-10.3_10.3.20-1.debian.tar.xz 4c7a778694e4b9ca8288817ce8933f2b 9262 database optional mariadb-10.3_10.3.20-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEmbRSsR88dMO0U+RvvthEn87o2ogFAl3Ke8wACgkQvthEn87o 2ogOWA//cDaNeVfzOw40C7fVysD6I4sZvQrxn9MwS0a80kScj/sUwfsetAp1qO4O oqYX5pWGKYxh84vCLLGzW2G7S2JEoHB2q6l94eyrvKXlX5u9RSkr+SdjGZE4ngRg VVhNbDLD/IiDsV7IVvaiW0AuguermJXjp3J5es07vV8a9OkTnfZhGiuKDj4og+P3 mUAzGY062GAvxpsV94QMi4gOB38q4pR+m06Slo8yJTDV32dZY/qZ17rT86vm9ABv ja5jjnJuADplv0n/MN/ks2NTUL9tnjFY+ofEdvUUDSSVg+tlaWJZs/Epxz+NXG8V 2GJks77CxSn8s+D6rES211r9D3ttShI4A0cRZVd6Vs4EiSejtqRJy1cAPt+vM3q2 yEwBdRd3xJoDZYXdCW3UzLdgrT+0ClOjMx3t0DNacIq4YqvKRiVsXdA7WGlHFC9/ +qym3Fyg9jCh/Rr87kXi2/zpRAtigDISwfxj8wHTD53daUGk179u8wlBZ+eieHG5
Accepted mariadb-10.3 1:10.3.19-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 07 Nov 2019 21:26:49 +0200 Source: mariadb-10.3 Binary: libmariadb-dev libmariadbclient-dev libmariadb-dev-compat libmariadb3 libmariadbd19 libmariadbd-dev mariadb-common mariadb-client-core-10.3 mariadb-client-10.3 mariadb-server-core-10.3 mariadb-server-10.3 mariadb-server mariadb-client mariadb-backup mariadb-plugin-connect mariadb-plugin-rocksdb mariadb-plugin-oqgraph mariadb-plugin-tokudb mariadb-plugin-mroonga mariadb-plugin-spider mariadb-plugin-gssapi-server mariadb-plugin-gssapi-client mariadb-plugin-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 Connector/C, compatibility symlinks libmariadb3 - MariaDB database client library libmariadbclient-dev - MariaDB database development files (transitional package) libmariadbd-dev - MariaDB embedded database, development files libmariadbd19 - MariaDB embedded database, shared library mariadb-backup - Backup tool for MariaDB server mariadb-client - MariaDB database client (metapackage depending on the latest vers mariadb-client-10.3 - MariaDB database client binaries mariadb-client-core-10.3 - MariaDB database core client binaries mariadb-common - MariaDB common metapackage mariadb-plugin-connect - Connect storage engine for MariaDB mariadb-plugin-cracklib-password-check - CrackLib Password Validation Plugin for MariaDB mariadb-plugin-gssapi-client - GSSAPI authentication plugin for MariaDB client mariadb-plugin-gssapi-server - GSSAPI authentication plugin for MariaDB server mariadb-plugin-mroonga - Mroonga storage engine for MariaDB mariadb-plugin-oqgraph - OQGraph storage engine for MariaDB mariadb-plugin-rocksdb - RocksDB storage engine for MariaDB mariadb-plugin-spider - Spider storage engine for MariaDB mariadb-plugin-tokudb - TokuDB storage engine for MariaDB mariadb-server - MariaDB database server (metapackage depending on the latest vers mariadb-server-10.3 - MariaDB database server binaries mariadb-server-core-10.3 - MariaDB database core server files mariadb-test - MariaDB database regression test suite mariadb-test-data - MariaDB database regression test suite - data files Changes: mariadb-10.3 (1:10.3.19-1) unstable; urgency=high . [ Otto Kekäläinen ] * New upstream version 10.3.17. Includes security fixes for: - CVE-2019-2938 - CVE-2019-2974 * Update symbols to match latest libmariadb_3 * Drop systemd service patch applied upstream . [ Faustin Lammler ] * Fix typo in Readme Checksums-Sha1: 5753b5942daa05fb70e68bba6152306b637a567b 4780 mariadb-10.3_10.3.19-1.dsc bc029650def064558c0eb21ddc9116d67e306e82 71989451 mariadb-10.3_10.3.19.orig.tar.gz 17b5604c207afc2ba4e7d8297f514e12d5432063 195 mariadb-10.3_10.3.19.orig.tar.gz.asc 16708eeffc40b23fdc4466f8e2ad903694d0a0c6 214192 mariadb-10.3_10.3.19-1.debian.tar.xz e1cca1edb376f1bbeefcf9566abbf3d0ee7655a7 9259 mariadb-10.3_10.3.19-1_source.buildinfo Checksums-Sha256: 1d2bbb83749df7cca7d7c8c0f8d1a24f03168b96a96b7b45b09a9a691f34ed03 4780 mariadb-10.3_10.3.19-1.dsc f20dea317fa65dbe387d43ea7fbb0f3240ce4ad1d4f6adb3be4c1d771d95deb7 71989451 mariadb-10.3_10.3.19.orig.tar.gz 03eaf83d59314b16fa2ce7e8fca4c0dc0da8fe00dedab932685e5c3e19acb254 195 mariadb-10.3_10.3.19.orig.tar.gz.asc 0668fedcaefc27bd2477e85c96f7a0e5a92b72a4436525ebd086c9cb2e7bd183 214192 mariadb-10.3_10.3.19-1.debian.tar.xz 9eb1ffc9b4078e73e3b4d8708635e39b8b509fe3c362429d10abc633af984280 9259 mariadb-10.3_10.3.19-1_source.buildinfo Files: ed0d19cc4eaa2c47293b5e32a0ca8801 4780 database optional mariadb-10.3_10.3.19-1.dsc de8eb9a7d45d21e2d96e46cdc7c6e036 71989451 database optional mariadb-10.3_10.3.19.orig.tar.gz 3badc68459193e52531961167e07f7f3 195 database optional mariadb-10.3_10.3.19.orig.tar.gz.asc 90ba98ceff588f361e41465f7caab7ef 214192 database optional mariadb-10.3_10.3.19-1.debian.tar.xz 34506348460cbdc79ed2fe07d024298d 9259 database optional mariadb-10.3_10.3.19-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEmbRSsR88dMO0U+RvvthEn87o2ogFAl3EcLMACgkQvthEn87o 2oh1rBAAnbCNtCBYhskzG28R1hyEFbcdxA64+57EMwup7mEmFoTaF19ZuM16LVYE TnfE8gGBaCozgr0F6hVVxMzRVE8RnJIrBjFjC3+iVF0kb5VnWmd3mpiL1kmBRNbc Le2O6DjtENt9md5bl62SeoOu3eLHqrdfTGPXsWzD8/hz02TYkrEdZtiAt5erl4gQ TfHd2Tb0g7NRgLIYhq5Dn2hMEJGVm1urwNaUmDBIHFTbsVCT8pjs6FoeHKGVi4xv PeaSLPU6F4o+KkhDYAPXmejCp6Ngbw10QXzaYihOTkTwtm7/aXyr09SeWaHTlBsO x7Z25vkFBtvKCeSJGbM0+50rDxTK/89LGI7SfTgElLmxQMPBGKcAtP5+ExOm5QmH rZDHhBTdmjKJrLxEY5DdKeWMVbvZo0mLjJqoLVJoLeXmNCeGaFdm530224+HG1zQ Cst194uM8xiFMTcH9K1YijRA9XSJ56tt9q3PGC0BIQagWSLOKIkcSxYavvrFhGTa gU3LG9d1bvRXaBnasyCn+MHepLgfsLSEjY3CgfwMF8e2ekIluXDRL1TODommaN24 3u3lfytp8yTvLHBUN+eOXy2ap4y3dDGXa1fcBh0qGDkZUQ8+3gG8vWupP+DxAvo9
Accepted entr 4.3-1 (source) into unstable
-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 commands when files change Closes: 914660 Changes: entr (4.3-1) unstable; urgency=low . [ Yuri D'Elia ] * New upstream version 4.3 * Update libbsd-overlay.patch to use the bundled kqueue wrapper * Allow overriding pkg-config and DEB_HOST_ARCH_OS (Closes: #914660) * Do not require root for building * Switch to debhelper 12 * No longer alias NEWS as the upstream changelog * Update Standards-Version to 4.4.1 Checksums-Sha1: ed594d8338adb134adc2e9e8ceabc5d70e02adfd 1841 entr_4.3-1.dsc 4dc984ccef78aa3d12ba74632cddc5a6607dbf35 24118 entr_4.3.orig.tar.gz 918e054a0af4f95740a2a498e3fe31da81eef804 7128 entr_4.3-1.debian.tar.xz 46506936dd0e9052441e0663e896cda1033a5d24 6376 entr_4.3-1_source.buildinfo Checksums-Sha256: 13a9bc56ee1d6492a47c416c9acd1513a02abe769b26daa174abd604ac81dfd7 1841 entr_4.3-1.dsc 68404dfc1e04546328e75f2edd61da095490937f44202a2821dc492f2e09809e 24118 entr_4.3.orig.tar.gz 09718e98f58349a7dc53e19d45f4ff41dfe2c764939d5f7ee2d7057dfbd7aa24 7128 entr_4.3-1.debian.tar.xz d8b93e6e4e86d5b44984b1b16424d82ac6109b8302ac3b20b667556f494ed72f 6376 entr_4.3-1_source.buildinfo Files: d932dc6e35f5d97efc788d103c415093 1841 misc optional entr_4.3-1.dsc 57c207aaeb6d43679e70f3d20e1140f7 24118 misc optional entr_4.3.orig.tar.gz 3e12bbae1c5bbe9ef789d860d55ec487 7128 misc optional entr_4.3-1.debian.tar.xz 60c9689cec3a3b5656b66d3e850e7c49 6376 misc optional entr_4.3-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEmbRSsR88dMO0U+RvvthEn87o2ogFAl20cCQACgkQvthEn87o 2ohijQ/6AlRe7bbyWYdBx4xCHXthtOtvNkWPPM5LSlhlQ59/vEPIf+bKs3VFDhNd 7WuOKDvrIR9zu/qWzWn8RKMzkEY/e0vsDCyYCexprF0XjBTikNltZSjLQvQ4xW9l 7W5z79CAEQtfT5OP3j1mjcrrT4UkW2Z08ObURKG1e5thujau7mWbrNI+azxth8dF Fe8wCH1Buz4VjfJEsHifSk9BaNhkAmjnlYFcBoKMeQWE/c2eyWXiAUOvtVdt5YFM b+bXCAqS0+zM0gmbOczt1ONb9/Tz5xz0iKjYChlfj/gJ767FD+FOjrXKdYEDtgnG I4VWtJQSSXs9XkYVdkafu2gbZ+iKyTV/2YR7GSQX1hVKkOJXXNF85bnNbuhDeMvt rnhvu+saQEDOdGgTBqqTE1kB/jFBvhqIyRmh0xK2xoon2AyuV4tWgMM1TtyI9UBL 214Lqcv6RZQDrBgkOsl7/WWPRjxYLRWNh7Ol/d6SBl2OrUtfSaARLkS5mGPYmhaz rBWmH6gHemnotXYl1zveZzyTJC0RwsGk4TEyeq0G9ELUw2v9GYvQEO31Rj+ga54N L8jNvfGxAle1f5IYLldGu08OrtqtX42OX9tD3P26ZcRc8pIxQF3N7uq/4KPhjPxN gmGCgRHY9b/6auIkWSI7JFEU7xARZ99daQddSdOtcD/LCyPGWfg= =YSnh -END PGP SIGNATURE-
devscripts uninstallable in Debian Sid due to unmet dependencies
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 root@dda7794f2e25:/# apt update Get:1 http://cdn-fastly.deb.debian.org/debian sid InRelease [139 kB] Get:2 http://cdn-fastly.deb.debian.org/debian sid/main amd64 Packages [8244 kB] Fetched 8383 kB in 8s (1107 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done 24 packages can be upgraded. Run 'apt list --upgradable' to see them. root@dda7794f2e25:/# apt install devscripts Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: devscripts : Depends: libipc-run-perl but it is not going to be installed Depends: libmoo-perl but it is not going to be installed Depends: libwww-perl but it is not going to be installed Recommends: libgitlab-api-v4-perl but it is not going to be installed Recommends: licensecheck but it is not going to be installed Recommends: lintian but it is not going to be installed Recommends: liblwp-protocol-https-perl but it is not going to be installed Recommends: libsoap-lite-perl but it is not going to be installed E: Unable to correct problems, you have held broken packages. root@dda7794f2e25:/# apt install lintian Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: lintian : Depends: libapt-pkg-perl but it is not going to be installed Depends: libcgi-pm-perl but it is not going to be installed Depends: libclass-accessor-perl but it is not going to be installed Depends: libclone-perl but it is not going to be installed Depends: libemail-valid-perl but it is not going to be installed Depends: libio-async-loop-epoll-perl (>= 0.20) but it is not going to be installed Depends: libipc-run-perl but it is not going to be installed Depends: liblist-moreutils-perl but it is not going to be installed Depends: libmoo-perl but it is not going to be installed Depends: libxml-simple-perl but it is not going to be installed Depends: libyaml-libyaml-perl but it is not going to be installed Recommends: libperlio-gzip-perl but it is not going to be installed E: Unable to correct problems, you have held broken packages. root@dda7794f2e25:/# apt install libmoo-perl Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libmoo-perl : Depends: libimport-into-perl but it is not going to be installed Depends: libmodule-runtime-perl (>= 0.014) but it is not going to be installed Recommends: libclass-xsaccessor-perl (>= 1.18) but it is not going to be installed Recommends: libsub-name-perl (>= 0.08) but it is not going to be installed E: Unable to correct problems, you have held broken packages.
Accepted galera-3 25.3.28-1 (source) into unstable
-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 Description: galera-3 - Replication framework for transactional applications galera-arbitrator-3 - Galera arbitrator daemon Closes: 940200 Changes: galera-3 (25.3.28-1) unstable; urgency=medium . * New upstream version 25.3.28 (Closes: #940200) * Remove patch for #927846 as it was applied upstream. * Mark autopkgtests with new 'superficial' as it applies to this package Checksums-Sha1: 19f23e35896e5108c6bbccbcfa6b7fd125fcb0cc 2377 galera-3_25.3.28-1.dsc 3d60fc0d850cb8b36f2396b02d4df5b1cb3db2ba 3381709 galera-3_25.3.28.orig.tar.gz 0f1f487781208112f7bfb0f9617f3c32e6a1 473 galera-3_25.3.28.orig.tar.gz.asc 5a312424c42e31ec7a68b855bb803dfd1dc255fa 16560 galera-3_25.3.28-1.debian.tar.xz 663da65ca60c55d5927e5e438ab6f499674eeaea 6708 galera-3_25.3.28-1_source.buildinfo Checksums-Sha256: a9256e92ec363bc03eece866939a48e3bbb5fa38ba76676dcbd8e2565444b2e6 2377 galera-3_25.3.28-1.dsc 4ad97d7b3108757e7b6d73529822313e7f291d87e1ef70e4554e489780e95d79 3381709 galera-3_25.3.28.orig.tar.gz e461d16ab0ad967c828d683a09e042504cbff7776d57b81f8a440b75cf94f614 473 galera-3_25.3.28.orig.tar.gz.asc 5153f60593b6bc2242326ce99b5f49637db1e2af733e5b60bcb43f4e2e9b1352 16560 galera-3_25.3.28-1.debian.tar.xz e201c523dfc1f55a5a4e5d81f4e887d68523cbf19029571140f27bf9e3650e49 6708 galera-3_25.3.28-1_source.buildinfo Files: 4159038ebe69f8d3bab6aba430e30be6 2377 database optional galera-3_25.3.28-1.dsc 67e3b8008d4ca888dbb0f3bb59678f61 3381709 database optional galera-3_25.3.28.orig.tar.gz 8bc6f69f50871eb6268916b7112fb34d 473 database optional galera-3_25.3.28.orig.tar.gz.asc 28df5a488bda64ffdb3b1b8f2be8112a 16560 database optional galera-3_25.3.28-1.debian.tar.xz 5405de31cce8bcc773328e93e9f7bbdc 6708 database optional galera-3_25.3.28-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEmbRSsR88dMO0U+RvvthEn87o2ogFAl1/ttYACgkQvthEn87o 2oisEg/9GEUtM3fptcvDJ8fhzZSRA/QOwPrNrB3gwCjMbpstquyhMc9FgdiXLhNB aIZHAvWTsrBi0c0Y3OaNxcAhZAYRyJBy7bu7a4SEXWFY+YbqchmSM2Hy47dvT+B/ /aJCFcdsH4fVx0dzcx3Iq1maSUFNZh8ELsLU18cafkzdxYVH0eALBSqCE51cZnez Ublh9lQe+e0oDYzyH2ue4hXuhfjYzD0HScw/mlVmLHY0MIK6pExrllPA78D+1mA0 J8tqyh23WinJ6APSWWju8v0NxICGR/6K8Mskm0Xb2hKpXhlC3wplY8pqOL6fXD+d IH1FbzU6buJtD8lvosSrfuI6bRb5r4R5bqZtmQgdAO3yuEcTA0wECCRyfiCFZoM9 RLOBRD31gqeTr2SRKbJeq9DbkgTBkj11RGTIecUoAM/tTXwb6n6MUPN37d4osgOU LboHiAGFBLMTSxQfniM+9O+v0MSaD16ypROlV1Y22QHwJe5hdVNd4Alu04+Rdy7V oE8AuLtjov5gl6f38ou8c9Pqm9RP4maj3m9rFNySL9TL8c26kU+l1ZW8ztQ6jx98 bwHPK/2ooiH/CQ5KVT/l+iZJ405z896zERslcP9v0F15x6NTjA/yMvhLk/iZnb+w NcC4tJCEdl50PpWzisZflYHjhZlWXLMfVuBGgSqRB4w7D/bpl1U= =ccej -END PGP SIGNATURE-
Accepted mariadb-10.3 1:10.3.18-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 12 Sep 2019 15:51:04 +0300 Source: mariadb-10.3 Binary: libmariadb-dev libmariadbclient-dev libmariadb-dev-compat libmariadb3 libmariadbd19 libmariadbd-dev mariadb-common mariadb-client-core-10.3 mariadb-client-10.3 mariadb-server-core-10.3 mariadb-server-10.3 mariadb-server mariadb-client mariadb-backup mariadb-plugin-connect mariadb-plugin-rocksdb mariadb-plugin-oqgraph mariadb-plugin-tokudb mariadb-plugin-mroonga mariadb-plugin-spider mariadb-plugin-gssapi-server mariadb-plugin-gssapi-client mariadb-plugin-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 Connector/C, compatibility symlinks libmariadb3 - MariaDB database client library libmariadbclient-dev - MariaDB database development files (transitional package) libmariadbd-dev - MariaDB embedded database, development files libmariadbd19 - MariaDB embedded database, shared library mariadb-backup - Backup tool for MariaDB server mariadb-client - MariaDB database client (metapackage depending on the latest vers mariadb-client-10.3 - MariaDB database client binaries mariadb-client-core-10.3 - MariaDB database core client binaries mariadb-common - MariaDB common metapackage mariadb-plugin-connect - Connect storage engine for MariaDB mariadb-plugin-cracklib-password-check - CrackLib Password Validation Plugin for MariaDB mariadb-plugin-gssapi-client - GSSAPI authentication plugin for MariaDB client mariadb-plugin-gssapi-server - GSSAPI authentication plugin for MariaDB server mariadb-plugin-mroonga - Mroonga storage engine for MariaDB mariadb-plugin-oqgraph - OQGraph storage engine for MariaDB mariadb-plugin-rocksdb - RocksDB storage engine for MariaDB mariadb-plugin-spider - Spider storage engine for MariaDB mariadb-plugin-tokudb - TokuDB storage engine for MariaDB mariadb-server - MariaDB database server (metapackage depending on the latest vers mariadb-server-10.3 - MariaDB database server binaries mariadb-server-core-10.3 - MariaDB database core server files mariadb-test - MariaDB database regression test suite mariadb-test-data - MariaDB database regression test suite - data files Closes: 939819 Changes: mariadb-10.3 (1:10.3.18-1) unstable; urgency=medium . * New upstream version 10.3.18. Fixes regression introduced in 10.3.17 (MDEV-20247: Replication hangs with "preparing" and never starts) (Closes: #939819) * Minort Gitlab-CI improvements Checksums-Sha1: 833542d304b6f560b2fb8308753e48a1802aea27 4780 mariadb-10.3_10.3.18-1.dsc 922a317edd6f44baacc49831ca278e7a9878a363 71950543 mariadb-10.3_10.3.18.orig.tar.gz 0c3a6922a528c6353dec7d99b2a2244c13eb6a25 195 mariadb-10.3_10.3.18.orig.tar.gz.asc c8661dfa0e0d1465543f579312618fa1b732d4e8 214368 mariadb-10.3_10.3.18-1.debian.tar.xz db65d184e0397f145aaff2b01200664ff087c500 9251 mariadb-10.3_10.3.18-1_source.buildinfo Checksums-Sha256: 9ac8ef87a15d014fd3aa18497dbed39fab32d938a3b1fc17f4c1745a4580af59 4780 mariadb-10.3_10.3.18-1.dsc 69456ca85bf9d96c6d28b4ade2a9f6787d79a602e27ef941f9ba4e0b55dddedc 71950543 mariadb-10.3_10.3.18.orig.tar.gz a906486edc01f4bef7bc479d9b05b162bac7fff30ea1b0e9138d6c1e81ca76ae 195 mariadb-10.3_10.3.18.orig.tar.gz.asc b341567e23fcce7270cec1e3ea7bfff73479384de91f663ecb54ac45e76aecca 214368 mariadb-10.3_10.3.18-1.debian.tar.xz 396e3e8288eabeae431b8a89bfe25b619a376c51e646c7eb37a0e8f49b4d0e0e 9251 mariadb-10.3_10.3.18-1_source.buildinfo Files: 4f9587d3894df1fc701043361dda27b2 4780 database optional mariadb-10.3_10.3.18-1.dsc b3524c0825c3a1c255496daea38304a0 71950543 database optional mariadb-10.3_10.3.18.orig.tar.gz d9f419b5f50eaa3357ae925d0777ca60 195 database optional mariadb-10.3_10.3.18.orig.tar.gz.asc 3fdde5b6e2b43316ea9100bf4cffaf3f 214368 database optional mariadb-10.3_10.3.18-1.debian.tar.xz 68aee6637b9a50b08a16eab3800d58a7 9251 database optional mariadb-10.3_10.3.18-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEmbRSsR88dMO0U+RvvthEn87o2ogFAl17THgACgkQvthEn87o 2oi5jhAAosTq3+9gjbsYhN/yp8FVGGdJiAMRzDrVUg26qbZIwvSkfTHYKnDN2AK1 fF2KuEW/JEN72pGVXncFvL8t49a4GL+va9rflaa8vX3bZhdz4IQh63//A+ohcH+K Uk2SOGZj+UFHG1wPBbs0F3A0TxT/6HloqtraH7kfsLZId6AeL4ZyupkdaHOB+I9v lqIdd+CGclpVVWod/9Gg6RU0UBxeUBhIWhePckZhw8AV2klPHMvsej2w2gBsrZ4k YxO13q1C3Rb0BDvWNRGRXXql08JeD9zQNXXC682cHZj6kAIK5vCG3xBjLIXS IiJtDzzJDbImZifRtjDzpaMYnWjmPzKOOijLj2N28MLAMuSFmREscD51qi4CxNHG TEv6vSr3FfKh0Sx0T8x4x7nH3ESgNns+yMdHrNK4gu052OTVtcH52xfNlfA983qo 1qYXsnTxZMtP/uqz/BEx1Hb08uqYxHf4TfEHtXBU/MQHopjU9gdqZs+3ezU2sEGg UnzZSMsXJIDR7b8u8ftMkHNNtqKiB1zBgXLbS2mcVVXsK4HCKcdw4dO8c07KLqx5 uVAELMTD5y+beQ+PJG8amozXxp7guMknNVxSfPa93u/1FLo1sx+Vn6KDklbqNPhx XTkFZ+LkzZjj2TBIuNMoGWAMzMa3rRVe8ksQz+p7aSZgoBa++xw= =kepq --
Accepted rdiff-backup 1.3.3-1 (source) into unstable
-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 Description: rdiff-backup - remote incremental backup Closes: 607257 656436 881347 Changes: rdiff-backup (1.3.3-1) unstable; urgency=medium . [ Otto Kekäläinen ] * New upstream release 1.3.3 * Fix crashing on Exception '[Errno 61] No data available' (Closes: #881347) . [ Rémi Laurent ] * Fix harmless option typo in bash-completion file (Closes: #656436) . [ Christian Hammers ] * Extend --no-compress defaults by .iso/vob/mdf (Closes: #607257) Checksums-Sha1: bada4cce4a9c2ca33738c115132427fe465b528a 2092 rdiff-backup_1.3.3-1.dsc b36c9b5c06941a86210242f8213f60153a1eba28 198412 rdiff-backup_1.3.3.orig.tar.gz 4d4d7e644957402207fadf02c4dbdd81fd79d996 14628 rdiff-backup_1.3.3-1.debian.tar.xz fad9e50682dbb0928e1e397f5cfd9bfafc9bd997 6977 rdiff-backup_1.3.3-1_source.buildinfo Checksums-Sha256: eab40cee11e493968daa674df870498542d2351e9248792fcafa697976df5e21 2092 rdiff-backup_1.3.3-1.dsc ee030ce638df0eb1047cf72578e0de15d9a3ee9ab24da2dc0023e2978be30c06 198412 rdiff-backup_1.3.3.orig.tar.gz 111ebc0d8181bf71a49aae3a7f562dcb77aee7df4744e7a2682d07f89f9dbe79 14628 rdiff-backup_1.3.3-1.debian.tar.xz b9c0a349f42a3678633a3c6cfa969b8891b45ec10149195e00d32cef99f29d04 6977 rdiff-backup_1.3.3-1_source.buildinfo Files: 9ee7ad8cd6be259a9e8b1949ada058d9 2092 utils optional rdiff-backup_1.3.3-1.dsc e3ec506c01e12b693adb79751daa7c63 198412 utils optional rdiff-backup_1.3.3.orig.tar.gz c7d1818f799ed92017253271a734d5f5 14628 utils optional rdiff-backup_1.3.3-1.debian.tar.xz 50e8dd1ae95350ff26ca8e57d6f9587b 6977 utils optional rdiff-backup_1.3.3-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEmbRSsR88dMO0U+RvvthEn87o2ogFAl1Elw0ACgkQvthEn87o 2ohrPw//Q0oH1m+UuCrA25xIIIXo4P/SO263/E18p2OIqDftX0QgMwr3wOLB7KJQ FjO+/onKjYsfNJ3ZFdJzybMY1oMYQkiDzjuQywPtcI/HLUPx6Y2oJXW2/rW7rqsJ /vcTzM4m9xojpFeYkHFz96kaN96JkhrshifOEv4tiCioO9imp2DR4R5uwVXEQ2HM MDewbiK9BMt/dkJIWUJN3yr2/3BLTPvSZwkRCiF7UFBZJIUW/bx/Nxi0We/0Yaiv Fl5ERGuunDlRyBEZMDXcr/Hb6a/HVxYas92rYqUjNxCfBwfFb5FiahzQHDthsRm3 m+BTMCYGLtgAfbgXQEOZcxCyugPnSUq+8dlmE+qr75fukc4fGjPitJrt0+1J7ddu rQMorOSO8k930TG0xRGvmrzubnAhlJcN2ETyZvbMHxeuwih7b3BtW6suTNR3MPvm e+NOOuL/luPQMKQeG6l5Fky0MCJkLDeK5y6rycuJCEYvnKTuau106rvY61bn8iA3 kiGFJ+qOoJCalLd1u9R7ZOCAc+9iS13VvLOt1XcMHkK6D1TFxEKuZZMhCVXZaek9 EPiNMPN5EKT/0LHEi0ljoVYqtCzSE5wSt1WsjiVuASnrojFJ7KUNHsqdMXwfAWh4 P32qAwGuh+kahdXpXaxtLACfxKXUUN/KA8XdjtoXAkir4krGipM= =A6ai -END PGP SIGNATURE-
Accepted mariadb-10.3 1:10.3.17-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 02 Aug 2019 17:53:22 +0100 Source: mariadb-10.3 Binary: libmariadb-dev libmariadbclient-dev libmariadb-dev-compat libmariadb3 libmariadbd19 libmariadbd-dev mariadb-common mariadb-client-core-10.3 mariadb-client-10.3 mariadb-server-core-10.3 mariadb-server-10.3 mariadb-server mariadb-client mariadb-backup mariadb-plugin-connect mariadb-plugin-rocksdb mariadb-plugin-oqgraph mariadb-plugin-tokudb mariadb-plugin-mroonga mariadb-plugin-spider mariadb-plugin-gssapi-server mariadb-plugin-gssapi-client mariadb-plugin-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 Connector/C, compatibility symlinks libmariadb3 - MariaDB database client library libmariadbclient-dev - MariaDB database development files (transitional package) libmariadbd-dev - MariaDB embedded database, development files libmariadbd19 - MariaDB embedded database, shared library mariadb-backup - Backup tool for MariaDB server mariadb-client - MariaDB database client (metapackage depending on the latest vers mariadb-client-10.3 - MariaDB database client binaries mariadb-client-core-10.3 - MariaDB database core client binaries mariadb-common - MariaDB common metapackage mariadb-plugin-connect - Connect storage engine for MariaDB mariadb-plugin-cracklib-password-check - CrackLib Password Validation Plugin for MariaDB mariadb-plugin-gssapi-client - GSSAPI authentication plugin for MariaDB client mariadb-plugin-gssapi-server - GSSAPI authentication plugin for MariaDB server mariadb-plugin-mroonga - Mroonga storage engine for MariaDB mariadb-plugin-oqgraph - OQGraph storage engine for MariaDB mariadb-plugin-rocksdb - RocksDB storage engine for MariaDB mariadb-plugin-spider - Spider storage engine for MariaDB mariadb-plugin-tokudb - TokuDB storage engine for MariaDB mariadb-server - MariaDB database server (metapackage depending on the latest vers mariadb-server-10.3 - MariaDB database server binaries mariadb-server-core-10.3 - MariaDB database core server files mariadb-test - MariaDB database regression test suite mariadb-test-data - MariaDB database regression test suite - data files Closes: 910902 Changes: mariadb-10.3 (1:10.3.17-1) unstable; urgency=high . * New upstream version 10.3.17. Includes security fixes for: - CVE-2019-2737 - CVE-2019-2739 - CVE-2019-2740 - CVE-2019-2758 - CVE-2019-2805 * Multiple Gitlab-CI/Salsa-CI improvements * Dependency in resolveip is still included (Closes: #910902) * Update libmariadb3 symbols to match MariaDB Connector C 3.1 API * Add Lintian override for new test binary wsrep_check_version * Gitlab-CI: Clean away one excess comment left from b9d633b38 Checksums-Sha1: cf9459db83be68f77dfd91c45c1b4408d281aa54 4780 mariadb-10.3_10.3.17-1.dsc 16edbd4762c8804118dda10de713cbddc675df5a 71894997 mariadb-10.3_10.3.17.orig.tar.gz 5aa36a844eb7fe8979c333786aa82365c2eaaddf 181 mariadb-10.3_10.3.17.orig.tar.gz.asc 33218fc6afcb965cb4ff52009b702d6ebd97984f 214312 mariadb-10.3_10.3.17-1.debian.tar.xz 352c1b9fb739338c1f730df7bf9124216e41faf7 9231 mariadb-10.3_10.3.17-1_source.buildinfo Checksums-Sha256: 6b6c1b62d9703832afebada4e0e01685a8c728c1d3e343f54f39f28e06b8ff2e 4780 mariadb-10.3_10.3.17-1.dsc 20a1ea4fc59aae89dcc82aff0d4907b036daf9bfbd252f08162399f055097097 71894997 mariadb-10.3_10.3.17.orig.tar.gz 989f24ffd89310a8c79bee4a3164f5495b1dba0e7d6b9966db3d88957c9ea698 181 mariadb-10.3_10.3.17.orig.tar.gz.asc f7898d635e639ae4c48f96016d783b844f0b35e9867315f792f0c70edbf4a510 214312 mariadb-10.3_10.3.17-1.debian.tar.xz 79526b3174c185265f5375815ba14ca728c8653cfeb4cdf4a01e41d95a9e177d 9231 mariadb-10.3_10.3.17-1_source.buildinfo Files: d26bb47306013d0263d5f4e07a25219b 4780 database optional mariadb-10.3_10.3.17-1.dsc 6bcee042bcc393cfcffeccbddbf6fe0e 71894997 database optional mariadb-10.3_10.3.17.orig.tar.gz 6ca67cdcf3f2442888f24d967e1ee538 181 database optional mariadb-10.3_10.3.17.orig.tar.gz.asc 37107886787c90040792faed5e5068cd 214312 database optional mariadb-10.3_10.3.17-1.debian.tar.xz 33bea5508e216a9e2f066f62cbe933d2 9231 database optional mariadb-10.3_10.3.17-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEmbRSsR88dMO0U+RvvthEn87o2ogFAl1EazoACgkQvthEn87o 2oiIxQ/+KvcgZXMBpmXwKctWSGAcQUTszLNhGf8JH6TYMZM4KdRFI0RbmAHa9aE1 USjNB/jw4WAci/O3Ks4dXhNthTCKYC+5XlzoB+yeIzI9O0fjkHgLWYRHcMBpwTzI ql0S51h0Zlxw2eg32vP3UlUeTgvMuVnCRj0OL5hTKTYxFH5q9CdPPg/eOHPAP3Jj Y1FUu4MdF2wUH+uJpBBg0V4Sn/Px4z/J7EtykO4vPlkzCASoCvHAzMD0q8B6Zg95 lA9HhiBg/Ip8iHQMBbWyEfHnnhKOjozPu9Nj+kxT2nB7BZR0Ni1U/qDBofYAcAMM fWsdlTR73GODKpNYVyErfrNoJ9a3jrot95ebFOdQPIxIRH51kzQZyya/C4NXdxV9 sMSnKk
Accepted rdiff-backup 1.2.8-8 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 30 Jul 2019 00:12:53 +0300 Source: rdiff-backup Binary: rdiff-backup Architecture: source amd64 Version: 1.2.8-8 Distribution: unstable Urgency: medium Maintainer: Python Applications Packaging Team Changed-By: Otto Kekäläinen Description: rdiff-backup - remote incremental backup Closes: 928885 Changes: rdiff-backup (1.2.8-8) unstable; urgency=medium . [ Jakub Wilk ] * Use canonical URIs for Vcs-* fields. . [ Ondřej Nový ] * d/changelog: Remove trailing whitespaces * d/control: Remove ancient X-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 completion file in correct path * Add upstream metadata with new upstream at Github.com/Rdiff-backup * Update copyright to follow DEP5 format * Add dh-python as build dependency * Switch to buildsystem pybuild * Fail on missing files to be explicit on what files go where * Watch for updates for any release, not just 1.2.x series * Add simple Debian autopkgtest smoke test * Build using librsync 2.0 series to fix security issue (Closes: #928885) * Sync _librsyncmodule.c from Duplicity to be librsync2 compatible Checksums-Sha1: a58b3f64743e91855c548b545db5f41ed434a3df 2092 rdiff-backup_1.2.8-8.dsc 1b26ea1611eaf4d48935f3b2aa56ea27ff2ff021 14052 rdiff-backup_1.2.8-8.debian.tar.xz 96ff361caefd6c830fed42ca99d7ad8f836529d4 6634 rdiff-backup_1.2.8-8_amd64.buildinfo 968661d8191889e11803777f378f6f4b4f14774a 173420 rdiff-backup_1.2.8-8_amd64.deb Checksums-Sha256: bcf94db52d6a4caa5cc733cfdf4d4fb92989fdc24ce469b61dd7da73653a1051 2092 rdiff-backup_1.2.8-8.dsc 3f49ed80039ad4e92e1c65fb8569a92e6c51cbe44d107cb21cc8a903e4c23493 14052 rdiff-backup_1.2.8-8.debian.tar.xz 60ba1a840a83765054317d37fca64ae4b8dd6fe3eb0922ae5c3efc2fd0d9b0ce 6634 rdiff-backup_1.2.8-8_amd64.buildinfo dce6033138915d4997a8429e84327aa842f40bc333e780efef624da502daf44b 173420 rdiff-backup_1.2.8-8_amd64.deb Files: bd1245ec790dd60bc1b7f69ecec351fb 2092 utils optional rdiff-backup_1.2.8-8.dsc af1e4945e3e2405e25962acba3db8eb5 14052 utils optional rdiff-backup_1.2.8-8.debian.tar.xz e9193e95ec0f44ce900bcd47f15cf849 6634 utils optional rdiff-backup_1.2.8-8_amd64.buildinfo d4e31f596fc9950f23fb783654995048 173420 utils optional rdiff-backup_1.2.8-8_amd64.deb -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEmbRSsR88dMO0U+RvvthEn87o2ogFAl0/YkkACgkQvthEn87o 2oh+9A/+Kd+i8wTzK9d9lhOyoxbh19icWwzok1kSwm/10/4DADvHbvH6vGMzTVEB 8EB9Kjg/IMhSzhGvIzyqn1uR+YXPVmQTuAVnd+w7lq73yBsX10Vo/BgLbLH7ktsP vByRIaTIIIet1nphe9BbZNPJmq0XPQKLixP/sGlieOFBprKjWdMimnOq8dtqHNJn MMiVagaYiEsYSxN2zlj9rjcmqNC2TwxRLWO3tQi+UIfmD91vUoyXJRxJrrelsfP2 ML9APT+Db4FAqV2T3Pf9C+2ImOj4JISS1kd6aaMLsv4sYn45IdiQHvC3WlRFBg8Z 8see15VGwlEJ8Z4Q04s88GcxOeUH0mScFVFLk6iQ0tkncX5+utHH0D/M001/84jH Z99BDVkLXC3Gtc2Gz6XzJhkx0TuJ+vA+JgPZ0Ct49ORXLwh8Zkyq+g1l+27+SRtd zff+4oBvLe5b2jEPuIqI7cm0EbMz+ZE3f8YxYOZa7/3qCij+UAAxz0bH//0eYQGw JUvKfxNoTpyBlqrvkvaJ5x7t4CON9Mx2ld+LbVfBjvtrsUvOewzC2dT+kOM3PU8T 51ItfTpeBBjh9iDzHG8sQj19DQhf0+lSw+Y/rc86Dojn3QhhdLCWgQ44BzXpy/Xy /1s0qkxFCOQX+0bWs3e+2QediJNKaIGpWuR+2rLh7IDPlAtbeQU= =aaaL -END PGP SIGNATURE-
Accepted galera-3 25.3.27-1 (source) into unstable
-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 Description: galera-3 - Replication framework for transactional applications galera-arbitrator-3 - Galera arbitrator daemon Closes: 927846 Changes: galera-3 (25.3.27-1) unstable; urgency=medium . * New upstream version 25.3.27 * Include full CC-BY-SA-3.0 license in debian/copyright to satisfy Lintian * Drop manual dbgsym creation as this is nowadays automatic * Apply upstream patch for FTBFS on hppa, hurd and kfreebsd-* (Closes: #927846) Checksums-Sha1: 6f0f103a76ca289a380730cbc948a69c84ba7482 2377 galera-3_25.3.27-1.dsc 8a28754a84230c21f9c408d8d38b7c8848c9008e 3379722 galera-3_25.3.27.orig.tar.gz ed8347caa910ed554b8715fc82ef0b0a5bcceca1 473 galera-3_25.3.27.orig.tar.gz.asc 12ecd40a8ddcf7bea7f76de7821a91dea10bfecf 17172 galera-3_25.3.27-1.debian.tar.xz a178a844df04c9196b138d2f4563de45268b4e71 6528 galera-3_25.3.27-1_source.buildinfo Checksums-Sha256: 95f54cc7d7d29bedd71c7267e807b8b6deda6c43a5fc1bd27eef1c18ca522de0 2377 galera-3_25.3.27-1.dsc 79fc8d7655f6d654ec6909ed631bd92fa434666384b28ef21208066e8be67732 3379722 galera-3_25.3.27.orig.tar.gz 232fe6cfb23999d7fd8cbf624df224f36027a6ac2e59e7b5104f93c746578acd 473 galera-3_25.3.27.orig.tar.gz.asc 064fe89779f52e88f98e3147913fd3c8e6fcf64e8c9ef052e901dcf86a20e1dc 17172 galera-3_25.3.27-1.debian.tar.xz b205594fc0521e23c49f10162b9c7ff1e99da8dff41fdc8907d6325abf8f3b5e 6528 galera-3_25.3.27-1_source.buildinfo Files: 82a725e8d8960f5deff95f156d4592f6 2377 database optional galera-3_25.3.27-1.dsc d9b6b8d07147421b70143034634369ba 3379722 database optional galera-3_25.3.27.orig.tar.gz 75c7f1f2b9d8a7cf74f61a6945bd4085 473 database optional galera-3_25.3.27.orig.tar.gz.asc b49cc3d65caf42042c48bb4cb680c496 17172 database optional galera-3_25.3.27-1.debian.tar.xz 3ac22ec59fc3027cc14050c53fe028f9 6528 database optional galera-3_25.3.27-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEmbRSsR88dMO0U+RvvthEn87o2ogFAl08rW4ACgkQvthEn87o 2ojH1Q/7BY5+AmTtk6uiT/PWplFyYTdwGEYohDqszubytHOP166HchiWJMCgAQd1 /AOOk7hEjGVwzqszmlDG7KSYsxvuddxx2+5GAv7BldPXBqf8Xg2mg6ZTOb8UkROL 6hCKvHr1AJaGAYsnpg1tQFUGHfu1Ry4C9JVcIOBgU08cYXBJ3EnTCqbZcyiJUU+G UvLhzTgE4+iQrJLjgY63k54JIoc2iBAxUGx+tDuIPVShC+wMFga4MisZW9FoDN2o S4yqZP0kVuTLJvJ70VUqkR5b7JPTb2RSwuuiumHZmbXnjVkA+VswEOusY4/Xq1ru g6rb9fzy4Soieb5Avci4fAGvkPuq0QIjyVpCU57av1bjPqzvCEuF5FLJhBkyWTrn XQ2R/m7ZItuPLFVqkQgcfmm388hzs2osxPrEGNU9HM3R6ESRMul0+H3ryT5wdX68 kWsL5Z4PcBonWb6qGgd//QuSYVmkRR3F3eB+HIJbWjh8Glf47/vBA63oOZnW7Nf1 Imgh23SH1yXAXnBc9orxhHVoh5FrbaMbGi9xy/t4JCnbD5dx+6hp1JJMaiKRnMOl ZyUuLJIV8Nf2sIbZwVC6ygSmB33pQZZThA4vkqCIAGyUeCzoCAMLVCnin88I41g7 XfiQNFb6AgDY1XT1dtUQNRyoOdxDDNmd3ZLU04duPk19/zm+rl4= =qEe8 -END PGP SIGNATURE-
Accepted galera-3 25.3.27-1~exp1 (source) into experimental
-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 Kekäläinen Description: galera-3 - Replication framework for transactional applications galera-arbitrator-3 - Galera arbitrator daemon Changes: galera-3 (25.3.27-1~exp1) experimental; urgency=medium . * New upstream version 25.3.27 * Bugfix: Actually apply new patch that was omitted from patches/series Checksums-Sha1: 5e464e95e5104b881e257c8fa1fcfe2f6db3687a 2397 galera-3_25.3.27-1~exp1.dsc 8a28754a84230c21f9c408d8d38b7c8848c9008e 3379722 galera-3_25.3.27.orig.tar.gz ed8347caa910ed554b8715fc82ef0b0a5bcceca1 473 galera-3_25.3.27.orig.tar.gz.asc aefce4107a6e4892a1245ba3aeaa54fa70d8adb2 10548 galera-3_25.3.27-1~exp1.debian.tar.xz de47db92b90bdc7b765fe202f6cdf71696f1a9d4 6548 galera-3_25.3.27-1~exp1_source.buildinfo Checksums-Sha256: a437108651994549b90bc748b77eb2b10c1b0a5b8170eef4ac8681c75956dc65 2397 galera-3_25.3.27-1~exp1.dsc 79fc8d7655f6d654ec6909ed631bd92fa434666384b28ef21208066e8be67732 3379722 galera-3_25.3.27.orig.tar.gz 232fe6cfb23999d7fd8cbf624df224f36027a6ac2e59e7b5104f93c746578acd 473 galera-3_25.3.27.orig.tar.gz.asc e9063ba2fdc3634923233cd15b5afc7c77bfde5493bb15bb5a1c1a09ea815a64 10548 galera-3_25.3.27-1~exp1.debian.tar.xz 0c007db4d1eb8461fc4556cc37d7f8b6aaf899ef0b3389c148f5f0f75951a8ff 6548 galera-3_25.3.27-1~exp1_source.buildinfo Files: 48e2011e19bf6e645b686a1cf6cf2b91 2397 database optional galera-3_25.3.27-1~exp1.dsc d9b6b8d07147421b70143034634369ba 3379722 database optional galera-3_25.3.27.orig.tar.gz 75c7f1f2b9d8a7cf74f61a6945bd4085 473 database optional galera-3_25.3.27.orig.tar.gz.asc 51352f93fdbe57294aaaecc8bcd39fa3 10548 database optional galera-3_25.3.27-1~exp1.debian.tar.xz 34c1f1a4f102a64f7c7b5a8ac7f41bbe 6548 database optional galera-3_25.3.27-1~exp1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEmbRSsR88dMO0U+RvvthEn87o2ogFAl06DGsACgkQvthEn87o 2ojIqA//f+OQqHh9es4q51ICwidicp8wZMZpkvTxCDpDhQqOM2FzbCNdl5VADsZQ 1ig3hOg23ACJgGhZbE5tLV28pnvSO24+j8I+bBPJzkaJGexv21jy2gJ09TaUNYO5 EG011UI3IVzv7CtfwhvgcPYeE+Nc0TcYHseTudXEPWrvFBrRf3Jly9UUjGUQk+s7 4u/idwPt/hyB1MNft1uQh/9FNp7r91ANvL89Mdl6PjXou8dLKo6dvaVuodYrFyHW PlMaIZYg4bYtvR/yqImm0nXM/wB7y1SK3v1DDjETZ19LsgtVStG+E5z0ugH6Hnrr Pf/jKPmlzOjjd50VezHngXxNMyTOAQcvyvwF88mHlDhLnf7BihSVptCZ0kgtICq7 MuTVodYPaZR2gPB20xoxhk2Cz2sLe572ln3m5c59iLfGOimjevIrUHtlXtMR97p9 B9aMXrhhnFf8Kp+4hpWwnSZGltR+h83IXf7pLmZmzj+5QGMCLIut+c2ktuC197GU /sI28he1vfH1GUbr3UHdkoQ2Caiz0AwUTeNVkJm2rCk6yMKfH0gQLqpKTNpYoyog 2azY1Umr20QhTarp7K5VUpJEiYwWMAgLF47Ekkm7qIIc5K13GJBnNIeocMyh4HjJ NTMZMuPyQooF3K5xEXSRrreMMU2V4KmiDJpWopyJQ8WBzVplyZc= =no6Y -END PGP SIGNATURE-
Accepted mariadb-10.3 1:10.3.16-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 22 Jun 2019 16:45:18 +0200 Source: mariadb-10.3 Binary: libmariadb-dev libmariadbclient-dev libmariadb-dev-compat libmariadb3 libmariadbd19 libmariadbd-dev mariadb-common mariadb-client-core-10.3 mariadb-client-10.3 mariadb-server-core-10.3 mariadb-server-10.3 mariadb-server mariadb-client mariadb-backup mariadb-plugin-connect mariadb-plugin-rocksdb mariadb-plugin-oqgraph mariadb-plugin-tokudb mariadb-plugin-mroonga mariadb-plugin-spider mariadb-plugin-gssapi-server mariadb-plugin-gssapi-client mariadb-plugin-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 Connector/C, compatibility symlinks libmariadb3 - MariaDB database client library libmariadbclient-dev - MariaDB database development files (transitional package) libmariadbd-dev - MariaDB embedded database, development files libmariadbd19 - MariaDB embedded database, shared library mariadb-backup - Backup tool for MariaDB server mariadb-client - MariaDB database client (metapackage depending on the latest vers mariadb-client-10.3 - MariaDB database client binaries mariadb-client-core-10.3 - MariaDB database core client binaries mariadb-common - MariaDB common metapackage mariadb-plugin-connect - Connect storage engine for MariaDB mariadb-plugin-cracklib-password-check - CrackLib Password Validation Plugin for MariaDB mariadb-plugin-gssapi-client - GSSAPI authentication plugin for MariaDB client mariadb-plugin-gssapi-server - GSSAPI authentication plugin for MariaDB server mariadb-plugin-mroonga - Mroonga storage engine for MariaDB mariadb-plugin-oqgraph - OQGraph storage engine for MariaDB mariadb-plugin-rocksdb - RocksDB storage engine for MariaDB mariadb-plugin-spider - Spider storage engine for MariaDB mariadb-plugin-tokudb - TokuDB storage engine for MariaDB mariadb-server - MariaDB database server (metapackage depending on the latest vers mariadb-server-10.3 - MariaDB database server binaries mariadb-server-core-10.3 - MariaDB database core server files mariadb-test - MariaDB database regression test suite mariadb-test-data - MariaDB database regression test suite - data files Closes: 930314 Changes: mariadb-10.3 (1:10.3.16-1) unstable; urgency=medium . [ Otto Kekäläinen ] * New upstream version 10.3.16 * Make libzstd dependency versioned as RocksDB need at least 1.3.3. This fixes build errors across different build environments. * Update Gitlab CI for better quality control and long-term maintenance. . [ Helmut Grohne ] * Improve cross building (Closes: #930314) Checksums-Sha1: dbe0a577867c6afaaeeea6c9e68c6547ddc597b1 4780 mariadb-10.3_10.3.16-1.dsc 6a4ee3be06f38b9aef1cd4f99099abea6a17de69 70862041 mariadb-10.3_10.3.16.orig.tar.gz 4dde3d6cbd9fd8af94e7c49625b5fe367c026aec 181 mariadb-10.3_10.3.16.orig.tar.gz.asc 8f7fc78dd9a71ea0bf471ba9658d4cdbd4d7e6c6 216132 mariadb-10.3_10.3.16-1.debian.tar.xz 64ef07cc31c9e62fe16ef5ce9b215afaaf588692 9118 mariadb-10.3_10.3.16-1_source.buildinfo Checksums-Sha256: c3795b6335a264093fd1d0cd714c2b0a800d21cc195bb0529f9519bbe29f9775 4780 mariadb-10.3_10.3.16-1.dsc 39e9723eaf620afd99b0925b2c2a5a50a89110ba50040adf14cce7cf89e5e21b 70862041 mariadb-10.3_10.3.16.orig.tar.gz f11b68a03cfae7233a5da12119e20fd5c1ff6a2c1ee1260ef6871f5682ef8a84 181 mariadb-10.3_10.3.16.orig.tar.gz.asc e54bed06548b5fe0eb7ade9dd6f43af002e38656a173a5601c3afd268e364cc5 216132 mariadb-10.3_10.3.16-1.debian.tar.xz b5734a065bcfa4a67b3e36bdd1c4cec87fdc6e29615b9f77e7d8892cb1d07387 9118 mariadb-10.3_10.3.16-1_source.buildinfo Files: 67f002f6ce9654bb2954c92b56d79587 4780 database optional mariadb-10.3_10.3.16-1.dsc 11220d0b94c5c24caa2e1e9eaba38e31 70862041 database optional mariadb-10.3_10.3.16.orig.tar.gz 2f3014582e06a0ea8df4f60ed0d9b93d 181 database optional mariadb-10.3_10.3.16.orig.tar.gz.asc 03fb014f7b850b8ffb0c9b023d93edf9 216132 database optional mariadb-10.3_10.3.16-1.debian.tar.xz f3fae6235a6de43c1c1af8a8c9ff7873 9118 database optional mariadb-10.3_10.3.16-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEmbRSsR88dMO0U+RvvthEn87o2ogFAl0OQCUACgkQvthEn87o 2oh0/w//QBiZjJg1ZN4tcd0MT+IhOAZBKLTQz7x27mvMaZOvNcUC5UgoYYzx11rq t1Ug6sr2ajgVgoGGN+ISHu+oJ+1BHO8xceaXaBxyfNoJmeJ3sHgOx4u9kzu5s8iU z5+UWbNJwO61WU0+VkIxDVwk3qi52kNtn68gnBLU0ngAsKnxle0ud2wUzjNoS3ZF FFPwU4DBIkSA9v9lg07aPANMwFBNvsag7ib7P0CRHmHespCb1HgesByMk9yemWLS PeaoFVWM2Li9/NA2zkYPc5SUCQ9hS9CSx4vrTVzrwsBeNSe8BcUKlsLRBQIHDlGv AgrVclsOdrso3htRJ0vV3W25aKnrnxCA0GIFVluVvRWqmsxY0s7njv5rGDRIRl6k ICu7/IYXBmNiklGRKbqgX4DrwIgC5FyfQyTxg8tmvUOKMdOsGqD5uElD1SCC/Ajg l5SMiqiITI1XAGLhC3UpgbGfXxX7PzuHySqqqNYN0TSjN9BOGre+vXVCg5tLnHrV TiHCCuSg1XJI71A+y5EoEZprZUt6TcD2DPvI3WJkxqrQBLovdOyw4J01I3P6yS
Accepted mariadb-10.3 1:10.3.15-2 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 07 Jun 2019 09:13:35 +0300 Source: mariadb-10.3 Binary: libmariadb-dev libmariadbclient-dev libmariadb-dev-compat libmariadb3 libmariadbd19 libmariadbd-dev mariadb-common mariadb-client-core-10.3 mariadb-client-10.3 mariadb-server-core-10.3 mariadb-server-10.3 mariadb-server mariadb-client mariadb-backup mariadb-plugin-connect mariadb-plugin-rocksdb mariadb-plugin-oqgraph mariadb-plugin-tokudb mariadb-plugin-mroonga mariadb-plugin-spider mariadb-plugin-gssapi-server mariadb-plugin-gssapi-client mariadb-plugin-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 Connector/C, compatibility symlinks libmariadb3 - MariaDB database client library libmariadbclient-dev - MariaDB database development files (transitional package) libmariadbd-dev - MariaDB embedded database, development files libmariadbd19 - MariaDB embedded database, shared library mariadb-backup - Backup tool for MariaDB server mariadb-client - MariaDB database client (metapackage depending on the latest vers mariadb-client-10.3 - MariaDB database client binaries mariadb-client-core-10.3 - MariaDB database core client binaries mariadb-common - MariaDB common metapackage mariadb-plugin-connect - Connect storage engine for MariaDB mariadb-plugin-cracklib-password-check - CrackLib Password Validation Plugin for MariaDB mariadb-plugin-gssapi-client - GSSAPI authentication plugin for MariaDB client mariadb-plugin-gssapi-server - GSSAPI authentication plugin for MariaDB server mariadb-plugin-mroonga - Mroonga storage engine for MariaDB mariadb-plugin-oqgraph - OQGraph storage engine for MariaDB mariadb-plugin-rocksdb - RocksDB storage engine for MariaDB mariadb-plugin-spider - Spider storage engine for MariaDB mariadb-plugin-tokudb - TokuDB storage engine for MariaDB mariadb-server - MariaDB database server (metapackage depending on the latest vers mariadb-server-10.3 - MariaDB database server binaries mariadb-server-core-10.3 - MariaDB database core server files mariadb-test - MariaDB database regression test suite mariadb-test-data - MariaDB database regression test suite - data files Changes: mariadb-10.3 (1:10.3.15-2) unstable; urgency=medium . [ Julien Muchembled ] * Fixup RocksDB test on s390x, not available there . [ Otto Kekäläinen ] * Purge deleted translations from debian/po * Rename 'mariadbcheck' to 'mariadb-check' as upstream is doing in 10.4 Checksums-Sha1: ba1f2f4537cdd72f4a11513857d8b6da1eb5a351 4739 mariadb-10.3_10.3.15-2.dsc 64166b6605a8797347204804fea9d423fc3fc843 215820 mariadb-10.3_10.3.15-2.debian.tar.xz 8a88dfea850bc63efe13865b1cf9d45ce65c9c7b 9118 mariadb-10.3_10.3.15-2_source.buildinfo Checksums-Sha256: 98ee3f72dab84db9569f7773dfdebf9d4508ef886f2b25d2ab592214a0e20920 4739 mariadb-10.3_10.3.15-2.dsc 5554085bf886d876a8898942aea430deea7145d02f4c8fcc085dfe8382e74555 215820 mariadb-10.3_10.3.15-2.debian.tar.xz 948710ec895597c3c0139f6b9a1baaa327c8abd4f813409b03ad19814ceed7bd 9118 mariadb-10.3_10.3.15-2_source.buildinfo Files: 61c6e436d33d57c82ae344128b1d4c30 4739 database optional mariadb-10.3_10.3.15-2.dsc 456577dfdaa05c6c9ee6db9753f6ee72 215820 database optional mariadb-10.3_10.3.15-2.debian.tar.xz d8296332f333cb84610818c59386bd15 9118 database optional mariadb-10.3_10.3.15-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEmbRSsR88dMO0U+RvvthEn87o2ogFAlz6AS0ACgkQvthEn87o 2oh9Jw/+IAs0lD8Y/jZYs+Qwe9NwH3EBwl3se6R2VZ/rE4eErN51e7t96NYUZwzy eiCzG45+76tt7cT89IJ8jlCQES9pDs84f6OCMlrJARIKFlUdpftMZAw0iIAMsJfO waE1S6o9+flu2nc2PRd5vmzA3XekerO74VdUWiEBxbUGVPMA1M0rOEgoInAlTgY8 XkeLbGz2yUi3j5KW6/E7MZqdODrhvDfXYJ5Bjl7A1Y2APVk3f0PTzQfDTDxNd7yn LZbLmxUOTPw1GLTLXj2QMX+zkrWyzD2Kw/wKxUOI/H2Aylrvrl8UGhCdSsjD5iVp JSXCbBAhP6RlIq+Nw8FY0KJcI7EqLDjmKw+Rywr6XMCI+WqJV46I1VwpapIeR6dR nnFFaj1jSfz2pRkSMWf2CkqQI1iZjSIjSmgbU72VVeg6TKxsbYzc42/8IwIV/rvO 1XX1iVgwtJpiTex9f+DolUta8A+tXLQfsQz2JKFb1SqAmcSB6RG5BLA9WuR1JCtP Nmm/VcIjKHrSFWkgSIoNUUo90xGrYld9Yh/T8ofLCHPDi0+Ii9AU4q7RsObSEXo9 zKri07GLdW/DCVfcxpddntPDCWsIG6uWaLcw1vsWkaQ2AD2C2aSQ65pVhfKUgpB/ PQ5hah/XY6c+OyBjjpcDiIL/2geJwgRowlbChMzgitarPt/Xd8s= =lnR2 -END PGP SIGNATURE-
Accepted galera-3 25.3.26-2~exp1 (source) into experimental
-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 Kekäläinen Description: galera-3 - Replication framework for transactional applications galera-arbitrator-3 - Galera arbitrator daemon Closes: 927846 Changes: galera-3 (25.3.26-2~exp1) experimental; urgency=medium . * Apply upstream patch for FTBFS on hppa, hurd and kfreebsd-* (Closes: #927846) Checksums-Sha1: b99261109c678b6ab67a5a9db00240b181d02764 2397 galera-3_25.3.26-2~exp1.dsc b2dd170764ad3292bde032c79e6097a0e1247023 10540 galera-3_25.3.26-2~exp1.debian.tar.xz 1efc965717a0af3e6be802f78f8532a00c495401 6474 galera-3_25.3.26-2~exp1_source.buildinfo Checksums-Sha256: f01e58cad64e1e383e7bc79164a5b2cb34e05564f05c97e81754f755dbaeab70 2397 galera-3_25.3.26-2~exp1.dsc ffd751f652c50a8543c24bd28ad0d5d8a12df8133eb778a43b1d0271b79c413e 10540 galera-3_25.3.26-2~exp1.debian.tar.xz 56523f5dc37228fe2956af29af5391820b91694f4e0a9addb8e8e6e5a24407fb 6474 galera-3_25.3.26-2~exp1_source.buildinfo Files: 9d13c0171924fad7497245b57675d5a6 2397 database optional galera-3_25.3.26-2~exp1.dsc 38e4cd0b68348f117ccf1e724b900470 10540 database optional galera-3_25.3.26-2~exp1.debian.tar.xz 549a64c54f4a57f2381d89852907fbef 6474 database optional galera-3_25.3.26-2~exp1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEmbRSsR88dMO0U+RvvthEn87o2ogFAlz6CcoACgkQvthEn87o 2og7KhAAqaUcEMvi/qBmU+rY7DSRo6QXx3YyPBlbnACliPru9NAhQnZVY5tkiXz9 M6D9/IfjokAHcT5ynt/u5sLxej36PXM7kr3ACutgxnbuAEnRIReYMyk1G1G0HOxR 2y0bY4SydWJWjy5CmrArQJ2b0UuW44Baf99JZoLDpG6PWys6/Sz2NrZHyznh8PsF tLedWmP2YdaDuhgo3v0HRqDdzSdy63ZLLWcFE2Q+xIHH4NkitYvWObJxq7j5iDud SuR/8KWYeL15MjFFiAfoP1yqiSKIjvIb7yvsbynNPMWP/H4JKv8FK2WRZIDVm3gn E28ZlLpHhc6HpdszciN9AkNobzamkiDj2nnbE4Y8T2tL0DafhHCxeU1Q1dVGgMA8 p9p4l/p4ZZhqUTop7TdPUe97mJ4JWS4N5n8lmuw0tzEQ8gA8wJ+16LT6RrWCMT46 EcIqdQoOA1AwAqx9RrcAGQOplRTdQw4rsBeiE3oRquuMqovmmEaMkMjwRrwcDJO+ Kipnp1FjlZ5JdlGavDVRVjRsjj9nmiAK2lKiqKf8RfvulVtOFd6RVNXFxhRBBRS2 SQD+P0s6C1+oKx2UuPm/G/eFcB6TYNBZDzZHebnnQPo1YIqzihhFhAtf3rlc13+H E9nX8A0hg7zM846soO7h3ZGddr6n4w8+wrzjaE97eHj14cr/M+E= =+UnP -END PGP SIGNATURE-
Accepted mariadb-10.3 1:10.3.15-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 21 May 2019 10:45:37 +0300 Source: mariadb-10.3 Binary: libmariadb-dev libmariadbclient-dev libmariadb-dev-compat libmariadb3 libmariadbd19 libmariadbd-dev mariadb-common mariadb-client-core-10.3 mariadb-client-10.3 mariadb-server-core-10.3 mariadb-server-10.3 mariadb-server mariadb-client mariadb-backup mariadb-plugin-connect mariadb-plugin-rocksdb mariadb-plugin-oqgraph mariadb-plugin-tokudb mariadb-plugin-mroonga mariadb-plugin-spider mariadb-plugin-gssapi-server mariadb-plugin-gssapi-client mariadb-plugin-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 Connector/C, compatibility symlinks libmariadb3 - MariaDB database client library libmariadbclient-dev - MariaDB database development files (transitional package) libmariadbd-dev - MariaDB embedded database, development files libmariadbd19 - MariaDB embedded database, shared library mariadb-backup - Backup tool for MariaDB server mariadb-client - MariaDB database client (metapackage depending on the latest vers mariadb-client-10.3 - MariaDB database client binaries mariadb-client-core-10.3 - MariaDB database core client binaries mariadb-common - MariaDB common metapackage mariadb-plugin-connect - Connect storage engine for MariaDB mariadb-plugin-cracklib-password-check - CrackLib Password Validation Plugin for MariaDB mariadb-plugin-gssapi-client - GSSAPI authentication plugin for MariaDB client mariadb-plugin-gssapi-server - GSSAPI authentication plugin for MariaDB server mariadb-plugin-mroonga - Mroonga storage engine for MariaDB mariadb-plugin-oqgraph - OQGraph storage engine for MariaDB mariadb-plugin-rocksdb - RocksDB storage engine for MariaDB mariadb-plugin-spider - Spider storage engine for MariaDB mariadb-plugin-tokudb - TokuDB storage engine for MariaDB mariadb-server - MariaDB database server (metapackage depending on the latest vers mariadb-server-10.3 - MariaDB database server binaries mariadb-server-core-10.3 - MariaDB database core server files mariadb-test - MariaDB database regression test suite mariadb-test-data - MariaDB database regression test suite - data files Closes: 921599 928230 928393 Changes: mariadb-10.3 (1:10.3.15-1) unstable; urgency=high . [ Otto Kekäläinen ] * New upstream version 10.3.15. Includes security fixes for (Closes: #928393): - CVE-2019-2628 - CVE-2019-2627 - CVE-2019-2614 * Includes upstream fix for MDEV-18721: Host option in configuration file is ignored (Closes: #921599) . [ Gregor Riepl ] * Extend mariadb/mysql_config to support --libmysqld-libs (Closes: #928230) . [ Julien Muchembled ] * Enable LZ4 for InnoDB and LZ4 for RocksDB Checksums-Sha1: 7f780b3c56e57ee560a1bf9600aa6d97a8369276 4739 mariadb-10.3_10.3.15-1.dsc 134f6a1ee6bf3048580eca945a51cb3c9bda7cbe 70824529 mariadb-10.3_10.3.15.orig.tar.gz 6f7443abc6feb52ba65846a76bb61223a719e43a 181 mariadb-10.3_10.3.15.orig.tar.gz.asc c3d3d13b42016285a3fae0851c20fdf2985cbf5e 223992 mariadb-10.3_10.3.15-1.debian.tar.xz b3021e9d9f7e55eb232d4552561de4480711 9104 mariadb-10.3_10.3.15-1_source.buildinfo Checksums-Sha256: 6c090a441ff1f8cbf156826303478e47c4c584823fb9b25006ed5aad97279979 4739 mariadb-10.3_10.3.15-1.dsc 27f391a54d544f93850d4edfb3ef1b4cf24f8e27e61e51727b0e7d31bb4d6968 70824529 mariadb-10.3_10.3.15.orig.tar.gz e1c988f3692971d2f978ecfa749ca1c8a3fe26caf7c8bd0ce7355fe92639897e 181 mariadb-10.3_10.3.15.orig.tar.gz.asc e3e395e5e9b270cceb1dd8d2da0e5dc641acde3b9f287d107073b79eb7415922 223992 mariadb-10.3_10.3.15-1.debian.tar.xz 6561fdeee047ad9a8644e23cbbaa0637b477bae91ae86de4dc57616288067207 9104 mariadb-10.3_10.3.15-1_source.buildinfo Files: 61e417d5fa36a944279b0c8eab0c495a 4739 database optional mariadb-10.3_10.3.15-1.dsc 08edd8b5060a181e6dd3c6aac23218cd 70824529 database optional mariadb-10.3_10.3.15.orig.tar.gz f6ac546f13da54a0946afda66b2717ff 181 database optional mariadb-10.3_10.3.15.orig.tar.gz.asc 375761ee16a05208bd34469d7ccb49f8 223992 database optional mariadb-10.3_10.3.15-1.debian.tar.xz 6a020a7498cfdfdbcf3f2c9e439aadca 9104 database optional mariadb-10.3_10.3.15-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEmbRSsR88dMO0U+RvvthEn87o2ogFAlzjrSMACgkQvthEn87o 2ojCAg//aEAsN+Ms/D7D0XS6VQg1q07Nl7LwvwfaKJy2fDFkvkzZ55/L1yctTQcH biOgucBuB2bmuufx7MKO17UV2fGvePLGaYfL3+Cp0Fl3XXU0mG3k9DJJglhu1xfM iZmGR8zcto/fs3AEAqcs1tPJRns+CrhmPgyC2L18lAtyxYb4tbxunu0Yx28YuFKC Hqqu0iCUm/R8CmRisQOiLseEpmvp10pGnojnhDxpq12ddvyFsuka6fOJLXWc+1JC mFFCwFYE5nsXUje2pMRbmY/yeabf/jBx28TT92BfuYx89H/WQC7eQqFRs8Ai441n kIPJM5FyjZdlGhnFeXK9APsJ0oqtGeHp2ijbH440fmQKTn9PCS/7I7cgFTLMz6Fq UkA/qjSnXld0eWBTgdqHuNA2oKRTpPMdMZlXRNlcSz/bZF+DLx+YrV56HlAJJS0l d
Accepted galera-3 25.3.26-1 (source) into unstable
-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 Description: galera-3 - Replication framework for transactional applications galera-arbitrator-3 - Galera arbitrator daemon Changes: galera-3 (25.3.26-1) unstable; urgency=medium . * New upstream version 25.3.26 Checksums-Sha1: e0d65ef298c759ab386e6f2f4654c477c66081c6 2374 galera-3_25.3.26-1.dsc 5490c4c5946d680b966079734989380e6fac68b4 3377928 galera-3_25.3.26.orig.tar.gz 700f3514e90101d12ac10400ae2fb178872bc1bf 473 galera-3_25.3.26.orig.tar.gz.asc d126a5ee8146c2a6742bdbea90668da033dcdfd0 9752 galera-3_25.3.26-1.debian.tar.xz 9413778df8ec45f208eb7f883edaa4d588b9c8e1 6442 galera-3_25.3.26-1_source.buildinfo Checksums-Sha256: 8bb5a1e3df3f7bdeeef2686b05f3ea643bd41466c47c8c4df73c9b8876b0af41 2374 galera-3_25.3.26-1.dsc d03e32a79466dd0736c0ad150512e6161081e8cb493346a02a6667625e4b67e5 3377928 galera-3_25.3.26.orig.tar.gz 15b8e9a42e1d188b958c48f5b8ffdcbab6c9b4c5558ab09c1488b267e3a6b626 473 galera-3_25.3.26.orig.tar.gz.asc 16da3cd28e95db2eab67b7f57915cabbe38a4fcef241104eb4f98d09e3fcd58a 9752 galera-3_25.3.26-1.debian.tar.xz 719fa4b3f223247fb9dcfb88ea0105fb585752e5b087187a4d120f1bf57a946d 6442 galera-3_25.3.26-1_source.buildinfo Files: ca71230ac771804b88a2bf6f79f61d4e 2374 database optional galera-3_25.3.26-1.dsc 7c13e516107fdf541fa6807ac570e6dc 3377928 database optional galera-3_25.3.26.orig.tar.gz 59709f779fc89dad0d66be358c2ec7eb 473 database optional galera-3_25.3.26.orig.tar.gz.asc 5ba1b3736db51441cd6bf8437afa6f16 9752 database optional galera-3_25.3.26-1.debian.tar.xz d31d3477e5203d49ff222beff92b998c 6442 database optional galera-3_25.3.26-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEmbRSsR88dMO0U+RvvthEn87o2ogFAly+6FsACgkQvthEn87o 2oh8qhAAwbDBHwePJ2sMMh3Agk2vKoGxQGnZ1g7//7PKZA+4fE3U2zYYfZw7aHD4 28M8dqucDt0cncy2usLQNF1ZdroRGaYEUwdRxEiZ6bEhWwTdzPKImaHCJqexQaqZ Kk6kI+mtbvEyrRV1MyCNAyLPGtalc0Tl/9eori3SLZebaRBtOlHEr/eJfXLN2DZK MYaBUg297rHHDlc0t/acpcWsKx06826Jxv+ViH/Ocn2xUMdMpscGBdb5fA8X43XJ dCx88wwYHvPQxm/7YcbyX2mwzBir7xF8t9N6KsGvdH8QbTTwAjEkX5V9UDxSrVqD a90u1binCxLSgoU0A9TuIXa8AcZ4Gl6Qcn4Y/MliuVfS62vPONGm+jDQOuEtIPfN wBRA6iNnh3AoYVLj/xHQovxxJOzoTlPx5f0/3bb1/yCAZYvpqJhefhzteRG/auDO PhDmxBy/P9POAqFLaXUF4kde0+aerQhpewRSYcif7bvCsOKamFg7QEWAc/HSBaoB UXVTSRla7d83V257RuQZ0rmGYqbi4I+343uGcha8L59nSpq20ZlvFGnxtGXFIVHX y1Ej/2j8tfOf8r5zIrTCFTLNmO5W9pB5EO3bHG5PSAElfjQXKYHrucVsjJr2/Pe5 kFRgFX34dfTobY3FCmQXLUzJ8vNsNVFaFJHRVly3n6FputnYljs= =Tonw -END PGP SIGNATURE-
Accepted mariadb-10.3 1:10.3.14-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 19 Apr 2019 14:38:26 +0300 Source: mariadb-10.3 Binary: libmariadb-dev libmariadbclient-dev libmariadb-dev-compat libmariadb3 libmariadbd19 libmariadbd-dev mariadb-common mariadb-client-core-10.3 mariadb-client-10.3 mariadb-server-core-10.3 mariadb-server-10.3 mariadb-server mariadb-client mariadb-backup mariadb-plugin-connect mariadb-plugin-rocksdb mariadb-plugin-oqgraph mariadb-plugin-tokudb mariadb-plugin-mroonga mariadb-plugin-spider mariadb-plugin-gssapi-server mariadb-plugin-gssapi-client mariadb-plugin-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 Connector/C, compatibility symlinks libmariadb3 - MariaDB database client library libmariadbclient-dev - MariaDB database development files (transitional package) libmariadbd-dev - MariaDB embedded database, development files libmariadbd19 - MariaDB embedded database, shared library mariadb-backup - Backup tool for MariaDB server mariadb-client - MariaDB database client (metapackage depending on the latest vers mariadb-client-10.3 - MariaDB database client binaries mariadb-client-core-10.3 - MariaDB database core client binaries mariadb-common - MariaDB common metapackage mariadb-plugin-connect - Connect storage engine for MariaDB mariadb-plugin-cracklib-password-check - CrackLib Password Validation Plugin for MariaDB mariadb-plugin-gssapi-client - GSSAPI authentication plugin for MariaDB client mariadb-plugin-gssapi-server - GSSAPI authentication plugin for MariaDB server mariadb-plugin-mroonga - Mroonga storage engine for MariaDB mariadb-plugin-oqgraph - OQGraph storage engine for MariaDB mariadb-plugin-rocksdb - RocksDB storage engine for MariaDB mariadb-plugin-spider - Spider storage engine for MariaDB mariadb-plugin-tokudb - TokuDB storage engine for MariaDB mariadb-server - MariaDB database server (metapackage depending on the latest vers mariadb-server-10.3 - MariaDB database server binaries mariadb-server-core-10.3 - MariaDB database core server files mariadb-test - MariaDB database regression test suite mariadb-test-data - MariaDB database regression test suite - data files Closes: 921599 924498 926231 Changes: mariadb-10.3 (1:10.3.14-1) unstable; urgency=medium . [ Otto Kekäläinen ] * Rename and re-organize gitlab-ci.yml stages * Refactor gitlab-ci.yml to be optimal for a life in Buster * Ensure cmake builds also apply CPPFLAGS flags for hardening to fully work * New upstream version 10.3.14. Includes MariaDB Connector C 3.0.10 which includes an improved impelemntation of mysql_real_connect() that respects the my.cnf "host" option (Closes: #921599). This upstream release also fixes an indexes problem on import dump SQL (MDEV-18577) and many other InnoDB corruption issues (Closes: #924498). * Enable automatic restarts from maint scripts in gitlab-ci.yml * Automate renaming MySQL auth_socket correctly in mysql_upgrade (Closes: #926231) . [ Andreas Beckmann ] * Use piuparts with --testdebs-repo so dependencies of each install resolve Checksums-Sha1: 985f7db9b9a2498f99caa14bf42484e96ebe6c3e 4699 mariadb-10.3_10.3.14-1.dsc 06c5a22afbaac0283c9398baaf19749ac570892d 70771337 mariadb-10.3_10.3.14.orig.tar.gz 6532a5436c8199616a16aee1906f92f2a80677d0 181 mariadb-10.3_10.3.14.orig.tar.gz.asc 559c0225f64db798dee617a1e561cb06c8728a7a 223020 mariadb-10.3_10.3.14-1.debian.tar.xz ffcca5b7b8a30ae0a331a5b70ecdc7cf0dd96394 9104 mariadb-10.3_10.3.14-1_source.buildinfo Checksums-Sha256: 50f1b396eba727b41c3a22d4b4a349926cbe5896d39bdfc16e1c45535c22cbd7 4699 mariadb-10.3_10.3.14-1.dsc ba1c94d92fc8ebdf9b8a1d1b93ed6aeeead33da507efbbd4afcf49f32023e054 70771337 mariadb-10.3_10.3.14.orig.tar.gz c86944ca87b09d782ee11031848115c6e01a1d2dac3e2cd3dfcdc1103756d83b 181 mariadb-10.3_10.3.14.orig.tar.gz.asc 5b1c3380cf6d3f3008bdc29d94afeb92e795494c9bfc5940a0e224ae4d17f315 223020 mariadb-10.3_10.3.14-1.debian.tar.xz 0fe494527d854fa08f8215806d3e632eb381282a4ee3e907240d9cfd597257e7 9104 mariadb-10.3_10.3.14-1_source.buildinfo Files: bf8bddda11bc69a6fd397f94fde0b7f5 4699 database optional mariadb-10.3_10.3.14-1.dsc b1b9628bbc3ff15e8f5cfc7896c73975 70771337 database optional mariadb-10.3_10.3.14.orig.tar.gz 5b16675df2dbda257a1db9143f01c38c 181 database optional mariadb-10.3_10.3.14.orig.tar.gz.asc 5c12940feb46113c89e214c2643d6be0 223020 database optional mariadb-10.3_10.3.14-1.debian.tar.xz 634ce0da080519fa4d6203dec89c90bb 9104 database optional mariadb-10.3_10.3.14-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEmbRSsR88dMO0U+RvvthEn87o2ogFAly5s+QACgkQvthEn87o 2ogH/BAArptLi6/PMzCarz8J02PkQci9TpIf5nlL9dLTsiGAZg1aYDpBXl
Re: Seeking hardening flag / blhc expoert
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 --- a/debian/rules +++ b/debian/rules @@ -7,6 +7,11 @@ export DH_VERBOSE=1 export DEB_BUILD_MAINT_OPTIONS = hardening=+all DPKG_EXPORT_BUILDFLAGS = 1 include /usr/share/dpkg/default.mk +# CPPFLAGS are nor read by CMake, so copy them to CXXFLAGS +# See why at https://cmake.org/Bug/view.php?id=12928 +# This is needed for e.g. all automatic Debian hardening flags to apply on all cmake builds. +CFLAGS+=$(CPPFLAGS) +CXXFLAGS+=$(CPPFLAGS) # Only do a strict symbol checking on Linux ifneq (,$(filter linux,$(DEB_HOST_ARCH_OS))) https://salsa.debian.org/mariadb-team/mariadb-10.3/commit/fc4f33cf40d0a10ef5d1992accd2af734ba96356 Results at: https://salsa.debian.org/mariadb-team/mariadb-10.3/-/jobs/154355
Re: Seeking hardening flag / blhc expoert
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? hardening-check --verbose --color mysqld mysqld: Position Independent Executable: yes Stack protected: yes Fortify Source functions: yes (some protected functions found) unprotected: strcpy unprotected: strcat unprotected: recv unprotected: snprintf unprotected: getcwd unprotected: readlink unprotected: memset unprotected: poll unprotected: fread unprotected: fgets unprotected: strncpy unprotected: sprintf unprotected: stpcpy unprotected: strncat unprotected: memcpy unprotected: read unprotected: confstr unprotected: pread64 unprotected: memmove unprotected: gethostname protected: strcpy protected: snprintf protected: vfprintf protected: memset protected: poll protected: vasprintf protected: fread protected: strncpy protected: sprintf protected: vsprintf protected: memcpy protected: fdelt protected: realpath protected: pread64 protected: vsnprintf protected: fprintf protected: memmove protected: printf Read-only relocations: yes Immediate binding: yes [1] https://cmake.org/Bug/view.php?id=12928
Re: Seeking hardening flag / blhc expoert
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 but since we are on a new debhelper it is advised not to be used. It suggests using /usr/share/dpkg/buildflags.mk but since we already call default.mk the buildflags.mk should be included. There are some variables set, but since the cmake command does not include them, changes in them does not have an effect. There is no explanation about that flags do what and which are the relevant ones, so blindly just defining everything does not seem like a savvy solution. I would appreciate if you can pinpoint what is the missing flag exactly and what is now not passed to cmake correctly.. > > d/rules: > > https://salsa.debian.org/mariadb-team/mariadb-10.3/blob/master/debian/rules > One of the problems is using $(MAKE) instead of dh_auto_build and so on. > There are other problems in this file. Since the build command is constructed in the override_dh_auto_configure stanza this is the only way I am aware that I can pass it on to dh_auto_build. I am happy to try out alternative ways if you have concrete suggestions on how to refactor the d/rules file Thanks for pointers and help!
Seeking hardening flag / blhc expoert
Hello!
Is there any hardening flag / cmake expert around who could help me
get the hardening flags perfect in MariaDB 10.3?
Current state of build logs issues:
https://qa.debian.org/bls/packages/m/mariadb-10.3.html
The blhc tool currently outputs this:
$ blhc --debian --line-numbers --color ${WORKING_DIR}/*.build || [ $? -eq 1 ]
9962:CPPFLAGS missing (-D_FORTIFY_SOURCE=2):
/usr/lib/ccache/x86_64-linux-gnu-g++
-I/tmp/building/package/builddir/storage/tokudb/PerconaFT/snappy/src/build_snappy
-std=c++11 -g -O2 -fdebug-prefix-map=/tmp/building/package=.
-fstack-protector-strong -Wformat -Werror=format-security -pie -fPIC
-Wl,-z,relro,-z,now -fstack-protector --param=ssp-buffer-size=4
-fno-rtti -Wno-shadow -Wno-implicit-fallthrough -std=c++11
-Wno-missing-field-initializers -Wno-missing-field-initializers
-Wstrict-null-sentinel -Winit-self -Wswitch -Wtrampolines -Wlogical-op
-Wno-error=missing-format-attribute -Wno-error=maybe-uninitialized
-fno-rtti -fno-exceptions -Wno-error=nonnull-compare -Wpacked
-fno-omit-frame-pointer -Wno-error=strict-overflow -fexceptions
-Wextra -Wno-missing-noreturn -Wmissing-declarations -Wpointer-arith
-Wcast-align -O2 -g -DNDEBUG -fPIC -Wno-sign-compare
-Wno-unused-function -Wno-unused-parameter -fvisibility=hidden -fPIC
-o CMakeFiles/snappy.dir/snappy.cc.o -c
/tmp/building/package/builddir/storage/tokudb/PerconaFT/snappy/src/build_snappy/snappy.cc
9964:CPPFLAGS missing (-D_FORTIFY_SOURCE=2):
/usr/lib/ccache/x86_64-linux-gnu-g++
-I/tmp/building/package/builddir/storage/tokudb/PerconaFT/snappy/src/build_snappy
-std=c++11 -g -O2 -fdebug-prefix-map=/tmp/building/package=.
-fstack-protector-strong -Wformat -Werror=format-security -pie -fPIC
-Wl,-z,relro,-z,now -fstack-protector --param=ssp-buffer-size=4
-fno-rtti -Wno-shadow -Wno-implicit-fallthrough -std=c++11
-Wno-missing-field-initializers -Wno-missing-field-initializers
-Wstrict-null-sentinel -Winit-self -Wswitch -Wtrampolines -Wlogical-op
-Wno-error=missing-format-attribute -Wno-error=maybe-uninitialized
-fno-rtti -fno-exceptions -Wno-error=nonnull-compare -Wpacked
-fno-omit-frame-pointer -Wno-error=strict-overflow -fexceptions
-Wextra -Wno-missing-noreturn -Wmissing-declarations -Wpointer-arith
-Wcast-align -O2 -g -DNDEBUG -fPIC -Wno-sign-compare
-Wno-unused-function -Wno-unused-parameter -fvisibility=hidden -fPIC
-o CMakeFiles/snappy.dir/snappy-c.cc.o -c
/tmp/building/package/builddir/storage/tokudb/PerconaFT/snappy/src/build_snappy/snappy-c.cc
9966:CPPFLAGS missing (-D_FORTIFY_SOURCE=2):
/usr/lib/ccache/x86_64-linux-gnu-g++
-I/tmp/building/package/builddir/storage/tokudb/PerconaFT/snappy/src/build_snappy
-std=c++11 -g -O2 -fdebug-prefix-map=/tmp/building/package=.
-fstack-protector-strong -Wformat -Werror=format-security -pie -fPIC
-Wl,-z,relro,-z,now -fstack-protector --param=ssp-buffer-size=4
-fno-rtti -Wno-shadow -Wno-implicit-fallthrough -std=c++11
-Wno-missing-field-initializers -Wno-missing-field-initializers
-Wstrict-null-sentinel -Winit-self -Wswitch -Wtrampolines -Wlogical-op
-Wno-error=missing-format-attribute -Wno-error=maybe-uninitialized
-fno-rtti -fno-exceptions -Wno-error=nonnull-compare -Wpacked
-fno-omit-frame-pointer -Wno-error=strict-overflow -fexceptions
-Wextra -Wno-missing-noreturn -Wmissing-declarations -Wpointer-arith
-Wcast-align -O2 -g -DNDEBUG -fPIC -Wno-sign-compare
-Wno-unused-function -Wno-unused-parameter -fvisibility=hidden -fPIC
-o CMakeFiles/snappy.dir/snappy-sinksource.cc.o -c
/tmp/building/package/builddir/storage/tokudb/PerconaFT/snappy/src/build_snappy/snappy-sinksource.cc
9968:CPPFLAGS missing (-D_FORTIFY_SOURCE=2):
/usr/lib/ccache/x86_64-linux-gnu-g++
-I/tmp/building/package/builddir/storage/tokudb/PerconaFT/snappy/src/build_snappy
-std=c++11 -g -O2 -fdebug-prefix-map=/tmp/building/package=.
-fstack-protector-strong -Wformat -Werror=format-security -pie -fPIC
-Wl,-z,relro,-z,now -fstack-protector --param=ssp-buffer-size=4
-fno-rtti -Wno-shadow -Wno-implicit-fallthrough -std=c++11
-Wno-missing-field-initializers -Wno-missing-field-initializers
-Wstrict-null-sentinel -Winit-self -Wswitch -Wtrampolines -Wlogical-op
-Wno-error=missing-format-attribute -Wno-error=maybe-uninitialized
-fno-rtti -fno-exceptions -Wno-error=nonnull-compare -Wpacked
-fno-omit-frame-pointer -Wno-error=strict-overflow -fexceptions
-Wextra -Wno-missing-noreturn -Wmissing-declarations -Wpointer-arith
-Wcast-align -O2 -g -DNDEBUG -fPIC -Wno-sign-compare
-Wno-unused-function -Wno-unused-parameter -fvisibility=hidden -fPIC
-o CMakeFiles/snappy.dir/snappy-stubs-internal.cc.o -c
/tmp/building/package/builddir/storage/tokudb/PerconaFT/snappy/src/build_snappy/snappy-stubs-internal.cc
Full log at:
https://salsa.debian.org/mariadb-team/mariadb-10.3/-/jobs/153422
d/rules:
https://salsa.debian.org/mariadb-team/mariadb-10.3/blob/master/debian/rules
Accepted mariadb-10.3 1:10.3.13-2 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 01 Apr 2019 23:05:31 +0300 Source: mariadb-10.3 Binary: libmariadb-dev libmariadbclient-dev libmariadb-dev-compat libmariadb3 libmariadbd19 libmariadbd-dev mariadb-common mariadb-client-core-10.3 mariadb-client-10.3 mariadb-server-core-10.3 mariadb-server-10.3 mariadb-server mariadb-client mariadb-backup mariadb-plugin-connect mariadb-plugin-rocksdb mariadb-plugin-oqgraph mariadb-plugin-tokudb mariadb-plugin-mroonga mariadb-plugin-spider mariadb-plugin-gssapi-server mariadb-plugin-gssapi-client mariadb-plugin-cracklib-password-check mariadb-test mariadb-test-data Architecture: source Version: 1:10.3.13-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 Connector/C, compatibility symlinks libmariadb3 - MariaDB database client library libmariadbclient-dev - MariaDB database development files (transitional package) libmariadbd-dev - MariaDB embedded database, development files libmariadbd19 - MariaDB embedded database, shared library mariadb-backup - Backup tool for MariaDB server mariadb-client - MariaDB database client (metapackage depending on the latest vers mariadb-client-10.3 - MariaDB database client binaries mariadb-client-core-10.3 - MariaDB database core client binaries mariadb-common - MariaDB common metapackage mariadb-plugin-connect - Connect storage engine for MariaDB mariadb-plugin-cracklib-password-check - CrackLib Password Validation Plugin for MariaDB mariadb-plugin-gssapi-client - GSSAPI authentication plugin for MariaDB client mariadb-plugin-gssapi-server - GSSAPI authentication plugin for MariaDB server mariadb-plugin-mroonga - Mroonga storage engine for MariaDB mariadb-plugin-oqgraph - OQGraph storage engine for MariaDB mariadb-plugin-rocksdb - RocksDB storage engine for MariaDB mariadb-plugin-spider - Spider storage engine for MariaDB mariadb-plugin-tokudb - TokuDB storage engine for MariaDB mariadb-server - MariaDB database server (metapackage depending on the latest vers mariadb-server-10.3 - MariaDB database server binaries mariadb-server-core-10.3 - MariaDB database core server files mariadb-test - MariaDB database regression test suite mariadb-test-data - MariaDB database regression test suite - data files Closes: 905599 910902 925117 Changes: mariadb-10.3 (1:10.3.13-2) unstable; urgency=medium . [ Olaf ] * Use upstream conf defaults (Closes: #905599). This is critically important so that nothing defined in the configuration would hold back upstream improvements in default option values. . [ Otto Kekäläinen ] * Extend gitlab-ci.yml to include MySQL to MariaDB upgrade testing and also refine automatic testing in many ways to ensure as little regressions as possible. * Automatically rename 'auth_socket' to 'unix_socket' when upgrading from MySQL 5.7 which otherwise would completely fail. * Drop the transitional libmariadbclient18 package (Closes: #925117) * Move resolveip from mariadb-server-10.3 to -core-10.3 (Closes: #910902) * Move all mariadb-server-x.x *.sql files to mariadb-server-core-x.x package Checksums-Sha1: 3246e0afa6d28bcaa20309ab6337b1fb8304a60c 4699 mariadb-10.3_10.3.13-2.dsc 34f9e99a80ce278df8bc7f6825a9348733180a9e 268644 mariadb-10.3_10.3.13-2.debian.tar.xz 01ceac6498104df1004a59800f88e11dc6bdbb14 9070 mariadb-10.3_10.3.13-2_source.buildinfo Checksums-Sha256: 401e607590e25566f7af0aebd4a801690d78a2256e711a8413d475a7182d6828 4699 mariadb-10.3_10.3.13-2.dsc f7e9979ecfe5a5ba99b8316fb1e4bcb6b8587262254945877fcf0856a601ce96 268644 mariadb-10.3_10.3.13-2.debian.tar.xz 69b5b205afc87cd073324e3ef5fb37124278f742213284d7b878c8557e20fd54 9070 mariadb-10.3_10.3.13-2_source.buildinfo Files: d1df603c67fd0ad4552819be9a5655ed 4699 database optional mariadb-10.3_10.3.13-2.dsc e8085f1ef365a595c70697e0880964a6 268644 database optional mariadb-10.3_10.3.13-2.debian.tar.xz 5c9d680fe6cfeaf84a3d785ae77dbd0a 9070 database optional mariadb-10.3_10.3.13-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEmbRSsR88dMO0U+RvvthEn87o2ogFAlyied0ACgkQvthEn87o 2oiKMBAAgqlJ3HRVYI0IHPKCAwD4gmjnPdpYVOja5X3KoRvSoEE8LfY+l9LF0Kdo heubh18GIv+qQT/WkTeBdJ0WTmCeIkQSYfFiVQ8R5dO+8JlxwZ+zoSz4gulhW7au lsF02IdAOwkBmZWCgTLOJJ8P5YSy3Zxarx3XYAuFPINonWJgZyOKByKgaYJGK2FI PKKkbS1cH+Vjrt/rpFl5wslgpdZzCrH/X68enrl/Z0lG31GZHEGu0ep3l6cIcGUg dRFudi+cQEgjy60QXSVYD2cdDdM8q3GhvxM9Mgs0J+wkq1Q6rDkOXIvbQm4QeHKH 8cPvE7qicl3mAwc3UFncqwNgBJ6cbxsv5sHaJJ+t9hLzj9jstd3k+Xt+H0seLvCc Cte9L8SNOSs4UTX2T1ixfs1viqWHQSg29pbKMecRHT6KUP7D/so3+AUGJI4gjH+w lt9SiaO3nmXlBWrpyvR+SscgOzyGlbg3jx3Mtn3b2ZCDVoTnzrfAZbBy4bSZ123a v2sNxT34Spxc+R1QB0JnViFnZkz7OmR+0W9Vy05io5iha3yz9hGVFY6Y979+qsFW VhKHzDA3+iU+bp6WzoTPRZ7Pq07+eIV3xIfy8TCW5uzjlTS/afkaJZDSNL5TMoXU lxRhDX9R6itjWMA0G008YaE22egXnEfh1YrUGVNjmdDjfKMIHDE= =w1l1
