Processing commands for cont...@bugs.debian.org:
> severity 897947 important
Bug #897947 [mikutter] mikutter: Twitter Consumer Key/Secret (CK/CS) suspended
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
897947:
Package: mikutter
Version: 3.6.7+dfsg-1
Severity: grave
mikutter's Twitter Consumer Key/Secret (CK/CS) has been suspended since
2018/5/4 morning (JST). So mikutter cannot be authenticated by Twitter
and mikutter users cannot use Twitter by mikutter.
mikutter users can replace them with their own
Processing commands for cont...@bugs.debian.org:
> Tags 897114 +patch
Bug #897114 [src:ifrit] ifrit FTBFS with cmake 3.11.1
Added tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
897114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897114
Debian
Tags 897114 +patch
thanks
This was blocking a transition in raspbian, so I whipped up a fix. Debdiff at
http://debdiffs.raspbian.org/main/i/ifrit/ifrit_4.1.2-5%2brpi1.debdiff , no
intent to NMU in Debian.
The only tricky bit was that there seems to have been a typo in debian/rules,
there was
Processing commands for cont...@bugs.debian.org:
> reassign 895292 systemd-shim
Bug #895292 [systemd] Restart, Suspend, Hibernate, Shut Down all greyed out in
lightdm
Bug reassigned from package 'systemd' to 'systemd-shim'.
No longer marked as found in versions systemd/238-4.
Ignoring request to
Package: visualvm
Version: 1.3.9-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
visualvm will not start since upgrade of libnb-*-java to 8.1+dfsg1-8. It just
pauses at the splash screen for a while and then exits with code 2. strace
suggests it tries some sort of
Your message dated Sat, 05 May 2018 00:49:32 +
with message-id
and subject line Bug#895863: fixed in python-acme 0.24.0-2
has caused the Debian Bug report #895863,
regarding python-acme: Unroutable maintainer address
to be marked as done.
This means that
Am Freitag, den 04.05.2018, 12:59 +0200 schrieb Andreas Beckmann:
> during a test with piuparts I noticed your package uses a very generic
> python module name that now clashes with other packages:
>
> /usr/lib/python3/dist-packages/scripts/__init__.py
Thanks for the hint. I agree, that this
Followup-For: Bug #887135
Control: reassign -1 wnpp
Control: retitle -1 O: manpages-pt -- Portuguese Versions of the Manual Pages
Control: severity -1 normal
more than 3 months have passed without reaction to this bug,
therefore orphaning it now on behalf of the MIA team.
--
tobi
-- System
Processing control commands:
> reassign -1 wnpp
Bug #887135 [src:manpages-pt] manpage-pt: Is package unmaintained?
Bug reassigned from package 'src:manpages-pt' to 'wnpp'.
No longer marked as found in versions manpages-pt/20040726-4.
Ignoring request to alter fixed versions of bug #887135 to the
Processing commands for cont...@bugs.debian.org:
> found 897482 1.2.3-2
Bug #897482 [src:brailleutils] brailleutils: FTBFS: [javac]
/<>/src/org/daisy/braille/pef/PEFNamespaceContext.java:37: error:
PEFNamespaceContext is not abstract and does not override abstract method
Hi Sergei,
On Wed, May 02, 2018 at 06:25:55PM +, Sergei Golovan wrote:
> Hi Bruno,
>
> If you have access to the ppc64el hardware, could you test the fix (I've
> attached a diff, which is to be applied to the 2.1.0-15 sources)? If it's
> okay, I'll ask the release team about a stable update.
Your message dated Fri, 04 May 2018 19:50:06 +
with message-id
and subject line Bug#897458: fixed in mongo-java-driver 3.6.3-1
has caused the Debian Bug report #897458,
regarding mongo-java-driver: FTBFS: ManualTaglet.java:17: error: package
Just thinking: Maybe it does indeed have something to do with the size
of u-boot. The one from bodhi is 524 KB, whereas the Debian one is 599 KB.
Am 04.05.2018 um 20:40 schrieb Markus Krebs:
Interesting thoughts, but: I tried again flashing both from within
Debian and from u-boot (using
* Markus Krebs [2018-05-04 20:40]:
> Interesting thoughts, but: I tried again flashing both from within Debian
> and from u-boot (using ${filesize}). $filesize is accepted and flashing
> works, but the plug doesn't boot.
> Flashing (again with $filesize, just to confirm it
It looks like the relevant part of the log is:
,
| nodejs tools/build.js --release --no-minify
| module.js:549
| throw err;
| ^
|
| Error: Cannot find module 'acorn/walk'
| ...
`
It looks like acorn moved some things around, and acorn/walk is now
acorn/dist/walk. It seems to
Processing commands for cont...@bugs.debian.org:
> tags 896840 + pending
Bug #896840 [src:lintian] lintian: testsuite failures with file 5.33
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
896840:
tags 896840 + pending
thanks
Hi all,
> lintian: testsuite failures with file 5.33
Just went to look into this further and realised that I had lost:
< dwfreed> lamby: "pie executable" did not exist as a possible output
of file before this release
< lamby> dwfreed: Can you
Interesting thoughts, but: I tried again flashing both from within
Debian and from u-boot (using ${filesize}). $filesize is accepted and
flashing works, but the plug doesn't boot.
Flashing (again with $filesize, just to confirm it works) the u-boot
from bodhi-linux (the one I was referring to)
Your message dated Fri, 04 May 2018 18:34:52 +
with message-id
and subject line Bug#881749: fixed in bundler 1.16.1-2
has caused the Debian Bug report #881749,
regarding redmine: creates world-writable tempdir /tmp/bundler/home
to be marked as done.
This
Your message dated Fri, 4 May 2018 20:18:59 +0200
with message-id <4aec5f69-f7bc-d855-3722-1b116d7ce...@debian.org>
and subject line rsvg_pixbuf_from_file_at_size broken in recent librsvg2-2
has caused the Debian Bug report #886833,
regarding rsvg_pixbuf_from_file_at_size broken in recent
Your message dated Fri, 4 May 2018 19:40:44 +0200
with message-id
and subject line
has caused the Debian Bug report #896656,
regarding libsynctex1: Texmaker-libsynctex1:amd64 2018.20180416.47457-1
to be marked as done.
This means that you
Your message dated Fri, 4 May 2018 19:40:44 +0200
with message-id
and subject line
has caused the Debian Bug report #896656,
regarding texmaker: Texmaker fails to start due to new libsynctex1
to be marked as done.
This means that you claim
Your message dated Fri, 4 May 2018 19:40:44 +0200
with message-id
and subject line
has caused the Debian Bug report #896656,
regarding texmaker does notr start "symbol lookup error" and "undefined symbol:
synctex_next_result"
to be marked as
Your message dated Fri, 4 May 2018 19:40:44 +0200
with message-id
and subject line
has caused the Debian Bug report #896567,
regarding texmaker: FTBFS against newer libsyntex
to be marked as done.
This means that you claim that the problem has
Your message dated Fri, 04 May 2018 17:34:44 +
with message-id
and subject line Bug#897466: fixed in bart 0.4.03-2
has caused the Debian Bug report #897466,
regarding bart-view: FTBFS: multind.h:17:10: fatal error: misc/nested.h: No
such file or directory
* Vagrant Cascadian [2018-05-04 08:40]:
> I do recall that there was some incompatible change regarding the
> environment size on some of the marvell platforms, as u-boot.kwb grew
> large enough to overwrite the environment section.
Uh, this might not be an u-boot issue then
Processing control commands:
> reassign -1 bart
Bug #897466 [src:bart-view] bart-view: FTBFS: multind.h:17:10: fatal error:
misc/nested.h: No such file or directory
Bug reassigned from package 'src:bart-view' to 'bart'.
No longer marked as found in versions bart-view/0.1.00-1.
Ignoring request
Control: reassign -1 bart
On Thu, May 03, 2018 at 08:21:35PM +, Uecker, Martin wrote:
>
> this is now fixed in the git repo for bart (not bart-view!).
Bug reassigned by this mail - will upload soon.
Thanks a lot for the quick fix
Andreas.
--
http://fam-tille.de
Processing control commands:
> tag -1 pending
Bug #897898 [openldap] libldap-common is missing
Added tag(s) pending.
--
897898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897898
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Uploaded new packages. Builds are underway now and should become
available in unstable after the 19:52 UTC dinstall run.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello Moritz,
first thanks for your work.
Am Freitag, den 04.05.2018, 14:36 +0200 schrieb Moritz Muehlenhoff:
> B0;115;0cOn Fri, May 04, 2018 at 02:21:41PM +0200, Moritz Muehlenhoff
> wrote:
> > On Wed, May 02, 2018 at 12:02:03PM +0200, Moritz
On 2018-05-04, Martin Michlmayr wrote:
> * Markus Krebs [2018-05-04 06:33]:
>> Version: 2018.03+dfsg1-2
>>
>> The u-boot.kwb provided at https://forum.doozan.com/read.php?3,12381 works.
>
> That is version 2017.07. If you have time, could you try some
>
Control: tag -1 pending
Hello,
Bug #897149 in apt 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/apt-team/apt/commit/39d9e217a22901892647499ee695ba472a111d25
Processing control commands:
> tag -1 pending
Bug #897149 [src:apt] Package erroneously expects googletest headers in
/usr/include
Bug #897459 [src:apt] apt: FTBFS:
./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8:
undefined reference
Hi,
On 03/05/18 16:27, Alberto Molina Coballes wrote:
> Thanks James, these kinds of errors are often difficult to deal with.
>
> Do you think that it should be enough disabling parallel build in dh?
> Tested on amd64 seems to work properly.
Yes that should workaround the problem.
It seems to
Your message dated Fri, 04 May 2018 15:13:25 +
with message-id
and subject line Bug#897483: fixed in ust 2.10.1-3
has caused the Debian Bug report #897483,
regarding ust: FTBFS: LTTngUst.c:20:10: fatal error: org_lttng_ust_LTTngUst.h:
No such file or
Processing control commands:
> fixed -1 3.7-1
Bug #897525 [libcommons-lang3-java] access-modifier-checker: FTBFS: Failed to
execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar
Marked as fixed in versions libcommons-lang3-java/3.7-1.
> close -1
Bug #897525 [libcommons-lang3-java]
Control: fixed -1 3.7-1
Control: close -1
Processing commands for cont...@bugs.debian.org:
> retitle 893167 eboard: stack smashing & source repository update
Bug #893167 [eboard] Stack smashing protection trigged in eboard
Changed Bug title to 'eboard: stack smashing & source repository update' from
'Stack smashing protection trigged in
Processing commands for cont...@bugs.debian.org:
> severity 897898 grave
Bug #897898 [openldap] libldap-common is missing
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
897898:
Hi Lucas,
On Wed, May 02, 2018 at 10:52:53PM +0200, Lucas Nussbaum wrote:
>
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
>
> Relevant part (hopefully):
> > rx/perf.ok
> > volser/vos-man..ok
> > volser/vos..FAILED 5
> >
Processing commands for cont...@bugs.debian.org:
> forwarded 897644 https://github.com/spacetelescope/gwcs/pull/119
Bug #897644 [python-gwcs] python-gwcs depends on cruft package python-asdf
Set Bug forwarded-to-address to
'https://github.com/spacetelescope/gwcs/pull/119'.
> thanks
Stopping
B0;115;0cOn Fri, May 04, 2018 at 02:21:41PM +0200, Moritz Muehlenhoff wrote:
> On Wed, May 02, 2018 at 12:02:03PM +0200, Moritz Muehlenhoff wrote:
> > Hi Jörg,
> >
> > On Mon, Apr 30, 2018 at 09:59:11PM +0200, Jörg Frings-Fürst wrote:
> > >
> > > for the liboinig transition I testing the build
On Wed, May 02, 2018 at 12:02:03PM +0200, Moritz Muehlenhoff wrote:
> Hi Jörg,
>
> On Mon, Apr 30, 2018 at 09:59:11PM +0200, Jörg Frings-Fürst wrote:
> >
> > for the liboinig transition I testing the build of hhvm again libonig
> > 6.8.1-1.
> >
> > The build fails with
> >
> > [quote]
> > In
Your message dated Fri, 04 May 2018 12:04:46 +
with message-id
and subject line Bug#897501: fixed in xmds2 2.2.3+dfsg-6
has caused the Debian Bug report #897501,
regarding xmds2: FTBFS: tests failed
to be marked as done.
This means that you claim that the
* Markus Krebs [2018-05-04 06:33]:
> Version: 2018.03+dfsg1-2
>
> The u-boot.kwb provided at https://forum.doozan.com/read.php?3,12381 works.
That is version 2017.07. If you have time, could you try some
versions from http://snapshot.debian.org/package/u-boot/ Not all of
Package: python3-hbmqtt
Version: 0.9.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package uses a very generic
python module name that now clashes with other packages:
/usr/lib/python3/dist-packages/scripts/__init__.py
Package: python3-cclib
Version: 1.5.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package uses a very generic
python module name that now clashes with other packages:
/usr/lib/python3/dist-packages/scripts/__init__.py
Your message dated Fri, 04 May 2018 10:51:41 +
with message-id
and subject line Bug#896796: fixed in vulkan 1.1.73+dfsg-1
has caused the Debian Bug report #896796,
regarding vulkan: missing build dependency on python3-distutils
to be marked as done.
This
On Wed, May 02, 2018 at 11:02:55PM +0200, Valentin Vidic wrote:
> Thanks, I can reproduce the errors too and will try to figure it out.
> The build was definitely working less than month ago when the last
> version was released, so something else in the system has changed.
After updating
Hi,
since version 2, upstream of asdf does no longer support Python 2 [1];
therefore it is removed from the package. I therefore would recommend to
also remove the Python 2 version of gwcs.
[1] http://asdf.readthedocs.io/en/latest/asdf/changes.html
Best regards
Ole
On 07.03.2018 13:13, James Cowgill wrote:
> 3dldf FTBFS on the above architectures with the error:
>> ../src/3dldf tngnts_1.ldf
>> GNU 3DLDF Version 2.0.3
>> Copyright (C) 2013 The Free Software Foundation
>> Author: Laurence D. Finston
>>
Just for the records: I tried to build the package
> dblatex converts a ` (back-tick) from the xml input from into \`{} in
> the LaTeX source. AFAIK (I'm not 100% sure) this was never correct, the
This was a bug in xecjk which is already fixed, will be in one of the
next uploads.
Norbert
--
PREINING Norbert
Processing commands for cont...@bugs.debian.org:
> reassign 897661 texmaker
Bug #897661 [libsynctex1] libsynctex1: Texmaker-libsynctex1:amd64
2018.20180416.47457-1
Bug reassigned from package 'libsynctex1' to 'texmaker'.
No longer marked as found in versions texlive-bin/2018.20180416.47457-1.
Your message dated Fri, 04 May 2018 08:00:33 +
with message-id
and subject line Bug#896733: fixed in nosexcover 1.0.11-1.1
has caused the Debian Bug report #896733,
regarding nosexcover: missing build dependency on dh-python
to be marked as done.
This
On 04/28/2018 03:15 PM, Adrian Bunk wrote:
> Source: ppl
> Version: 1:1.2-2
> Severity: serious
>
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ppl.html
>
> ...
> pl-1.2/doc/bugseng_logo.pdf>] [4] [1] [2] (./index.tex
> Underfull \hbox (badness 1) detected at line 9
>
Processing control commands:
> reassign -1 libpoppler-glib8 0.63.0-2
Bug #897464 [src:ruby-cairo] ruby-cairo: FTBFS: ERROR: Test "ruby2.5" failed:
Error: test: time(PDFSurfaceTest::#set_metadata::modified date):
Poppler::Error::Invalid: Failed to load document
Bug reassigned from package
Control: reassign -1 libpoppler-glib8 0.63.0-2
Control: forcemerge 896596 -1
--
Regards,
dai
GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839 619D D439 668E
signature.asc
Description: PGP signature
Source: libtcd
Version: 2.2.2-2
Severity: serious
Tags: buster sid
Hi,
Your package is not binNMU safe. This is reported by the lintian tag
https://lintian.debian.org/tags/not-binnmuable-any-depends-any.html
Basically your package libtcd-dev has:
Depends: libtcd0 (= ${source:Version})
That
Source: p7zip-rar
Version: 16.02-1
Severity: grave
Tags: security upstream
Hi,
The following vulnerability was published for p7zip-rar.
CVE-2018-10115[0]:
| Incorrect initialization logic of RAR decoder objects in 7-Zip 18.03
| and before can lead to usage of uninitialized memory, allowing
61 matches
Mail list logo