since the alioth.debian.org is down.
Vilnius University Institute of Biotechnology, Saulėtekio al. 7, room V325
LT-10257 Vilnius, Lithuania
some time ago I've requested to join DPMT as 'merkys' (DD). I used to have
write access as 'merkys-guest', which could be revoked now.
-- Forwarded message -
Date: Tue, 16 Apr 2019, 19:24
Subject: Request to join the DPMT
I would like
On 2019-10-21 16:29, MARIE Alexandre wrote:
> This one works perfectly fine, thanks a lot for giving me some time to help !
You're welcome :)
On 2019-10-21 16:15, MARIE Alexandre wrote:
> I tried it as you said but I still get the same error :
Hmm. The layout on PyPI seems to have changed. Could you try this now?:
On 2019-10-21 15:47, MARIE Alexandre wrote:
> @PACKAGE@-@ANY_VERSION@(?:_src)?@ARCHIVE_EXT@ debian uupdate
Try putting @ANY_VERSION@ inside parenthesis:
@PACKAGE@-(@ANY_VERSION@)(?:_src)?@ARCHIVE_EXT@ debian uupdate
Hope this helps,
On 2019-10-21 16:01, MARIE Alexandre wrote:
> Thanks for your fast answer, but I made a mistake when I pasted the error
> from the bash.
> Here is the real error (according to the d/watch file I gave you) :
I see. Have you tried the third PyPI watch file example from the manpage of
Recently cherrytree  has been rewritten from Python to C++, thus it
no longer belongs in DPT. Could someone with adequate permissions
transfer it from DPT to generic Debian group on salsa.d.o?
Alternatively, one could grant me permission to manage cherrytree so as
I could transfer it
On 2021-05-10 13:35, Martin wrote:
> trac is a long-time Debian package, uploaded first by Jesus
> Climent in 2004. I like the traditional look of Trac and its
> climate-friendly resource usage :-)
> Now, while Trac is still maintained upstream and has been ported
> to Python 3
On 2021-05-10 16:06, Martin wrote:
> On 2021-05-10 14:00, Andrius Merkys wrote:
>> I do not think that slowing down of development is reason serious enough
>> to remove a package which is otherwise fine. Or are there other reasons
>> that I am not aware of?
> I don
On 2021-02-12 16:18, Simon McVittie wrote:
> We have a python3 package already. If I saw a python3 package and a
> python3-core package, I would expect that either they're the same thing,
> or python3-core is a smaller and less fully-featured version of python3.
> Conversely, we already have a
On 2021-09-15 15:46, Neil Williams wrote:
> The package does not seem to have a current version control repository.
> That would be a good start. There doesn't seem to be a project in
> salsa.debian.org and it would
On Mon, 2 Aug 2021, 13:35 Torrance, Douglas, wrote:
> I've recently packaged pynauty , which provides a Python interface to
>  for computing automorphism groups of graphs.
> I'm a DM, but this package would be NEW, so I need a sponsor. Would
> anyone be
> willing to review?
I am working to package sphinx_press_theme (ITP bug #996543). According
to Python package naming conventions  proper binary package name for
it would be python3-sphinx-press-theme. However, most of sphinx theme
packages seem to be named $THEME_NAME-sphinx-theme (source package),
On 2021-10-21 14:38, Dmitry Shachnev wrote:
> On Thu, Oct 21, 2021 at 10:26:53AM +0300, Andrius Merkys wrote:
>> Is it OK to follow  and stay faithful to upstream name, or should I
>> rename both source and binary packages to match already existing sphinx
On 2021-12-01 14:31, Simon Chopin wrote:
> TL;DR: Does it make sense to upload the intermediary upstream version
> 3.4.8 or rather wait for someone to work on the Rust-based later versions?
I would say yes. python-cryptography >= v3.4.6 is needed to update
python-autobahn . Thomas
On 2021-12-01 19:22, Thomas Goirand wrote:
> On 12/1/21 4:05 PM, Andrius Merkys wrote:
>> On 2021-12-01 14:31, Simon Chopin wrote:
>>> TL;DR: Does it make sense to upload the intermediary upstream version
>>> 3.4.8 or rather wait for someone to work on th
On 2021-12-02 11:42, Tristan Seligmann wrote:
>> python-cryptography_3.4.8-1_source.changes uploaded successfully to localhost
Great, thanks a lot!
On 2022-06-02 11:23, Julian Gilbey wrote:
> When I updated pytest-mock, I noticed that pytest is somewhat out of
> date and it would be good to upgrade it. But it's quite a major
> package, and I don't really want to do it without a go-ahead from
> Perhaps we could upload
On 2022-06-08 14:47, Julian Gilbey wrote:
> 1. finalcif: it seems like an update to python3-gemmi has broken this
Yes, this is indeed the case with finalcif. Will report and investigate
On 2022-06-07 04:01, Sandro Tosi wrote:
> I would consider pytest a "core" python package, and so a complete
> rdeps rebuild is appropriate
+1. That is what I meant by suggesting ratt-rebuilding all the rdeps.
Mail list logo