Source: visp
Version: 3.1.0-1
Severity: serious
Tags: upstream
Justification: fails to build from source (but built successfully in the past)
User: debian-m...@lists.debian.org
Usertags: mips
Builds of visp for big-endian architectures have been failing lately,
with errors in all 12
Source: gimagereader
Version: 3.2.1-1
Tags: upstream patch
User: helm...@debian.org
Usertags: rebootstrap
Forwarded: https://github.com/manisandro/gImageReader/pull/284
gdk-pixbuf-pixdata is deprecated:
https://bugzilla.gnome.org/show_bug.cgi?id=776004
Source: ndpi
Version: 2.2-1
Severity: important
Tags: upstream
Justification: fails to build from source (but built successfully in the past)
User: debian-sp...@lists.debian.org
Usertags: sparc64
The latest build of ndpi for sparc64 (admittedly not a release
architecture) failed because most or
Source: easytag
Version: 2.4.3-1
Tags: upstream patch
User: helm...@debian.org
Usertags: rebootstrap
gdk-pixbuf-pixdata is deprecated:
https://bugzilla.gnome.org/show_bug.cgi?id=776004
https://git.gnome.org//browse/gdk-pixbuf/tree/NEWS#n96
easytag uses it. By doing so it fails cross compilation
Hi,
On 02/01/18 15:57, Aaron M. Ucko wrote:
> Source: ndpi
> Version: 2.2-1
> Severity: serious
> Tags: upstream
> Justification: fails to build from source (but built successfully in the past)
> User: debian-m...@lists.debian.org
> Usertags: mips
>
> Builds of ndpi for mips, s390x, and the
Source: ndpi
Version: 2.2-1
Severity: important
Tags: upstream
Justification: fails to build from source (but built successfully in the past)
User: debian-h...@lists.debian.org
Usertags: hppa
The latest build of ndpi for hppa (admittedly not a release
architecture) failed with multiple test suite
Package: gajim
Version: 1.0.0~alpha2-1
Severity: normal
Dear Maintainer,
After upgrading to 1.0.0~alpha2, when I start gajim I no longer have
access to my openbox window decorations. Therefore, I can't make my
gajim window sticky, or use any of the other openbox features.
I tried running with
Hi "ydirson",
On Tue, 2018-01-02 at 16:09 +0100, ydir...@free.fr wrote:
> Package: mini-buildd
> Version: 1.0.29
>
> With no external keyring software installed, python-keyring defaults
> to alt.files, and the impact
> on scripting (eg. launching auto-setup for a test) is quite high:
>
> * have
Source: ndpi
Version: 2.2-1
Severity: important
Tags: upstream
Justification: fails to build from source (but built successfully in the past)
User: debian-al...@lists.debian.org
Usertags: alpha
The latest build of ndpi for alpha (admittedly not a release
architecture) failed with multiple test
Source: ndpi
Version: 2.2-1
Severity: serious
Tags: upstream
Justification: fails to build from source (but built successfully in the past)
User: debian-m...@lists.debian.org
Usertags: mips
Builds of ndpi for mips, s390x, and the non-release architectures
powerpc and ppc64 all failed because
Le 2018-01-02 12:44, James Cowgill a écrit :
...zip...
Note that the prefix does *not* have a trailing slash in debian/rules:
override_dh_auto_configure:
$(WAF) configure --prefix=/usr
So the simple fix is to use "--prefix=/usr/", but arguably this is an
upstream bug as well since
Source: libkcapi
Version: 1.0.0-2
Severity: important
Justification: fails to build from source
Builds of libkcapi for hurd-i386 (admittedly not a release
architecture) have been failing. The immediate issue is the Hurd's
notorious lack of a static PATH_MAX. Although that would certainly be
Package: cryptsetup
Version: 2:1.7.5-1
Severity: normal
Hi,
Like https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792552 , my
shutdown process never ends due to 'stopping remaining crypto disks'.
Though, nothing else appears after it, it just hangs.
my /etc/crypttab :
home/dev/nvme0n1p3none
Package: wnpp
Severity: wishlist
Owner: Guus Sliepen
* Package name: mstch
Version : 1.0.2
Upstream Author : Daniel Sipka
* URL : https://github.com/no1msd/mstch
* License : MIT
Programming Lang: C++
Description : Mustache
Hi!
Upstream (who is not overly excited with the idea of supporting random
git snapshots of Tesseract) speaking here.
* Helmut Grohne , 2018-01-02, 13:47:
But for the new tesseract the output is:
Error opening data file
Source: libmsv
Version: 1.1-4
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: environment
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
Hi,
Whilst working on the Reproducible Builds effort [0], we noticed
that libmsv could not be built
Package: mini-buildd
Version: 1.0.32~bpo9+1
yann@buildd:~$ mini-buildd-tool admin@buildd:8066 status
[admin@buildd:8066] Password:
Saving 'mini-buildd' passwords to 'keyrings.alt.file.EncryptedKeyring' with
policy 'Ask':
Save password for 'admin@buildd:8066': (Y)es, (N)o, (A)lways, Ne(v)er?
On Tue, Oct 10, 2017 at 11:12:16PM +0200, Ludens wrote:
> On Sat, 7 Oct 2017 23:28:57 +0200 Julian Andres Klode
> wrote:
> > JFTR: I wrote an implementation of parts of happy eyeballs for another
> > bug we should probably merge in here, but it fails the test suite on
> > CI:
Package: debheler
Version: 11
Severity: normal
cmake 3.9.5-1~bpo9+1 is now in stretch-backports.
Hi Daniel,
On Thu, 2017-02-16 at 13:54 -0500, Daniel Kahn Gillmor wrote:
> Package: ui-auto
> Version: 1.2.9
(...)
> the debrsign workflow isn't a particularly safe one (see discussion
> on
> https://bugs.debian.org/855282 and https://bugs.debian.org/855320).
>
> ui-auto should not encourage
Package: mini-buildd
Version: 1.0.29
With no external keyring software installed, python-keyring defaults to
alt.files, and the impact
on scripting (eg. launching auto-setup for a test) is quite high:
* have to enter keyring password for each keyring access
* a single error in one of those
Package: slic3r
Version: 1.2.9+dfsg-6.1~deb9u1
Severity: serious
Control: found -1 1.2.9+dfsg-6.1
The binaries shipped except slic3r cannot find Slic3r.pm
in the non-standard location, e.g.:
$ split_stl
Can't locate Slic3r.pm in @INC (you may need to install the Slic3r module)
(@INC contains:
I managed to rebuild - ran debian/rules build and the bug is still there.
Marc Auslander
From: "Debian Bug Tracking System"
To: marca...@gmail.com
Date: 01/01/2018 02:03 PM
Subject:Bug#886021: Info received (Or backport)
Thank you for the additional
Package: kernel-package
Version: 13.018
Severity: normal
Tags: patch
Attached patch includes `objtool` binary in kernel-headers package
generated by make-kpkg. This binary needs to be included to sucessfully
build all out-of-tree kernel modules, when kernel code include metadata
are generated by
Control: severity -1 serious
Roger Shimizu:
> I confirmed that there's only one package need to be installed
> specifically: libdbus-glib-1-2
[...]
> I'll only add libdbus-glib-1-2 as dependency.
Thanks for confirming. Making this bug RC then, as per policy.
Cheers,
--
intrigeri
Package: python3-keyring
Version: 10.5.1-1
After updating just this package on stretch to get the keyring binary:
$ keyring get mini-buildd admin
Error initializing plugin kwallet = keyrings.alt.kwallet.
Traceback (most recent call last):
File
Thorsten Glaser writes:
> Package: nullmailer
> Version: 1:2.1-5
> Severity: serious
> Justification: fails to install
> Control: notfound -1 1:2.1-3
>
> Investigating (0) nullmailer:amd64 < 1:2.1-3 -> 1:2.1-5 @ii umU Ib >
> Broken nullmailer:amd64 Depends on systemd-sysv:amd64 <
Source: android-platform-frameworks-base
Version: 1:7.0.0+r33-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Hi!
I'm afraid your package fails to build:
In file included from include/androidfw/AssetDir.h:25:0,
from
Hi Rene, upgrading to version 5.4.4-1 solve the problem ...
Thank you and regards!
Guido
Package: nullmailer
Version: 1:2.1-5
Severity: serious
Justification: fails to install
Control: notfound -1 1:2.1-3
Investigating (0) nullmailer:amd64 < 1:2.1-3 -> 1:2.1-5 @ii umU Ib >
Broken nullmailer:amd64 Depends on systemd-sysv:amd64 < none | 236-2 @un uH >
Considering systemd-sysv:amd64
This looks to be a dependency problem. Upgrading everything else in sid
made this problem go away.
--
Dwayne C. Litzenberger
OpenPGP: 19E1 1FE8 B3CF F273 ED17 4A24 928C EC13 39C2 5CF7
control: forwarded -1 https://github.com/s3tools/s3cmd/issues/945
hello,
lets see what upstream has to say
G.
Source: e2fsprogs
Version: 1.43.8-1
Severity: serious
Tags: upstream patch
Hi,
The latest upload of e2fsprogs FTBFS on all big-endian architectures due
to two problems in swapfs.c:
> ../../../../lib/ext2fs/swapfs.c: In function 'ext2fs_swap_super':
> ../../../../lib/ext2fs/swapfs.c:132:2:
Package: ftp.debian.org
User: release.debian@packages.debian.org
Usertags: rm
X-Debbugs-Cc: tx...@packages.debian.org
Please remove txaws from Debian.
txaws was removed from Debian Testing and not included in the Stretch
release because it fails to build from source. [1] txaws is now
Source: xppaut
Version: 6.11b+1.dfsg-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Hi!
I'm afraid your package fails to build:
dh_fixperms
chown: cannot access 'debian/xppaut/usr/share/doc/xppaut/examples/ode/t.so': No
such file or
On Wed, Sep 20, 2017 at 11:13 PM, intrigeri wrote:
> Roger Shimizu:
>> Can you confirm it still occurs on latest version, 0.2.8-1, which hit
>> sid/buster/stretch-bpo/jessie-bpo-sloppy?
>
> `ldd ~/.local/share/torbrowser/tbb/x86_64/tor-browser_en-US/Browser/libxul.so'
> tells
Package: python-keyczar
Version: 0.716+ds-1
Severity: important
Dear Maintainer,
Package has started to FTBFS with new pyasn1 like so:
==
ERROR: testParseX509 (util_test.ParseX509Test)
Package: tracker.debian.org
Severity: wishlist
Hello everybody, and happy new year,
Emails sent by the GitLab system installed on salsa.debian.org using the
"Emails on push" integration setting contain a "X-GitLab-Project:"
header by default. How about changing vendor/debian/rules.py so that
Control: reopen -1
Sadly, the thing is not fixed yet as other tests rely on the same kind of
methods.
We're discussing the matter.
--
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2
signature.asc
Description: PGP signature
"H.-Dirk Schmitt" writes:
I undertand you have a clear idea in your head of what's going wrong,
but please try to answer the precise questions asked.
> As written in the report, no error message is shown during normally
> processing with apt-get or dpkg.
>
> The error
Package: ocrodjvu
Version: 0.10.2-1
Severity: important
After upgrading tesseract to 4.x, ocrodjvu does not work for me at all.
The immediate error message is:
usage: ocrodjvu [options] FILE
ocrodjvu: error: language pack for the selected language (eng) is not
available
That's when I
Control: tags -1 - upstream
On Tue, Jan 02, 2018 at 10:57:44AM +0100, Mark Wielaard wrote:
> Could you please file a bug for that. I am not aware of any such issue.
> So would like to fix it, and would if I knew about it. Thanks.
No. Matthias Klose will file them, when he considers gcc-8 ready
I'm sure most people are aware of this but in case it helps someone
trying to work around the issue, I can log in successfully after
editing /etc/xrdp/sesman.ini, by changing the following under the
[Xorg] section:
58c58
< param=Xorg
---
> param=/usr/lib/xorg/Xorg
which bypasses the Xorg wrapper
On Mon, 2018-01-01 at 19:11 +0100, Gérard ROBIN wrote:
> In fact I use stretch in my laptop and the stretch kernel is
> linux-image-4.9.0-4-amd64, and with this kernel the frequency
> is displayed correctly. It's after installing the kernel
> linux-image-amd64 (4.13+86~bpo9+1) that I noticed
Package: calendarserver
Version: 9.1+dfsg-1
Severity: normal
After upgrading from version 7.0+dfsg-2, the server (using the
postgresql backend) fails to start.
This occurs even when attempting to run the calendarserver_upgrade
script, and even when the updates in
Hi Mattia,
On Tue, Jan 02, 2018 at 10:57:04AM +0100, Mattia Rizzolo wrote:
> On Tue, Jan 02, 2018 at 10:45:33AM +0100, Mattia Rizzolo wrote:
> > On Tue, Jan 02, 2018 at 09:27:47AM +0100, Salvatore Bonaccorso wrote:
> > > I've prepared an NMU for libxml2 (versioned as 2.9.4+dfsg1-6.1) and
> > >
Control: tag -1 + patch
Ronny Standtke:
> The attached patch (against the current version in git) fixes this issue.
Looks good to me.
Hi Tomasz,
Tomasz Buchert wrote:
> I wanted to switch nghttp2 to compat=11, but this causes
> binaries-have-file-conflict:
>
> W: nghttp2 source: binaries-have-file-conflict libnghttp2-dev libnghttp2-doc
> usr/share/doc/libnghttp2-dev/AUTHORS
> W: nghttp2 source: binaries-have-file-conflict
Source: kamailio
Version: 5.1.0-1
Severity: wishlist
Hi,
I noticed from the build log on mips64el a lot of warnings like this:
> In file included from ../../core/parser/../mem/../atomic/atomic_native.h:50:0,
> from ../../core/parser/../mem/../futexlock.h:42,
>
Control: tags -1 moreinfo
On Tue, 02 Jan 2018 12:28:13 +0100 Tomasz Buchert wrote:
> Package: debhelper
> Version: 11
> Severity: normal
>
> Dear Maintainer,
>
> I wanted to switch nghttp2 to compat=11, but this causes binaries-have-file-
> conflict:
>
> W: nghttp2 source:
Source: kamailio
Version: 5.1.0-1
Severity: serious
Tags: sid buster
Hi,
kamailio FTBFS on arm64 and mips64el with the error:
> /usr/bin/make --no-print-directory -C ./squirrel/squirrel
> CC_EXTRA_FLAGS="-fPIC" \
> OUT="../../libsquirrel.a" sq64
> gcc -O2 -m64 -D_SQ64 -fno-exceptions
2017-12-30 18:10 GMT+02:00 Otto Kekäläinen :
> I have prepared 10.1.30 for upload to Stretch and work is pushed to
> git.debian.org.
> CVE entries are updated
> https://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.1.git/commit/?h=stretch
>
> Currently the test builds on arm64 are
On martedì 2 gennaio 2018 12:51:48 CET Martin Steigerwald wrote:
> These dependencies are what appears to prevent the upgrade of KF 5.41 from
> experimental.
>
> merkaba:~#130> LANG=C apt install -t experimental plasma-framework kinit
> […]
> The following packages will be REMOVED:
> kde-full
Dear Pino.
Pino Toscano - 02.01.18, 12:32:
> reassign 886107 kdepim-runtime
> forcemerge 885111 886107
> thanks
>
> On martedì 2 gennaio 2018 10:43:56 CET Martin Steigerwald wrote:
> > Package: kdepim
> > Version: 4:16.04.3+5.95
> > Severity: normal
[…]
> > Today I tried again to upgrade to KF
On 02/01/18 12:28, Tomasz Buchert wrote:
> [...]
For repro case, see:
https://anonscm.debian.org/cgit/collab-maint/nghttp2.git/commit/?id=3980b752463f2ab67a3fcd0712d9f060b721999f
I worked around the problem by not installing the docs in libnghttp2-doc:
Dear Martin,
Martin Steigerwald wrote:
> Today I tried again to upgrade to KF 5.41 from experimental and aptitude
> stumbled over updating some -dev packages I had still installed.
>
> I removed them and was surprised that apt removed kdepim + kmail as well.
>
> Afterwards I reinstalled kdepim
Control: retitle -1 showq: does not start
Control: severity -1 grave
Control: tags -1 confirmed
Hi,
On 06/12/17 00:12, treb...@tuxfamily.org wrote:
> Package: showq
> Version: 0.4.1+git20161215~dfsg0-2
>
> Dear debian maintainers,
>
> trying to launch showq (debian stretch here) doesn't work
Package: icedtea-web
Version: 1.6.2-3.1
Can you please update icedtea-web to version 1.7.1?
Version 1.7 has been released in July 2017 and contains important bugfixes
and support for JDK9.
Here are the two release announcements:
On 26.12.2017 22:15, Vincent Bernat wrote:
> ❦ 26 décembre 2017 21:08 +0200, Timo Aaltonen :
>
> Do you expect one of us to upload or did you want to do that yourself
> (both are fine for me)?
I didn't read the bug history. I'll upload a new version
reassign 886107 kdepim-runtime
forcemerge 885111 886107
thanks
On martedì 2 gennaio 2018 10:43:56 CET Martin Steigerwald wrote:
> Package: kdepim
> Version: 4:16.04.3+5.95
> Severity: normal
>
> Dear Sandro, dear Maxy, dear Pino, dear maintainers,
There is no maxy in this case.
> Today I tried
Package: debhelper
Version: 11
Severity: normal
Dear Maintainer,
I wanted to switch nghttp2 to compat=11, but this causes binaries-have-file-
conflict:
W: nghttp2 source: binaries-have-file-conflict libnghttp2-dev libnghttp2-doc
usr/share/doc/libnghttp2-dev/AUTHORS
W: nghttp2 source:
On 02/01/18 11:55, Axel Beckert wrote:
> Hi Emilio,
>
> Emilio Pozuelo Monfort wrote:
>> On Sat, 30 Dec 2017 04:28:21 +0100 Axel Beckert wrote:
>> This is blocking the ocaml transition, so I may remove approx from testing to
>> unblock the transition.
>
> JFTR: The bug report I
On Tue, 2018-01-02 at 08:47 +0100, Christian Ehrhardt wrote:
> On Fri, Dec 29, 2017 at 3:55 PM, Luca Boccassi
> wrote:
> > On Mon, 2017-12-18 at 07:40 +0100, Christian Ehrhardt wrote:
> > > On Sun, Dec 17, 2017 at 4:48 PM, Luca Boccassi
> > > wrote:
> > > > On
Package: kdepim
Version: 4:16.04.3+5.95
Severity: normal
Dear Sandro, dear Maxy, dear Pino, dear maintainers,
A happy, peaceful and successful new year to you!
Today I tried again to upgrade to KF 5.41 from experimental and aptitude
stumbled over updating some -dev packages I had still
Package: leiningen
Version: 2.8.1-3
Severity: minor
Dear maintainer,
The short description doesn't tell you what Leiningen is for.
'Automate' could mean all sorts of things and the "without setting your
hair on fire" seems unnecesarily promotional.
May I suggest
build and dependency
On Mon, Jan 01, 2018 at 05:09:21PM -0500, Marvin Renich wrote:
> IOW, using pkg-name:amd64 in the log loses information that is harder to
> recover, while using pkg-name:all hides an internal detail of aptitude's
> processing that is trivial to obtain.
I can't argue about aptitudes log, but it
Hi Matt,
Upgrading both dependencies seems to be harder to do it simultaneously,
than your first approach, to do the upgrading in sequence.
I am not experienced with GTK3 and Webkit2Gtk at all, so what I am going to
say may have to be taken with a grain of salt, and may not be workable at
all.
Hi Emilio,
Emilio Pozuelo Monfort wrote:
> On Sat, 30 Dec 2017 04:28:21 +0100 Axel Beckert wrote:
> This is blocking the ocaml transition, so I may remove approx from testing to
> unblock the transition.
JFTR: The bug report I cloned from this bug report (#885822) already
put
On 2017-10-27 17:26, Angel Abad wrote:
> Because there is no official release with these changes, I will
> write upstream developer and I will tell you.
Was there any outcome? TIA!
On Sat, 30 Dec 2017 04:28:21 +0100 Axel Beckert wrote:
> Control: clone -1 -2
> Control: retitle -2 approx: FTBFS with ocaml 4.05.0: Some fatal warnings were
> triggered
> Control: found -2 5.8-1
> Control: fixed -2 5.9-1
> Control: close -2
>
> Hi Ole and Eric,
>
> Ole
Source: klystrack
Version: 0.20171212-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
Hi,
Whilst working on the Reproducible Builds effort [0], we noticed
that klystrack could not be
BTW. I see two GCC8 related fixes in elfutils git since the last
release:
commit 268a27211b152d876185ff95255e5025c43b9c13
Author: Mark Wielaard
Date: Mon Nov 20 14:11:02 2017 +0100
libdwfl: Don't dereference possibly unaligned auxv entry pointer from core.
The
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello Brian,
please can you test the release 120.2.2-3 from unstable?
Many thanks!
CU
Jörg
- --
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N
Package: mutt
Version: 1.9.2-1
Severity: wishlist
At some point in the past (while it was neomutt maybe?) this awesome
'abort_noattach' variable appeared.
I love it, could you please include that thing in the mutt package? :)
TIA!
--
regards,
Mattia Rizzolo
GPG Key:
Source: gcc-8
Version: 7.2.0-18
Severity: normal
User: debian-...@lists.debian.org
Usertags: m68k
Hello!
Please disable gccgo in gcc-8 on m68k, the build currently fails [1]:
go1: internal compiler error: in set_from, at go/gofrontend/types.cc:2569
mmap: Permission denied
Please submit a full
On Tue, Jan 02, 2018 at 10:45:33AM +0100, Mattia Rizzolo wrote:
> On Tue, Jan 02, 2018 at 09:27:47AM +0100, Salvatore Bonaccorso wrote:
> > I've prepared an NMU for libxml2 (versioned as 2.9.4+dfsg1-6.1) and
> > uploaded it to DELAYED/2. Please feel free to tell me if I
> > should delay it longer.
Hi Helmut,
On Tue, 2018-01-02 at 09:42 +0100, Helmut Grohne wrote:
> For example, it FTBFS with gcc-8 atm.
Could you please file a bug for that. I am not aware of any such issue.
So would like to fix it, and would if I knew about it. Thanks.
> Even if that checking was happening in
> practise,
Control: tags -1 fixed-upstream
Control: forwarded -1
https://bazaar.launchpad.net/~foxtrotgps-team/foxtrotgps/trunk/revision/303
On Tue, 2018-01-02 at 10:56 +0800, Paul Wise wrote:
> I've started working on this upstream.
I've implemented this in upstream bzr.
--
bye,
pabs
On Tue, Jan 02, 2018 at 09:27:47AM +0100, Salvatore Bonaccorso wrote:
> I've prepared an NMU for libxml2 (versioned as 2.9.4+dfsg1-6.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.
Usually I consider a bad idea incorporating patches like this that
Hi Stuart,
> +and not $fname =~ m,/_sources/license\.rst(\.txt)?$,o
>
> BTW this should include license.txt too from sphinx before 1.6(ish).
Thanks. Mattia spotted this actually, so we ended up with:
It also looks similar to this bug report:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884116
Package: wnpp
Severity: normal
I am orphaning the oolite package. Upstreams embeds an outdated copy
of a library dependency [α], for sensible reasons summarized at [β].
Building in a way compatible with Debian standards, if even possible,
would require much more efforts than I can afford.
[α]
tags 886101 + pending
thanks
Fixed in Git:
https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=346fca797fef1537a780cea437b27c9c469a56dd
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
Hey Patrick,
When rendering to .webm, kdenlive passes
acodec=vorbis
to melt.
Here's an example
$ /usr/bin/melt /tmp/saved.mlt in=0 out=63 -profile atsc_1080p_25 -consumer
avformat:/home/kingsley/tmp/test.webm f=webm vcodec=libvpx acodec=vorbis crf=23
vb=0 quality=good aq=6
Package: lintian
Version: 2.5.65
Severity: wishlist
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org
Hi,
Please warn about packages that ship Python Python Hypothesis
example files.
These are not useful in the binary package or end-users, and as
they contain andom/non-determinstic
Source: todoman
Version: 3.2.4-3
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: randomness
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
Hi,
Whilst working on the Reproducible Builds effort [0], we noticed
that todoman could not be built
On Mon, Jan 01, 2018 at 06:31:37PM +0100, Mark Wielaard wrote:
> In general we try to catch any compiler errors and build with pre-release
> gcc versions. Please do report any you catch upstream. Thanks.
History shows that this trying is not working in practise. For example,
it FTBFS with gcc-8
> it seems empty directories sometimes get missing in dpkg. Not sure yet
> whether this is a bug and if so, in which package.
I have had more of those recently:
Sample:
/etc/logcheck/ignore.d.paranoid
/etc/logcheck/ignore.d.workstation
/etc/pkcs11
On Mon, Jan 01, 2018 at 03:47:04PM +, Brian Potkin wrote:
> evince can get remote printer information from cups-browsed but, if the
> latter is not running, it browses the Bonjour broadcasts of servers and
> printers directly, just as avahi-browse does.
I cannot confirm the described
Hi,
> IMHO these should emit a tag at at least warning/normal level.
Note to implementor that that we have some very similar wishlist
requests:
#885974 "lintian: warn about non-git Vcs fields"
#886057 "lintian: warn about
orphaned-package-not-maintained-in-debian.org-infrastracture"
Package: src:gcc-7
Version: 7.2.0-18
Please consider backport the patch of PR target/82981.
It fix a problem of link kernel on mips64r6.
[2] said that is also fixes an ICE on arm.
[1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82981
[2]
Control: forwarded -1 https://bugs.launchpad.net/soundconverter/+bug/1740830
On 2018-01-01 17:28:14, Jeremy Bicha wrote:
> Source: soundconverter
> Version: 3.0.0~beta1-2
> Severity: important
> User: pkg-gnome-maintain...@lists.alioth.debian.org
> Usertags: oldlibs gconf
> Tags: sid buster
>
>
On 02/01/18 02:06, jus...@justin.sh wrote:
> I'm running Debian testing on an X1 Carbon 5th gen with the following kernel,
>
>> Linux debian 4.14.0-2-amd64 #1 SMP Debian 4.14.7-1 (2017-12-22) x86_64
>> GNU/Linux
>
> I'm experiencing latency issues with the trackpoint and I came across your
>
❦ 2 janvier 2018 02:02 +0100, Andreas Henriksson :
>> I have removed deps to gnomeui (gconf had already been removed) from Xnee
>> sources.
>
> Vincent, please see the attached debdiff that incorporates Henriks
> change as a patch in debian/patches/ for your convenience.
>
On 01/02/2018 01:15 AM, Josip Rodin wrote:
> All of those changes related to HAVE_COURIER sound like something that
> should be possible to figure out on runtime.
That's exactly what I thought as well and proposed, but upstream
rejected as an additional security risk.
> I still don't see a
I hope you're right, though I didn't get any segfault message in my
dmesg when I tried it just now.
Torbjörn Andersson
Sorry.
here the diff between the original (with OCL_IGNORE_SELF_TEST=1 ) and
without:
achim@data:~$ /usr/lib/x86_64-linux-gnu/beignet/utest_run > /tmp/out3
achim@data:~$ diff /tmp/out /tmp/out3
912,927c912,927
< compiler_time_stamp()tmEvt 0 0 1 tmDiff 23336 14470
< tmEvt 0 0 1 tmDiff 23336
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
severity 873480 important
thanks
this issue is real. downgrading to 3.6.1-4 solves the error at hand.
that patch should be reversed and if needed reimplemented to not break
other stuff.
- --
brother
http://sis.bthstudent.se
-BEGIN PGP
tags 885873 + fixed-upstream
thanks
Merged upstream :)
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
Hi Niels,
Niels Thykier wrote:
> My 2 cents: I do not think we should propose a mass-move until salsa is
> out of the beta. Given that the admins have not commited to not wiping
> the database, nagging people to move seems counter productive
> (especially if a wipe is performed later).
Granted.
201 - 300 of 305 matches
Mail list logo