Control: severity 920695 important
On Thu 2019-02-28 22:06:09 -0500, Daniel Kahn Gillmor wrote:
> So i'm marking #920695 as fixed in 3.2.1-1 with the hope of getting all
> of these migrations to move forward.
I've tagged the shared git repo for both knot-dns and for knot-resolver
source package
Processing control commands:
> severity 920695 important
Bug #920695 [src:knot-resolver] knot-resolver: uninstallable and FTBFS in
stretch-backports
Severity set to 'important' from 'serious'
--
920695: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920695
Debian Bug Tracking System
Contact
Processing commands for cont...@bugs.debian.org:
> fixed 920695 3.2.1-1
Bug #920695 [src:knot-resolver] knot-resolver: uninstallable and FTBFS in
stretch-backports
Marked as fixed in versions knot-resolver/3.2.1-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Control: 920695 fixed 3.2.1-1
I'm able to rebuild knot-resolver just fine on stretch, when i build
3.2.1-1 against a backported knot 2.7.6-2. I'll be uploading those to
stretch-backports shortly, but they can't go in until they've reached
testing.
But knot won't go into testing untlik
Hi Steve,
Moritz Mühlenhoff (2019-02-26):
> On Fri, Feb 15, 2019 at 07:28:57PM +0100, Cyril Brulebois wrote:
> > Right, this also breaks the build of the debian-installer source package
> > on amd64 since its build dependencies cannot be satisfied.
>
> Is there an ETA for a fix?
We're getting
Your message dated Fri, 01 Mar 2019 01:49:15 +
with message-id
and subject line Bug#922773: fixed in adequate 0.15.2
has caused the Debian Bug report #922773,
regarding FTBFS since the acl/attr uploads of 2019-05-15+16
to be marked as done.
This means that you claim that the problem has been
tags 923365 - moreinfo
close 923365
thanks
Big oops! Sorry, I have now double-checked and the report was based on
a build log dated 2019-02-26, but apparently it took a while for me to
actually submit the bug. The underlying bug in texlive was fixed in
the meantime.
The package is sunny
Processing commands for cont...@bugs.debian.org:
> tags 923365 - moreinfo
Bug #923365 [src:ftgl] ftgl: FTBFS in sid (LaTeX error)
Removed tag(s) moreinfo.
> close 923365
Bug #923365 [src:ftgl] ftgl: FTBFS in sid (LaTeX error)
Marked Bug as done
> thanks
Stopping processing here.
Please contact
Processing commands for cont...@bugs.debian.org:
> tags 922773 + pending
Bug #922773 [src:adequate] FTBFS since the acl/attr uploads of 2019-05-15+16
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
922773:
Processing control commands:
> block 922004 by -1
Bug #922004 [release.debian.org] transition: clamav
922004 was not blocked by any bugs.
922004 was not blocking any bugs.
Added blocking bug(s) of 922004: 923498
--
922004: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922004
923498:
Source: cyrus-imapd
Version: 3.0.8-3
Severity: Serious
Control: block 922004 by -1
By the time we planned the transition for libclamav there was no
cyrus-imapd package which depended on libclamav-dev but this changed. I
just realised that.
The package failed to build because the ABI on clamav's
On 28/02/19 16:44, Thorsten Glaser wrote:
please do consider uploading 4.19.24 to buster/sid with some haste.
We have headless virtualisation hosts being unreachable/frozen now,
and while these are “only” development systems, this is untenable.
Like you I'm looking forward for that kernel.
On Thu, 28 Feb 2019 at 21:28:47 +0100, Mattia Rizzolo wrote:
> There shouldn't be debs in Files but not in Binaries. Which packages are
> missing there?
The test that I added using Salvatore's .changes file says the -dbgsym
packages aren't listed in Binary:
Warning: hyperv-daemons-dbgsym not
> Am 27.02.2019 um 22:31 schrieb Paul Thomas :
>
> OK, a couple of updates.
>
> First, I tracked down line ptp4l call that starts this off, it's the
> ioctl(fd, SIOCSHWTSTAMP, ); line 88 in sk.c. I can see if a
> standalone program that just does that ioctl has the same affect.
>
> Second, I
Your message dated Thu, 28 Feb 2019 21:03:39 +
with message-id
and subject line Bug#920269: fixed in groff 1.22.4-3
has caused the Debian Bug report #920269,
regarding groff: gropdf can execute arbitrary commands
to be marked as done.
This means that you claim that the problem has been dealt
On Thu, Feb 28, 2019 at 20:10:46 +0100, Sébastien Villemot wrote:
> If you don't have the time to do the upload today, I will do it
> tomorrow.
>
> Note that you'll have to create a new git branch, named "buster",
> branching off at 4.4.1-4, since master already contains 5.1.0.
I've done exactly
Processing control commands:
> tag -1 pending
Bug #923442 [src:octave] octave: FTBFS (/bin/sed: can't read
libinterp/parse-tree/oct-parse.cc-t: No such file or directory)
Added tag(s) pending.
--
923442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923442
Debian Bug Tracking System
Control: tag -1 pending
Hello,
Bug #923442 in octave 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:
Your message dated Thu, 28 Feb 2019 19:54:59 +
with message-id
and subject line Bug#919344: fixed in openssh 1:7.9p1-8
has caused the Debian Bug report #919344,
regarding adequate reports obsolete-conffile in openssh-client
to be marked as done.
This means that you claim that the problem has
Processing control commands:
> retitle -1 mergechanges: Regression: --indep/source breaks multi-line Binary
> fields
Bug #923427 [devscripts] mergechanges: Regression: --indep/source
mangles/breaks (valid?) Binary fields
Changed Bug title to 'mergechanges: Regression: --indep/source breaks
Control: retitle -1 mergechanges: Regression: --indep/source breaks multi-line
Binary fields
Control: forwarded -1
https://salsa.debian.org/debian/devscripts/merge_requests/112
Control: tags -1 + patch
On Thu, 28 Feb 2019 at 17:59:25 +, Simon McVittie wrote:
> I'll try to put together some
Package: alpine
Version: 2.21+dfsg1-1.1
Severity: serious
If I take a message, reply to it, then go to the Subject line,
press ^K to remove the existing (possibly damaged) text and type
new text (possibly to change the subthread subject), the eMail
gets sent out AND Fcc’d without both In-Reply-To
Control: tag -1 pending
Hello,
Bug #920269 in groff 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:
Processing control commands:
> tag -1 pending
Bug #920269 [groff] groff: gropdf can execute arbitrary commands
Added tag(s) pending.
--
920269: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920269
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Hi Markus!
On Thu, Feb 28, 2019 at 08:27:11PM +0100, Markus Frosch wrote:
> thanks I just did so, and uploaded a new version.
yay, very cool!
> During testing I noticed the "refactoring" patch actually broke logging,
> and therefor reposync working.
ouch, sorry.
> I fixed it with an
Am 22.02.19 um 10:26 schrieb Holger Levsen:
> please adopt yum-utils and get the changes from experiemental into
> sid/buster before the freeze is fully in effect. You still have almost a
> week to do that! ;)
>
> Also if you do that, please dont forget to include the changes from my
> NMU.
>
>
The problem here is the API compatibility break in glslang, described in
https://github.com/KhronosGroup/glslang/issues/1538#issuecomment-431643795
Changes related to the new glslang version seem to be bundled in
https://github.com/baldurk/renderdoc/commit/2ea6174c83c3c55f504c107303991d9bb2aa9af3
Le jeudi 28 février 2019 à 09:53 -0800, Mike Miller a écrit :
> Control: tags -1 + patch
>
> On Thu, Feb 28, 2019 at 10:08:33 +, Santiago Vila wrote:
> > I tried to build this package in buster but it failed:
>
> […]
> > /bin/sed: can't read libinterp/corefcn/oct-tex-parser.cc-t: No such
> >
Control: tag -1 pending
Hello,
Bug #919344 in openssh 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:
Processing control commands:
> tag -1 pending
Bug #919344 [openssh-client] adequate reports obsolete-conffile in
openssh-client
Added tag(s) pending.
--
919344: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919344
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
On Tue, Feb 26, 2019 at 11:57:00PM +0100, Dominik George wrote:
> How about the attached approach?
>
> It uses dpkg-maintscript-helper in openssh-client to remove the
> conffile. dpkg-maintscript=helper does all the magic to determine
> whether the file was changed by the user. Here, we use the
Your message dated Thu, 28 Feb 2019 19:06:59 +
with message-id
and subject line Bug#923223: fixed in libxml-parser-perl 2.44-4
has caused the Debian Bug report #923223,
regarding XML::Parser::parsefile() uses 2-argument open
to be marked as done.
This means that you claim that the problem
The actual error message is
"""
CMake Error at CMakeLists.txt:298 (message):
MPIIO package needs LAMMPS to be build with MPI
Call Stack (most recent call first):
CMakeLists.txt:304 (pkg_depends)
"""
It seems to mean MPI is not found. After removing QUIET from
find_package(MPI):
-- Found
Processing commands for cont...@bugs.debian.org:
> tags 903698 + buster-ignore
Bug #903698 [dh-python] sphinxbase: build appears broken for multiple python3
versions
Added tag(s) buster-ignore.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
903698:
Processing control commands:
> tags -1 + moreinfo
Bug #923365 [src:ftgl] ftgl: FTBFS in sid (LaTeX error)
Added tag(s) moreinfo.
--
923365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923365
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 + moreinfo
Hi Santiago!
2019-02-26 23:28 Santiago Vila:
Package: src:ftgl
Version: 2.4.0-2
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in sid but it failed:
(Yes, I know that it built ok 4 hours ago, but apparently not anymore)
Your message dated Thu, 28 Feb 2019 18:19:38 +
with message-id
and subject line Bug#922960: fixed in capstone 4.0.1+really+3.0.5-1
has caused the Debian Bug report #922960,
regarding new libcapstone-dev pkg-config does not provide include path, breaks
compatibility
to be marked as done.
On Thu, Feb 28, 2019 at 05:59:25PM +, Simon McVittie wrote:
> For now, is it OK to make mergechanges use a perl one-liner involving
> Dpkg::Control to do the heavy lifting?
yes
> For the future, do the devscripts maintainers have a preference for the
> implementation language of a
On Thu, Feb 28, 2019 at 11:50:04AM +0100, Xavier wrote:
> Patch is ready in salsa repo:
>
> if (ref $file or $file eq '-') {
> open(FILE, $file) or croak "Couldn't open $file:\n$!";
> } else {
> open(FILE, '<', $file) or croak "Couldn't open $file:\n$!";
> }
>
>
On Thu, 28 Feb 2019 at 17:03:44 +0100, Mattia Rizzolo wrote:
> If I see this correctly, it's all because the code reads only the first
> line of the Binary field, without considering it may be a multiline
> field (and tbh I didn't even realized it could be…)
I must admit I hadn't realised there
Control: tags -1 + patch
On Thu, Feb 28, 2019 at 10:08:33 +, Santiago Vila wrote:
> I tried to build this package in buster but it failed:
[…]
> /bin/sed: can't read libinterp/corefcn/oct-tex-parser.cc-t: No such file or
> directory
Confirmed separately in upstream Octave development, this
Processing control commands:
> tags -1 + patch
Bug #923442 [src:octave] octave: FTBFS (/bin/sed: can't read
libinterp/parse-tree/oct-parse.cc-t: No such file or directory)
Added tag(s) patch.
--
923442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923442
Debian Bug Tracking System
Contact
Processing commands for cont...@bugs.debian.org:
> retitle 923467 libvigraimpex: FTBFS (Could not import extension
> sphinx.ext.pngmath)
Bug #923467 [src:libvigraimpex] libvigraimpex: FTBFS (Could not import
extension sphinx.ext.pngmathCould not import extension sphinx.ext.pngmath)
Changed Bug
Processing control commands:
> forwarded -1 https://github.com/ukoethe/vigra/issues/462
Bug #923467 [src:libvigraimpex] libvigraimpex: FTBFS (Could not import
extension sphinx.ext.pngmathCould not import extension sphinx.ext.pngmath)
Set Bug forwarded-to-address to
Control: forwarded -1 https://github.com/ukoethe/vigra/issues/462
On 2019-02-28 Santiago Vila wrote:
> Package: src:libvigraimpex
> Version: 1.10.0+git20160211.167be93+dfsg1-1
> Severity: serious
> Tags: ftbfs
> Dear maintainer:
> I tried to build this package in buster but it failed:
> [...]
Your message dated Thu, 28 Feb 2019 17:37:18 +
with message-id
and subject line Bug#923013: fixed in xen 4.11.1+26-g87f51bf366-3
has caused the Debian Bug report #923013,
regarding xen: FTBFS when built with dpkg-buildpackage -A
to be marked as done.
This means that you claim that the
I had this message after I removed libfreecad-python2-0.17 which was
preventing my updated freecad from running properly
I then did
apt-get install freecad-python3
I got the message
Setting up python3-pyside2.qtopengl (5.11.2-3) ...
Setting up libfreecad-python3-0.18 (0.18~pre1+dfsg1-4) ...
Version: 2~c2
c-t-b-mipsen now built.
Your message dated Thu, 28 Feb 2019 18:13:47 +0100
with message-id <91459d68-7e96-16c8-7867-7dcbb4699...@debian.org>
and subject line c-t-b-mipsen now built
has caused the Debian Bug report #921421,
regarding gcc-8-cross-mipsen: FTBFS in sid (Version in Debian Archive >=
Version in
Processing commands for cont...@bugs.debian.org:
> tags 923330 - pending
Bug #923330 [jajuk] jajuk: Fails to start with Java Runtime Environment 1.7
minimum required. You use a JVM ext.JVM@23fc625e
Removed tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need
Hi Scott,
On Tue, 15 Jan 2019 11:03:33 + Scott Kitterman
wrote:
> I think rebuilding the rdepends is a reasonable next step. I'll try
> that and see if anything is affected.
Did you get around to do this?
Paul
signature.asc
Description: OpenPGP digital signature
Package: src:libbpp-core
Version: 2.4.1-2
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-arch
dh build-arch
Hi GNOME maintainers,
On Sun, 23 Sep 2018 10:35:50 + Santiago Vila wrote:
> I'm reporting this as serious because it happens on the buildds:
>
>
https://buildd.debian.org/status/fetch.php?pkg=gnome-keyring=s390x=3.28.2-1=1526387132=0
Any progress on this? We are nearing the full freeze.
Hi Libvirt maintainers,
On Sun, 23 Sep 2018 10:35:52 + Santiago Vila wrote:
> I'm reporting this as serious because it happens on the buildds:
>
>
https://buildd.debian.org/status/fetch.php?pkg=gtk-vnc=amd64=0.6.0-3=1486745781=0
Any progress on this? We are nearing the full freeze.
Paul
Source: exiv2
Version: 0.26-1
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://github.com/Exiv2/exiv2/issues/712
Hi,
The following vulnerability was published for exiv2.
CVE-2019-9144[0]:
| An issue was discovered in Exiv2 0.27. There is infinite
Source: exiv2
Version: 0.26-1
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://github.com/Exiv2/exiv2/issues/711
Hi,
The following vulnerability was published for exiv2.
CVE-2019-9143[0]:
| An issue was discovered in Exiv2 0.27. There is infinite
Your message dated Thu, 28 Feb 2019 16:20:06 +
with message-id
and subject line Bug#921291: fixed in openhft-chronicle-bytes 1.1.15-2
has caused the Debian Bug report #921291,
regarding openhft-chronicle-bytes: FTBFS on i386
to be marked as done.
This means that you claim that the problem
The problem here is the weak declaration:
$ eu-readelf --symbols=.dynsym /lib64/libcap-ng.so.0.0.0 | grep pthread_atfork
28: 0 NOTYPE WEAK DEFAULTUNDEF pthread_atfork
In the Fedora 29 build, the constructor looks like this:
Dump of assembler code for function
Processing commands for cont...@bugs.debian.org:
> unarchive 904808
Bug #904808 {Done: Pierre Chifflier } [libcap-ng0]
libcap-ng0: libcap-ng's use of pthread_atfork causes segfaults
Bug #914565 {Done: Pierre Chifflier } [libcap-ng0]
php7.3-intl: Segfaults after apache2 graceful restart
Bug
Hi,
On Thu, Feb 28, 2019 at 07:38:36AM +0100, Salvatore Bonaccorso wrote:
> I had prepared an upload where I issued mergechanges --indep on the
> _amd64.changes to produce a changes to include only source packages
> and architecture-independent packages.
>
> $ mergechanges --indep -f
On Thu, Feb 28, 2019 at 12:06:18PM +, Dmitry Bogatov wrote:
>
> [2019-02-27 21:20] Niko Tyni
> > > - update perl to build-depend on libgdbm-dev (>= 1.18-2) and Break
> > > older versions of libmarc-charset-perl (and any other perl packages
> > > bundling GDBM or NDBM databases)
> > >
>
Your message dated Thu, 28 Feb 2019 15:49:55 +
with message-id
and subject line Bug#923420: fixed in coreutils 8.30-3
has caused the Debian Bug report #923420,
regarding coreutils: mv broken when file system doesn't support RENAME_NOREPLACE
to be marked as done.
This means that you claim
Your message dated Thu, 28 Feb 2019 15:49:55 +
with message-id
and subject line Bug#923420: fixed in coreutils 8.30-3
has caused the Debian Bug report #923420,
regarding zfs-dkms 0.7.12-4 postinstall failed
to be marked as done.
This means that you claim that the problem has been dealt with.
Hi Debian Linux kernel maintainers,
On Wed, 27 Feb 2019, Dragan Milenkovic wrote:
> > Hello Dragan, do you know if the patch was eventually included upstream and
> > possibly in which version?
>
> Hello, Cesare. It was included in 4.20.11 and 4.19.24.
please do consider uploading 4.19.24 to
Processing commands for cont...@bugs.debian.org:
> reassign 923462 coreutils
Bug #923462 [zfs-dkms] zfs-dkms 0.7.12-4 postinstall failed
Bug reassigned from package 'zfs-dkms' to 'coreutils'.
No longer marked as found in versions zfs-linux/0.7.12-4.
Ignoring request to alter fixed versions of bug
Processing commands for cont...@bugs.debian.org:
> reassign 923420 coreutils
Bug #923420 [coreutils] coreutils: mv broken when file system doesn't support
RENAME_NOREPLACE
Ignoring request to reassign bug #923420 to the same package
> forcemerge 923420 923462
Bug #923420 [coreutils] coreutils:
Processing control commands:
> forcemerge 923420 -1
Bug #923420 [coreutils] coreutils: mv broken when file system doesn't support
RENAME_NOREPLACE
Unable to merge bugs because:
package of #923462 is 'zfs-dkms' not 'coreutils'
Failed to forcibly merge 923420: Did not alter merged bugs.
--
Package: src:libvigraimpex
Version: 1.10.0+git20160211.167be93+dfsg1-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
make:
Hi Michael, all,
On Fri, 18 Aug 2017 21:02:21 +0800 zaoqi wrote:
> Segmentation fault
Can you please update us on the status of the two RC bugs that are filed
against synaptic? Has there been any progress? Do you believe that this
is still happening? Do these bugs actually have the same root
Package: src:lammps
Version: 0~20181211.gitad1b1897d+dfsg1-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep
Your message dated Thu, 28 Feb 2019 14:59:57 +
with message-id
and subject line Bug#923456: fixed in llvm-toolchain-7 1:7.0.1-8
has caused the Debian Bug report #923456,
regarding llvm-toolchain-7: clang(|++-$VERSION) segfault in two autopkgtests
to be marked as done.
This means that you
Your message dated Thu, 28 Feb 2019 14:52:06 +
with message-id
and subject line Bug#923445: fixed in ghc 8.4.4+dfsg1-2
has caused the Debian Bug report #923445,
regarding ghc: FTBFS (The 'ghc-flag' directive is already registered to domain
std)
to be marked as done.
This means that you
Processing commands for cont...@bugs.debian.org:
> fixed 919869 4.1.0-2
Bug #919869 {Done: Thomas Andrejak } [prelude-lml]
prelude-lml: purging prelude-lml deletes /etc/prelude-lml/ruleset/*.rules owned
by prelude-lml-rules
Marked as fixed in versions prelude-lml/4.1.0-2.
> thanks
Stopping
Processing commands for cont...@bugs.debian.org:
> severity 903828 grave
Bug #903828 [src:accountsservice] accountsservice: CVE-2018-14036: insufficient
path check in user_change_icon_file_authorized_cb() in user.c
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.
Package: freecad
Version: 0.18~pre1+dfsg1-4
Severity: grave
Dear Maintainer,
I have been using freecad for several months. Today, after upgrading
the system, it has stop working. I get the following message on the
terminal:
~$ freecad
FreeCAD 0.18, Libs: 0.18R
© Juergen Riegel, Werner Mayer,
Processing control commands:
> found 919953 1.0~beta20-1
Bug #919953 [dune] /usr/bin/dune and `dune' binary package should refer to
dune-common
Marked as found in versions dune/1.0~beta20-1.
> severity 919953 important
Bug #919953 [dune] /usr/bin/dune and `dune' binary package should refer to
Control: found 919953 1.0~beta20-1
Control: severity 919953 important
On Sun, 20 Jan 2019 22:19:01 + Ian Jackson
wrote:
> According to Debian policy file conflicts should be resolved by no-one
> using the conflicting name. This applies to /usr/bin/dune.
>
> Additionally, the only referent
Your message dated Thu, 28 Feb 2019 14:12:14 +
with message-id
and subject line Bug#917491: fixed in debian-installer-netboot-images 20190118
has caused the Debian Bug report #917491,
regarding debian-installer-netboot-images: FTBFS (BAD signature from "Debian
Archive Automatic Signing Key
Your message dated Thu, 28 Feb 2019 13:49:46 +
with message-id
and subject line Bug#919247: fixed in kthresher 1.4.0-1
has caused the Debian Bug report #919247,
regarding kthresher: cronjob exits with error after package removal
to be marked as done.
This means that you claim that the
> The build was made in my autobuilder with "dpkg-buildpackage -A"
Sorry, I meant "dpkg-buildpackage -B" here, as the package does not
create any arch-indep packages.
Thanks.
Hello
Le 28/02/2019 à 13:38, Paul Gevers a écrit :
Source: llvm-toolchain-7
Version: 1:7.0.1-7
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression
Dear maintainers,
With a recent upload of llvm-toolchain-7 the autopkgtest of
Package: src:libbpp-phyl
Version: 2.4.1-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-arch
dh build-arch
Source: llvm-toolchain-7
Version: 1:7.0.1-7
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression
Dear maintainers,
With a recent upload of llvm-toolchain-7 the autopkgtest of
llvm-toolchain-7 and clazy fail in testing when that
Package: src:renderdoc
Version: 1.2+dfsg-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-arch
dh build-arch --buildsystem cmake
Package: src:metview
Version: 5.3.0-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep --buildsystem=cmake
[2019-02-27 21:20] Niko Tyni
> > - update perl to build-depend on libgdbm-dev (>= 1.18-2) and Break
> > older versions of libmarc-charset-perl (and any other perl packages
> > bundling GDBM or NDBM databases)
> >
> > - update libmarc-charset-perl (and any other perl packages bundling
> >
Hey,
> Looks like this has never been in the core package:
I mentioned that, too. But I printend the command that fails:
/usr/bin/mysql_install_db --defaults-file= --force --basedir=/usr
--datadir=/home/siducer/.local/share/akonadi/db_data/
I this command also fails with the same error (not
Hi Julien
This autopkgtest failure still prevents mercurial 4.9-2 from migrating
to testing.
On 2019/02/18 14:08, Graham Inggs wrote:
Do you have any ideas on how to suppress the deprecation warnings?
I didn't figure out how to do this, but I patched them out of mercurial.
With this local
Le 27/02/2019 à 20:06, Niko Tyni a écrit :
> On Wed, Feb 27, 2019 at 05:16:03PM +0100, gregor herrmann wrote:
>
>> 2) This fix would also suite the documentation of tv_imdb which says:
>>
>> tv_imdb --imdbdir [--help] [--quiet]
>>[--with-keywords] [--with-plot]
>>[--movies-only]
Processing commands for cont...@bugs.debian.org:
> notfound 918632 simplejson/3.16.0-1
Bug #918632 [src:simplejson, src:json-schema-validator] simplejson breaks
json-schema-validator autopkgtest
No longer marked as found in versions simplejson/3.16.0-1.
> reassign 918632 json-schema-validator
notfound 918632 simplejson/3.16.0-1
reassign 918632 json-schema-validator
thanks
I'll seek removal of the orphaned json-schema-validator source package
in due course.
--
Neil Williams
h...@codehelp.co.uk
pgpgTCIPlpcle.pgp
Description: OpenPGP digital signature
Your message dated Thu, 28 Feb 2019 10:19:56 +
with message-id
and subject line Bug#923402: fixed in mu-editor 1.0.2+dfsg-2
has caused the Debian Bug report #923402,
regarding mu-editor: FTBFS with python3-pkg-resources 40.8.0: TypeError:
expected str, bytes or os.PathLike object, not Win
to
Hi all,
On 18-02-2019 23:04, Neil Williams wrote:
> Unless there are any relevant bug reports filed against simplejson or
> some other confirmation of the bug as being caused by simplejson within
> say a week to 10 days, I'll assign this just to json-schema-validator
> and seek removal of
Package: src:ghc
Version: 8.4.4+dfsg1-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules binary-indep
dh binary-indep
Processing control commands:
> severity 922946 normal
Bug #922946 [gazebo] gazebo: please don’t depend on the hinted Roboto fonts
Severity set to 'normal' from 'serious'
--
922946: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922946
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Control: severity 922946 normal
On Thu, 28 Feb 2019 at 11:04, Santiago Vila wrote:
> On Fri, 22 Feb 2019, Andrej Shadura wrote:
>
> > The Roboto upstream no longer provides hinted fonts, so
> > fonts-roboto-hinted is now a transitional package providing symlinks to
> > the unhinted fonts. Please
Package: src:octave
Version: 4.4.1-4
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules binary-indep
dh binary-indep
Processing commands for cont...@bugs.debian.org:
> severity 922946 serious
Bug #922946 [gazebo] gazebo: please don’t depend on the hinted Roboto fonts
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
922946:
Control: tag -1 pending
Hello,
Bug #922741 in grub2 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:
Processing control commands:
> tag -1 pending
Bug #922741 [grub-efi] grub-efi: grub-install indicates "no errors" when
there's insufficient disk space in EFI partition
Added tag(s) pending.
--
922741: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922741
Debian Bug Tracking System
Contact
1 - 100 of 107 matches
Mail list logo
