Bug#1061410: python3-trio: AttributeError: module 'eventlet.green.select' has no attribute 'epoll'

severity 1061410 wishlist thanks This doesn't seem like a bug in python-trio to me. It's simply using select.epoll(). If that's being monkey patched by gevent in a way that breaks things then that seems like either a gevent problem or a fundamental incompatibility in trying to use Trio at the

Bug#1037016: mk-build-deps fails if the package version is 0

to reproduce: # mkdir debian # cat > debian/changelog test (0) UNRELEASED; urgency=medium * Test mk-build-deps -- Robie Basak Thu, 01 Jun 2023 16:03:13 + # cat > debian/control Source: test Build-Depends: hello # mk-build-deps -i -r dpkg-buildpackage: info: source package test-build-dep

Bug#1033606: Add dep8 tests for mosh

+ + [ Sergio Durigan Junior ] + * d/t/upstream-tests: New dep8 test which runs the upstream test +suite against a system mosh. + + [ Robie Basak ] + * d/t/smoke: smoke test for mosh using pexpect. + + -- Robie Basak Wed, 22 Mar 2023 13:36:00 + + mosh (1.4.0-1build1) lunar; urgency=medium

Bug#1030487: python-trustme: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

clone 1030487 -1 reassign -1 python3-service-identity 18.1.0-7 retitle -1 Missing dependency on python3-six makes package unusable thanks On Sat, Feb 04, 2023 at 08:58:30AM +0100, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build > on amd64. [...] > >

Bug#1026155: python-trio: diff for NMU version 0.22.0-0.1

On Sat, Dec 17, 2022 at 07:28:24AM +0100, Jochen Sprickerhof wrote: > I've prepared an NMU for python-trio (versioned as 0.22.0-0.1) and > uploaded it to DELAYED/5. Please feel free to tell me if I > should delay it longer. Thank you for working on this! Assuming it builds and passes tests OK, +1

Bug#1024016: mysql-8.0: CVE-2022-39400 CVE-2022-39402 CVE-2022-39403 CVE-2022-39408 CVE-2022-39410 CVE-2022-21594 CVE-2022-21599 CVE-2022-21604 CVE-2022-21608 CVE-2022-21611 CVE-2022-21617 CVE-2022-21

On Sun, Nov 13, 2022 at 08:31:24PM +0100, Moritz Mühlenhoff wrote: > The following vulnerabilities were published for mysql-8.0. FTR, an update to 8.0.31 to fix these is already prepared and being tested at https://salsa.debian.org/mariadb-team/mysql/-/merge_requests/65 signature.asc

Bug#1022994: Bug#1023778: TMPDIR behaviour in maintainer scripts [was: Re: Bug#1023778: mysql-server-8.0: fails to restart on upgrade with libpam-tmpdir]

On Sun, Nov 13, 2022 at 05:46:00PM +0100, Marco d'Itri wrote: > On Nov 13, Robie Basak wrote: > > > This seems inconsistent to me. Where is the expectation that TMPDIR must > > be unset if dropping privileges coming from? Obviously for users of > Where is the expectation tha

Bug#1022994: Bug#1023778: TMPDIR behaviour in maintainer scripts [was: Re: Bug#1023778: mysql-server-8.0: fails to restart on upgrade with libpam-tmpdir]

On Sun, Nov 13, 2022 at 04:16:29PM +0100, Marco d'Itri wrote: > And I think that it would be wrong to have dpkg generally unset $TMPDIR, > because if root sets it then it would be reasonable to expect that also > dpkg and the maintainer scripts use it (as long as they are not dropping >

Bug#1022994: Bug#1023778: TMPDIR behaviour in maintainer scripts [was: Re: Bug#1023778: mysql-server-8.0: fails to restart on upgrade with libpam-tmpdir]

On Sun, Nov 13, 2022 at 02:58:47PM +, Simon McVittie wrote: > If the maintainer script is *dropping* privileges from root down to a > system user, then I think the maintainer script is/should be responsible > for doing that privilege drop in a way that works... Agreed, but amongst various

Bug#1022994: Bug#1023778: TMPDIR behaviour in maintainer scripts [was: Re: Bug#1023778: mysql-server-8.0: fails to restart on upgrade with libpam-tmpdir]

On Sun, Nov 13, 2022 at 02:21:58AM +0100, Marco d'Itri wrote: > On Nov 12, Otto Kekäläinen wrote: > > > 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

Bug#1023778: TMPDIR behaviour in maintainer scripts [was: Re: Bug#1023778: mysql-server-8.0: fails to restart on upgrade with libpam-tmpdir]

On Thu, Nov 10, 2022 at 10:46:55PM +, brian m. carlson wrote: > > I think it's more wide than that: If you change UID, you need to > > sanitise the environment. Your HOME is likely to be wrong. PATH might > > very well be pointing at directories which are not appropriate for the > > user

Bug#1023778: TMPDIR behaviour in maintainer scripts [was: Re: Bug#1023778: mysql-server-8.0: fails to restart on upgrade with libpam-tmpdir]

On Thu, Nov 10, 2022 at 05:37:53PM +0100, Tollef Fog Heen wrote: > I think it's more wide than that: If you change UID, you need to > sanitise the environment. Your HOME is likely to be wrong. PATH might > very well be pointing at directories which are not appropriate for the > user you're

Bug#1023778: TMPDIR behaviour in maintainer scripts [was: Re: Bug#1023778: mysql-server-8.0: fails to restart on upgrade with libpam-tmpdir]

On Thu, Nov 10, 2022 at 12:08:55PM +0100, Marco d'Itri wrote: > > But are you in essence saying that libpam-tmpdir requires that *every > > maintainer script* that runs things as non-root, or starts processes > > that do that, unset TMPDIR first? > This would not be right, because it is totally

Bug#1023778: TMPDIR behaviour in maintainer scripts [was: Re: Bug#1023778: mysql-server-8.0: fails to restart on upgrade with libpam-tmpdir]

Thank you for the report. Adding debian-devel@ and the libpam-tmpdir maintainer for wider discussion. On Thu, Nov 10, 2022 at 12:54:34AM +, brian m. carlson wrote: > On my systems, I use libpam-tmpdir, which provides each user with a > private temporary directory owned and accessible only by

Bug#1020518: [debian-mysql] Bug#1020518: Bug#1020518: libmariadb3 is a client library that include marriadb-common that will mess with /etc/mysql/my.cnf

On Thu, Sep 22, 2022 at 11:32:05PM +0200, Ghislain Adnet wrote: > in fact /etc/mysql/mariadb.cnf does not exist as there is a mysql server and > not a mariadb one. mariadb-common ships /etc/mysql/mariadb.cnf. > I have a perconna mysql server running and i want to install mytop that > require a

Bug#1020518: [debian-mysql] Bug#1020518: Bug#1020518: libmariadb3 is a client library that include marriadb-common that will mess with /etc/mysql/my.cnf

On Thu, Sep 22, 2022 at 05:28:27PM +0100, Robie Basak wrote: > Again, note that I'm still speculating here because I don't follow the > exact sequence of events which is causing the third party packaging to > trip up here. If there's something we're doing wrong then we should fix > it,

Bug#1020518: [debian-mysql] Bug#1020518: libmariadb3 is a client library that include marriadb-common that will mess with /etc/mysql/my.cnf

On Thu, Sep 22, 2022 at 06:21:34PM +0200, Ghislain Adnet wrote: > So perhaps we could see it another way : > in this particular case i think that a client library, if it find an existing > /etc/mysql/my.cnf, should not do anything as it is there adn so everything it > need is okay. > There is no

Bug#1020518: [debian-mysql] Bug#1020518: libmariadb3 is a client library that include marriadb-common that will mess with /etc/mysql/my.cnf

On Thu, Sep 22, 2022 at 05:10:05PM +0200, nobody wrote: >* What outcome did you expect instead? > >installing a client library should not require anything on the server side > and should not modify server configuration of mariadb or other mysql flavors > (imho ;p) Both MySQL/MariaDB

Bug#1020505: debuginfod is configured by an environment variable instead of /etc

Package: libdebuginfod-common Version: 0.187-2 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu kinetic Hi, libdebuginfod-common sets DEBUGINFOD_URLS to a reasonable default (after prompting appropriately because it's a privacy leak otherwise). But Debian Policy 9.9 says: "Programs

Bug#1002239: google-authenticator: FTBFS: dh_auto_test: error: make -j4 test VERBOSE=1 returned exit code 2

Hi, On Tue, Dec 21, 2021 at 05:33:17PM +0100, Lucas Nussbaum wrote: > Source: google-authenticator > Version: 20191231-2 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20211220 ftbfs-bookworm > > Hi, > > During a rebuild of all

Bug#1005720: [debian-mysql] Bug#1005720: mysql-8.0: FTBFS with OpenSSL 3.0

On Fri, Jul 01, 2022 at 05:45:12PM +0200, Bastian Germann wrote: > Lena, please tag the changelog entries accordingly, at least for RC bugs so > they do not keep the package from migrating. Note that mysql-8.0 is permanently blocked from migrating by order of the release team. They want MariaDB

Bug#1010804: frogatto: Missing Build-Depends on libopengl-dev

Package: frogatto Version: 1.3.1+dfsg-5 Severity: serious Tags: patch Justification: fails to build from source (but built successfully in the past) User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu kinetic ubuntu-patch *** /tmp/tmpULOMPK/bug_body In Ubuntu, the build was failing with

Bug#1010621: Missing dependency on fdisk

Package: cloud-guest-utils Version: 0.31-2 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu kinetic Hi, cloud-guest-utils is missing a dependency on whatever supplies sfdisk or sgdisk (eg. fdisk and gdisk), so growpart fails by default. gdisk is a Recommends. Should this be a Depends,

Bug#1010372: [debian-mysql] Bug#1010372: mysql-8.0: Should mysql-8.0 be removed from unstable?

Hi Salvatore, On Fri, Apr 29, 2022 at 09:52:04PM +0200, Salvatore Bonaccorso wrote: > Should mysql-8.0 be dropped completely from the archive or is there > still interest in keeping in in unstable? I think this is a dupe of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004180? Was asking

Bug#1004180: [debian-mysql] Bug#1004180: mysql-8.0: should mysql-8.0 be removed from unstable?

On Sat, Jan 22, 2022 at 10:53:48AM +0100, Salvatore Bonaccorso wrote: > While mysql-8.0 itself won't enter testing, the version in unstable is > as well only from february 2021, lacking behind several updates for > fixes in the Oracle CPUs. > > Should mysql-8.0 be removed as well from unstable?

Bug#1000866: Source package is missing files required to make a derived work

Source: debianutils Severity: serious Justification: FTBFS when making a derived work, contrary to the spirit of the Debian Social Contract Version: 5.5-1 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu jammy Hi, If I patch the debianutils source package, then I find that I cannot

Bug#998699: Bug#998700: python-trio: Please package new upstream version

forcemerge 998699 998700 tags 998699 + help thanks On Sat, Nov 06, 2021 at 03:24:48PM -0400, Boyuan Yang wrote: > As listed on https://tracker.debian.org/pkg/python-trio , package python-trio > has new upstream releases that should be packaged. Please consider updating > this package in Debian.

Bug#985320: [debian-mysql] Bug#985320: mariadb-common: Spurious messages when installing package

Hi, On Tue, Mar 16, 2021 at 12:23:53AM +0100, jpp wrote: > When upgrading python3-mysqldb apt also update mariadb-common and I get some > spurious messages : > Setting up mariadb-common (1:10.5.9-1) ... > update-alternatives: using /etc/mysql/mariadb.cnf to provide /etc/mysql/my.cnf > (my.cnf) in

Bug#983044: Please update to ssh-import-id 5.11

Source: ssh-import-id Version: 5.10-1 Severity: wishlist Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu hirsute ubuntu-patch Hi, I just uploaded ssh-import-id 5.11 to Ubuntu. I think it's suitable for upload to Debian also. You can grab it from: dget

Bug#981195: mysql-5.7: should mysql-5.7 be removed from Debian unstable?

forcemerge 969095 981195 thanks On Wed, Jan 27, 2021 at 03:11:40PM +0100, Salvatore Bonaccorso wrote: > While mysql-5.7 is already not present in testing, I wonder if the > mysql-5.7 package should be alltogether removed in the Debian archives > as well from unstable. Agreed. We already have a

Bug#969602: lptools: UnicodeDecodeError in lp-project-upload

tags 969602 + patch thanks I just bumped into this. The solution is to open the release tarball and its signature as binary, as follows. This should probably just be squashed into debian/patches/02_python3: --- a/bin/lp-project-upload 2020-12-07 19:40:42.0 + +++

Bug#972445: [debian-mysql] Bug#972445: mysql-server-8.0: possibly erroneous inclusion of mecab libraries

tags 972445 + wontfix thanks On Sun, Oct 18, 2020 at 07:18:13PM +, Norwid Behrnd wrote: > Expected solution: the installation of package mysql-server should > skip the installation of these four libraries. Debian generally configures packages to support every feature shipped in Debian that

Bug#969095: RM: mysql-5.7 -- ROM; superseded by mysql-8.0

On Sat, Oct 03, 2020 at 11:59:26AM -0700, Sean Whitton wrote: > Looks like there is still a rdep on pytest-services. Sorry. It looks like I missed searching for reverse build dependencies. I filed a blocking bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971670 against src:pytest-services

Bug#971670: Build dependency on deprecated package

Source: pytest-services Version: 2.1.0-1 src:pytest-services 2.1.0-1 build depends on mysql-testsuite-5.7, which is now deprecated in favour of 8.0. Please use mysql-testsuite-8.0 instead, or better, use mysql-testsuite which is a metapackage that depends on the current version. This is blocking

Bug#971367: [debian-mysql] Bug#971367: mariadb-10.5 should not embed wolfssl

Hi, The relevant previous bug is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921488 where the packaging switched from "system" to "bundled". Switching back to "system" would regress that licensing problem. Also relevant is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924937 which is

Bug#887007: [debian-mysql] Bug#887007: Bug#887007: my.cnf handling collides with MySQL

I think the original idea was: Keep the client configuration common to both MySQL and MariaDB as much as possible. This is because we do want the clients to be coinstallable and also because users often don't have control of the client in use since it goes through a client library they didn't

Bug#887007: [debian-mysql] Bug#887007: Bug#887007: my.cnf handling collides with MySQL

On Mon, Sep 28, 2020 at 03:31:37PM +0300, Otto Kekäläinen wrote: > We still have this situation in mariadb-10.5. How do you suggest we > change the current situation to remedy this? I think we should move the symlink claim handling from mariadb-common to mariadb-server-. Then it'd work the same

Bug#969115: [debian-mysql] Bug#969115: mysql-5.7: FTBFS with GCC 10: multiple definition of symbols

tags 969115 + wontfix thanks Hi, Thank you for the FTBFS report. As it happens src:mysql-5.7 has been deprecated by src:mysql-8.0 and I filed a removal bug 969095 for src:mysql-5.7. So it seems pointless to fix this now. Robie On Thu, Aug 27, 2020 at 09:48:21PM +0200, Aurelien Jarno wrote: >

Bug#969095: RM: mysql-5.7 -- ROM; superseded by mysql-8.0

Package: ftp.debian.org Severity: normal Binary movements: libmysqld-dev is gone in src:mysql-8.0 - this feature is no longer supported upstream. The other binary packages have direct replacements: libmysqlclient20 -> libmysqlclient21 s/5.7/8.0/ There's also a new binary package mysql-router.

Bug#968854: [debian-mysql] Bug#968854: libmysqld-dev uninstallable in Debian Sid due to recent mysql-8.0 upload

tags 968854 + moreinfo thanks libmysqld is no longer part of MySQL and so libmysql-dev is no longer a binary source package produced by MySQL packaging. src:mysql-8.0 does not produce libmysqld-dev. The libmysqld-dev package in unstable is left over from src:mysql-5.7 which needs to be removed.

Bug#968149: mysql-router-dbgsym,mysql-server-core-8.0-dbgsym: file conflict due to shared build-id

Thank you for the report. On Sun, Aug 09, 2020 at 09:48:13PM +0200, Andreas Beckmann wrote: > This is likely caused by the corresponding binary packages shipping > identical binaries (or librariesi, ...) with different names. Looks like this is because this file is shipped in both mysql-router

Bug#968356: transition: mysql-8.0

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Though this is a transition, I don't think it requires the usual coordination with the release team because it won't entangle with anything. src:mysql-5.7 generates binary package

Bug#953259: Missing modules in build: regression since buster

tags 953259 + patch user ubuntu-de...@lists.ubuntu.com usertag 953259 + ubuntu-patch thanks Looking at the previous build of 2.0.27, it looks like only three extra modules are different with 3.4.0-2. The rest are being automatically enabled by the configure script, when previously they were

Bug#953259: Missing modules in build: regression since buster

Package: inspircd Version: 3.4.0-2 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu focal Hi, I noticed that some modules such as m_ldapauth and m_ldapoper are missing from the build, which is a regression from 2.0.27-1 in Buster. AFAICT, the change was made in the packaging update

Bug#943149: pam-mysql: Python2 removal in sid/bullseye

tags 943149 + patch thanks Hi, I understand that this is blocked in Debian by the marked bug. I have fixed this in Ubuntu with the attached patch though, which I hope is helpful when this bug is unblocked in Debian. Robie diff -Nru pam-mysql-0.8.1/debian/tests/auth

Bug#953030: bacula-sd.postinst fails on systems with protected_regular=2 enabled

Hi, On Tue, Mar 03, 2020 at 05:53:31PM +0100, Carsten Leonhardt wrote: > thanks for the patch. I've commited a change to our git repository based > on it. For consistency I changed the order in similar postinst files > too. Thank you! I grabbed your commit in Ubuntu to replace my patch.

Bug#953030: bacula-sd.postinst fails on systems with protected_regular=2 enabled

://lists.ubuntu.com/archives/ubuntu-devel/2020-February/040904.html From 2efa5028139683bd851c76ab117cc47cf698e2b3 Mon Sep 17 00:00:00 2001 From: Robie Basak Date: Mon, 2 Mar 2020 20:19:27 + Subject: [PATCH] * d/bacula-sd.postinst: change temporary file ownership after writing

Bug#952744: MySQL tests fail

. Regardless, attached is the fix for the failures themselves. From ce4d5170dd8ebd179bfbb773b250667f15376e15 Mon Sep 17 00:00:00 2001 From: Robie Basak Date: Thu, 27 Feb 2020 15:49:16 + Subject: [PATCH] * d/p/test_mysql_date_tz.patch: fix MySQL test timezone inputs. --- debian/patches/series

Bug#952743: Test suite failures don't fail the build

attached. From 7bb6ed96a6900a6178ca390a3d2ce99c7ca4cacc Mon Sep 17 00:00:00 2001 From: Robie Basak Date: Thu, 27 Feb 2020 15:48:31 + Subject: [PATCH] * d/p/test_exception_failure.patch: make test exceptions fail the test suite and thus the build. --- debian/patches/series

Bug#952378: spamassassin: Example config needs a way of whitelisting GPG signed mail (EG from DDs)

On Mon, Feb 24, 2020 at 01:56:59AM +1100, Russell Coker wrote: > It would be good if the example configuration included a way of whitelisting > mail from known good GPG keys. An example configuration that would be useful > in real use would be the Debian developer keylist. I think this is a

Bug#951600: "debian/rules build" fails to call defined build-indep target, causing FTBFS

Source: zoneminder Version: 1.32.3-2 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu focal ubuntu-patch Severity: serious Justification: policy violation in behaviour of build target causing FTBFS Tags: patch Hi, In Ubuntu this package FTBFS. The reason seems to be that the

Bug#935042: Program phones home by default

On Sun, Oct 13, 2019 at 11:02:45PM +0200, Birger Schacht wrote: > The problem is that the package will be removed from unstable in a > couple of days because of this bug report. 3 month is sometimes not that > much time to fix a bug or even comment on a bug report. And the release > of bullseye is

Bug#935042: Program phones home by default

On Sun, Oct 13, 2019 at 05:23:40PM +0200, Birger Schacht wrote: > Robie, could you please point out the part of the Debian policy that > this package is violating? I cannot. I believe that this issue is such a clear violation of Debian's philosophy that it has never been necessary to document it

Bug#941986: [debian-mysql] Bug#941986: mariadb-client-10.3: InnoTop crashes during use

On Tue, Oct 08, 2019 at 11:31:14AM -0400, Michael Krieger wrote: > This is because technically 10.3 is not officially supported by innotop, and > so it uses old legacy code which returns incorrect results. > > While innotop doesn't get support 10.3, us shipping innotop with MariaDB 10.3 > means

Bug#935042: your mail

On Mon, Sep 30, 2019 at 12:39:33PM +0200, Michael Boelen wrote: > Although I can understand the sentiment of disabling "phoning home" > functionality, it is there with a good reason. It helps people to learn > when their software is (very) outdated, especially when it comes to doing a > security

Bug#935042: Program phones home by default

Package: lynis Version: 2.6.2-1 Severity: serious Justification: privacy leak By default, this program appears to make a DNS query to lynis-latest-version.cisofy.com. thus leaking information about the system and the fact that the user is running an audit. This is particularly egregious in the

Bug#925463: pytest: Please provide a pytest binary for Python 3.x

[I'm not the maintainer; just driving by] On Mon, Mar 25, 2019 at 01:14:34PM +, Joel Cross wrote: > I noticed today that while the python3-pytest package works fine when invoked > as `python3 -m pytest`, it does not provide a binary, and the only binary > provided is as part of the

Bug#931804: python3-trustme: Key size too small

Hi Matthias, On Wed, Jul 10, 2019 at 05:42:03PM +0200, Matthias Urlichs wrote: > Package: python3-trustme > Version: 0.4.0-3 > Severity: important > Tags: patch > > Debian changed the default key size requirement to 2048 bits, thus keys > generated with trustme no longer work. I don't

Bug#927118: unblock: python-trustme/0.4.0-3

. This fixes another FTBFS due to test failure in the case that +the openssl binary package is installed, which is not a build dependency, +but apparently the buildds have it by default. Closes: #926652. + + -- Robie Basak Sat, 13 Apr 2019 17:30:20 +0100 + +python-trustme (0.4.0-2) unstable

Bug#926652: python-trustme: FTBFS on all

package is installed, which is not a build dependency, +but apparently the buildds have it by default. Closes: #926652. + + -- Robie Basak Sat, 13 Apr 2019 17:30:20 +0100 + python-trustme (0.4.0-2) unstable; urgency=medium * Explicitly build-depend on python3-idna to fix FTBFS. diff -Nru

Bug#926652: python-trustme: FTBFS on all

On Mon, Apr 08, 2019 at 01:38:04PM +, Ivo De Decker wrote: > The latest version of python-trustme in unstable fails on all: See also bug 925576. I haven't got round to looking at it yet. I hope to investigate and fix it soon; patches also welcome. signature.asc Description: PGP signature

Bug#925576: unblock: python-trustme/0.4.0-2

Hi Paul, On Sun, Mar 31, 2019 at 10:40:38AM +0200, Paul Gevers wrote: > The fix doesn't prevent the package from FTBFS. Please check > https://buildd.debian.org/status/fetch.php?pkg=python-trustme=all=0.4.0-2=1553646768=0 Thanks. I only spotted that after you approved the unblock request. It did

Bug#925576: unblock: python-trustme/0.4.0-2

/changelog 2019-03-26 23:23:50.0 + @@ -1,3 +1,10 @@ +python-trustme (0.4.0-2) unstable; urgency=medium + + * Explicitly build-depend on python3-idna to fix FTBFS. +Closes: #925566. + + -- Robie Basak Tue, 26 Mar 2019 23:22:42 + + python-trustme (0.4.0-1) unstable; urgency

Bug#925566: python-trustme: FTBFS: dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.7 returned exit code 13

On Tue, Mar 26, 2019 at 09:49:00PM +0100, Lucas Nussbaum wrote: > During a rebuild of all packages in buster (in a buster chroot, not a > sid chroot), your package failed to build on amd64. Thank you for this report. It looks like python-trustme (build time) tests uses the idna directly, so an

Bug#924937: libpq5: OpenSSL license contamination of GPL reverse-dependencies

On Tue, Mar 19, 2019 at 10:49:06AM +0100, Christoph Berg wrote: > Re: Robie Basak 2019-03-18 <20190318165800.gc12...@mal.justgohome.co.uk> > > It is well understood that the OpenSSL license is not "compatible" with > > the GPL (either version 2 or 3); and fur

Bug#924937: libpq5: OpenSSL license contamination of GPL reverse-dependencies

Package: libpq5 Version: 11.2-2 Severity: serious Affects: bandwidthd-pgsql dballe inspircd libnss-pgsql2 libodb-pgsql-2.4 pmacct r-cran-rpostgresql saga sphinxsearch tora ulogd2-pgsql yubikey-server-c Justification: renders many Debian packages undistributable Hello, It's come to my attention

Bug#921687: [debian-mysql] Bug#921687: systemctl just hangs on stoping or starting mysql-server-5.7

Hi, Could this be the issue described here: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1600164 ? Apart from that, I don't know of anyone else affected by this, so I don't think we can treat it as a bug in the mysql-server-5.7 package without further details of why it must be a bug

Bug#921423: /var/log/letsencrypt gets wiped on transitional package purge

Package: letsencrypt Version: 0.28.0-1 Severity: grave Justification: causes data loss User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu disco Steps to reproduce: 1. Start on sid 2. apt install letsencrypt # using transitional package 3. Use letsencrypt or certbot 4. Later, note the

Bug#914172: [debian-mysql] Bug#914172: Bug#914172: Bug#914172: mariadb-server-10.1: mariadb-server sec-update (10.1.37-0+deb9u1) uninstalls default-mysql-server, mysql-server, mariadb-server-10.1 & ma

On Thu, Nov 22, 2018 at 10:44:42AM +0100, David Escala wrote: > Perhaps we should change the apt dist-upgrade command for security updates > (suggestions?), but > not adding new dependencies in a security update may also be a good policy. You should use apt pinning to restrict package upgrades to

Bug#895458: [debian-mysql] Status of debconf translation handling in mysql-5.7, help needed?

Hi Helge, On Wed, Nov 14, 2018 at 01:34:45PM +0100, Helge Kreutzmann wrote: > your package mysql-5.7 has several unhandled debcon > translations, some of then available for several month. I see that > several uplaods have been made, is there a reason for not including > those translations? Do you

Bug#893740: scons: diff for NMU version 3.0.1-1.1

On Fri, Nov 09, 2018 at 03:08:27PM +, Robie Basak wrote: > I've prepared an NMU for scons (versioned as 3.0.1-1.1) and > uploaded it to DELAYED/10. Please feel free to tell me if I > should delay it longer, or upload it some other way. Thank you for the upload. I've cancelled my NM

Bug#913424: trio does not have a stable API

Source: python-trio Version: 0.9.0-1 Severity: serious Forwarded: https://github.com/python-trio/trio/issues/1 Trio upstream do not yet consider the API stable, so in my opinion this package is not yet ready for a stable Debian release. Please use this bug for discussion if you think this status

Bug#893740: scons: diff for NMU version 3.0.1-1.1

(Closes: +#893740). + + -- Robie Basak Fri, 09 Nov 2018 14:45:13 + + scons (3.0.1-1) unstable; urgency=medium * New upstream release: diff -Nru scons-3.0.1/debian/patches/0110-remove_stale_files.patch scons-3.0.1/debian/patches/0110-remove_stale_files.patch --- scons-3.0.1/debian

Bug#900296: ITP: trio -- Async/await-native Python3 I/O library for humans and snake people

On Sat, Oct 13, 2018 at 09:03:47PM +0200, Matthias Urlichs wrote: > On 13.10.18 17:43, Robie Basak wrote: > > Any news on this? If not, any objection to me taking over this ITP? > > Go for it. You'll have to package a couple of small dependencies first > (sniffio, outcome). On

Bug#910960: ITP: python-outcome -- capture the outcome of Python function calls

Package: wnpp Severity: wishlist Owner: Robie Basak * Package name: python-outcome Version : 1.0.0-1 Upstream Author : Nathaniel J. Smith * URL : https://github.com/python-trio/outcome * License : Apache-2.0 or Expat Programming Lang: Python Description

Bug#910956: ITP: python-sniffio -- detect which async Python library is in use

Package: wnpp Severity: wishlist Owner: Robie Basak * Package name: python-sniffio Version : 1.0.0-1 Upstream Author : Nathaniel J. Smith * URL : https://github.com/python-trio/sniffio * License : Apache-2.0 or Expat Programming Lang: Python Description

Bug#910951: ITP: python-trustme -- fake certificate authority for test use

Package: wnpp Severity: wishlist Owner: Robie Basak * Package name: python-trustme Version : 0.4.0 Upstream Author : Nathaniel J. Smith * URL : https://github.com/python-trio/trustme * License : Apache-2.0 or Expat Programming Lang: Python Description

Bug#903917: Acknowledgement (libsss-sudo.postinst clobbers local change to /etc/nsswitch.conf)

I wonder if "dpkg -P libsss-sudo" is a reasonable workaround. Are there any cases where libsss-sudo needs to be installed but not active in nsswitch.conf? signature.asc Description: PGP signature

Bug#903917: libsss-sudo.postinst clobbers local change to /etc/nsswitch.conf

Package: libsss-sudo Version: 1.16.2-1 Severity: serious Justification: policy violation (section 10.7.3) User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu cosmic Steps to reproduce: 1. apt install sssd 2. Edit /etc/nsswitch.conf and remove "sss" from the "sudoers" entry 3. apt install

Bug#902603: /var/log/iptraf not created by default

Package: iptraf-ng Version: 1:1.1.4-6 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu cosmic The iptraf-ng package arranges to logrotate in /var/log/iptraf. The iptraf-ng -L option logs to /var/log/iptraf by default. Since the packaging doesn't currently create /var/log/iptraf, this

Bug#902601: freshclam apparmor profile prevents some operations

Package: clamav-freshclam Version: 0.100.0+dfsg-1 Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu cosmic ubuntu-patch Hi, We've received a downstream report of the following AppArmor denial: Jun 26 16:31:12 localhost kernel: [21690.397358] audit: type=1400

Bug#865931: [debian-mysql] Bug#865931: Dealing with new packaging policy

On Fri, Jun 15, 2018 at 04:42:20PM +0200, Narcis Garcia wrote: > Applications and CMS ask user for username to create their > databases and dedicated accounts. This is not solved with unattended > install of MariaDB server because those programs don't use "sudo", and > new Debian packaging policy

Bug#899959: bind9: Invalid maintainer address pkg-dns-de...@lists.alioth.debian.org

Fix proposed in: https://salsa.debian.org/dns-team/bind9/merge_requests/3 signature.asc Description: PGP signature

Bug#898161: dh_missing(1) manpage contradicts itself on default behaviour

Package: debhelper Version: 11.2.1 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu bionic X-Debbugs-Cc: ni...@thykier.net dh_missing(1) says: "Please note that without either of these options, dh_missing will silently do nothing." However, it later says that --list-missing "is the

Bug#898148: [debian-mysql] Bug#898148: mysql-server: it does not allow me to change the database

tags 898148 + moreinfo severity 898148 normal thanks Thank you for your report. Please explain what steps you followed with full details (what commands you typed, what configuration files you changed and how, etc) and explain exactly what you were expecting and what happened instead. Until

Bug#896709: [debian-mysql] Bug#896709: innobackupex: Error: Unsupported server version: '5.7.21-1-log'

tags 896709 + moreinfo thanks This doesn't appear to be a bug report. Please see https://www.debian.org/Bugs/Reporting (in particular the section entitled "The body of the report") and https://www.chiark.greenend.org.uk/~sgtatham/bugs.html and provide a full explanation. signature.asc

Bug#884462: Please update mongodb to 3.6

I've updated Ubuntu to mongodb 3.6. Rather than spam the bug with the entire patchset, you can view the changes I had to make here: https://git.launchpad.net/ubuntu/+source/mongodb/log?id=upload/1%253.6.3-0ubuntu1 signature.asc Description: PGP signature

Bug#895623: golang-github-juju-testing: dep8 test failure with mongodb 3.6

Package: golang-github-juju-testing Version: 0.0~git20170608.2fe0e88-3 Severity: normal Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu bionic ubuntu-patch In Ubuntu, the attached patch was applied to achieve the following: I'm bumping up to mongodb 3.6, which isn't

Bug#895548: Sources are missing, contrary to lintian override comment

Source: golang-github-smartystreets-goconvey Version: 1.6.1-3 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu bionic debian/source/lintian-overrides says: ## False-positives, sources provided in "debian/missing-sources": However there is no debian/missing-sources provided. So the

Bug#890446: bcache-tools: /dev/bcache/{by-uuid,by-label} symlinks not present after reboot

For the record, I've been reluctant to commit this without it having been accepted and resolved upstream. signature.asc Description: PGP signature

Bug#823860: bcache-tools: bcache does not work with suspend

On Mon, May 09, 2016 at 01:22:43PM -0400, Scott Moser wrote: > There is an initial /lib/systemd/system-sleep/bcache.sh in the Ubuntu bug. > The script there intends to use /lib/systemd/system-sleep/ . However, > systemd-suspend.service(8) has the following to say: > > | Note that scripts or

Bug#774797: initramfs-tools: Include bcache.ko by default

This seems like a good idea and a reasonable request, but needs someone to volunteer a patch. signature.asc Description: PGP signature

Bug#893897: Preferred method to request update from maintainer scripts not documented

Source: initramfs-tools Version: 0.130 Severity: wishlist bcache-tools currently just calls "update-initramfs -u" from its postinst. On initial review, this seemed inefficient to me over using the trigger. It looks like you actually wrap yourself to activate the trigger, so in practice it makes

Bug#893621: mongodb binaries can't be used directly

the same pattern +already established with MySQL and MariaDB packaging. + + -- Robie Basak <robie.ba...@ubuntu.com> Tue, 13 Feb 2018 11:35:01 + + mongodb (1:3.4.7-1ubuntu2) bionic; urgency=high * No change rebuild against openssl1.1. diff --git a/debian/control b/debian/control

Bug#892922: memcached.service is less secure by default

/null +++ b/debian/patches/restore-systemd-sandboxing @@ -0,0 +1,61 @@ +Author: Robie Basak <robie.ba...@canonical.com> +Description: Restore systemd sandboxing + Upstream regressed systemd sandboxing for everyone by default because RHEL + cannot support it. Put it back again to avoid this func

Bug#892732: [debian-mysql] Bug#892732: mysql-server: service start/stop or restart sometimes fails because mysql is still running after the stop

reassign 892732 mariadb-server-10.1 thanks mysql-server 5.5.+default is a transitional package in stretch that leads to mariadb-server-10.1, so reassigning. Robie signature.asc Description: PGP signature

Bug#888956: dep8 tests regressed by removal of mariadb-test

Source: mariadb-10.1 Version: 1:10.1.29-6 Severity: important User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu bionic X-Debbugs-CC: Ondřej Surý Commit 27202e3 regressed dep8 tests in buster since debian/tests/control declares a dependency on mariadb-test but this

Bug#887007: my.cnf handling collides with MySQL

Package: mariadb-client-10.1 Version: 1:10.1.29-6 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu bionic Steps to reproduce: apt install mariadb-client-10.1 apt install mysql-server-5.7 The second command will cause mariadb-client-10.1 because of a conflict with mysql-client-5.7,

Bug#885589: Test suite fails

Package: openscad-testing Version: 2015.03-2+dfsg-2+b1 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu bionic Running "openscad-testrun --virtual" fails on sid. Expected: pass The failures are as follows. AFAICT, echotest_rands cannot possibly work because I can't find the source

Bug#885429: Please add dep8 test

Source: openscad Version: 2015.03-2+dfsg-2 Severity: wishlist Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu bionic ubuntu-patch Thank you for the openscad-testing package. It was very helpful in pinning down a bug I'm chasing. Please could you add a dep8

  1   2   3   4   >