On Sat, 01 Dec 2018 at 17:18:35 +, Holger Levsen wrote:
> https://tests.reproducible-builds.org/debian/issues/unstable/paths_vary_due_to_usrmerge_issue.html
> lists these packages.
>
> what surprises me currently, are those 3 packages which are reproducible
> in buster (even though we also var
On Sun, 02 Dec 2018 at 21:21:40 +0900, Hideki Yamane wrote:
> - What is the problem? (broken build for which packages? Just R?)
The problem we're aware of is:
Some packages auto-detect the absolute path to an executable (for example
bash or perl) and hard-code it into their output (for example
On Sun, 02 Dec 2018 at 20:16:10 +0100, Marc Haber wrote:
> On Sat, Dec 01, 2018 at 11:36:45PM +0100, Didier 'OdyX' Raboud wrote:
> > A merged-/usr has a /bin → /usr/bin symlink; so a .deb package unpacking
> > /bin/grep will make that binary end up in /usr/bin/grep; but the
> > /bin → /usr/bin syml
On Sun, 02 Dec 2018 at 19:54:39 +, Simon McVittie wrote:
> When installed on a merged /usr system:
Oops, of course this should have said:
.deb contains -> /bin/grep/usr/bin/perl
/bin/fooexists thanks to /bin symlink exists thanks to /bin symlink
/usr/b
On Sun, 02 Dec 2018 at 21:04:55 +0100, Marc Haber wrote:
> The next debhelper change might choose to give / instead of /usr as a
> target directory by default, moving hundreds of megabytes from /usr to /
> over time.
I don't think anyone is proposing that. There's no reason why it would be
preferr
Control: retitle 914897 tech-ctte: Should debootstrap disable merged /usr by
default?
I'm retitling the bug to avoid misrepresenting the technical committee's
position on this. We have been asked to overrule the debootstrap
maintainer, but we have not yet come to a conclusion on whether we should
On Thu, 15 Mar 2018 at 20:23:59 +0200, Adrian Bunk wrote:
> On Thu, Mar 15, 2018 at 06:38:30PM +0100, Andreas Metzler wrote:
> > ---
> > ./libinput-1.10.3-builtwithmeson0.44.1-1/debian/libinput-dev/usr/lib/x86_64-linux-gnu/pkgconfig/libinput.pc
> > 2018-03-15 18:24:08.366925927 +0100
> > +
Control: tags -1 + pending
On Sat, 17 Mar 2018 at 16:05:02 -0400, Jeremy Bicha wrote:
> I have proposed a merge request to fix this issue.
> https://salsa.debian.org/xorg-team/lib/libinput/merge_requests/1
This has now been merged.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892956 and ups
Control: forwarded -1 https://gitlab.gnome.org/GNOME/gtk/issues/114
Control: tags -1 + pending fixed-upstream
On Wed, 21 Mar 2018 at 11:08:18 +0100, Marcus Lundblad wrote:
> libgtk-3-0: All wayland clients crash (seems to happen when the screen was
> locked for a while)
>
> This seems to be this
Control: tags -1 + patch fixed-upstream
Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=788706
On Mon, 26 Mar 2018 at 16:11:31 +0300, Adrian Bunk wrote:
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rhythmbox.html
>
> ...
> In file included from
> /usr/lib
Package: 2to3
Version: 3.6.5~rc1-1
Severity: grave
Justification: renders package unusable
2to3/3.6.5~rc1-1 depends on python3-lib2to3 (>= 3.6.5~rc1-3~) which
doesn't seem to exist yet. piuparts demonstrates this failing:
https://piuparts.debian.org/sid/source/p/python3-defaults.html
Looking at i
Control: tags -1 + fixed-upstream pending
Control: forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=57077
On Tue, 27 Mar 2018 at 13:41:03 +0300, Adrian Bunk wrote:
> libtool: error: cannot find the library 'libpolkit-gobject-1.la' or
> unhandled argument 'libpolkit-gobject-1.la'
[...]
On Tue, 27 Mar 2018 at 23:48:35 +0300, Adrian Bunk wrote:
> pkg_resources.DistributionNotFound: The 'msgpack-python' distribution was not
> found and is required by asgi-ipc
Looks like more fallout from
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893844
but in this case presumably it'll nee
Control: tags -1 + moreinfo
On Wed, 28 Mar 2018 at 19:22:41 +0200, geodeb wrote:
> until gnome 3.26 it was correctly detected. now it works
> only on full hd resolution. higher resolutions cause the blackout of both the
> displays and the only way out is to power off.
This is not a bug in gnome-c
On Sat, 31 Mar 2018 at 09:18:46 +0800, Paul Wise wrote:
> I recently auto-upgraded evolution from testing to unstable because
> evolution-rss got auto-removed from testing due to the gconf transition
> so unattended-upgrades upgraded it to the latest unstable version.
Using unattended-upgrades wit
Control: retitle -1 glib2.0: gio/tests/gapplication.c:572:test_quit: assertion
failed: (activated)
On Tue, 03 Apr 2018 at 15:31:34 +0800, Boyuan Yang wrote:
> Justification: fails to build from source on release architecture (but
> built successfully in the past)
This looks like a transient fail
Control: retitle -1 FTBFS: Failed to register: The connection is closed;
gio/tests/gapplication.c:572:test_quit: assertion failed: (activated)
Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=768996
Control: found -1 2.49.3-1
On Tue, 03 Apr 2018 at 11:00:23 +0100, Simon McVittie
On Wed, 04 Apr 2018 at 00:51:04 +0200, Axel Beckert wrote:
> since very recently, emacs25 on armhf (but not on amd64) crashes for
> me as follows:
>
> emacs25: symbol lookup error:
> /usr/lib/arm-linux-gnueabihf/libgobject-2.0.so.0: undefined symbol:
> g_date_copy
I would normally ask: if you r
On Wed, 04 Apr 2018 at 10:41:01 +0300, Adrian Bunk wrote:
> On Wed, Apr 04, 2018 at 09:10:31AM +0200, Axel Beckert wrote:
> >...
> > ~ → ldd /usr/lib/arm-linux-gnueabihf/glib-2.0/gio-querymodules
> > libgio-2.0.so.0 => /usr/lib/arm-linux-gnueabihf/libgio-2.0.so.0
> > (0x76e3f000)
> >
Control: tags -1 + patch pending
On Tue, 03 Apr 2018 at 11:24:38 +0100, Simon McVittie wrote:
> [This] is an intermittent failure present since before stretch. I could
> reproduce it on amd64 by running
>
> /usr/lib/glib2.0/installed-tests/glib/gapplication --tap
>
> seve
close 870811 1.50a+dfsg1-3+deb9u1
found 870811 1.50a+dfsg1-3
thanks
CVE-2017-11721 has been fixed in iortcw in all applicable suites.
On Mon, 07 Aug 2017 at 15:47:16 +0100, jcowg...@debian.org wrote:
> It appears that your package provides an external symbol that is
> affected by the recent name mangling changes in GCC 7. See:
> https://gcc.gnu.org/gcc-7/porting_to.html#conversion-op-mangling
I started to look into fixing this b
Package: bubblewrap
Version: 0.1.8-3
Severity: serious
Tags: upstream fixed-upstream pending
Justification: Policy 2.2.1
The cat picture displayed in the HTMLized README on Github
(bubblewrap.jpg) is a CC-BY-ND photo sourced from Flickr. This is not a
DFSG-compliant license, and the prevailing int
Control: clone -1 -2
Control: retitle -2 FTBFS on mips64el: various test failures
On Sat, 23 Sep 2017 at 12:29:08 +0200, Emilio Pozuelo Monfort wrote:
> Let's track the mips64el failure in a different bug, as it's
> completely different from this.
Cloned away. I haven't investigated those failure
Control: tags -1 sid
On Fri, 22 Sep 2017 at 16:36:26 +0200, Stéphane Glondu wrote:
> Please recompile polygen with OCaml 4.05.0. This cannot be done with a
> binNMU, since polygen is arch:all.
The fixed polygen won't migrate to buster until the new OCaml does, but
this is not actually a bug that
On Sun, 01 Oct 2017 at 23:36:52 +0200, Michael Biebl wrote:
> >> The remaining problem seems to be a big-endian issue (mips, s390x,
> >> hppa, powerpc, sparc64). ppc64 fails in a slightly different
> >> manner, might just be it's failing earlier for a different reason
> >> but would also suffer fr
Source: lwt
Version: 2.7.1-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Control: block 871469 by -1
https://buildd.debian.org/status/fetch.php?pkg=lwt&arch=arm64&ver=2.7.1-1&stamp=1507629114&raw=0
https://buildd.debian.org/status/fetch.php?pkg=
Source: lwt
Version: 2.7.1-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Control: block 871469 by -1
https://buildd.debian.org/status/fetch.php?pkg=lwt&arch=armel&ver=2.7.1-1&stamp=1507629485&raw=0
https://buildd.debian.org/status/fetch.php?pkg=
Package: osc
Version: 0.162.1-1
Severity: grave
Justification: osc tool becomes mostly unusable
This is probably a bug in libssl1.1 or in python-m2crypto, but I'm
reporting it against osc for now, because that's the only place I know
how to reproduce it at the moment. X-Debbugs-Cc'd to the lower-l
On Sun, 08 Apr 2018 at 09:49:14 +0200, Sven Joachim wrote:
> Current glib2.0 source can be built with either meson or autotools, and
> debian/rules should probably specify which one to use. Feel free
> reassign a clone of this bug back to glib2.0 for that, but "debian/rules
> clean" even fails whe
Digikam still works with exiv2 0.25. It's just that a lot of fixes have
gone into 0.26 that prevent crashs in digikam, that's why its cmake file
has a >=0.26 dependency.
signature.asc
Description: OpenPGP digital signature
I totally understand that, I am just trying to get infos to you as
debian maintainer from my (at the moment admittedly almost non-existing)
involvement upstream. Exiv2 0.26 will likely not get into testing.
Upstream does backport a lot of security fixes to 0.26, but negated
creating a dot release o
(I don't speak for the GNOME team, or for Josselin, who is officially
this package's maintainer; please don't assume I do.)
On Sun, 08 Apr 2018 at 22:19:43 +0300, Adrian Bunk wrote:
> I hereby declare my intent to adopt gconf.
Thank you for offering to take over this package. Do you also intend
t
On Thu, 12 Apr 2018 at 15:03:11 +0200, Gert Wollny wrote:
> Hi Adrian,
(Adrian won't have seen this unless he's subscribed to the bug or
package, because bug submitters don't normally get copies of bug mail
in the Debian BTS; adding him to Cc.)
> as the maintainer of amide[1], a package that dep
Control: tags -1 + upstream wontfix
Control: user pkg-gnome-maintain...@lists.alioth.debian.org
Control: usertags -1 + unmaintained-upstream
On Sun, 24 Dec 2017 at 09:12:19 -0500, Jeremy Bicha wrote:
> pygtk is unmaintained upstream. It has not had a release since GNOME 3
> was released in 2011.
On Thu, 12 Apr 2018 at 23:12:44 +0300, Adrian Bunk wrote:
> On Mon, Apr 09, 2018 at 04:12:47PM +0100, Simon McVittie wrote:
> > - src:orbit2 (orphaned library needed by gconf)
> > - src:libidl (orphaned library needed by orbit2)
>
> Where does gconf depend on these?
I tho
On Thu, 12 Apr 2018 at 23:32:45 +0300, Adrian Bunk wrote:
> On Thu, Apr 12, 2018 at 06:09:32PM +0100, Simon McVittie wrote:
> > particularly if you plan to modify things that are annoying to do via
> > a patch series, like the build system.
>
> I do not see any reason for ch
llowing
sha512 checksum:
d7e45a4395a8c7632187ca5c8b837bad0d7583f66ce5f5d2b8f1acabf9ff2539d038a16986f9846818183f5c3268a613580a98ad72f3766e286e6273d57ddc78
kpatch_0.5.0.orig.tar.gz
Regards
Simon
--
+ privacy is necessary
+ using gnupg http://gnupg.org
+ public key id: 0x92FEFDB7E44C32F9
diff -u -r kpatch-0.3.2/debian/changelog kpatch
Control: tags -1 + moreinfo unreproducible
On Mon, 23 Apr 2018 at 13:02:26 +0200, Vincent Lefevre wrote:
> On 2018-04-18 14:43:47 -0400, rektide de la faye wrote:
> > I recently updated a number of packages on my Debian/testing laptop,
> > via aptitude and included in that upgrade to satisfy depen
On Mon, 23 Apr 2018 at 17:11:11 +0200, Michael Biebl wrote:
> @smcv: Do you think this is a failure of dpkg/apt cleaning up old
> versions? My suspicion is rather, that there is some old copy of libglib
> lying around in /lib/x86_64-linux which was copied there by some 3rd
> party installer, possib
On Tue, 24 Apr 2018 at 01:33:02 -0400, rektide wrote:
> Hi sorry for the delay. Per request:
>
> $ ls -il {,/usr}/lib/x86_64-linux-gnu/libglib-2.0.so*
> 42488866 lrwxrwxrwx 1 root root 23 Mar 22 05:08
> /lib/x86_64-linux-gnu/libglib-2.0.so.0 -> libglib-2.0.so.0.5600.0
> 3373718 -rw-r--r-- 1
On Sat, 28 Apr 2018 at 13:03:14 +0200, Harald Welte wrote:
> Package: osc
> Version: 0.162.1-1
> Followup-For: Bug #895035
>
> I also see "double free or corruption" 100% reproducible when using osc on
> unstable
> for the past few weeks
I tried rebuilding older openssl versions, and the regress
On Wed, 02 May 2018 at 18:34:35 +0200, Kurt Roeckx wrote:
> On Wed, May 02, 2018 at 05:19:20PM +0100, Simon McVittie wrote:
> > * https://github.com/openssl/openssl/pull/5967
>
> Is it urgunt to fix this in testing/unstable?
Probably not, unless it makes other packages regress? T
Control: owner -1 tsimo...@ubuntu.com
I can take care of this when I do the next QA upload for this package.
Thanks!
--
Simon Quigley
tsimo...@ubuntu.com
tsimonq2 on freenode and OFTC
5C7A BEA2 0F86 3045 9CC8
C8B5 E27F 2CF8 458C 2FA4
0
@@ -1,3 +1,16 @@
+mixxx (2.0.0~dfsg-7.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+
+ [ Sebastian Ramacher ]
+ * Remove used B-D on libaudiofile-dev
+
+ [ Simon McVittie ]
+ * Add patch from James Cowgill to fix FTBFS with newer sqlite3
+(Closes: #868612)
+
+ -- Simon McVitti
4807d6f7d9aa9478f27431784a1422d271ef3c26
Author: Simon McVittie
Date: Mon Jul 24 11:08:18 2017 +0100
Non-maintainer upload 2.0.0~dfsg-7.1
Gbp-Dch: ignore
diff --git a/debian/changelog b/debian/changelog
index af37538..2f9010b 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,16 @@
+mixxx (2.0.0
On Mon, 24 Jul 2017 at 14:04:03 +0200, Mattia Rizzolo wrote:
> I've merged your changes and added a tag to the git repository; please
> feel free to reschedule it to delayed/0.
Thanks, done (assuming I got my dcut syntax right).
S
Control: retitle 865803 libsoup2.4 FTBFS: Unacceptable TLS certificate
Control: tags 865803 + upstream patch fixed-upstream
Control: forwarded 865803 https://bugzilla.gnome.org/show_bug.cgi?id=784949
On Sun, 25 Jun 2017 at 00:49:53 +0300, Adrian Bunk wrote:
> FAIL: misc-test 4 /misc/aliases
This
automatically by
'git-post-receive-tag-pending-commitmsg' hook).
---
commit 38aa4129282bfbcfadfc02fa021bb06518ddbe7a
Author: Simon Quigley
Date: Sun Jul 30 14:56:25 2017 -0500
Solve binary file conflict between abiword-dbgsym and
abiword-plugin-grammar-dbgsym (Closes: #868537).
Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=785113
On Tue, 01 Aug 2017 at 00:47:43 +0200, Michael Biebl wrote:
> Am 01.08.2017 um 00:34 schrieb Adrian Bunk:
> >>> File "/usr/lib/python3.5/encodings/ascii.py", line 26, in decode
> >>> return codecs.ascii_decode(input, sel
Source: dbus-python
Version: 1.2.8-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Build-time tests for dbus-python 1.2.8-1 failed on the armhf buildd. I
re-ran the tests 100 times in a loop on the armhf porterbox 'harris'
and they failed 6 times
2151f46331cd88 Mon Sep 17 00:00:00 2001
From: Simon McVittie
Date: Mon, 14 May 2018 18:24:09 +0100
Subject: [PATCH 2/3] Only build on amd64
fakemachine currently assumes that the linker is
/lib64/ld-linux-x86-64.so.2, the standard C library is
/lib/x86_64-linux-gnu/libc.so.6, and qemu-syste
ently hard-coded.
By inspection of its source code, it should also have at least a Suggests
(probably a Recommends) on e2fsprogs, for mkfs.ext4.
Please consider the attached patch.
Thanks,
smcv
>From 67763c9fa94d9088537a314dbf050f69ac9af760 Mon Sep 17 00:00:00 2001
From: Simon McVittie
D
Control: tags 898651 + patch
On Mon, 14 May 2018 at 18:34:23 +0100, Simon McVittie wrote:
> Please consider the attached patch.
Note that this doesn't do anything for dependent packages like
debos, which will probably need similar dependencies.
What I proposed adding to fakemachine, whi
Package: btrfs-progs
Version: 4.16.1-1
Severity: grave
Justification: renders package unusable (fails to install)
Preparing to unpack .../04-btrfs-progs_4.16.1-1_amd64.deb ...
Unpacking btrfs-progs (4.16.1-1) over (4.15.1-2) ...
...
Processing triggers for initramfs-tools (0.130) ...
update-initra
Control: tags -1 + patch fixed-upstream
On Wed, 02 May 2018 at 17:19:20 +0100, Simon McVittie wrote:
> * https://github.com/openSUSE/osc/issues/398
>
> """
> - m2crypto 0.29 does no SSL_free(...) (which is fixed in 0.30)
> (that's why this bug
Control: tags -1 + moreinfo
On Fri, 18 May 2018 at 15:21:57 +0200, Josep M. Perez wrote:
> gnome-shell crashes when I press meta+L to lock the session. After the third
> failed attempt, it crashes and also suspends the computer.
How reproducible is this? If you reboot your computer and try repeat
Source: gstreamer1.0
Version: 1.14.1-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Recent versions of dh-autoreconf automatically run gtkdocize if gtk-doc
is found in configure.ac. This caused gstreamer1.0/1.14.1-1 to FTBFS on
all architectures
Control: retitle -1 gstreamer1.0: run gtkdocize during build
Control: severity -1 wishlist
On Sat, 19 May 2018 at 13:08:12 +0100, Simon McVittie wrote:
> Recent versions of dh-autoreconf automatically run gtkdocize if gtk-doc
> is found in configure.ac. This caused gstreamer1.0/1.14.1-1 to
On Sun, 20 May 2018 at 14:25:06 +0800, Boyuan Yang wrote:
> > dh_autoreconf --as-needed
> > Can't exec "gtkdocize": No such file or directory at
> > /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 356.
>
> I think this bug is caused by https://bugs.debian.org/898916 .
>
> Dear maintainer, please
On Sun, 20 May 2018 at 11:13:10 +0100, Simon McVittie wrote:
> On Sun, 20 May 2018 at 14:25:06 +0800, Boyuan Yang wrote:
> > > dh_autoreconf --as-needed
> > > Can't exec "gtkdocize": No such file or directory at
> > > /usr/share/perl5/Debian/Debhelper/
On Tue, 22 May 2018 at 11:18:04 +0200, Josep M. Perez wrote:
> So, I opened dconf-editor and saw that for some reason
> /org/gnome/shell/disable-extension-version-validation was active, and that
> was the default value.
That is correct. By default extensions don't need to declare compatibility
wit
Source: attal
Severity: serious
User: debian...@lists.debian.org
Usertags: proposed-removal
attal fails to build from source since 2016, and depends on Qt 4 which
is no longer maintained. It was not released with stretch. I think it
might be time for this package to be removed from unstable.
If y
Source: attal-themes
Severity: serious
User: debian...@lists.debian.org
Usertags: proposed-removal
Control: block -1 by 900468
attal fails to build from source since 2016, and depends on Qt 4 which
is no longer maintained. It was not released with stretch. attal-themes
appears to be a data package
On Mon, 09 Oct 2017 at 10:36:52 +0100, Simon McVittie wrote:
> On Sun, 01 Oct 2017 at 23:36:52 +0200, Michael Biebl wrote:
> > >> The remaining problem seems to be a big-endian issue (mips, s390x,
> > >> hppa, powerpc, sparc64). ppc64 fails in a slightly different
&
On Sun, 01 Oct 2017 at 19:03:46 +0100, Simon McVittie wrote:
> On Sat, 23 Sep 2017 at 12:29:08 +0200, Emilio Pozuelo Monfort wrote:
> > Let's track the mips64el failure in a different bug, as it's
> > completely different from this.
>
> Cloned away. I haven'
ts one of those failures. I've left mozjs52
compiling on mips (minkus) overnight to see whether both big-endian
32-bit architectures behave the same.
On Thu, 12 Oct 2017 at 00:16:32 +0100, Simon McVittie wrote:
> ## ecma_6/TypedArray/sort_snans.js: rc = 3, run time = 0.055719
> ecma_6/shell
Control: retitle 877428 mozjs52: FTBFS on mips64el: regress-157652.js timeout;
regress-422348.js timeout; ecma_6/Array/for_of_1.js got 150, expected 300
[Re-sending to the correct clone, sorry for the noise]
On Sun, 01 Oct 2017 at 19:03:46 +0100, Simon McVittie wrote:
> On Sat, 23 Sep 2017
4:
ecma_6/TypedArray/sort_snans.js: got -1.8938930325389462e+304, expected NaN
Control: retitle -4 mozjs52: FTBFS on s390x, powerpc64 (64-bit BE) with same
tests failing
On Thu, 12 Oct 2017 at 01:31:08 +0100, Simon McVittie wrote:
> I've left mozjs52
> compiling on mips (minkus) ove
d2b4568abf4b43a26c8c1033295d8e40e56408ba
Author: Simon McVittie
Date: Thu Oct 12 20:20:56 2017 +0100
Close #873778 now that I've cloned away the test failures
diff --git a/debian/changelog b/debian/changelog
index cd8a0ed..763be40 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -13,7 +13,9 @@ mozjs52 (52.
On Thu, 12 Oct 2017 at 01:37:51 +0100, Simon McVittie wrote:
> On mips64el there are a couple of timeouts (knowing mips*, probably
> an arbitrary timeout is just too short):
>
> TEST-UNEXPECTED-FAIL | js1_5/Array/regress-157652.js | (args: "") | (TIMEOUT)
> TEST-UNEXPE
On Thu, 12 Oct 2017 at 08:08:42 +0100, Simon McVittie wrote:
> On Thu, 12 Oct 2017 at 01:31:08 +0100, Simon McVittie wrote:
> > I've left mozjs52
> > compiling on mips (minkus) overnight to see whether both big-endian
> > 32-bit architectures behave the same.
>
>
On Thu, 12 Oct 2017 at 01:31:08 +0100, Simon McVittie wrote:
> powerpc64 (pizzetti) gets the same test failures as s390x (zelenka),
> suggesting that they are something that happens on big-endian 64-bit.
> hppa doesn't seem to have a porterbox and sparc64's (notker) was
> un
Control: reopen 878236
On Wed, 11 Oct 2017 at 15:13:56 +0100, Simon McVittie wrote:
> dh_install: Cannot find (any matches for)
> "/usr/lib/ocaml/lwt/dlllwt-unix_stubs.so" (tried in ., debian/tmp)
> dh_install: liblwt-ocaml missing files:
> /usr/lib/ocaml/lwt/dlllwt-unix
On Thu, 21 Sep 2017 at 07:41:30 -0400, Jeremy Bicha wrote:
> On Fri, Sep 8, 2017 at 2:06 PM, Michael Biebl wrote:
> > The version from experimental apparently breaks other packages like
> > gnome-weather:
>
> Yes, I remember now that several GNOME 3.22 packages had to be updated
> to work with gj
Package: gjs
Version: 1.50.1-2
Severity: serious
Affects: gnome-documents
X-Debbugs-Cc: debian-m...@lists.debian.org
mozjs52 now works at least partially on mips (although there are thousands
of test failures, #878284) but gjs doesn't even start:
(sid_mips-dchroot)smcv@minkus ~ % js52
js>
On Mon, 16 Oct 2017 at 07:57:45 +0100, Simon McVittie wrote:
> My changes in pkg-gnome git are not believed to be sufficient: in
> addition to turning off the JIT, Adrian says we need to fix atomic
> operations to not use jit/none/AtomicOperations-none.h. (It isn't
> at al
Source: babeltrace
Version: 1.5.3-2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: debian-ker...@lists.debian.org
libbabeltrace1 (= 1.5.3-2) merges the contents of libbabletrace-ctf1 into
the libbabeltrace1 package. This makes packages like gdb uninstallable.
Similarly, libb
On Thu, 19 Oct 2017 at 11:18:28 +0300, Adrian Bunk wrote:
> Control: retitle -1 Please make libbabeltrace-ctf{1,-dev} provides versioned
>
> On Thu, Oct 19, 2017 at 08:28:46AM +0100, Simon McVittie wrote:
> >...
> > Please do one of these as soon as possible:
> >...
>
On Fri, 20 Oct 2017 at 14:36:06 +0200, Markus Koschany wrote:
> If you insist on severity
> serious for such a problem, then bug reports with the same severity
> should be filed against packages
>
> a) that do not recreate their build system at build time
> b) all packages that contain a prebuil
On Fri, 20 Oct 2017 at 16:22:38 +0200, Markus Koschany wrote:
> So you are basically saying that the situation for configure scripts is
> less clear-cut and you tend to acknowledge that this is a bug but
> usually not a release critical one and it also depends on how the
> copyright holder is treat
close 878519 52.3.1-6
thanks
This was a mozjs52 bug, not a gjs bug. It got reopened when I reassigned it.
e used for apport-gtk integration (but that feature is off
+by default) and for apt integration via synaptic-pkexec (but that
+feature has been patched out because it depends on direct access to
+internal dpkg files).
+
+ -- Simon McVittie Thu, 19 Oct 2023 08:53:46 +0100
+
lxsessio
Control: tag -1 pending
Hello,
Bug #1031842 in xdg-desktop-portal-gnome 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:
https://salsa.debian.org/gnome-team/xdg-desktop-portal-gnome/-/co
Control: tag -1 pending
Hello,
Bug #1056185 in gi-docgen 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:
https://salsa.debian.org/gnome-team/gi-docgen/-/commit/8590925586a8972e20bf82a44
Control: tag -1 pending
Hello,
Bug #1065493 in gtk+2.0 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:
https://salsa.debian.org/gnome-team/gtk2/-/commit/3406805d5833fc78ccab4c1aaff3cbc9
Control: tag -1 pending
Hello,
Bug #1065494 in gtk+3.0 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:
https://salsa.debian.org/gnome-team/gtk3/-/commit/1c4fb7e79ab1d3c28a957b777e692afa
/-/commits/ogre-13.3/?ref_type=heads
I'm currently super short on time but will try to help you with any
technical problems if you open a MR for a patch
Best regards from Freiburg
Simon
Am 06.03.24 um 08:46 schrieb Flavien Bridault:
Dear maintainer(s),
I took a look at the latest versi
Control: reassign -1 aptitude,libgtk2.0-0t64
Control: tags -1 + moreinfo
On Thu, 07 Mar 2024 at 16:10:17 +0100, Vincent Lefevre wrote:
> During an upgrade with aptitude:
>
> dpkg: dependency problems prevent removal of libgtk2.0-common:
> libgtk2.0-bin depends on libgtk2.0-common.
> libgtk2.0-0
NULL SDL object
On Sun, 04 Feb 2024 at 12:31:35 +0000, Simon McVittie wrote:
> When I try the command above, on GNOME in Wayland mode, I get what
> appears to be a different crash
Now reported separately as #1065709, which I now see was a duplicate
of #1057620 (I'll merge them).
&g
Control: block 1036884 by -1
On Sun, 10 Mar 2024 at 10:37:51 +0100, Aurelien Jarno wrote:
> weston fails to build in unstable since the upload of neatvnc in version
> 8.0. From my build log on amd64:
...
> | Dependency neatvnc found: NO found 0.8.0 but need: '< 0.8.0' ; matched: '>=
> 0.7.0'
Thi
On Sun, 10 Mar 2024 at 13:12:57 +0100, Sebastian Ramacher wrote:
> rtl-tspan: 2655 pixels changed with maximum difference of 112
This appears to have been caused by upgrading pango1.0 from 1.52.0
to 1.52.1. The librsvg test suite is unfortunately very sensitive to
differences in the exact version
Control: tags -1 + pending
On Sun, 10 Mar 2024 at 14:03:18 +, Simon McVittie wrote:
> On Sun, 10 Mar 2024 at 13:12:57 +0100, Sebastian Ramacher wrote:
> > rtl-tspan: 2655 pixels changed with maximum difference of 112
>
> This appears to have been caused by upgrading pango1.0 f
Control: retitle -1 librsvg: reftest regression for rtl-tspan with pango1.0
1.52.1: 2655 pixels differ from reference
Control: severity -1 important
On Sun, 10 Mar 2024 at 14:45:24 +, Simon McVittie wrote:
> For now, I'm testing an upload that will temporarily disable this test,
On Sat, 09 Mar 2024 at 12:29:26 +0100, Sebastian Ramacher wrote:
> linux_input.c: In function ‘translate_event’:
> linux_input.c:761:28: error: ‘const struct input_event’ has no member named
> ‘time’
> 761 | devt->timestamp = levt->time;
> |^~
This seems t
On Mon, 11 Mar 2024 at 08:13:30 -0400, Jeremy Bícha wrote:
> Although Debian has not yet gotten to pygobject in the time_t
> transition for armel/armhf, Ubuntu has and experienced a build test
> failure in test_gi.py for the test_time_t tests which I believe are
> using functions in glib2.0. I assu
On Sun, 25 Feb 2024 at 20:36:58 +0100, Lucas Nussbaum wrote:
> > FAIL: test_black (devscripts.test.test_black.BlackTestCase.test_black)
> > Test: Run black code formatter on Python source code.
I think lint checks like this one should be run by contributors and CI
when targeting the main branch, b
Package: gobject-introspection
Version: 1.78.1-16
Severity: serious
Justification: results in misbuilt packages
X-Debbugs-Cc: debian-cr...@lists.debian.org
When it converts GIR XML to binary typelib files, g-ir-compiler replaces
abstract types such as int and gsize (size_t) with concrete types suc
Control: clone -1 -2
Control: retitle -2 gi-compile-repository: generates incorrect typelib when
cross-compiling with different type sizes
Control: reassign -2 libglib2.0-dev 2.79.3-1
Control: tags -2 = experimental
On Fri, 15 Mar 2024 at 07:48:17 +, Simon McVittie wrote:
> When it conve
at pass 32-bit time_t would get automatically
extended, which is one solution.
/Simon
> Thanks!
>
>
> -- System Information:
> Debian Release: trixie/sid
> APT prefers unstable
> APT policy: (500, 'unstable'), (1, 'experimental')
> Architecture: amd64 (
601 - 700 of 1956 matches
Mail list logo
