Source: xorg-server
Version: 2:21.1.11-3
Severity: grave
Tags: security upstream patch
Justification: user security hole
X-Debbugs-Cc: jcris...@debian.org, Debian Security Team
The latest security fixes introduced a regression, apparently replacing
use-after-free with double-free in some
On Tue, Jan 16, 2024 at 11:02:25 +0100, Julien Cristau wrote:
> On Mon, Jan 15, 2024 at 16:14:17 +, Simon McVittie wrote:
>
> > The armel baseline does not have lock-free atomic operation opcodes. The
> > result is a build failure:
> >
> > https://buildd.debian
On Mon, Jan 15, 2024 at 16:14:17 +, Simon McVittie wrote:
> The armel baseline does not have lock-free atomic operation opcodes. The
> result is a build failure:
>
> https://buildd.debian.org/status/fetch.php?pkg=mesa=armel=23.3.3-1=1705055313=0
> > In file included from
Source: quilt
Version: 0.67+really0.67-2
Severity: grave
X-Debbugs-Cc: jcris...@debian.org, s...@debian.org
Hi,
As explained by Sune in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053444#17, reverting
the change from the previous upload in dh_quilt_unpatch is insufficient,
as it brings
Source: hg-git
Version: 1.0.2-1
Severity: grave
X-Debbugs-Cc: jcris...@debian.org
Hi,
hg-git looks like it needs an update for compatibility with current
mercurial, see e.g.
https://ci.debian.net/data/autopkgtest/testing/amd64/h/hg-git/38210693/log.gz
> ** Unknown exception encountered with
Control: severity -1 important
Control: tag -1 upstream
Control: retitle -1 mercurial: test-http-bad-server.t intermittent failure
Sounds like a flaky or racy test, downgrading.
On Tue, Sep 26, 2023 at 14:43:44 +0200, Lucas Nussbaum wrote:
> > --- /<>/tests/test-http-bad-server.t
> > +++
Source: sptag
Version: 0.0~git20230323.0341c33+ds-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: jcris...@debian.org
The latest sptag upload to experimental broke one of our buildds after
its log took up 70G disk space.
Control: forcemerge 1008244 -1
This is fixed in git, I need to get around to uploading an update.
Cheers,
Julien
On Tue, Dec 20, 2022 at 05:36:27PM +0100, Lucas Nussbaum wrote:
> Source: ca-certificates
> Version: 20211016
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
>
Source: mercurial
Version: 6.3.1-1
Severity: serious
Tags: upstream patch ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: jcris...@debian.org
Forwarded: https://bz.mercurial-scm.org/show_bug.cgi?id=6770
mercurial 6.3 fails its testsuite on
On Fri, Sep 2, 2022 at 15:01:01 +0200, Sylvestre Ledru wrote:
> Le 02/09/2022 à 13:18, Adrian Bunk a écrit :
> > On Fri, Sep 02, 2022 at 12:12:06PM +0200, Christoph Biedl wrote:
> > > Sylvestre Ledru wrote...
> > >
> > > > I don't think renaming is the right approach against an MS-DOS
> > > >
Control: reassign -1 libspdlog1 1:1.10.0+ds-0.1
Control: retitle -1 libspdlog1: ABI breakage without SONAME bump
Control: severity -1 serious
On Sun, Jul 31, 2022 at 10:32:48AM +0200, Stefan Pasteiner wrote:
> Package: nheko
> Version: 0.9.3+ds-1
> Severity: grave
> Justification: renders package
Package: mercurial
Version: 6.2-1
Severity: serious
Tags: upstream
Upstream commit be9bf75a837c looks like it broke the fsmonitor
extension:
> File "/usr/lib/python3/dist-packages/hgext/fsmonitor/__init__.py", line
> 338, in
> if e._v1_state() != b"n" or e._v1_mtime() == -1
>
Source: tortoisehg
Version: 6.1.1-3
Severity: serious
I uploaded mercurial 6.2-1 to sid yesterday, making thg uninstallable.
Cheers,
Julien
On Wed, Jun 22, 2022 at 10:50:48AM +0200, Michael Biebl wrote:
> Package: gnu-efi
> Version: 3.0.13+git20210716.269ef9d-2
> Severity: serious
> Forwarded: https://sourceforge.net/p/gnu-efi/bugs/28/
>
> Hi,
>
> since the latest update of binutils to 2.38.50.20220615,
> the systemd source package
Source: schroot
Version: 1.6.10-14
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
https://buildd.debian.org/status/fetch.php?pkg=schroot=all=1.6.10-14=1654764990=0
> make[3]: Entering directory '/<>/debian/build/po'
> cd
Control: tag -1 pending
Hello,
Bug #1011076 in mercurial 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: severity -1 normal
On Fri, Apr 15, 2022 at 10:36:54PM +0200, Paul Gevers wrote:
> I looked at the results of the autopkgtest of you package because it was
> showing up as a regression for the upload of python3-defaults. I noticed
> that the test regularly fails on several architectures.
Control: tag -1 upstream patch
Control: forwarded -1
https://gitlab.freedesktop.org/xorg/app/setxkbmap/-/merge_requests/4
On Mon, Apr 25, 2022 at 03:44:59PM +0200, Cyril Brulebois wrote:
> And thanks again for the quick turnaround for the libxrandr2 udeb
> addition. The next issue is
Package: dovecot-core
Version: 1:2.3.13+dfsg1-2
Severity: serious
X-Debbugs-Cc: jcris...@debian.org
This bit of dovecot-core.postinst breaks (at least on the second invocation) if
the snakeoil cert or key don't exist: test -e returns false, but ln -s fails
because the symlink is already there:
Control: tag -1 pending
Hello,
Bug #1008747 in mercurial 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 upstream
On Thu, Mar 31, 2022 at 07:27:51PM +0200, Graham Inggs wrote:
> As can be seen on reproducible builds [1], mercurial FTBFS with Python
> 3.10 as the default version. I've copied what I hope is the relevant
> part of the log below.
>
> This appears to be due to the
Control: fixed -1 6.1-1
On Sat, Mar 26, 2022 at 10:34:40PM +0100, Paul Gevers wrote:
> Version: 6.1-4
>
> Hi,
>
> On Thu, 24 Feb 2022 19:27:56 +0100 Paul Gevers wrote:
> > With a recent upload of pygments the autopkgtest of mercurial fails in
> > testing when that autopkgtest is run with the
, 2022 at 02:56:03PM +0100, Julien Cristau wrote:
> Source: nvidia-graphics-drivers-tesla-418
> Version: 418.226.00-1
> Severity: serious
>
> xorg-server's video ABI was recently bumped, and
> nvidia-graphics-drivers-tesla-418 only declares compatibility for up to
> v24.
>
> Cheers,
> Julien
Source: nvidia-graphics-drivers-tesla-418
Version: 418.226.00-1
Severity: serious
xorg-server's video ABI was recently bumped, and
nvidia-graphics-drivers-tesla-418 only declares compatibility for up to
v24.
Cheers,
Julien
Package: prosody
Version: 0.11.13-1
Severity: serious
Control: found -1 0.11.9-2+deb11u2
X-Debbugs-Cc: jcris...@debian.org
prosody's postinst seems to insist on creating
/etc/prosody/certs/localhost.{crt,key}, but does this in a fragile way.
They're created as symlinks, but the call to ln is
Control: reassign -1 postfix-mta-sts-resolver
On Mon, Nov 08, 2021 at 03:57:00PM +0200, Adrian Bunk wrote:
> On Tue, Oct 19, 2021 at 09:13:56AM +0200, Julien Cristau wrote:
> > On Mon, Oct 18, 2021 at 11:05:14PM +0200, Kurt Roeckx wrote:
> > > On Mon, Oct 18, 2021 at 10:40:
Control: tag -1 moreinfo
Control: severity -1 normal
On Wed, Jan 05, 2022 at 04:34:34PM +0100, Georges Gouriten wrote:
> File "/usr/lib/calibre/calibre/devices/smart_device_app/driver.py", line
> 2044, in
> from zeroconf import (BadTypeInNameException, _HAS_A_TO_Z,
> ImportError: cannot
Control: reassign -1 mercurial 5.9.3-1
Control: close -1 mercurial/6.0~rc0-1
On Sat, Nov 06, 2021 at 09:57:34PM +0100, Paul Gevers wrote:
> Source: git, mercurial
> Control: found -1 git/1:2.33.1-1
> Control: found -1 mercurial/5.9.3-1
> Severity: serious
> Tags: sid bookworm
> X-Debbugs-CC:
On Mon, Nov 15, 2021 at 01:54:36PM +, Dimitri John Ledkov wrote:
> > Also, build chroots must still be created without merged-usr for
> > sid/bookworm, until something's been done to migrate user systems.
>
> But Julien, you said that buildds run stable, meaning they are
> unaffected by this
Control: tag -1 - pending
On Wed, Oct 27, 2021 at 09:13:11AM +, Yadd wrote:
> Control: tag -1 pending
>
> Hello,
>
> Bug #997736 in moment-timezone.js 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
On Tue, Oct 26, 2021 at 04:14:35PM +0200, Paul Gevers wrote:
> Hi Diederik, all,
>
> On 26-10-2021 08:34, Diederik de Haas wrote:
> > Therefor it may be worth trying whether this bug is resolved as well.
>
> Well, it's not fixed in the Debian archive:
>
On Mon, Oct 18, 2021 at 11:05:14PM +0200, Kurt Roeckx wrote:
> On Mon, Oct 18, 2021 at 10:40:59PM +0200, Julien Cristau wrote:
> > On Mon, Oct 18, 2021 at 02:50:50PM +0200, Benjamin Hof wrote:
> > > Hi,
> > >
> > > I think the follow
On Mon, Oct 18, 2021 at 02:50:50PM +0200, Benjamin Hof wrote:
> Hi,
>
> I think the following change might be the relevant one:
>
> --- a/update-ca-certificates
> +++ b/update-ca-certificates
> @@ -164,8 +164,6 @@
>done
> fi
>
> -rm -f "$CERTBUNDLE"
> -
>
Control: tag -1 pending
Hello,
Bug #996005 in ca-certificates 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:
Hi,
On Sun, Oct 10, 2021 at 10:21:40PM +0200, Paul Gevers wrote:
> Source: postfix-mta-sts-resolver
> Version: 1.0.0-4
> Severity: serious
> Tags: sid bookworm
> User: debian...@lists.debian.org
> Usertags: needs-update
> Control: affects -1 src:ca-certificates
>
> [X-Debbugs-CC:
Package: tortoisehg
Version: 5.6.1-1
Severity: serious
Tags: bookworm sid
Hi,
mercurial 5.9 is now in sid, making tortoisehg uninstallable. There'll
hopefully be a tortoisehg 5.9 release in the near future...
Cheers,
Julien
Source: mercurial
Version: 5.9-1
Severity: serious
Tags: ftbfs
>From the log
https://buildd.debian.org/status/fetch.php?pkg=mercurial=s390x=5.9-1=1629766216=0
> --- /<>/tests/test-upgrade-repo.t
> +++ /<>/tests/test-upgrade-repo.t.err
> @@ -1531,9 +1531,8 @@
>sparserevlog
>store
>$
On Thu, Aug 12, 2021 at 11:13:59AM +0100, Chris Lamb wrote:
> Hey Julian,
>
> > sorry about my tone yesterday, and thanks for working on this, that's
> > great to hear.
>
> Really, no worries at all...
>
> Still, I'm somewhat at a loss to debug this. In the first instance, can
> one of you
On Wed, Aug 11, 2021 at 10:38:03PM -, Chris Lamb wrote:
> Julien Cristau wrote:
>
> > It'd be appreciated if you could make fixing this a priority, and
> > refrained from uploading further versions until then.
>
> Sure. Just to say though, your message was rather
On Sat, Feb 06, 2021 at 04:58:09PM +, Adam D. Barratt wrote:
> Source: redis
> Version: 5:6.2~rc3-1
> Severity: serious
> Tags: ftbfs
>
> Hi,
>
> Both s390x buildds hit OOM conditions while attempting to build redis
> 6.2 in experimental.
>
> The log from zani ends with:
>
> [33/63 done]:
Control: reassign -1 hdf5 1.10.5+repack-1~exp6
On Tue, May 18, 2021 at 07:48:08PM +0200, Dennis Filder wrote:
> X-Debbugs-CC: d.fil...@web.de
>
> On Tue, May 18, 2021 at 06:47:38PM +0200, Christoph Berg wrote:
>
> > Can you share the apt command and output that led to this removal?
>
> I
On Mon, Apr 19, 2021 at 06:28:05PM +0200, Julian Andres Klode wrote:
> On Mon, Apr 19, 2021 at 06:08:23PM +0200, Julien Cristau wrote:
> > On Mon, Apr 19, 2021 at 06:01:18PM +0200, Julian Andres Klode wrote:
> > > I see. Nobody pinged me since then, but it is indeed fixed in the
On Mon, Apr 19, 2021 at 06:01:18PM +0200, Julian Andres Klode wrote:
> I see. Nobody pinged me since then, but it is indeed fixed in the
> 1.8.5 stable update that at least one release team member was
> not exited about.
>
> https://salsa.debian.org/apt-team/apt/-/compare/1.8.2.2...1.8.5
>
> So
On Tue, Apr 13, 2021 at 07:33:04PM +0200, Chris Hofstaedtler wrote:
> * Julien Cristau [210413 17:32]:
> > I'm not sure that's quite correct as it doesn't restore the backwards
> > compatibility that python broke. On the other hand I don't know if
> > python even provide
Control: tag -1 upstream
Control: tag -1 - patch
On Tue, Apr 13, 2021 at 06:18:52PM +0200, Ivo De Decker wrote:
> control: tags -1 patch
>
> Hi Julien,
>
> On Wed, Apr 07, 2021 at 08:42:06AM +0200, Lucas Nussbaum wrote:
> > Source: mercurial
> > Version: 5.6.1-2
> > Severity: serious
> >
I've started to look at it, I'm afraid building up context on this
stuff to understand what it's doing is going to take a while...
Cheers,
Julien
On Tue, Apr 06, 2021 at 10:31:51PM +0200, Ivo De Decker wrote:
> Hi Julien,
>
> Do you have any comment on the merge request Andreas submitted to
>
Control: tag -1 moreinfo
Control: severity -1 wishlist
On Wed, Apr 07, 2021 at 11:40:34AM +0200, Andreas Beckmann wrote:
> Package: ca-certificates
> Version: 20210119
> Severity: serious
>
> Hi,
>
> as I had commented on
> https://salsa.debian.org/debian/ca-certificates/-/merge_requests/6
>
>
Package: gitlab-shell
Version: 13.13.0+debian-1+b1
Severity: serious
/usr/bin/check seems like an awfully generic program name to be shipped
in something like gitlab-shell. Please don't.
Thanks,
Julien
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT
Control: severity -1 wishlist
On Fri, Mar 19, 2021 at 04:58:47PM +0100, Leandro Lucarella wrote:
> Package: git-hub
> Version: 1.0.3-1
> Severity: grave
> Justification: renders package unusable
>
The fact that there's a new upstream release does not in itself make the
current package unusable.
On Mon, Mar 15, 2021 at 05:44:44PM +, Thorsten Glaser wrote:
> Hi Julien,
>
> >Yes, they're different. I'm not sure what you're asking.
>
> the reason for the difference; sorry if I was unclear.
>
They're different versions of the mozilla root store, so they include
different sets of CA
On Sat, Mar 13, 2021 at 08:32:32PM +, Thorsten Glaser wrote:
> Hi,
>
> the changelogs seem to differ in re-added certificates:
>
Yes, they're different. I'm not sure what you're asking.
Cheers,
Julien
On Mon, Feb 08, 2021 at 09:41:17AM +0100, Eduard Bloch wrote:
> @Julien: okay to add myself as Uploader and upload?
No.
Cheers,
Julien
Control: tag -1 pending
Hello,
Bug #980576 in mercurial 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 upstream fixed-upstream patch
On Mon, Feb 01, 2021 at 05:42:04PM +0100, Julien Cristau wrote:
> On Mon, Feb 01, 2021 at 08:14:13AM -0800, Steve Langasek wrote:
> > Package: mercurial
> > Version: 5.6.1-1
> > Followup-For: Bug #980576
> > User: ub
On Mon, Feb 01, 2021 at 08:14:13AM -0800, Steve Langasek wrote:
> Package: mercurial
> Version: 5.6.1-1
> Followup-For: Bug #980576
> User: ubuntu-de...@lists.ubuntu.com
> Usertags: origin-ubuntu hirsute ubuntu-patch
>
> Dear maintainers,
>
> Attached is a patch that makes the mercurial test
ls on how this
> affected .NET users building on Debian.
>
> Thanks
>
> Michael
>
>
> On Thu, 28 Jan 2021 15:17:34 +0100 “Julien Cristau"
> wrote:
> > Hi,
>
> >
>
> > I'm not sure why this is blowing up again this week when things have
>
&
Hi,
I'm not sure why this is blowing up again this week when things have
been in a bit of a limbo state since June last year, but in any case
I've just pushed a change to buster to try and revert the blacklisting
of legacy Symantec CAs. That should hopefully make it to the archive in
the next
Source: firefox
Version: 83.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Log:
https://buildd.debian.org/status/fetch.php?pkg=firefox=arm64=83.0-1=1606251110=0
Excerpt:
> In file included from Unified_cpp_js_src_wasm0.cpp:20:
>
Source: firefox
Version: 83.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Forwarded: https://bugzilla.mozilla.org/show_bug.cgi?id=1680495
The log at
https://buildd.debian.org/status/fetch.php?pkg=firefox=armhf=83.0-1=1605661388=0
On Wed, Dec 02, 2020 at 12:10:43PM +0100, Moritz Muehlenhoff wrote:
> I'll compare them with yours tonight, but I'd expect them to be identical
> given
> how close buster is to upstream.
>
Yeah, they're the same. Thanks for getting this rolling.
Cheers,
Julien
020-December/003066.html
+(closes: #976216)
+ * Fix XkbSetDeviceInfo() and SetDeviceIndicators() heap overflows
+(CVE-2020-25712)
+ * Check SetMap request length carefully (CVE-2020-14360)
+
+ -- Julien Cristau Wed, 02 Dec 2020 11:39:24 +0100
+
xorg-server (2:1.20.4-1+deb10u1) bus
Control: severity -1 normal
Control: tags -1 - ftbfs
Control: retitle -1 RM: mrs -- ROM, incompatible with current libzeep
On Mon, Nov 16, 2020 at 08:10:11AM +0100, Maarten L. Hekkelman wrote:
> Package: ftp.debian.org
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source
On Tue, Oct 20, 2020 at 05:54:19PM +0200, Michael Biebl wrote:
> So I decided to do that, and NMU enigmail.
> I used Gregors patches from [1] (thanks for that!) with some minor changes
> - Updated to 2.2.4 (instead of 2.2.2)
> - Marked the upload as NMU (versioned as 2:2.2.4-0.1) and removed
On Fri, Oct 23, 2020 at 12:20:30PM +0200, Steinar H. Gunderson wrote:
> On Fri, Oct 23, 2020 at 11:33:41AM +0200, Julien Cristau wrote:
> > https://github.com/axboe/liburing/commit/25bbcbef3e0a8bfba8044be55d08d5116c51dccd
> > seems to have bumped SONAME upstream.
>
> T
On Fri, Oct 23, 2020 at 10:47:57AM +0200, Steinar H. Gunderson wrote:
> On Fri, Oct 23, 2020 at 09:55:36AM +0200, Steinar H. Gunderson wrote:
> > If this were somehow only about newer functionality or critical fixes, it
> > could
> > be fixed by bumping the versioned dependency, but rhis goes
On Thu, Jan 25, 2018 at 03:25:32PM +0300, Dmitry E. Oboukhov wrote:
> Package: firefox
> Version: 58.0-1
> Severity: grave
>
> I used FF58b4, it works fine.
> Then I upgraded it to FF58b14, it crashed from time to time.
>
> Today I upgraded FF to 58.0, it crashes each 1 minute (see backtrace)
>
Control: severity -1 important
Control: tag -1 moreinfo
On Mon, Sep 07, 2020 at 11:59:34AM -0400, Christophe Kalt wrote:
> Package: xserver-xorg-core
> Version: 2:1.20.9-1
> Severity: grave
>
> Same setup was working with 2:1.20.7-2, but with 2:1.20.9-1 crashes on startup
> (xinit).
Control: severity -1 important
Control: reassign -1 mesa
On Thu, Aug 27, 2020 at 06:36:27PM -0700, Phil Dibowitz wrote:
> Package: xserver-xorg-video-amdgpu
> Version: 19.1.0-1
> Severity: grave
> Justification: causes non-serious data loss
>
> Dear Maintainer,
>
> About once a day my Xserver
On Wed, Sep 09, 2020 at 11:07:23AM +0200, Jean-Marc LACROIX wrote:
>
> ansible@vm-buster-amd64-190:~$ sudo apt install -y libgl1-mesa-dri
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Some packages could not be installed. This may mean that you
Control: tag -1 moreinfo unreproducible
On Wed, Sep 09, 2020 at 10:23:53AM +0200, Jean-Marc LACROIX wrote:
> Package: xbase-clients
> Version: 3.2-2
That is not the version of xbase-clients in any Debian release as far as
I can tell.
> Severity: grave
>
> Dear maintainers,
>
> It seems there
Control: reassign -1 libwayland-dev 1.18.0-2~exp1
Control: affects -1 + src:xorg-server
On Sun, Aug 30, 2020 at 09:21:55PM +0200, Salvatore Bonaccorso wrote:
> Source: xorg-server
> Version: 2:1.20.8-2
> Severity: serious
> Justification: FTBFS
> X-Debbugs-Cc: car...@debian.org
>
> Hi
>
> When
Package: swi-prolog
Severity: serious
X-Debbugs-Cc: jcris...@debian.org
Hi,
swi-prolog autopkgtests are currently failing:
https://ci.debian.net/data/autopkgtest/testing/amd64/s/swi-prolog/6535300/log.gz
>From what I can tell, there's a step in the build process to generate
test certs, which
Control: tag -1 pending
Hello,
Bug #956007 in mercurial 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:
On Mon, Jun 22, 2020 at 19:46:21 +0200, Michael Meskes wrote:
> > Depending on bsdmainutils to get col et al seems entirely right, it's
> > been right forever, there doesn't seem to be a reason to break that
> > both
> > for dependent packages and for end users. Especially not without
> >
On Mon, Jun 22, 2020 at 19:04:49 +0200, Michael Meskes wrote:
> > I think it's probably best at this point to have bsdmainutils depend
> > on
> > bsdextrautils. That gets rid of the breakage in the place where it
> > originated, and doesn't leave things without a transition path.
>
> I beg to
On Mon, Jun 22, 2020 at 13:37:56 -0300, David Bremner wrote:
> Michael Meskes writes:
>
> > On Mon, 2020-06-22 at 11:37 -0300, David Bremner wrote:
> >> Michael Meskes writes:
> >>
> >> > > IMO the move of col needs to be rolled back ASAP. And, if it is
> >> > > to
> >> >
> >> > Why? Care
On Mon, Jun 22, 2020 at 03:42:33PM +0200, Michael Meskes wrote:
> > 'm adding the maintainers of util-linux (bsdextrautils) and
> > bsdmainutils
> > to Cc. Which path forward do you see for this issue? A similar issue
> > seems to affect many packages, such as:
> > ...
>
> It seems to me there
Control: tag -1 pending
Hello,
Bug #961245 in mercurial 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:
On Fri, May 22, 2020 at 10:46:29AM +0200, Jakub Wilk wrote:
> * Axel Beckert , 2020-05-22, 00:22:
> > dpkg: error processing archive
> > /var/cache/apt/archives/mercurial-common_5.4-1_all.deb (--unpack):
> > trying to overwrite
> > '/usr/lib/python2.7/dist-packages/hgext/git/__init__.py', which
On Wed, Jun 17, 2020 at 07:00:43 +0100, Adam D. Barratt wrote:
> On Wed, 2020-06-17 at 00:14 +0200, Lucas Nussbaum wrote:
> > Apparently the condition where this happens is quite rare
> > occurences on 08/2019, 12/2019, 06/2020), so notifying me after the
> > files were cleaned up from /tmp makes
On Wed, Dec 18, 2019 at 02:03:13PM +0100, Julien Cristau wrote:
> Control: severity -1 serious
>
> On Thu, Aug 08, 2019 at 01:45:27PM +0200, Julien Cristau wrote:
> > On Wed, Jul 17, 2019 at 10:11:39PM +0200, Lucas Nussbaum wrote:
> > > On 17/07/19 at 14:01 +02
On Thu, Jun 04, 2020 at 11:19:31PM +0200, Julien Cristau wrote:
> The arch:all failure is at grnet and that buildd has both v4 and v6
> addresses, so presumably unrelated.
>
A further give-back seems to have worked, so 3.6.13-4 managed to build
on all arches and move to testing now
On Thu, Jun 4, 2020 at 22:18:10 +0300, Adrian Bunk wrote:
> On Thu, Jun 04, 2020 at 07:55:32PM +0200, Julien Cristau wrote:
> > Control: tag -1 moreinfo
> >
> > On Thu, Jun 04, 2020 at 07:59:22PM +0300, Adrian Bunk wrote:
> > >
On Thu, Jun 04, 2020 at 07:32:13PM +0200, Andreas Metzler wrote:
> On 2020-06-04 Adrian Bunk wrote:
> > Source: gnutls28
> > Version: 3.6.13-2
> > Severity: serious
> > Tags: ftbfs
>
> > https://buildd.debian.org/status/logs.php?pkg=gnutls28=3.6.13-3
> >
Control: tag -1 moreinfo
On Thu, Jun 04, 2020 at 07:59:22PM +0300, Adrian Bunk wrote:
> FAIL: dtls_hello_random_value
> =
>
> testing: default
> client:156: client: Handshake failed: Resource temporarily unavailable, try
> again.
> server:271: server: Handshake has
Control: tag -1 patch
On Tue, Jun 02, 2020 at 08:09:43AM +0200, Salvatore Bonaccorso wrote:
> On Tue, Jun 02, 2020 at 06:40:41AM +0200, Salvatore Bonaccorso wrote:
> > Source: perl
> > Version: 5.30.3-1
> > Severity: serious
> > Justification: FTBFS
> >
> > Hi Dom an Niko
> >
> > Guess you have
Hi Dmitry,
mercurial in experimental is built for python3, is there a chance you
could test sphinx-patchqueue with it before I upload to sid?
Thanks,
Julien
:02.0 +0200
@@ -1,3 +1,11 @@
+fontconfig (2.13.1-4.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Hopefully this otherwise dummy upload lets us work around bug #960679.
+ * Add missing Breaks for the -doc package split (closes: #960598)
+
+ -- Julien Cristau Fri, 15 May 2020 12:55:02
Source: fontconfig
Version: 2.13.1-2
Severity: serious
libfontconfig1 Depends on fontconfig-config (>= ${source:Version})
If the arch:amd64 buildd is faster than the arch:all one, as happened
with 2.13.1-4.1, the new libfontconfig1 becomes uninstallable, and,
because fontconfig indirectly
On Thu, May 07, 2020 at 09:48:34PM +1000, Dmitry Smirnov wrote:
> On Thursday, 7 May 2020 7:04:17 PM AEST Julien Cristau wrote:
> > This use of Provides is not acceptable. The systemctl package does not
> > in any way provide the same functionality / interfaces as the syst
Control: reassign -1 xserver-xorg-core 2:1.20.4-1
Control: tag -1 important
On Tue, Jul 23, 2019 at 01:31:36PM +0200, Lucas Nussbaum wrote:
> Since upgrading from Debian 9 to Debian 10, I experience crashes when
> unplugging my dock station.
>
> The end of the log is:
>
> [ 12796.678] (II)
Package: tmux
Version: 3.1-1
Severity: serious
Hi,
on apt upgrade in testing today I was greeted by this NEWS entry from
tmux saying:
The server protocol was changed in an incompatible manner, we recommend
that you close any open tmux sessions before proceeding with the upgrade.
I don't
On Sun, Apr 26, 2020 at 18:28:07 +0200, Santiago Vila wrote:
> On Sun, Apr 26, 2020 at 06:09:53PM +0200, Julien Cristau wrote:
> > On Wed, Dec 27, 2017 at 11:42:35PM +0100, Santiago Vila wrote:
> > > reopen 880233
> > > thanks
> > >
> > > Hi.
>
Control: severity -1 wishlist
On Fri, Jan 10, 2020 at 08:54:07PM +0100, Gianfranco Costamagna wrote:
> Severity: serious
Why?
Cheers,
Julien
On Tue, Dec 31, 2019 at 18:25:04 -0500, Sandro Tosi wrote:
> On Tue, Dec 31, 2019 at 6:11 PM Julien Cristau wrote:
> >
> > Nak. I don't want to drop python support at this stage.
>
> can you explain why? there is no package in debian depending on
> python-hglib, and i
Nak. I don't want to drop python support at this stage.
Julien
On December 31, 2019 11:58:44 PM GMT+01:00, Sandro Tosi
wrote:
>Control: tags 937808 + patch
>
>
>Dear maintainer,
>
>I've prepared an NMU for python-hglib (versioned as 2.6.1-1.1). The
>diff
>is attached to this message.
>
On Mon, Dec 02, 2019 at 07:37:02PM +, Chris Lamb wrote:
> Hi Julien,
>
> > It seems to me the test is inherently extremely sensitive to the exact
> > version of black used, so it probably shouldn't be part of autopkgtests?
>
> Mmm, except I anticipated this at the time with the following
>
Package: diffoscope
Severity: serious
Tags: bullseye sid
X-Debbugs-Cc: bl...@packages.debian.org
diffoscope autopkgtests fail with the current version of "black" in sid:
https://ci.debian.net/data/autopkgtest/unstable/amd64/d/diffoscope/3557636/log.gz
It seems to me the test is inherently
Source: openfoam
Version: 1906+dfsg1-1
Severity: serious
Hi,
Looking at https://buildd.debian.org/status/logs.php?pkg=openfoam the
build time for your package increased unreasonably in this version.
Cheers,
Julien
Package: hgsubversion
Version: 1.9.3+git20190419+6a6ce-1
Severity: grave
Tags: bullseye sid
The current version of hgsubversion in sid doesn't work with hg 5.2, as
evidence by the autopkgtest failing.
Specifically, the mercurial.repository module moved to
mercurial.interfaces.repository.
1 - 100 of 3073 matches
Mail list logo
