Source: python-btrees
Version: 4.3.1-1
Severity: minor
Dear Maintainer,
Working with the ‘python-btrees’ packages requires understanding how
it works and what it does.
Please set a “Suggests: python-btrees-doc” dependency to the binary
package ‘python-btrees’, or other binary packages for which
Package: jupyter-nbextension-jupyter-js-widgets
Version: 5.2.2-2
Severity: minor
Dear Maintainer,
I recently installed notebook and some related packages but had problems.
Then I decided to purge all the packages but
jupyter-nbextension-jupyter-js-widgets
fails with the fillowing error message:
On 01/01/17 17:30, Dominik George wrote:
> Hi,
>
> I was able to identify the issue, but need help fixing it.
>
> The problem is that the testing module uses the default root user of the
> newly created database, and it uses the UNIX socket, and that has
> peercred authentication by default in Ma
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 02 Jan 2017 02:20:09 +0800
Source: pylama
Binary: python-pylama python3-pylama pylama
Architecture: source
Version: 7.3.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team
Changed-By
pylama_7.3.3-1_source.changes uploaded successfully to localhost
along with the files:
pylama_7.3.3-1.dsc
pylama_7.3.3.orig.tar.gz
pylama_7.3.3-1.debian.tar.xz
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
___
Pyt
On 01/01/17 at 18:58 +0500, Andrey Rahmatullin wrote:
> On Sun, Jan 01, 2017 at 02:05:44PM +0100, Lucas Nussbaum wrote:
> > I could on 2016-12-19. Could you post a build log and diff it with mine?
> Attached. I couldn't see anything interesting in the diff, but the failing
> tests succeed and are n
FYI: The status of the pydbus source package
in Debian's testing distribution has changed.
Previous version: (not in testing)
Current version: 0.5.1-1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you will
FYI: The status of the toolz source package
in Debian's testing distribution has changed.
Previous version: 0.8.1-1
Current version: 0.8.2-1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you will receive
l
FYI: The status of the webtest source package
in Debian's testing distribution has changed.
Previous version: 2.0.23-1
Current version: 2.0.24-1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you will recei
FYI: The status of the python-decorator source package
in Debian's testing distribution has changed.
Previous version: 4.0.6-1
Current version: 4.0.10-1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you wi
FYI: The status of the python-slugify source package
in Debian's testing distribution has changed.
Previous version: 1.2.0-1
Current version: 1.2.1-1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you will
FYI: The status of the python-btrees source package
in Debian's testing distribution has changed.
Previous version: (not in testing)
Current version: 4.3.1-1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day y
FYI: The status of the python-aiohttp source package
in Debian's testing distribution has changed.
Previous version: 1.1.5-1
Current version: 1.2.0-1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you will
Hi,
I was able to identify the issue, but need help fixing it.
The problem is that the testing module uses the default root user of the
newly created database, and it uses the UNIX socket, and that has
peercred authentication by default in MariaDB.
I tried the following to disable peercred for t
On Sun, Jan 01, 2017 at 02:05:44PM +0100, Lucas Nussbaum wrote:
> I could on 2016-12-19. Could you post a build log and diff it with mine?
Attached. I couldn't see anything interesting in the diff, but the failing
tests succeed and are not skipped.
--
WBR, wRAR
python-traits_4.6.0-1_amd64.log.
Hi
On 01/01/17 at 17:00 +0500, Andrey Rahmatullin wrote:
> I cannot reproduce this.
I could on 2016-12-19. Could you post a build log and diff it with mine?
Thanks
Lucas
signature.asc
Description: PGP signature
___
Python-modules-team mailing list
P
Control: severity -1 important
Hi,
> We're aiming at dropping mysql from testing/stretch because of concerns from
> the
> security team. See email threads in debian-release@ and pkg-mysql-maint@.
ok, that changes things.
It's very unfortunate that this was not really announced anywhere.
Still
Processing control commands:
> severity -1 important
Bug #848287 [src:python-testing.mysqld] python-testing.mysqld: (build-)depends
on mysql-{client,server}
Severity set to 'important' from 'serious'
--
848287: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848287
Debian Bug Tracking System
C
I cannot reproduce this.
--
WBR, wRAR
signature.asc
Description: PGP signature
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
On 01/01/17 12:49, Dominik George wrote:
> Hi,
>
>> You should have kept me in Cc if you wanted me to see your reply and have a
>> chance to reply.
>
> sorry, I just cannot remember that the Debian BTS does not automatically
> notify the submitter ☹.
>
> So, I have several problems:
>
> * I ca
Hi,
> You should have kept me in Cc if you wanted me to see your reply and have a
> chance to reply.
sorry, I just cannot remember that the Debian BTS does not automatically
notify the submitter ☹.
So, I have several problems:
* I cannot find the formal transition for this.
* I cannot see tha
21 matches
Mail list logo
