Is this test actually right? Shouldn't it be Angle::Gradians?
CHECK_THROWS( WallsSurveyParser("400g").azimuth(Angle::Degrees) )
same for;
CHECK_THROWS( WallsSurveyParser("-0.1g").azimuth(Angle::Degrees) );
CHECK_THROWS( WallsSurveyParser("N100gE").azimuth(Angle::Degree
Processing control commands:
> block -1 with 891690
Bug #892426 [src:pocl] pocl: FTBFS on most non-x86 architectures: 12-16% of
tests pass
892426 was not blocked by any bugs.
892426 was not blocking any bugs.
Added blocking bug(s) of 892426: 891690
--
892426: https://bugs.debian.org/cgi-bin/bug
On 2018-01-31 20:59 +, Philip Schuchardt wrote:
> Nice! I wonder if i386 don’t support exceptions properly or something...
It's not that simple.
I found out how to run specific tests with catch. There are two other groups of
tests which are expected to throw and those work OK:
(sid_i386-dchr
On 2018-03-08 18:20 +, Wookey wrote:
> It looks like we have libstdc++6 and libstdc++-dev virtual
> packages. Is it OK to build-depend on just a virtual package? Perusing
> Policy has not made me much wiser.
Using:
Build-Depends: libstdc++-dev
builds OK, but I found the info pointing out that
Your message dated Fri, 09 Mar 2018 03:10:46 +
with message-id
and subject line Bug#892375: fixed in isl 0.19-1~exp3
has caused the Debian Bug report #892375,
regarding isl: Incomplete debian/copyright?
to be marked as done.
This means that you claim that the problem has been dealt with.
If t
Your message dated Fri, 09 Mar 2018 01:49:12 +
with message-id
and subject line Bug#890106: fixed in colmap 3.4-2
has caused the Debian Bug report #890106,
regarding colmap: baseline violation on amd64/i386 and FTBFS everywhere else
to be marked as done.
This means that you claim that the pro
tag 868404 + pending
thanks
Some bugs in the swt-gtk package are closed in revision
6925d8298081d484ab9873b601664dbc8c9e24b6 in branch ' master-4.3' by
Jeremy Bicha
The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/swt-gtk.git/commit/?id=6925d82
Commit message:
Import D
Processing commands for cont...@bugs.debian.org:
> tag 868404 + pending
Bug #868404 {Done: Jeremy Bicha } [src:swt4-gtk] swt4-gtk:
Please drop the (build-)dependency against gnome-vfs
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
868404: h
Package: lyx-common
Version: 2.3.0-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Either lyx-common scripts should be python neutral - run both with python 2.7
and python 3.x or explicitely specify python3 in the shebang line.
File "/usr/share/lyx/scripts/convertDe
Your message dated Thu, 08 Mar 2018 23:19:35 +
with message-id
and subject line Bug#892411: fixed in java3d 1.5.2+dfsg-13
has caused the Debian Bug report #892411,
regarding java3d FTBFS on armhf: compile-ogl fails
to be marked as done.
This means that you claim that the problem has been deal
tag 892411 + pending
thanks
Some bugs in the java3d package are closed in revision
d17a89ba073c90777eda223e5e32305a74092796 in branch 'master' by
Emmanuel Bourg
The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/java3d.git/commit/?id=d17a89b
Commit message:
Added the clie
Processing commands for cont...@bugs.debian.org:
> tag 892411 + pending
Bug #892411 [src:java3d] java3d FTBFS on armhf: compile-ogl fails
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
892411: https://bugs.debian.org/cgi-bin/bugreport.cgi?bu
Le 08/03/2018 à 21:13, Adrian Bunk a écrit :
> Likely caused by:
>
> openjdk-8 (8u144-b01-1) unstable; urgency=medium
> ...
> * debian/rules:
> - add aarch32 hotspot support.
> - build aarch32 using client jvm-variant (no server in aarch32 port).
Good analysis, thank you. I'll add the
On Thu, Mar 8, 2018 at 4:26 PM, Ximin Luo wrote:
> Do you have some advice on how to migrate? Last time I checked there was no
> straightforward 1-1 correspondence between the libsecret vs the
> libgnome-keyring API and data models.
>
> Forcing people to do extra work they don't know how to do,
Le 08/03/2018 à 22:50, Nicolas Braud-Santoni a écrit :
> Given that this is the last activity and the package, that the last upload
> is almost 2 years old, and that no progress has been made towards fixing the
> RC bugs (esp. the issues wrt. security), should we ask ftp-masters to remove
> this p
* Jindřich Makovička [2018-03-08 19:46 +]:
> There is a fix in upstream master.
>
> https://github.com/systemd/systemd/pull/8391
Patched Debian sources and tried to build packages:
OK: 239
FAIL: 1
SKIP: 15
TIMEOUT:0
debian/rules:281: recipe for target 'override_dh_auto
Processing commands for cont...@bugs.debian.org:
> retitle 892415 nvcc wants GCC 6 which we want to remove
Bug #892415 [nvidia-cuda-toolkit] eztrace-contrib: build-depends on GCC 6
Changed Bug title to 'nvcc wants GCC 6 which we want to remove' from
'eztrace-contrib: build-depends on GCC 6'.
> th
Control: clone -1 -2
Control: reassign -2 nvidia-cuda-toolkit
Control: block -1 by -2
Control: block 892403 by -2
Hello,
po...@debian.org, on jeu. 08 mars 2018 18:48:47 +0100, wrote:
> eztrace-contrib build-depends on GCC 6.
> starpu-contrib build-depends on GCC 6.
This is due to CUDA, whose ver
Processing control commands:
> clone -1 -2
Bug #892389 [src:eztrace-contrib] eztrace-contrib: build-depends on GCC 6
Bug 892389 cloned as bug 892415
> reassign -2 nvidia-cuda-toolkit
Bug #892415 [src:eztrace-contrib] eztrace-contrib: build-depends on GCC 6
Bug reassigned from package 'src:eztrace-
On Mon, Nov 21, 2016 at 09:33:18PM +0100, Hilko Bengen wrote:
> * Emmanuel Bourg:
> > Do you think elasticsearch should be removed from unstable?
>
> Not necessarily. It should just not become part of stretch because there
> is no sensible way to support it.
Given that this is the last activity a
Your message dated Thu, 08 Mar 2018 21:49:47 +
with message-id
and subject line Bug#882918: fixed in php-sql-formatter 1.2.17-3
has caused the Debian Bug report #882918,
regarding php-sql-formatter FTBFS with phpunit 6.4.4-2
to be marked as done.
This means that you claim that the problem has
Your message dated Thu, 08 Mar 2018 21:49:57 +
with message-id
and subject line Bug#891617: fixed in spyder 3.2.6+dfsg1-2
has caused the Debian Bug report #891617,
regarding DistributionNotFound: The 'pyopengl' distribution was not found
to be marked as done.
This means that you claim that th
Your message dated Thu, 08 Mar 2018 21:49:57 +
with message-id
and subject line Bug#891618: fixed in spyder 3.2.6+dfsg1-2
has caused the Debian Bug report #891618,
regarding DistributionNotFound: The 'pyqt5' distribution was not found
to be marked as done.
This means that you claim that the p
Your message dated Thu, 08 Mar 2018 21:34:32 +
with message-id
and subject line Bug#891215: fixed in qmmp 1.2.0-1
has caused the Debian Bug report #891215,
regarding qmmp FTBFS: AutoMoc error
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Do you have some advice on how to migrate? Last time I checked there was no
straightforward 1-1 correspondence between the libsecret vs the
libgnome-keyring API and data models.
Forcing people to do extra work they don't know how to do, or else risk losing
their most precious data, is extremely
Processing commands for cont...@bugs.debian.org:
> limit source php-sql-formatter
Limiting to bugs with field 'source' containing at least one of
'php-sql-formatter'
Limit currently set to 'source':'php-sql-formatter'
> tags 882918 + pending
Bug #882918 [src:php-sql-formatter] php-sql-formatter
Your message dated Thu, 08 Mar 2018 21:06:31 +
with message-id
and subject line Bug#892019: fixed in python-meshio 1.11.7-2
has caused the Debian Bug report #892019,
regarding python-meshio: Installs test files to /usr/lib/python3/dist-packages
to be marked as done.
This means that you claim
Your message dated Thu, 08 Mar 2018 21:06:19 +
with message-id
and subject line Bug#883352: fixed in php-doctrine-cache-bundle 1.3.2-3
has caused the Debian Bug report #883352,
regarding php-doctrine-cache-bundle FTBFS: test failures
to be marked as done.
This means that you claim that the pr
Processing commands for cont...@bugs.debian.org:
> limit source php-doctrine-cache-bundle
Limiting to bugs with field 'source' containing at least one of
'php-doctrine-cache-bundle'
Limit currently set to 'source':'php-doctrine-cache-bundle'
> tags 889799 + pending
Bug #889799 [php-doctrine-cach
Source: java3d
Version: 1.5.2+dfsg-11
Severity: serious
Tags: buster sid
https://tests.reproducible-builds.org/debian/rb-pkg/buster/armhf/java3d.html
https://buildd.debian.org/status/fetch.php?pkg=java3d&arch=armhf&ver=1.5.2%2Bdfsg-12&stamp=1520519146&raw=0
...
compile-ogl:
...
[exec] ld: ca
* Diederik de Haas [2018-03-08 20:29 +0100]:
> Package: systemd
> Followup-For: Bug #892360
>
> Wanting to let you know that I had no problem on my PC (from which I'm
> reporting) and also not on my laptop.
>
> I did not have to specify any (systemd related) kernel parameters
> $ cat /proc/cmdl
There is a fix in upstream master.
https://github.com/systemd/systemd/pull/8391
--
Jindřich Makovička
Your message dated Thu, 08 Mar 2018 20:42:09 +0100
with message-id <1520538129.15837.2.ca...@debian.org>
and subject line Re: xul-ext-compactheader: uninstallable in jessie
has caused the Debian Bug report #837387,
regarding xul-ext-compactheader: uninstallable in jessie and wheezy
to be marked as
Your message dated Thu, 08 Mar 2018 19:34:11 +
with message-id
and subject line Bug#892391: fixed in blackbox 0.70.1-36
has caused the Debian Bug report #892391,
regarding blackbox: build-depends on GCC 6
to be marked as done.
This means that you claim that the problem has been dealt with.
If
* Elimar Riesebieter [2018-03-08 19:13 +0100]:
[...]
> ATM I am building a x86 with CONFIG_CGROUP_CPUACCT=not set. Let's
> wait and see
"CONFIG_CGROUP_CPUACCT is not set" gives the same error as shown in
the picture of my initial bug report.
The problem must be triggerd from within systemd
Package: systemd
Followup-For: Bug #892360
Wanting to let you know that I had no problem on my PC (from which I'm
reporting) and also not on my laptop.
I did not have to specify any (systemd related) kernel parameters
$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-4.15.0-1-amd64
root=UUID=a2a5e481-0ac6
Your message dated Thu, 08 Mar 2018 19:19:14 +
with message-id
and subject line Bug#891911: fixed in bogofilter 1.2.4+dfsg1-11
has caused the Debian Bug report #891911,
regarding bogofilter: not binNMU safe
to be marked as done.
This means that you claim that the problem has been dealt with.
Hello,
I'm interested in potentially taking on maintenance of this package. I
am new to Debian but I'd like to start contributing.
To explore this possibility, I've created a proof-of-concept transition
script. Please take a look at the attached script and let me know your
thoughts and suggestion
Processing control commands:
> severity -1 serious
Bug #886145 [src:shutter] shutter: Don't recommend libgoo-canvas-perl
Severity set to 'serious' from 'important'
--
886145: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886145
Debian Bug Tracking System
Contact ow...@bugs.debian.org with pr
On 3/8/18 7:26 PM, Eric Valette wrote:
On 3/8/18 7:13 PM, Elimar Riesebieter wrote:
I do have CONFIG_CGROUP_CPUACCT=y on my amd64 kernels and systemd
runs fine...
Ok. So still in line with hypothesis...
ATM I am building a x86 with CONFIG_CGROUP_CPUACCT=not set. Let's
wait and see
Processing commands for cont...@bugs.debian.org:
> tags 871694 + buster sid
Bug #871694 {Done: Adrian Bunk } [src:bogofilter]
bogofilter-common: bogofilter-bdb-1.2.4+dfsg1-9+b1 depends on bogofilter-common
(same version),the latter does not exist
Bug #871774 {Done: Adrian Bunk } [src:bogofilter]
On 3/8/18 7:13 PM, Elimar Riesebieter wrote:
I do have CONFIG_CGROUP_CPUACCT=y on my amd64 kernels and systemd
runs fine...
Ok. So still in line with hypothesis...
ATM I am building a x86 with CONFIG_CGROUP_CPUACCT=not set. Let's
wait and see
And I'm rebuilding my failing kernel wi
On 2018-03-08 18:48 +0100, po...@debian.org wrote:
> Source: dewalls
> Severity: serious
> Tags: sid buster
> User: debian-...@lists.debian.org
> Usertags: gcc-6-rm
>
> Hi,
>
> dewalls build-depends on GCC 6. We now have GCC 7 (default) and GCC 8
> in the archive, so please make your package buil
* Eric Valette [2018-03-08 19:08 +0100]:
> On 3/8/18 7:03 PM, Elimar Riesebieter wrote:
> > * Michael Biebl [2018-03-08 18:54 +0100]:
> >
> > [...]
> > > Can you check your custom kernel config, specifically if
> > > CONFIG_CGROUP_CPUACCT=y
> >
> > I do have CONFIG_CGROUP_CPUACCT=y
> >
> > We
On 3/8/18 7:03 PM, Elimar Riesebieter wrote:
* Michael Biebl [2018-03-08 18:54 +0100]:
[...]
Can you check your custom kernel config, specifically if
CONFIG_CGROUP_CPUACCT=y
I do have CONFIG_CGROUP_CPUACCT=y
Well, but why does 237 works with the very same kernel?
In my case it is not set,
* Michael Biebl [2018-03-08 18:54 +0100]:
[...]
> Can you check your custom kernel config, specifically if
> CONFIG_CGROUP_CPUACCT=y
I do have CONFIG_CGROUP_CPUACCT=y
Well, but why does 237 works with the very same kernel?
Elimar
--
Numeric stability is probably not all that
important wh
Source: thunderbird
Severity: serious
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: gcc-6-rm
Hi,
thunderbird build-depends on GCC 6. We now have GCC 7 (default) and
GCC 8 in the archive, so please make your package build with a newer
compiler (preferably the default one) again, sin
Can you check your custom kernel config, specifically if
CONFIG_CGROUP_CPUACCT=y
Probably easiest if you just use grep
grep CGROUP /boot/config-$(uname -r)
Done in another private email. Can copy here:
diff config-4.14.0-3-amd64 config-4.14.23 | grep CGROUP
< CONFIG_BLK_CGROUP=y
< # CONFIG_
Am 08.03.2018 um 18:31 schrieb Elimar Riesebieter:
> * Michael Biebl [2018-03-08 17:09 +0100]:
>
>> Am 08.03.2018 um 17:05 schrieb Michael Biebl:
>>> Control: tags -1 moreinfo
>>>
>>> Am 08.03.2018 um 16:23 schrieb valette:
>>>
> [...]
>
>> Could you check if
>> https://github.com/systemd/system
> Source: node-xterm
> Version: 2.7.0+ds1-1
> Severity: serious
>
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/no
> de-xterm.html
>
> ...
>debian/rules override_dh_auto_build
> make[1]: Entering directory '/build/1st/node-xterm-2.7.0+ds1'
> tsc --project .
> src/utils/
Source: starpu-contrib
Severity: serious
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: gcc-6-rm
Hi,
starpu-contrib build-depends on GCC 6. We now have GCC 7 (default)
and GCC 8 in the archive, so please make your package build with a
newer compiler (preferably the default one) agai
Source: squid3
Severity: serious
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: gcc-6-rm
Hi,
squid3 build-depends on GCC 6. We now have GCC 7 (default) and GCC 8
in the archive, so please make your package build with a newer
compiler (preferably the default one) again, since we'd li
Source: shiboken
Severity: serious
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: gcc-6-rm
Hi,
shiboken build-depends on GCC 6. We now have GCC 7 (default) and GCC
8 in the archive, so please make your package build with a newer
compiler (preferably the default one) again, since we'
Source: dewalls
Severity: serious
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: gcc-6-rm
Hi,
dewalls build-depends on GCC 6. We now have GCC 7 (default) and GCC 8
in the archive, so please make your package build with a newer
compiler (preferably the default one) again, since we'd
Source: blackbox
Severity: serious
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: gcc-6-rm
Hi,
blackbox build-depends on GCC 6. We now have GCC 7 (default) and GCC
8 in the archive, so please make your package build with a newer
compiler (preferably the default one) again, since we'
Source: linux-grsec
Severity: serious
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: gcc-6-rm
Hi,
linux-grsec build-depends on GCC 6. We now have GCC 7 (default) and
GCC 8 in the archive, so please make your package build with a newer
compiler (preferably the default one) again, sin
Source: grub2
Severity: serious
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: gcc-6-rm
Hi,
grub2 build-depends on GCC 6. We now have GCC 7 (default) and GCC 8
in the archive, so please make your package build with a newer
compiler (preferably the default one) again, since we'd like
Source: kfreebsd-10
Severity: serious
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: gcc-6-rm
Hi,
kfreebsd-10 build-depends on GCC 6. We now have GCC 7 (default) and
GCC 8 in the archive, so please make your package build with a newer
compiler (preferably the default one) again, sin
Source: caffe-contrib
Severity: serious
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: gcc-6-rm
Hi,
caffe-contrib build-depends on GCC 6. We now have GCC 7 (default) and
GCC 8 in the archive, so please make your package build with a newer
compiler (preferably the default one) again,
Source: aqemu
Severity: serious
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: gcc-6-rm
Hi,
aqemu build-depends on GCC 6. We now have GCC 7 (default) and GCC 8
in the archive, so please make your package build with a newer
compiler (preferably the default one) again, since we'd like
Source: kodi
Severity: serious
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: gcc-6-rm
Hi,
kodi build-depends on GCC 6. We now have GCC 7 (default) and GCC 8 in
the archive, so please make your package build with a newer compiler
(preferably the default one) again, since we'd like t
Source: boost1.62
Severity: serious
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: gcc-6-rm
Hi,
boost1.62 build-depends on GCC 6. We now have GCC 7 (default) and GCC
8 in the archive, so please make your package build with a newer
compiler (preferably the default one) again, since w
Source: gmp-ecm
Severity: serious
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: gcc-6-rm
Hi,
gmp-ecm build-depends on GCC 6. We now have GCC 7 (default) and GCC 8
in the archive, so please make your package build with a newer
compiler (preferably the default one) again, since we'd
Source: firefox-esr
Severity: serious
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: gcc-6-rm
Hi,
firefox-esr build-depends on GCC 6. We now have GCC 7 (default) and
GCC 8 in the archive, so please make your package build with a newer
compiler (preferably the default one) again, sin
Source: boost1.63
Severity: serious
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: gcc-6-rm
Hi,
boost1.63 build-depends on GCC 6. We now have GCC 7 (default) and GCC
8 in the archive, so please make your package build with a newer
compiler (preferably the default one) again, since w
Source: eztrace-contrib
Severity: serious
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: gcc-6-rm
Hi,
eztrace-contrib build-depends on GCC 6. We now have GCC 7 (default)
and GCC 8 in the archive, so please make your package build with a
newer compiler (preferably the default one) ag
This sounded like an interesting software archeology problem...
Tom Lane of IJG posted a slightly later version of jpeg's configure.in
and associated files to the UnixOS2 mailing list in 2004:
http://unix.os2site.com/pub/list/unixos2/2004/03/2004Mar31000402.txt
> Let's see ... configure is built l
* Michael Biebl [2018-03-08 17:09 +0100]:
> Am 08.03.2018 um 17:05 schrieb Michael Biebl:
> > Control: tags -1 moreinfo
> >
> > Am 08.03.2018 um 16:23 schrieb valette:
> >
[...]
> Could you check if
> https://github.com/systemd/systemd/issues/8387
> looks related
>
> I.e. if booting with syst
Your message dated Thu, 08 Mar 2018 17:38:37 +
with message-id
and subject line Bug#892109: fixed in pdf2djvu 0.9.8-1
has caused the Debian Bug report #892109,
regarding pdf2djvu FTBFS with libpoppler-dev 0.62.0-2
to be marked as done.
This means that you claim that the problem has been dealt
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package resiprocate
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debi
Am 08.03.2018 um 18:27 schrieb Elimar Riesebieter:
> * Michael Biebl [2018-03-08 17:05 +0100]:
>
>> Control: tags -1 moreinfo
>>
>> Am 08.03.2018 um 16:23 schrieb valette:
>>
>>> Kernel: Linux 4.14.23 (SMP w/2 CPU cores; PREEMPT)
>>
>> Is this also happening with a Debian provided kernel?
>> I se
* Michael Biebl [2018-03-08 17:05 +0100]:
> Control: tags -1 moreinfo
>
> Am 08.03.2018 um 16:23 schrieb valette:
>
> > Kernel: Linux 4.14.23 (SMP w/2 CPU cores; PREEMPT)
>
> Is this also happening with a Debian provided kernel?
> I see both you and Elimar use a custom one.
Didn't test it.
>
Your message dated Thu, 08 Mar 2018 16:49:52 +
with message-id
and subject line Bug#891163: fixed in kstars 5:2.9.3-1
has caused the Debian Bug report #891163,
regarding kstars FTBFS: dh_install: Cannot find
"usr/lib/*/libexec/kauth/kauth_kstars_helper"
to be marked as done.
This means that
Hi,
it seems that we can't reproduce this bug anymore as golang went from
1.9 to 1.10 now.
Well, it fails on another issue on ppc64el, but it seems to be the same on
amd64 .
Should we close that bug ?
F.
pgpzgP_flZJ8n.pgp
Description: PGP signature
Source: devscripts
Version: 2.18.1
Severity: serious
X-Debbugs-Cc: Osamu Aoki
Hi Osamu-san :)
the new uscan_ftp tests seems to misbehave on mipsel/mips64el.
Just to mention one:
|testWatch4NonNativeDlUversion
|FTP starting ... /tmp/tmp.XEqC4nYhhq/repo
|uscan warn: In directory ., downloading
|
Am 08.03.2018 um 17:09 schrieb Michael Biebl:
> Could you check if
> https://github.com/systemd/systemd/issues/8387
> looks related
>
> I.e. if booting with systemd.unified_cgroup_hierarchy avoids the problem.
If not, follow the instructions at
https://freedesktop.org/wiki/Software/systemd/Debug
Am 08.03.2018 um 17:05 schrieb Michael Biebl:
> Control: tags -1 moreinfo
>
> Am 08.03.2018 um 16:23 schrieb valette:
>
>> Kernel: Linux 4.14.23 (SMP w/2 CPU cores; PREEMPT)
>
> Is this also happening with a Debian provided kernel?
> I see both you and Elimar use a custom one.
>
> Is this a vir
control: severity -1 important
Am 11.02.2018 um 10:48 schrieb Svein Engelsgjerd:
> Dear Maintainer,
>
> When I start openshot the GUI constantly flickers between the main
> window and the "welcome window" / tutorial dialog. It is not possible
> to click the next button so the welcome window preve
Processing commands for cont...@bugs.debian.org:
> tags 891163 + pending
Bug #891163 [src:kstars] kstars FTBFS: dh_install: Cannot find
"usr/lib/*/libexec/kauth/kauth_kstars_helper"
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
891163: htt
Processing control commands:
> tags -1 moreinfo
Bug #892360 [systemd] systemd pid 1 freezes at startup on x86 systems
Added tag(s) moreinfo.
--
892360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892360
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> severity -1 important
Bug #890102 [openshot] openshot: Openshot 2.4.1-2 will not start
Severity set to 'important' from 'grave'
--
890102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890102
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problem
Control: tags -1 moreinfo
Am 08.03.2018 um 16:23 schrieb valette:
> Kernel: Linux 4.14.23 (SMP w/2 CPU cores; PREEMPT)
Is this also happening with a Debian provided kernel?
I see both you and Elimar use a custom one.
Is this a virtualized environment or read hardware?
Do you get a coredump? If
Your message dated Thu, 08 Mar 2018 15:51:14 +
with message-id
and subject line Bug#889672: fixed in gcompris-qt 0.81-1
has caused the Debian Bug report #889672,
regarding gcompris-qt: Missing dependency
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Thu, 08 Mar 2018 15:51:14 +
with message-id
and subject line Bug#820496: fixed in gcompris-qt 0.81-1
has caused the Debian Bug report #820496,
regarding gcompris-qt: dependencies not automatically installed
to be marked as done.
This means that you claim that the problem ha
Source: isl
Version: 0.19-1~exp2
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Matthias Klose
Hi,
I just ACCEPTed isl from NEW but noticed it was missing attribution
in debian/copyright for at least imath/imath.c, interface/isl_test_python.py
etc.
(This is not exhaustive so please c
Source: proftpd-mod-fsync
Version: 0.2-1
Severity: serious
Tags: buster sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/proftpd-mod-fsync.html
...
mod_fsync.c:184:10: error: implicit declaration of function 'HANDLED'; did you
mean 'PR_HANDLED'? [-Werror=implicit-function-d
Source: proftpd-mod-msg
Version: 0.4.1-1.1
Severity: serious
Tags: buster sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/proftpd-mod-msg.html
...
mod_msg.c:56:3: error: #error "mod_msg requires Controls support
(--enable-ctrls)"
# error "mod_msg requires Controls support
Source: proftpd-mod-vroot
Version: 0.9.4-1
Severity: serious
Tags: buster sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/proftpd-mod-vroot.html
...
mod_vroot.c:1518:19: error: void value not ignored as it ought to be
if (cmd->argv[1][pathlen - 1] != '/') {
~~
Package: systemd
Version: 238-1
Followup-For: Bug #892360
I also get a sigsegv on two diferent machines after today upgrade.
You can reboot and use sysvinit mode => bug is realy in systemd.
Kernel and packages uptodate
-- Package-specific info:
-- System Information:
Debian Release: buster/sid
Your message dated Thu, 08 Mar 2018 15:08:06 +
with message-id
and subject line Bug#891360: fixed in python-magnumclient 2.8.0-1
has caused the Debian Bug report #891360,
regarding python-magnumclient FTBFS: test failures
to be marked as done.
This means that you claim that the problem has be
I also have a system crash at init, witha sigsegv that points in libc.
I use unstable today (8 march).
--eric
Your message dated Thu, 08 Mar 2018 16:00:23 +0100
with message-id <876066k3y0@gmail.com>
and subject line Re: Bug#892207: blender: fails to start
has caused the Debian Bug report #892207,
regarding blender: fails to start
to be marked as done.
This means that you claim that the problem has be
Control: tag -1 pending
Hello,
Bug #891360 in python-magnumclient 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/openstack-team/clients/python-magnumclient/co
Control: tag -1 pending
Hello,
Bug #891360 in python-magnumclient 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/openstack-team/clients/python-magnumclient/co
Processing control commands:
> tag -1 pending
Bug #891360 [src:python-magnumclient] python-magnumclient FTBFS: test failures
Added tag(s) pending.
--
891360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891360
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> tag -1 pending
Bug #891360 [src:python-magnumclient] python-magnumclient FTBFS: test failures
Ignoring request to alter tags of bug #891360 to the same tags previously set
--
891360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891360
Debian Bug Tracking Syste
Le 8 mars 2018 14:47, "Alberto Garcia" a écrit :
On Thu, Mar 08, 2018 at 02:22:37PM +0100, Julien Aubin wrote:
> No I confirm the offending packages are *gstreamer*bad from
> deb-multimedia.org
Is then problem solved if you use the official gstreamer packages
then?
Berto
Yes it is. It is rel
Processing commands for cont...@bugs.debian.org:
> severity 858819 serious
Bug #858819 [trac-email2trac] Typo causes error with Trac 1.2
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
858819: https://bugs.debian.org/cgi-bin
On Thu, Mar 08, 2018 at 02:22:37PM +0100, Julien Aubin wrote:
> No I confirm the offending packages are *gstreamer*bad from
> deb-multimedia.org
Is then problem solved if you use the official gstreamer packages
then?
Berto
Your message dated Thu, 08 Mar 2018 13:36:21 +
with message-id
and subject line Bug#891292: fixed in sisl 4.6.0-2
has caused the Debian Bug report #891292,
regarding sisl: FTBFS with glibc 2.27: error: 'MAXDOUBLE' undeclared (first use
in this function); did you mean 'DOUBLE'?
to be marked as
1 - 100 of 121 matches
Mail list logo
