tags 1061102 + moreinfo
thanks
Hi Jonas,
Looking at the output of the build log, the problem appears to be
this:
configure: error: in
`/build/biome-1.5.2/target/x86_64-unknown-linux-gnu/release/build/tikv-jemalloc-sys-2de43a13417834c8/out/build':
configure: error: cannot compute suffix of
severity 1062437 important
tags 1062437 +confirmed
thanks
Thanks for the bugreport! I agree that this is an important thing to fix and
we're not following the specification in
https://dep-team.pages.debian.net/deps/dep5/ here.
I don't think it violates policy 2.3 though; the meaning of the
We'll just need to do an upstrema release and an upload for this, the
change is already in upstream bzr.
I'll do this over the weekend; if I fail to do a release for some
reason then I'll ship the patch in Debian.
Jelmer
tags 1051766 + confirmed
thanks
On Tue, Sep 12, 2023 at 12:29:31PM +0200, Andreas Tille wrote:
> after upgrading to lintian-brush 0.150 apply-multiarch-hints just does
> not end and I need to kill the actual xterm (even ^C does not back the
> prompt). After killing the xterm it leaves a broken
fixed 1026331 0.145
thanks
On Sun, Dec 18, 2022 at 06:10:30PM +0100, Paul Gevers wrote:
> Source: lintian-brush
> Version: 0.144
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: regression
>
> Dear maintainer(s),
>
> With a recent upload of lintian-brush the autopkgtest of
binary
package for bookworm.
--
Jelmer Vernooij
PGP Key: https://www.jelmer.uk/D729A457.asc
an
argument that tla itself should be kept around, to at least allow
people to be able to access old repositories and migrate away.
--
Jelmer Vernooij
PGP Key: https://www.jelmer.uk/D729A457.asc
I've also uploaded a NMU to DELAYED/10, please feel free to cancel or
let me know here if you prefer not to see that go through.
Jelmer
--
Jelmer Vernooij
PGP Key: https://www.jelmer.uk/D729A457.asc
tags 1015914 +patch
thanks
Hi Paul, Sandro,
I've verified that node-clipboard works too, and proposed a PR at
https://salsa.debian.org/python-team/packages/sphinx-copybutton/-/merge_requests/2
Cheers,
Jelmer
Control: tag -1 pending
Hello,
Bug #1022283 in python-wikkid reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #1020024 in pydoctor reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #1013485 in python-debian reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #1012373 in dulwich reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
gt; --
> Ian JacksonThese opinions are my own.
>
> Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
> that is a private address which bypasses my fierce spamfilter.
--
Jelmer Vernooij
PGP Key: https://www.jelmer.uk/D729A457.asc
signature.asc
Description: PGP signature
forwarded 1000716 https://github.com/ponyorm/pony/issues/598
thanks
Upstream is working on this. See:
https://github.com/ponyorm/pony/commits/py_3_10_dev
https://github.com/ponyorm/pony/issues/598
Hi Steve,
On Thu, Sep 30, 2021 at 12:21:53PM -0700, Steve Langasek wrote:
> While tracking a build failure of breezy 3.2.1 in Ubuntu, I found that it is
> currently also reproducible in Debian unstable:
Thanks for the bug report.
> [...]
>
reassign 994223 python3-breezy
fixed 994223 3.2.0+bzr7543-1
thanks
On Thu, Sep 16, 2021 at 06:18:04AM +, Debian Bug Tracking System wrote:
> > retitle 994223 lintian-brush is unusable
> Bug #994223 [lintian-brush] lintian-brush unusable
> Changed Bug title to 'lintian-brush is unusable' from
Hi Andreas,
Thanks for the pointer - I hadn't realized that this bug was still
affecting testing.
How hard would it be to drop support for lintian-brush in
routine-update in testing? It looks like properly fixing this bug is
going to be tricky if it involves going via unstable - it would mean
severity 988166 normal
tags 988166 +upstream
thanks
I've moved Dulwich from Recommends to Depends for the moment. This will
at least work around the issue.
Ideally we'd keep dulwich as a recommends, but that will require some
investigation and fixes upstream.
On Thu, May 06, 2021 at 09:36:30PM +0200, Paul Gevers wrote:
> With a recent upload of breezy the autopkgtest of check-manifest fails
> in testing when that autopkgtest is run with the binary packages of
> breezy from unstable. It passes when run with only packages from
> testing. In tabular form:
On Fri, Apr 16, 2021 at 09:24:38AM +0200, Andreas Tille wrote:
> I've got a testing-removal warning for routine-update due this bug. I
> know you are usually very prompt in replying to issues thus I'm simply
> wondering whether you might have missed this bug report. I personally
> have never
Control: tag -1 pending
Hello,
Bug #972793 in hg-git reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
breaking the tests, so I'll file a separate (normal severity) bug
about that.
Tristan, are you happy for me to upload the package with that
change?
--
Jelmer Vernooij
PGP Key: https://www.jelmer.uk/D729A457.asc
=== modified file 'debian/changelog'
--- old/debian/changelog 2020-09-24 06:48:41 +
I can see two options here:
1) drop support for architectures not supported by upstream
2) disable the unsupported architecture check somehow
* either by setting the environment variable
* by patching out the check in the source code
I'm not entirely sure what the right thing is for our
Control: tag -1 pending
Hello,
Bug #952348 in backupchecker reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #952348 in backupchecker reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
severity 950470 important
thanks
On Sun, Feb 02, 2020 at 10:37:41AM +0100, Matthias Klose wrote:
> see
> https://buildd.debian.org/status/fetch.php?pkg=breezy=all=3.0.2-3=1580478666=0
>
> ==
> ERROR:
>
On Fri, Jan 31, 2020 at 11:47:40AM +0100, Gianfranco Costamagna wrote:
> Source: lintian-brush
> Version: 0.56
> Severity: serious
>
> Hello, looks like the new lintian removed one renamed tag in its latest
> version:
> * Remove data/override/renamed-tags; they are defined in the tag
>
On Fri, Jan 31, 2020 at 03:50:57AM +0100, Philippe Mathieu-Daudé wrote:
> On Thu, Jan 30, 2020 at 3:27 PM Jelmer Vernooij wrote:
> >
> > It looks like this package has been ported to Python 3, but has not
> > yet been uploaded. The last changelog entry on salsa
> > (http
a version of the package ported to Python 3, if
that would be useful.
--
Jelmer Vernooij
PGP Key: https://www.jelmer.uk/D729A457.asc
Hi Hans-Christoph,
I'm interested in pymtp, since gpodder can optionally use it. Thanks for
packaging it!
I'll prepare an upload to migrate it to Python3, and will move it to
the Python team.
Cheers,
Jelmer
--
Jelmer Vernooij
PGP Key: https://www.jelmer.uk/D729A457.asc
:
- few bugfixes
- added more options
- use Python3
-- Philippe Mathieu-Daudé Fri, 06 Dec 2019 15:53:10 +0100
Philippe, would you like me to sponsor an upload of the package?
--
Jelmer Vernooij
PGP Key: https://www.jelmer.uk/D729A457.asc
signature.asc
Description: PGP signature
Control: tag -1 pending
Hello,
Bug #948958 in python-pyscss reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
blocking ledger from migrating to testing.
It looks like the last upload (in unstable) doesn't actually migrate Python 3,
but just disables Python support altogether. :-(
I'll see if I can do an upload that just disables the Python tests for now.
Cheers,
Jelmer
--
Jelmer Vernooij
PGP Key:
FWIW Upstream is working on Python 3 support here:
https://github.com/rabbitvcs/rabbitvcs/issues/279
signature.asc
Description: PGP signature
severity 936454 normal
thanks
Resetting this to normal. As of 0.19.14-1 (uploaded at the same time as the
python-fastimport removal), Dulwich has stopped build-depending on
python-fastimport.
On Mon, Sep 23, 2019 at 12:50:14PM +0100, peter green wrote:
> Package: loggerhead
> Version: 1.19~bzr479+dfsg-3
> Severity: serious
>
> Loggerhead has multiple dependency issues.
>
> The loggerhead source package build-depends on python-subunit which is no
> longer built by the subunit source
Hi Kenneth, Ian,
On Wed, Jul 31, 2019 at 08:45:54PM -0500, Kenneth Pronovici wrote:
> On Wed, Jul 31, 2019 at 10:46 AM Ian Jackson
> wrote:
> > > Otherwise, I will see if I can determine how well the package works
> > > without epydoc installed. If it works (i.e. doesn't blow up) and I
> > >
severity 930213 normal
thanks
This only happens when bzr is used with paramiko and if there are SSH agent
keys. You should be able to work around this by setting
BZR_SSH=openssh in your environment or uninstalling paramiko.
Control: tag -1 pending
Hello,
Bug #913037 in dulwich reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:
retitle 913037 "test dulwich.tests.test_porcelain.PushTests.test_simple
contains race condition"
thanks
This is not a python3.7-specific issue, but a test that contains a
race condition that means it occasionally fails. This is reproducible
on other python versions as well (when running the test
Hi Steve,
On Wed, Nov 14, 2018 at 03:16:32PM -0800, Steve Langasek wrote:
> The syncthing-gtk package is uninstallable, because it depends on
> gir-1.2-glib-2.0, which does not exist. The correct spelling of this
> package name is gir1.2-glib-2.0. Please find a patch attached.
Argh, that was
On Sun, May 13, 2018 at 08:25:39PM -0400, Jeremy Bicha wrote:
> Source: lptools
> Version: 0.2.0-2
> Severity: serious
> User: pkg-gnome-maintain...@lists.alioth.debian.org
> Usertags: oldlibs pygtk
> Tags: sid buster
> X-Debbugs-CC: x...@debian.org, jel...@debian.org
>
> lptools depends on the
On Wed, Dec 06, 2017 at 05:45:11PM -0800, Vagrant Cascadian wrote:
> Package: bzr
> Version: 2.7.0+bzr6622-9
> Severity: serious
> Tags: patch
>
> The last armel bzr build failed to build from source, and I've tried to
> reproduce the issue unsuccessfully.
>
>
>
On Wed, Dec 06, 2017 at 05:45:11PM -0800, Vagrant Cascadian wrote:
> The last armel bzr build failed to build from source, and I've tried to
> reproduce the issue unsuccessfully.
>
>
> https://buildd.debian.org/status/fetch.php?pkg=bzr=armel=2.7.0%2Bbzr6622-9=1510195017=0
>
> I tried building
e0eb92b4f51b3ee27a8850ea7e0e651baa14971e
Author: Jelmer Vernooij <jel...@jelmer.uk>
Date: Mon Jul 24 23:51:11 2017 +
Stop shipping pypy C extensions in python-dulwich. Closes: #868542
diff --git a/debian/changelog b/debian/changelog
index 4084039..4840a64 100644
--- a/debian/changelog
+++ b/
I've uploaded a new Debian version to unstable packaging RC1.
Unfortunately there are a test failures on various
architectures. :(
Note that not all of these are release architectures, and that make
bails out once tests in one directory fail. Builders are still
running, but so far I've seen:
A brief update on this: a RC release has happened upstream, which is
versioned "7.0.1". A stable release (which will be "7.1") is in the
works, but may not make it before stretch.
signature.asc
Description: PGP signature
On Sat, Dec 10, 2016 at 05:08:00AM +0100, Diederik de Haas wrote:
> Package: irssi-plugin-quassel
> Version: 0~git20160612-1
> Severity: grave
> Justification: renders package unusable
>
> I followed the instructions from the README.md on github, but when I got
> to the '/load quassel' part I got
On Wed, Dec 07, 2016 at 05:47:52PM +, Ben Dooks wrote:
> The "bzr: ERROR: exceptions.TypeError: first argument must be string or
> compiled pattern" is still there after updating.
>
> bzr is already the newest version (2.7.0+bzr6619-1).
This has been fixed. The latest version of bzr
On Wed, Sep 14, 2016 at 11:51:14AM +0300, Vlad Orlov wrote:
> Hi,
>
> I'd like to know if there's any progress on uploading the new
> version to jessie-security. Just want to check if the update
> would fix https://bugs.debian.org/831851 as well.
See
d4092f0849e2ec1c92214da90d052c7947913d19
Author: Jelmer Vernooij <jel...@jelmer.uk>
Date: Sun Sep 4 14:21:37 2016 +
New upstream release.
diff --git a/debian/changelog b/debian/changelog
index 91abc96..711b647 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+samba (2:4.2.14+dfsg-0+deb8u1) UNRE
d29a694496549410931c88fccb18961399203c93
Author: Jelmer Vernooij <jel...@jelmer.uk>
Date: Sun Sep 4 14:21:37 2016 +
New upstream release.
diff --git a/debian/changelog b/debian/changelog
index 91abc96..8374733 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+samba (2:4.2.12+dfsg-0+deb8u1) UNRE
e23b11c3bccb7e463ffb51c86f3321cca63d57a9
Author: Jelmer Vernooij <jel...@jelmer.uk>
Date: Mon Jul 4 12:23:25 2016 +
Add patch gcc_6.patch, fixing compatibility with gcc 6. Closes: #812264
diff --git a/debian/changelog b/debian/changelog
index 02eaf36..06b215c 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3
fcb793364de9bda9fae4a05476cf414f46126bc5
Author: Jelmer Vernooij <jel...@jelmer.uk>
Date: Sat Apr 16 00:19:06 2016 +
Bump version in Replaces: samba-libs for samba-vfs-modules to 4.3.2+dfsg-1,
to fix jessie->stretch upgrades. Closes: #821070
diff --git a/debian/changelog b/debian/changelog
index 9b028f9..c1706
severity 815331 important
tags 815331 +moreinfo
thanks
Can you still reproduce this with current pypy? It doesn't segfault
for me.
signature.asc
Description: PGP signature
On Fri, Feb 12, 2016 at 09:34:03PM +0100, Vincent Ladeuil wrote:
> > Agustin Martin writes:
>
> > Package: bzrtools
> > Version: 2.6.0-2
> > Severity: serious
> > Justification: uninstallable in sid
>
> > Dear Maintainer,
>
> > Seems that
On Sun, Jan 24, 2016 at 11:44:53AM +1100, Brian May wrote:
> Ryan Tandy writes:
>
> > Since the .la files moved from /usr/lib/$arch to /usr/lib/$arch/heimdal,
> > looks like their contents also need to be updated.
>
> According to debian/changelog I deleted the *.la files in
On Sun, Jan 24, 2016 at 11:44:53AM +1100, Brian May wrote:
> Ryan Tandy writes:
>
> > Since the .la files moved from /usr/lib/$arch to /usr/lib/$arch/heimdal,
> > looks like their contents also need to be updated.
>
> According to debian/changelog I deleted the *.la files in
On Sun, Jan 03, 2016 at 10:38:12AM +1300, Andrew Bartlett wrote:
> On Thu, 2015-12-31 at 18:53 +1300, Andrew Bartlett wrote:
> > Just a quick note to say that the LDB build failure isn't a
> > regression
> > - whatever is going on here has always been going on, it just wasn't
> > tested before
On Sat, Jan 02, 2016 at 09:51:34PM +, Jelmer Vernooij wrote:
> On Sun, Jan 03, 2016 at 10:38:12AM +1300, Andrew Bartlett wrote:
> > On Thu, 2015-12-31 at 18:53 +1300, Andrew Bartlett wrote:
> > > Just a quick note to say that the LDB build failure isn't a
> > > r
On Sun, Jan 03, 2016 at 11:36:18AM +1300, Andrew Bartlett wrote:
> On Sat, 2016-01-02 at 22:22 +0000, Jelmer Vernooij wrote:
> > On Sun, Jan 03, 2016 at 11:00:44AM +1300, Andrew Bartlett wrote:
> > > On Sat, 2016-01-02 at 21:51 +0000, Jelmer Vernooij wrote:
> > > > On S
On Sun, Jan 03, 2016 at 11:00:44AM +1300, Andrew Bartlett wrote:
> On Sat, 2016-01-02 at 21:51 +0000, Jelmer Vernooij wrote:
> > On Sun, Jan 03, 2016 at 10:38:12AM +1300, Andrew Bartlett wrote:
> > > On Thu, 2015-12-31 at 18:53 +1300, Andrew Bartlett wrote:
> > >
63 matches
Mail list logo