Processing commands for cont...@bugs.debian.org:
> reassign 906744 dh-php
Bug #906744 {Done: Ondřej Surý } [php-yaml]
/usr/lib/php/20151012/yaml.so: cannot open shared object file
Bug reassigned from package 'php-yaml' to 'dh-php'.
No longer marked as found in versions php-yaml/2.0.2+1.3.1-2.
No
Your message dated Mon, 22 Oct 2018 06:04:02 +
with message-id
and subject line Bug#910306: fixed in electrum 3.2.3-1
has caused the Debian Bug report #910306,
regarding electrum FTBFS: mv: cannot stat
'debian/python3-electrum/usr/share/applications': No such file or directory
to be marked as
Your message dated Mon, 22 Oct 2018 04:49:27 +
with message-id
and subject line Bug#911434: fixed in prometheus 2.4.3+ds-2
has caused the Debian Bug report #911434,
regarding prometheus: FTBFS flaky shutdown test
to be marked as done.
This means that you claim that the problem has been dealt
On Fri, 19 Oct 2018 10:47:25 -0300
=?UTF-8?Q?Lisandro_Dami=C3=A1n_Nicanor_P=C3=A9rez_Meyer?=
wrote:
> Hi! I have been looking at this bug and then at the packaging and
> installed files.
>
> dpkg -L libsane tells me that the *only* public library shipped is
> /usr/lib//libsane.so.1
>
> The rest
Control: tag -1 pending
Hello,
Bug #911434 in prometheus 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/go-team/packages/prometheus/commit/76974d404f073b166c0
Processing control commands:
> tag -1 pending
Bug #911434 [prometheus] prometheus: FTBFS flaky shutdown test
Added tag(s) pending.
--
911434: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911434
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing commands for cont...@bugs.debian.org:
> tags 892334 + pending
Bug #892334 [src:libg15render] libg15render: Please use 'pkg-config' to find
FreeType 2
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
892334: https://bugs.debian.org/
Processing commands for cont...@bugs.debian.org:
> reopen 874685
Bug #874685 [src:sysvinit] Do not run init scripts under systemd
Bug 874685 is not marked as done; doing nothing.
> block 910444 by 874685
Bug #910444 [openrc] Filesystems listed in /etc/fstab are no more automatically
mounted since
Processing commands for cont...@bugs.debian.org:
> unarchive 874685
Bug #874685 {Done: Michael Biebl } [src:sysvinit] Do not run
init scripts under systemd
Unarchived Bug 874685
> reopen 874685
Bug #874685 {Done: Michael Biebl } [src:sysvinit] Do not run
init scripts under systemd
'reopen' may b
Hi Axel,
While I haven't tried to reproduce the bug with Sid yet, Bug 874685
looks extremely suspicious for causing this.
Yours,
Benda
tags 892334 + pending
thanks
Hugh McMaster :
> A rebuild of your package with freetype 2.9.1 installed confirmed that your
> package will FTBFS once the new version of freetype enters unstable. In
> almost all cases, this build failure was caused by the configure script not
> detecting the freetyp
Processing commands for cont...@bugs.debian.org:
> found 911418 0.9.12-2
Bug #911418 {Done: to...@debian.org (Dr. Tobias Quathamer)}
[rapid-photo-downloader] missing dependency: ImportError: cannot import name
'sip'
Marked as found in versions rapid-photo-downloader/0.9.12-2; no longer marked
a
On 2018-10-20 22:03:03, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the rapid-photo-downloader package:
>
> #911418: missing dependency: ImportError: cannot import name 'sip'
>
> It has been closed by to...@debian.org (Dr
Package: src:haskell-hastache
Version: 0.6.1-8
Severity: serious
Replacements for hastache are mustache and microstache
Package: src:haskell-cabal-file-th
Version: 0.2.4-3
Severity: serious
Source needs to be updated for Cabal API changes, if worth the
maintenance burden.
Package: src:haskell-hit
Version: 0.6.3-8
Severity: serious
If hit is worth keeping, here is a patch:
https://github.com/vincenthz/hit/pull/37
Processing control commands:
> reopen -1
Bug #886056 {Done: Markus Koschany } [src:morris] morris:
Depends on gconf
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed
Control: reopen -1
Control: severity -1 important
morris depends on gconf since the dependency removal was reverted.
It would be nice if it could be converted to gsettings for the Buster
release so that it can use the gconf helper to do the conversion and
we can remove gconf for the Bullseye rele
Hi all,
I was surprised and was hit with this bug today.
$ apt-cache policy lxqt-common
lxqt-common:
Installed: (none)
Candidate: 0.11.2-2
Version table:
0.11.2-2 500
500 http://deb.debian.org/debian unstable/main amd64 Packages
$ sudo aptitude install lxqt-common
The followin
Processing commands for cont...@bugs.debian.org:
> unarchive 886056
Bug #886056 {Done: Markus Koschany } [src:morris] morris:
Depends on gconf
Unarchived Bug 886056
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
886056: https://bugs.debian.org/cgi-bin/b
Jeremy Bicha wrote:
> On Sun, Oct 21, 2018 at 5:07 PM Yavor Doganov wrote:
> > This is slightly confusing to me; there is src:gtksourceview3 but I
> > cannot find src:gtksourceview4.
>
> Here are some links:
> https://tracker.debian.org/pkg/gtksourceview4
I feel stupid right now; I typed "gtksou
Your message dated Sun, 21 Oct 2018 22:20:00 +
with message-id
and subject line Bug#870815: fixed in libytnef 1.9.3-1
has caused the Debian Bug report #870815,
regarding libytnef: CVE-2017-12141: heap-buffer-overflow
to be marked as done.
This means that you claim that the problem has been de
Am 21.10.18 um 23:51 schrieb Yavor Doganov:
> Markus Koschany wrote:
>> I only noticed that the Close button in the "Info" submenu doesn't
>> work as intended.
>
> There is no "Info" submenu; I guess you mean the Close button in the
> About dialog? None of the patches touches this code and I ca
On Tue, Oct 16, 2018 at 12:49:36PM -0400, Jeremy Bicha wrote:
> Please port your package to gtk3 and gtksourceview4.
This is slightly confusing to me; there is src:gtksourceview3 but I
cannot find src:gtksourceview4. It's not in the NEW queue either. Is
it going to be a new source package? If y
Markus Koschany wrote:
> I only noticed that the Close button in the "Info" submenu doesn't
> work as intended.
There is no "Info" submenu; I guess you mean the Close button in the
About dialog? None of the patches touches this code and I can
reproduce with 1.8.1-7+b1 so it's not a regression.
>
Your message dated Sun, 21 Oct 2018 21:36:06 +
with message-id
and subject line Bug#856086: fixed in monster-masher 1.8.1-8
has caused the Debian Bug report #856086,
regarding monster-masher: Please drop the (build-)dependency against esound
to be marked as done.
This means that you claim tha
Your message dated Sun, 21 Oct 2018 21:36:06 +
with message-id
and subject line Bug#885037: fixed in monster-masher 1.8.1-8
has caused the Debian Bug report #885037,
regarding monster-masher: Please don't (Build-)Depend on gconfmm2.6
to be marked as done.
This means that you claim that the pr
On Sun, Oct 21, 2018 at 5:07 PM Yavor Doganov wrote:
> This is slightly confusing to me; there is src:gtksourceview3 but I
> cannot find src:gtksourceview4. It's not in the NEW queue either. Is
> it going to be a new source package? If yes, when it is going to be
> uploaded to Debian? (I assum
Hi Bernhard,
Bernhard Übelacker wrote:
> what CPU is inside the machine producing this cores?
→ grep model /proc/cpuinfo
model : 94
model name : Intel(R) Core(TM) i7-6700T CPU @ 2.80GHz
model : 94
model name : Intel(R) Core(TM) i7-6700T CPU @ 2.80GHz
model
Hi!
Thanks again for your patches to port monster-masher away from esound
and gconfmm. I only noticed that the Close button in the "Info" submenu
doesn't work as intended. Otherwise the game seems to work. Minor
nitpick: Please consider to submit a debdiff for future patches because
it is easier
Processing control commands:
> severity -1 serious
Bug #911548 [lirc] lirc: unowned broken symlinks after purge:
/usr/lib/python3/dist-packages/lirc* ->
/usr/lib/i386-linux-gnu/python3.6/site-packages/lirc*
Severity set to 'serious' from 'important'
--
911548: https://bugs.debian.org/cgi-bin/b
Processing commands for cont...@bugs.debian.org:
> block 910954 by 907316
Bug #910954 [src:tomboy-latex] tomboy-latex: Intent to remove from Debian
910954 was not blocked by any bugs.
910954 was not blocking any bugs.
Added blocking bug(s) of 910954: 907316
>
End of message, stopping processing he
Package: glewlwyd
Version: 1.4.6-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install,
remove+purge, and install again.
Like a plain failure on initial install this makes the package too buggy
for a relea
Processing control commands:
> block 885657 by -1
Bug #885657 [src:rarian] rarian: Don't release with Buster
885657 was blocked by: 885608 885667 885113 885609 885114 885614 885636 885654
885536 885115 885637 885611 885112 885638 885632
885657 was not blocking any bugs.
Added blocking bug(s) of 8
Source: amide
Version: 1.0.5-11
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs rarian
Tags: sid buster patch
Control: block 885657 by -1
scrollkeeper has been deprecated and unmaintained for years. Its
replacement, rarian has been deprecated for years too.
Processing control commands:
> tags -1 patch
Bug #885112 [src:synaptic] synaptic: Don't depend on rarian
Added tag(s) patch.
--
885112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885112
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 patch
fix proposed at https://github.com/mvo5/synaptic/pull/34
Thanks,
Jeremy Bicha
Processing control commands:
> block -1 by 907316 911197 911199 911200 911202
Bug #911562 [src:gnome-sharp2] gnome-sharp2: Intent to remove from Debian
911562 was not blocked by any bugs.
911562 was not blocking any bugs.
Added blocking bug(s) of 911562: 911200, 911197, 911199, 911202, and 907316
Source: gnome-sharp2
Version: 2.24.2-4
Severity: serious
X-Debbugs-CC: joshi...@microsoft.com
Control: block -1 by 907316 911197 911199 911200 911202
I have filed intent to remove bugs for all the packages that depend on
gnome-sharp2 because gnome-sharp2 is one of the packages blocking the
removal
Control: retitle -1 tomboy: Intent to remove from Debian
On Sat, Oct 13, 2018 at 3:21 PM Jeremy Bicha wrote:
> I suggest that its maintainers strongly consider removing tomboy from
> Debian now as part of the libgnome removal process.
I am updating the bug title to indicate that I will ask for t
Processing control commands:
> retitle -1 tomboy: Intent to remove from Debian
Bug #907316 [src:tomboy] tomboy: Is tomboy still being maintained?
Changed Bug title to 'tomboy: Intent to remove from Debian' from 'tomboy: Is
tomboy still being maintained?'.
--
907316: https://bugs.debian.org/cgi-
* Pirate Praveen [2018-10-22 01:00]:
ignition-msgs should say libprotobuf-dev (>= 3.6~) and upload as
1.0.0+dfsg1-6
and ignition-transport should say libignition-msgs-dev (>= 1.0.0+dfsg1-6)
I don't agree, both worked fine with older protobuf versions and where
not touched for the migration.
Processing commands for cont...@bugs.debian.org:
> tags 897812 + ftbfs
Bug #897812 [src:mongodb] mongodb: ftbfs with GCC-8
Added tag(s) ftbfs.
> tags 909906 + ftbfs
Bug #909906 [jsurf-alggeo] jsurf-alggeo: Invalid regex passed to jh_installlibs
Added tag(s) ftbfs.
> thanks
Stopping processing here
On 10/22/18 12:27 AM, Jochen Sprickerhof wrote:
> * Pirate Praveen [2018-10-22 00:19]:
>> See point 2 of
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910964#29
>>
>> May be you want to tighten the build dependency versions.
>
> Do you have an example how to do that?
> I'm not the maintain
Package: apacheds
Version: 2.0.0~M24-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m43.2s ERROR: FAIL: Broken symlinks:
/usr
tags 885037 + patch
thanks
Attached are patches which remove the libgnome and gconfmm
dependencies. (I know nothing about C++ so please bear with me. The
code appears to work but is likely to have some issues like memory
management bugs.)
Apart from removing libgnome2-dev and libgconfmm-2.6-dev
Processing commands for cont...@bugs.debian.org:
> tags 885037 + patch
Bug #885037 [src:monster-masher] monster-masher: Please don't (Build-)Depend on
gconfmm2.6
Added tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
885037: https://bugs.debian.org/c
Source: ovirt-guest-agent
Version: 1.0.13.dfsg-2
Severity: serious
Tags: ftbfs
ovirt-guest-agent fails to build from source in unstable, because pep8
started producing failures:
| make check-local
| make[3]: Entering directory '/<>'
| /usr/bin/pep8 --exclude="ovirt-guest-agent/setup.py" --filena
Your message dated Sun, 21 Oct 2018 19:07:16 +
with message-id
and subject line Bug#853643: fixed in ripmime 1.4.0.10.debian.1-2
has caused the Debian Bug report #853643,
regarding ripmime: ftbfs with GCC-7
to be marked as done.
This means that you claim that the problem has been dealt with.
Processing commands for cont...@bugs.debian.org:
> tags 856086 + patch
Bug #856086 [src:monster-masher] monster-masher: Please drop the
(build-)dependency against esound
Added tag(s) patch.
> tags 848052 + patch
Bug #848052 [monster-masher] monster-masher: Sounds are not working (Invalid
argumen
tags 856086 + patch
tags 848052 + patch
thanks
Attached is a patch which works for me; it replaces
add-esound-as-dependency.patch. You only have to replace libesd0-dev
with libcanberra-dev in Build-Depends and also remove -lesd from
DEB_LDFLAGS_MAINT_APPEND.
Description: Remove esound dependency;
Your message dated Sun, 21 Oct 2018 19:04:18 +
with message-id
and subject line Bug#903324: fixed in adasockets 1.11.1-2
has caused the Debian Bug report #903324,
regarding adasockets: FTBFS in buster/sid (dh_installdocs: Cannot find
"README.Debian")
to be marked as done.
This means that you
* Pirate Praveen [2018-10-22 00:19]:
See point 2 of
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910964#29
May be you want to tighten the build dependency versions.
Do you have an example how to do that?
I'm not the maintainer, but could commit as a team member.
Cheers Jochen
signatur
Source: opencascade
Version: 7.3.0+dfsg1-3
Severity: serious
Tags: ftbfs
opencascade fails to build from source on amd64 with symbol error. The
output is too long to include in a mail. reproducible builds have a log
though:
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/openca
Hi Liubov,
thanks a lot for your patch. I've tested it and uploaded the package.
Happy that you persist in the team
Andreas.
--
http://fam-tille.de
Source: node-mocha
Version: 4.1.0+ds1-2
Severity: serious
Tags: ftbfs
node-mocha fails to build from source in sbuild on unstable/amd64. A
build log ends with:
|debian/rules override_dh_installdocs
| make[1]: Entering directory '/<>'
| jekyll build --source ./docs --destination ./docs/_site -
Your message dated Sun, 21 Oct 2018 18:50:41 +
with message-id
and subject line Bug#909530: fixed in t-coffee 11.00.8cbe486-8
has caused the Debian Bug report #909530,
regarding t-coffee: autopkgtest regression
to be marked as done.
This means that you claim that the problem has been dealt wi
On Sun, 21 Oct 2018 20:27:32 +0200 Jochen Sprickerhof
wrote:
> This bug seems to be caused by trying to compile ignition-transport
> against an old libignition-msgs-dev, compiled against protobuf 3.0. In
> the meantime libignition-msgs-dev was compiled against protobuf 3.6 (in
> version 1.0.0+d
Source: lavacli
Version: 0.9.2-1
Severity: serious
Tags: ftbfs patch
lavacli fails to build from source in unstable. Here is a build log:
| dpkg-buildpackage: info: source package lavacli
| dpkg-buildpackage: info: source version 0.9.2-1
| dpkg-buildpackage: info: source distribution unstable
| d
Processing commands for cont...@bugs.debian.org:
> forwarded 910858 https://github.com/tpm2-software/tpm2-tss/issues/1171
Bug #910858 [src:tpm2-tss] tpm2-tss: FTBFS on big endian architectures: test
failures
Set Bug forwarded-to-address to
'https://github.com/tpm2-software/tpm2-tss/issues/1171'.
forwarded 910858 https://github.com/tpm2-software/tpm2-tss/issues/1171
thanks
On 12.10.2018 14:48, Emilio Pozuelo Monfort wrote:
> Source: tpm2-tss
> Version: 2.1.0-1
> Severity: serious
> Tags: ftbfs
>
> Hi,
>
> Your package failed to build on big endian architectures:
>
> [ RUN ] tpm2b_u
Your message dated Sun, 21 Oct 2018 20:27:32 +0200
with message-id <20181021182732.GA11157@vis>
and subject line Re: Bug#900429: protobuf 3.5.2 transition and
ignition-transport
has caused the Debian Bug report #900429,
regarding protobuf 3.5.2 transition and ignition-transport
to be marked as don
On 21/10/2018 20:19, Moritz Mühlenhoff wrote:
> On Sun, Sep 10, 2017 at 01:43:08PM +0200, Vincent Danjean wrote:
>> severity 874882 grave
>> tag 874882 +help
>> thanks
>>
>> Hi,
>>
>> Unless someone step up to maintain (debian and upstream) this
>> program, I will ask for its removal. Upstream
Your message dated Sun, 21 Oct 2018 18:34:09 +
with message-id
and subject line Bug#899503: fixed in fcitx-punc-ng 0.1.1~git20161101-2
has caused the Debian Bug report #899503,
regarding fcitx-punc-ng: Invalid maintainer address
pkg-ime-de...@lists.alioth.debian.org
to be marked as done.
Thi
On Sun, Sep 10, 2017 at 01:43:08PM +0200, Vincent Danjean wrote:
> severity 874882 grave
> tag 874882 +help
> thanks
>
> Hi,
>
> Unless someone step up to maintain (debian and upstream) this
> program, I will ask for its removal. Upstream is long dead. I
> kept this program in Debian while th
[2018-10-21 10:44] Andreas Beckmann
> Package: dvtm
> Version: 0.15-3~bpo9+1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> during a test with piuparts I noticed your package is not
> installable in stretch-backports:
> ncurses-term | 6.0+20161126-1+deb9u2 | stab
Hello Axel,
what CPU is inside the machine producing this cores?
Could you please check if your CPU supports avx2 instructions.
If an internet search tells me right this line should show
"avx2" for each core if yes:
grep -o 'avx[^ ]*' /proc/cpuinfo
Kind regards,
Bernhard
On Fri, Oct 12, 2018 at 08:07:48PM -0400, Afif Elghraoui wrote:
>
>
> على ٣/٢/١٤٤٠ هـ ٤:٣٣ م، كتب Moritz Mühlenhoff:
> > On Fri, Oct 13, 2017 at 12:52:55AM -0400, Afif Elghraoui wrote:
> > >
> > >
> >
> > What's the status? ori hasn't been uploaded since 21 months, is there
> > any progress
Hello,
just trying to reproduce the crash, but it does not happen for me
with the sequnce from the man page like below.
Could you probably provide some more information.
Either an minimal example database and selects that triggers the crash.
Or just a backtrace from an attached debugger.
You find
Your message dated Sun, 21 Oct 2018 17:04:55 +
with message-id
and subject line Bug#892350: fixed in m17n-lib 1.8.0-2
has caused the Debian Bug report #892350,
regarding m17n-lib: Please use 'pkg-config' to find FreeType 2
to be marked as done.
This means that you claim that the problem has b
Your message dated Sun, 21 Oct 2018 17:04:45 +
with message-id
and subject line Bug#902220: fixed in aspectc++ 1:2.2+git20181008-1
has caused the Debian Bug report #902220,
regarding Needs porting to LLVM 6.0.1
to be marked as done.
This means that you claim that the problem has been dealt wi
Upgrading from 20141022 to 20180922 seems to address all issues.
Can we close this ticket?
#884793 was due to user error, thus not breaking scripts. I still have
not seen a single situation in which the current behaviour (version
20180922) breaks scripts when used correctly. Make a Minimal,
Compl
Package: src:haskell-parsec
Version: 3.1.13.0-1
Severity: serious
parsec 3.1.13.0 is now bundled with ghc and this version should
not be shipped separately in buster.
Hi Holger,
Quoting Holger Levsen (2018-10-21 12:13:11)
> thanks for uploading monero 0.13.0.3-1! However you didn't seem to address
> #910517 "monero: FTBFS on i386: compiler runs our of memory" (which
> has a patch) so I believe monero will still FTBFS on i386 and thus not
> migrate to testing.
Your message dated Sun, 21 Oct 2018 15:20:31 +
with message-id
and subject line Bug#911440: fixed in syncthing 0.14.51+ds2-4
has caused the Debian Bug report #911440,
regarding syncthing: FTBFS too many arguments in call to
prometheus.NewProcessCollector
to be marked as done.
This means that
Quoting Ivo De Decker (2018-10-21 14:28:37)
> On 10/21/18 1:06 PM, Samuel Thibault wrote:
> > Jonas Smedegaard, le dim. 21 oct. 2018 12:56:02 +0200, a ecrit:
> >> I am clueless why that happens. Not sure, but I suspect it is a
> >> spurious error happening occationally and if so that a workaround
Your message dated Sun, 21 Oct 2018 15:05:32 +
with message-id
and subject line Bug#887600: fixed in asc 2.6.1.0-5
has caused the Debian Bug report #887600,
regarding asc: Detect freetype using pkg-config
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Downgrade fontconfig and libfontconfig from 2.13.1 to 2.13.0 solves
problem.
I have same freezes with CPU usage in other applications like Gimp and
Inkscape.
Here is blog post with some relaited info:
https://www.preining.info/blog/2018/10/firefox-got-maniac/
Source: open-build-service
Followup-For: Bug #903797
I checked 2.7 branch on upstream git. There was a merge for fixing
"Handle links properly when doing backend build operations". Do not
seems upstream also applied CVE-2018-7689 fix for 2.7.4.
https://github.com/openSUSE/open-build-service/co
Processing commands for cont...@bugs.debian.org:
> forwarded 911440 https://github.com/syncthing/syncthing/issues/5280
Bug #911440 [src:syncthing] syncthing: FTBFS too many arguments in call to
prometheus.NewProcessCollector
Set Bug forwarded-to-address to
'https://github.com/syncthing/syncthing
Control: tag -1 pending
Hello,
Bug #887600 in asc 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/games-team/asc/commit/1aa202ed8e2470b7845cae2b421ed643c767675
Processing control commands:
> tag -1 pending
Bug #887600 [asc] asc: Detect freetype using pkg-config
Added tag(s) pending.
--
887600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887600
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Sun, 21 Oct 2018 14:43:50 +
with message-id
and subject line Bug#899763: fixed in fcitx-fullwidthchar-enhance
0.0~git20150311-2
has caused the Debian Bug report #899763,
regarding fcitx-fullwidthchar-enhance: Invalid maintainer address
pkg-ime-de...@lists.alioth.debian.org
Your message dated Sun, 21 Oct 2018 13:49:30 +
with message-id
and subject line Bug#909542: fixed in opam 2.0.0-5
has caused the Debian Bug report #909542,
regarding opam: FTBFS when built with dpkg-buildpackage -A
to be marked as done.
This means that you claim that the problem has been deal
Your message dated Sun, 21 Oct 2018 13:49:30 +
with message-id
and subject line Bug#910222: fixed in opam 2.0.0-5
has caused the Debian Bug report #910222,
regarding opam: copyright file missing after upgrade (policy 12.5)
to be marked as done.
This means that you claim that the problem has b
On 2018-10-17 11:06, Debian Bug Tracking System wrote:
>* Create a new libtirpc-common package and move /etc/netconfig and
> netconfig.5 to it, do not conflit with libtirpc1 to ease the
> co-installation of libtirpc1 and libtirpc3 (Closes: #884029)
Once the transition is finished, pl
Processing control commands:
> severity -1 wishlist
Bug #905836 [openjdk-10-jre-headless] Uninstallable on a Clean Sid -
update-alternatives Fails to Create a Symbolic Link
Severity set to 'wishlist' from 'grave'
> tags -1 + wontfix
Bug #905836 [openjdk-10-jre-headless] Uninstallable on a Clean S
Control: severity -1 wishlist
Control: tags -1 + wontfix
No, this is not a clean sid install, it has the the man pages stripped. You
should report that to the provider of update-alternatives. There is nothing
that can be done in the openjdk packages.
Your message dated Sun, 21 Oct 2018 14:28:37 +0200
with message-id
and subject line Re: Bug#911522: ghostscript: FTBFS on amd64, i386
has caused the Debian Bug report #911522,
regarding ghostscript: FTBFS on amd64, i386
to be marked as done.
This means that you claim that the problem has been dea
Processing control commands:
> tags -1 moreinfo
Bug #911481 {Done: Alf Gaida } [libkrb5support0]
libkrb5support0:i386 has broken dependencies
Added tag(s) moreinfo.
> severity -1 normal
Bug #911481 {Done: Alf Gaida } [libkrb5support0]
libkrb5support0:i386 has broken dependencies
Severity set to
control: tags -1 moreinfo
control: severity -1 normal
Hi. Your bug is a little short on details, and I was not able to
reproduce. I took a new sid chroot, added i386 as an architecture, and
installed libkrb5support0:i386 by
apt install libkrb5support0:i386
I ended up with krb5 1.16.1-1 and lib
Control: retitle 911517 gimp: Crashes at startup due to deb-multimedia.org
libbabl with epoch
Control: tags 911517 + wontfix
On Sun, 21 Oct 2018 at 11:00:02 +0200, Adrian Immanuel Kiess wrote:
> gimp: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgegl-0.4.so.0:
> undefined symbol: babl_format
Your message dated Sun, 21 Oct 2018 12:10:11 +0100
with message-id <2018102011.ga...@espresso.pseudorandom.co.uk>
and subject line Re: Bug#911517: gimp: Crashes at startup with symbol lookup
error
has caused the Debian Bug report #911517,
regarding gimp: Crashes at startup with symbol lookup e
Processing control commands:
> retitle 911517 gimp: Crashes at startup due to deb-multimedia.org libbabl
> with epoch
Bug #911517 {Done: Simon McVittie } [gimp] gimp: Crashes at
startup with symbol lookup error
Changed Bug title to 'gimp: Crashes at startup due to deb-multimedia.org
libbabl wit
Jonas Smedegaard, le dim. 21 oct. 2018 12:56:02 +0200, a ecrit:
> I am clueless why that happens. Not sure, but I suspect it is a
> spurious error happening occationally and if so that a workaround is
> to simply request a binNMU.
>
> Help dearly appreciated either requesting a binNMU (by someo
Processing control commands:
> tags -1 help
Bug #911522 [src:ghostscript] ghostscript: FTBFS on amd64, i386
Added tag(s) help.
--
911522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911522
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 help
Hi Ivo,
Quoting Ivo De Decker (2018-10-21 12:08:43)
> The latest version of ghostscript in unstable fails on amd64, i386:
>
> https://buildd.debian.org/status/package.php?p=ghostscript
Thanks for reporting!
I am clueless why that happens. Not sure, but I suspect it is a
Your message dated Sun, 21 Oct 2018 10:34:31 +
with message-id
and subject line Bug#908854: fixed in gazebo 9.0.0+dfsg5-5
has caused the Debian Bug report #908854,
regarding gazebo FTBFS with protobuf 3.6 (fixed upstream in 9.2)
to be marked as done.
This means that you claim that the problem
On Tue, Sep 25, 2018 at 11:29:28PM +0200, Sebastian Andrzej Siewior wrote:
> On 2018-08-25 10:33:54 [+0200], Kurt Roeckx wrote:
> > On Fri, Jun 01, 2018 at 11:22:09AM +, Sandro Knauß wrote:
> > > Source: kopete
> > > Source-Version: 4:18.04.1-1
> > >
> > > We believe that the bug you reported
Your message dated Sun, 21 Oct 2018 10:19:30 +
with message-id
and subject line Bug#910217: fixed in apparmor 2.13.1-1
has caused the Debian Bug report #910217,
regarding apparmor: removed shipped file: /var/cache/apparmor/CACHEDIR.TAG
to be marked as done.
This means that you claim that the
1 - 100 of 123 matches
Mail list logo
