Hi,
this is already fixed in master branch, see
https://github.com/PhotoFilmStrip/PFS/issues/68.
I'll trigger a new bugfix release...
Thanks,
Jens
Zitat von Clint Adams (So 29 Mär 2020 15:29:49 CEST):
Package: photofilmstrip
Version: 3.7.2-2
Severity: serious
% photofilmstrip
Traceb
Package: wnpp
Severity: wishlist
Subject: ITP: r-bioc-mutationalpatterns -- GNU R comprehensive genome-wide
analysis of mutational processes
Package: wnpp
Owner: Andreas Tille
Severity: wishlist
* Package name: r-bioc-mutationalpatterns
Version : 1.12.0
Upstream Author : Francis
Hello Ximin,
Am 04.04.20 um 02:17 schrieb Ximin Luo:
> Hi Carsten, it might be a couple of weeks until we get this done.
> Have you tried just deleting the version constraint and using the
> existing version in Debian sid?
I've tried to figure out the right place there this version check is
happen
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Hello,
I would like to request a transition slot for schroedinger-maeparser
(experimental -> unstable) due to the changed binary package names.
Current ben tracker [1] is fine.
Affected
Control: reassign -1 src:pandas
Control: found -1 0.25.3+dfsg-8
Control: affects -1 src:python-geotiepoints
On 4/3/20 9:42 PM, Lucas Nussbaum wrote:
>> File "/usr/lib/python3/dist-packages/pandas/util/testing.py", line 18, in
>>
>> from matplotlib.cbook import MatplotlibDeprecationWarning
Package: stunnel4
Version: 3:5.56-1
Severity: normal
--- Please enter the report below this line. ---
There seems to be a race condition in handling child processes in the
test runtime that the script happens to loose on my system reliably.
Loosing in this case means spinning forever when child p
Jörg,
Quoting Gilles Filippini (2020-04-02 23:46:11)
> Johannes Schauer a écrit le 02/04/2020 à 22:57 :
> > Quoting Gilles Filippini (2020-04-02 22:37:42)
> >> The problem occurs in both cases:
> >>
> >> $ $ sudo sbuild-createchroot --make-sbuild-tarball=foo.tar.gz \
> >> --chroot-prefix=foo --k
Hello,
Same problem here, how I could install it?
Processing triggers for initramfs-tools (0.133+deb10u1) ...
update-initramfs: Generating /boot/initrd.img-5.4.0-0.bpo.4-amd64
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module
r8169
Thanks
Hi all,
I agree that rustup should be in Debian. Achieving this is currently blocked on
either of these two issues:
- https://github.com/rust-lang/rustup/issues/835 OR
- https://salsa.debian.org/rust-team/debcargo/-/merge_requests/22
If you want to help, achieving either of these would help to
Hi Carsten, it might be a couple of weeks until we get this done. Have you
tried just deleting the version constraint and using the existing version in
Debian sid?
X
Carsten Schoenert:
> Package: cargo
> Version: 0.40.0-3
> Severity: wishlist
>
> Dear Maintainer,
>
> I'm working on packaging
Control: severity -1 normal
On Sun, Mar 22, 2020 at 02:57:54PM +0100, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
> Relevant part (hopefully):
> [...]
> > Trailer-Test: f
> > 140691743627136:error:14095126:SSL routines:ssl3_read_n:un
Package: initramfs-tools
Version: 0.133+deb10u1
Severity: important
Dear Maintainer,
* What led up to the situation?
1. A single Btrfs rootfs on the top of lvm is converted to a raid 1 array by
adding a device (logical volume in this case) and running a Btrfs balance
convert start.
2. # upd
Package: libopenmpi3
Version: 4.0.3-1
Severity: important
Hi
I just found on **two** computers the same file, with completely wrong
file name character encoding:
$ cd /usr/lib/x86_64-linux-gnu
$ ls -l
'R'$'\361''9P'$'\f''*'$'\022\204''P'$'\005\260''"'$'\201\202''@'$'\233'':'$'\231''P'$'\002\f\n
Control: forwarded -1 https://github.com/EionRobb/purple-discord/issues/288
Control: tags -1 upstream
On Fri, 2020-04-03 at 18:49 +0200, Samuel Thibault wrote:
> It seems that somehow discord_socket_got_data passes an improper
> connection, I used the attached browntape patch in pidgin to at leas
Hi Jelmer,
> > Given that debhelper (now?) treats this as a fatal error, ie:
> >
> > dh: error: The debhelper-compat build-dependency must be in the
> > Build-Depends field (not build-depends-indep)
> >
> > A warning from Lintian would not be very practical. Would you concur?
> >
> Yes,
Package: debian-edu-config
Severity: wishlist
Currently (during the bullseye release cycle), chromium uses Google as
the default search provider.
With the below snippet dropped into
/etc/chromium/policies/managed/.json we could switch that to
DuckDuckGo:
{
"DefaultSearchProviderEnable
Dear Maintainer,
I rebuilt the kernel with KMEMLEAK and KASAN enabled to gather more information.
kmemleak did find some memleaks. After disabling and clearing kmemleak to
reclaim the memory however only a fraction of the expected memory was freed up.
After booting with kmemleak and kasan (no me
On 2020/04/03 21:24, Louis-Philippe Véronneau wrote:
> I was wondering if there was any progress on this ITP. Foliate looks
> nice and there is surprisingly few epub readers in Debian at the moment.
>
ftpmaster had some minor issue with the package and I just haven't had
time again to upload a new
Package: sponsorship-requests
Severity: normal
[[ Dear Andrew Pollock, as state in my mail from 2020-03-22, I am now
looking for a sponsor. Still, give the word and I'll stop. Thanks! ]]
Dear mentors,
I am looking for a sponsor ("-EviIL +pedantic", please) for the package
"sieve-connect"
* P
Package: wnpp
Severity: wishlist
Subject: ITP: r-cran-grimport2 -- GNU R importing 'SVG' graphics
Package: wnpp
Owner: Andreas Tille
Severity: wishlist
* Package name: r-cran-grimport2
Version : 0.2
Upstream Author : Simon Potter, Paul Murrell
* URL : https://cran.r-p
Package: debian-edu-config
Hi,
I wonder if we should pre-configure GNOME's http proxy settings as
well via Debian Edu via update-proxy-from-wpad.
I found a script that could be used as a knowledgebase for how to do
that (via gsettings):
https://github.com/himanshub16/ProxyMan/blob/master/
Below is why I was thinking $SHELL, especially since $FAKE_SHELL can
be used to override the /etc/passwd entry. Of course a desktop
environment or whatever might launch a terminal window without having
gone through login, although I imagine some logic in the display
manger should replicate login's
Package: wnpp
Severity: wishlist
Subject: ITP: r-cran-gridsvg -- GNU R export 'grid' graphics as SVG
Package: wnpp
Owner: Andreas Tille
Severity: wishlist
* Package name: r-cran-gridsvg
Version : 1.7
Upstream Author : Paul Murrell, Simon Potter
* URL : https://cran.r-
Hi Barak,
Barak A. Pearlmutter wrote:
> As a work-around, you can right click -> Preferences and change the
> shell going forward.
Yeah, found that already. But thanks!
> Obviously it's an upstream issue, so I'll raise it there.
Thanks. Also already checked if there is an issue for that upstrea
On Fri, 3 Apr 2020 23:28:04 +0200 Stephen Kitt wrote:
> On Fri, 3 Apr 2020 21:45:28 +0200, Lucas Nussbaum wrote:
> > During a rebuild of all packages in sid, your package failed to build
> > on amd64.
> >
> > Relevant part (hopefully):
> > > checking for amd64-w64-mingw32-gcc... no
> > > checkin
Package: wnpp
Severity: normal
I intend to orphan the python-tablib package. Indeed, it's not used in
OpenStack anymore, which was the only reason to keep it in Debian.
The package description is:
Tablib is a format agnostic tabular dataset library, written in Python. It
allows you to import, e
On 4/3/20 9:55 PM, Lucas Nussbaum wrote:
> Source: python-tablib
> Version: 0.13.0-1
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20200402 ftbfs-bullseye
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd6
Thanks for picking up this issue.
As a work-around, you can right click -> Preferences and change the
shell going forward.
But I agree it should default properly.
Obviously it's an upstream issue, so I'll raise it there.
But I'd think to the value of $SHELL (which is set by login to the
entry in /
On Fri, 3 Apr 2020 21:45:28 +0200, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
> Relevant part (hopefully):
> > checking for amd64-w64-mingw32-gcc... no
> > checking for x86_64-mingw32msvc-gcc... no
> > checking for amd64-mingw32msvc
Source: krb5
Version: 1.17-7
Severity: important
Tags: patch
User: debian-h...@lists.debian.org
Usertags: hurd
HI,
krb5 currently FTBFS on GNU/Hurd due to a missing MAXHOSTNAMELEN
definition. The attached patch fixes the build problem on GNU/Hurd by
adding a definition of MAXHOSTNAMELEN to src/li
---
debian/control | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/debian/control b/debian/control
index 5487a85..06e9241 100644
--- a/debian/control
+++ b/debian/control
@@ -2,7 +2,7 @@ Source: dbacl
Section: text
Priority: optional
Build-Depends: debhelper-compat (= 12),
-
On 2020-04-03 22:39:20 +0200, Tino Mettler wrote:
> Package: libdvdread7
> Version: 6.1.0-1
> Followup-For: Bug #955367
>
> Hi,
>
> as mentioned in the above videolan bug tracker, the crash can be fixed by
> just rebuilding libdvdnav against libdvdread7. No changes to the package
> are needed.
Package: libdvdread7
Version: 6.1.0-1
Followup-For: Bug #955367
Hi,
as mentioned in the above videolan bug tracker, the crash can be fixed by
just rebuilding libdvdnav against libdvdread7. No changes to the package
are needed. The build-dependency should be adjusted for correctness, though.
Re
Source: haskell-brick
Version: 0.46-2
Severity: serious
Control: fixed -1 0.47.1-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and
Source: lldpd
Version: 1.0.4-1
Severity: serious
Control: fixed -1 1.0.5-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "kcheckers"
* Package name: kcheckers
Version : 0.8.1-5
Upstream Author : Andi Peredri
Artur Wiebe
* URL : http://qcheckers.sourceforge.ne
Package: procps
Version: 2:3.3.16-4
Severity: normal
Tags: patch
Dear Maintainer,
pgrep reports that it cannot allocate 4611686018427387903 bytes when
it is run on current kernels. This is due to a change in the
sysconf(SC_ARG_MAX) value reported by the kernel that causes pgrep to
try to allocat
reopen 954620
thanks
On 22/03/20 at 14:21 +0100, Lucas Nussbaum wrote:
> Hi,
>
> I'm closing those bugs: those failures are no longer reproducible,
> checking again 12 hours later. Either they were caused by another
> package that was fixed in the meantime, or they are random failures.
This is a
Source: freeboard
Version: 1.1.0+dfsg.1-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules binar
Source: wala
Version: 1.5.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_a
Hi Graham,
On 3 April 2020 at 21:32, Graham Inggs wrote:
| Hi Dirk
|
| On Fri, 3 Apr 2020 at 20:27, Dirk Eddelbuettel wrote:
| > I am still (as always) lost by the process. Does that mean an upload to
| > unstable is now ok? Or not? I am unsure what "hand shake" from the ftp /
| > release te
Source: anet
Version: 0.4.2-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> /usr
Source: wine-development
Version: 5.5-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> checking for amd64-w64-mingw32
Source: ruby-fakeredis
Version: 0.7.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> ArgumentError:
>i
Source: dh-ada-library
Version: 6.19
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
Source: python-pymeasure
Version: 0.5-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/
Source: golang-github-vbatts-go-mtree
Version: 0.4.4-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules b
Source: pcscada
Version: 0.7.5-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> d
Source: haskell-gi-pango
Version: 1.0.19-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> test
reopen 954645
thanks
> I'm closing those bugs: those failures are no longer reproducible,
> checking again 12 hours later. Either they were caused by another
> package that was fixed in the meantime, or they are random failures.
Actually, this is reproducible.
Lucas
Source: python-geotiepoints
Version: 1.1.8-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> dh
Source: libcatmandu-filestore-perl
Version: 1.13-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> dpkg-buildpackage
>
Source: cinnamon-control-center
Version: 4.4.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> checking for LIBNMA_1
Source: libncursesada
Version: 6.1.20180127-5
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> checking for unistd.h...
Source: expeyes
Version: 4.7.6+repack-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[4]: Entering directory '/
Source: ruby-mail-room
Version: 0.10.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> Failure/Error:
> expect
Source: libtexttools
Version: 2.1.0-16
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/<
Source: birdfont
Version: 2.28.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
>
Source: wacomtablet
Version: 3.2.0-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory
> '/
Source: libflorist
Version: 2017-7
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/<>'
>
Source: node-tippex
Version: 3.0.0+ds-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> +-
Source: adabrowse
Version: 4.0.3-12
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
Source: lemonldap-ng
Version: 2.0.7+ds-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory '
Source: python-biom-format
Version: 2.1.8+dfsg-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering dir
Source: pangox-compat
Version: 0.0.2-5
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> /bin/bash ./libtool --tag=CC
Source: txtorcon
Version: 19.0.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
>
Source: ruby-slim
Version: 4.0.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> LoadError: cannot load such file --
Source: libgaminggear
Version: 0.15.1-9
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> cd /<>/obj-x86_64-linux-gnu/li
Source: libinput
Version: 1.15.4-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
>
Source: drms
Version: 0.5.7-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> dh build --with py
Source: python-apptools
Version: 4.5.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '
Source: influxdb-python
Version: 5.2.3-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> dh buil
Source: nordugrid-arc
Version: 6.5.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[7]: Entering directory '/<
Source: ofxstatement-plugins
Version: 20191114
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering direc
Source: dbusada
Version: 0.5.0-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> i
Source: mender-client
Version: 2.2.0-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<
Source: ufo2ft
Version: 2.12.2-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> d
Source: libalog
Version: 0.6.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> d
Source: adacgi
Version: 1.6-24
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> gpr
Source: rdkit
Version: 201909.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/<>/bui
Source: liblog4ada
Version: 1.3.1.b6dafb49-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directo
Source: ahven
Version: 2.7-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[3]: Entering directory '/<>/obj-dyna
Source: seqsero
Version: 1.0.1+dfsg-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> +---
Source: libxmlezout
Version: 1.06.2-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/<>
Source: python-tablib
Version: 0.13.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/
Source: tripwire
Version: 2.4.3.7-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[4]: Entering directory '/<>'
Source: python-peakutils
Version: 1.3.3+ds-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> dh
Source: dvdbackup
Version: 0.4.2-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I. -I.. -Wda
Source: diffoscope
Version: 138
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> +-
Source: python-cobra
Version: 0.14.2-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> dh build
Source: pynwb
Version: 1.2.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> dh build --with p
Package: src:gcc-9
Followup-For: Bug #954681
Control: reopen -1
Hello.
The initial symptom is cured, but the fix lets
debian/patches/ada-lib-info-source-date-epoch.diff modify
gcc/ada/libgnat/s-os_lib.ad[bs].
This invalidates the checksums embedded in the .ali files of
libgnat-9, causing a failu
Source: qevercloud
Version: 3.0.3+ds-5
Severity: serious
Tags: ftbfs
This essentially is a duplicate of #921297. That bug was reassigned to
texlive-latex-extra and it was resolved by having texlive-latex-extra
now recommend texlive-plain-generic. However, Build-Depends don't care
for Recommends. T
Source: libretro-desmume
Version: 0.9.11+git20160819+dfsg1-2
Severity: important
Tags: ftbfs patch upstream
libretro-desmume fails to build from source for mipsen architecture,
because it misses an #include for struct timeval. Please consider
applying the attached patch.
Helmut
--- libretro-desmu
Source: r-cran-uwot
Version: 0.1.8-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of r-cran-uwot the autopkgtest of r-cran-uwot fails
in testing when that autopkgtest is run with the binar
Hi Alex,
On Fri, Apr 03, 2020 at 05:21:57PM +0100, Alex Dewar wrote:
> Maybe try patching configure.ac so it looks for opencv4 rather than
> opencv. I'd like to also address this in my PR, only I'm not sure how to
> get autotools to look for opencv4 OR opencv without failing... Any ideas?
Please
Source: rss-bridge
Version: 2020-02-26+dfsg1-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of rss-bridge the autopkgtest of rss-bridge fails
in testing when that autopkgtest is run with t
Hi Dirk
On Fri, 3 Apr 2020 at 20:27, Dirk Eddelbuettel wrote:
> I am still (as always) lost by the process. Does that mean an upload to
> unstable is now ok? Or not? I am unsure what "hand shake" from the ftp /
> release team I should be waiting for.
Please not yet. Once r-base is uploaded to
Hi!
I was wondering if there was any progress on this ITP. Foliate looks
nice and there is surprisingly few epub readers in Debian at the moment.
I see you started to package this here:
https://salsa.debian.org/debian/foliate/
README.Debian mentions:
> The upstream tarball has been repacked to
Package: cargo
Version: 0.40.0-3
Severity: wishlist
Dear Maintainer,
I'm working on packaging current beta versions of Thunderbird for
experimental.
This is requiring a cargo version >= 1.41 (cargo --version).
Could you please consider to package the most recent version at least
for experimental?
1 - 100 of 201 matches
Mail list logo
