Processing control commands:
> severity -1 wishlist
Bug #920714 [src:lombok] lombok: Build-Depends on openjdk-8-jdk which will no
be in buster
Severity set to 'wishlist' from 'serious'
--
920714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920714
Debian Bug Tracking System
Contact
Control: severity -1 wishlist
Hi Andreas,
Actually lombok is the exception that is forcing us to ship (but not
support) openjdk-8-jdk in Buster. It's a build time only dependency,
lombok works with OpenJDK 11 at runtime.
Emmanuel Bourg
I've been busy, sorry - feel free to team upload/NMU it but I'm hoping to get
to it this weekend.
--
Geoffrey Thomas (via mobile)
geo...@ldpreload.com
> On Jan 28, 2019, at 08:56, Raphael Hertzog wrote:
>
> Hi,
>
>> On Sun, 24 Jun 2018, Geoffrey Thomas wrote:
>> Upstream is being slow to
Processing control commands:
> block 920037 with -1
Bug #920037 [src:openjdk-8] Don't include in buster
920037 was not blocked by any bugs.
920037 was not blocking any bugs.
Added blocking bug(s) of 920037: 920714
--
920037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920037
920714:
Source: lombok
Version: 1.16.22-6
Severity: serious
Control: block 920037 with -1
Hi,
your package still Build-Depends on openjdk-8-jdk which will not be part
of buster.
Andreas
Processing control commands:
> tag -1 pending
Bug #919876 [src:java-string-similarity] javadoc: The code being documented
uses modules but the packages defined in … are in the unnamed module
Added tag(s) pending.
--
919876: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919876
Debian Bug
Control: tag -1 pending
Hello,
Bug #919876 in java-string-similarity 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:
Control: tag -1 pending
Hello,
Bug #920188 in twitter-bootstrap4 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 #920188 [libjs-bootstrap4] broken: required library Popper.js missing
Ignoring request to alter tags of bug #920188 to the same tags previously set
--
920188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920188
Debian Bug Tracking System
Source: r-cran-repr
Version: 0.19.1-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Since the upload of r-cran-tibble 2.0.0-1 to unstable, r-cran-repr has
been failing its autopkgtests [1] with the following
Source: r-cran-repr
Version: 0.19.1-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Since the upload of r-cran-tibble 2.0.0-1 to unstable, r-cran-repr has
been failing its autopkgtests [1] with the following
Hi Guillem,
do you have any recommendations for this trigger loop?
I think at this point it is already dpkg 1.19.4 that is running
(dpkg is being upgraded during the same run).
On 2019-01-28 14:32, Christian Marillat wrote:
> On 28 janv. 2019 14:17, Andreas Beckmann wrote:
>
>> Package:
Hi,
On Sun, 24 Jun 2018, Geoffrey Thomas wrote:
> Upstream is being slow to put out a new release, there's some blocker
> involving the new freetds. I asked if that was resolved yet:
>
> https://github.com/pymssql/pymssql/issues/528
>
> At some point (probably in a month or two, honestly...)
Your message dated Mon, 28 Jan 2019 14:53:33 +0100
with message-id <3fbe04a7-64ec-05db-ee9d-5e0e3b7a7...@debian.org>
and subject line Re: Bug#907997: emacs-lucid: trying to overwrite
'/usr/share/emacs/25.2/etc/DOC', which is also in package emacs25 25.2+1-6+b2
has caused the Debian Bug report
Processing control commands:
> tag -1 pending
Bug #911616 [emacs-nox,emacs-gtk,emacs-lucid] emacs-common: copyright file
missing after upgrade of emacs-nox from stretch
Added tag(s) pending.
> tag 875430 pending
Bug #875430 [emacs25] emacs25: please add Breaks: edb (<< 1.32)
Added tag(s)
Followup-For: Bug #911616
Control: tag -1 pending
Control: tag 875430 pending
Control: tag 910925 pending
Control: tag 690771 pending
Control: tag 918646 pending
Hi Rob,
this issue is cuasing a lot of upgrade failures in piuparts.
I've prepared a NMU of the emacs package fixing this and some
On 28 janv. 2019 14:17, Andreas Beckmann wrote:
> Package: distcc
> Version: 3.3.2-7
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
>
> Hi,
>
> during a test with piuparts I noticed your package fails to upgrade from
> 'testing'.
> It installed fine in 'testing',
Processing commands for cont...@bugs.debian.org:
> severity 907754 important
Bug #907754 [src:webdis] webdis: FTBFS on i386, mips64el
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
907754:
On Sat, 1 Sep 2018 14:46:57 +0200 Mattia Rizzolo wrote:
> Source: webdis
> Version: 0.1.4+dfsg-1
> Severity: serious
>
> Dear maintainer,
>
> the package FTBFS on the buildds on i386 and mips64el:
It since built on i386 and the mips64el binary has been removed, so
downgrading to important.
Package: distcc
Version: 3.3.2-7
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails.
>From the attached log (scroll to the
Control: tag -1 - experimental
Control: close -1
There is no longer an outdated version in experimental.
Andreas
Processing control commands:
> tag -1 - experimental
Bug #785990 [src:distcc] distcc: deprecation of python-support
Removed tag(s) experimental.
> close -1
Bug #785990 [src:distcc] distcc: deprecation of python-support
Marked Bug as done
--
785990:
Package: python-jupyter-sphinx-theme
Version: 0.0.6+ds1-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually
Processing control commands:
> affects -1 + xtables-addons-dkms
Bug #917905 [xtables-addons-source] Fails to build for non-current kernel
version
Added indication that 917905 affects xtables-addons-dkms
> severity -1 serious
Bug #917905 [xtables-addons-source] Fails to build for non-current
Your message dated Mon, 28 Jan 2019 12:51:45 +
with message-id
and subject line Bug#920018: fixed in systemd 240-5
has caused the Debian Bug report #920018,
regarding Memory Leak in journald? Failed to write entry (23 items, 500
bytes), ignoring: Cannot allocate memory
to be marked as done.
Your message dated Mon, 28 Jan 2019 12:51:45 +
with message-id
and subject line Bug#919390: fixed in systemd 240-5
has caused the Debian Bug report #919390,
regarding udev: network interface gets ID_NET_NAME even when NAME has been set
by /etc/udev/rules.d/70-persistent-net.rules
to be
Source: python3.6
Severity: serious
We want to ship buster with python3.7 as the only python3 version. This bug
shall prevent python3.6 from re-entering testing.
Emilio
On Sun, 27 Jan 2019 15:10:39 -0500 Chris Manougian wrote:
> Hi Toni. I have an XPS 15 9570, which, I think, is basically the same
> machine, except yours uses an NVIDIA Quadro vs my GeForce GTX 1050Ti as a
> 2nd graphics card.
>
> A lot of problems with that secondary graphics card and linux.
Hi Alastair,
On Mon, Jan 28, 2019 at 09:50:30AM +, Alastair McKinstry wrote:
>Hi
>
>Yes, thanka for this patch. I'm reluctant to consider that binaries built on
>armhf failing on arm64 is an _RC Bug_, but its definitely undesirable.
It's not *yet* RC, but it's going to go that way soon. Our
Package: python3-adios
Version: 1.13.1-14
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails.
>From the attached log (scroll
[2019-01-23 12:41] Jonathan Nieder
> Dmitry Bogatov wrote:
> >> Jonathan Nieder wrote:
>
> >>> + * git-daemon-run: pre-create supervise directory so that postinst
> >>> +can start the service (thx Celejar and Dmitry Bogatov; closes:
> >>> +#919296).
> [...]
> > Wierd. It should work.
Processing control commands:
> tag -1 pending
Bug #916286 [src:traverso] traverso: baseline violation on i386
Added tag(s) pending.
--
916286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916286
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #916286 in traverso 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 Mon, 28 Jan 2019 12:21:27 +
with message-id
and subject line Bug#920662: fixed in orthanc-mysql 2.0-2
has caused the Debian Bug report #920662,
regarding orthanc-mysql: uses $(DEB_VERSION) as SOVERSION
to be marked as done.
This means that you claim that the problem has
Processing control commands:
> severity -1 normal
Bug #919962 [goaccess] Errors caused by not installing Recommend packages
Severity set to 'normal' from 'serious'
> retitle -1 goaccess: absence of optional packages looks like an error, but
> it's not
Bug #919962 [goaccess] Errors caused by not
Control: severity -1 normal
Control: retitle -1 goaccess: absence of optional packages looks like an error,
but it's not
On Sun, Jan 20, 2019 at 03:57:22PM +0800, 積丹尼 Dan Jacobson wrote:
> X-Debbugs-Cc: goacc...@prosoftcorp.com
> Package: goaccess
> Version: 1:1.2-4
>
> Versions of packages
Source: knot-resolver
Version: 2.3.0-3~bpo9+1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
User: debian...@lists.debian.org
Processing control commands:
> tags -1 moreinfo
Bug #920681 [src:astropy] atropy ftbfs with numpy 1.16
Added tag(s) moreinfo.
--
920681: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920681
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 moreinfo
Hi Matthias,
could you point me to a complete build log? 3.1.1-1 compiled fine with
numpy_1.16.0~rc2, and I just successfully tried with numpy 1.16.0. The
failure you mentioned happened in 3.1 and was the main reason for
upstream to make a 3.1.1 release.
Best
Ole
Your message dated Mon, 28 Jan 2019 11:19:49 +
with message-id
and subject line Bug#905254: fixed in libphp-phpmailer 6.0.6-0.1
has caused the Debian Bug report #905254,
regarding libphp-phpmailer: Please update to version 6.x
to be marked as done.
This means that you claim that the problem
Le 28/01/19 à 11:55, Matthias Klose a écrit :
On 28.01.19 11:48, Laurent Bigonville wrote:
Package: python3-gdbm
Version: 3.7.2-3
Severity: grave
Hi,
It seems that the gdbm module cannot be imported in python 3
import gdbm
Traceback (most recent call last):
File "", line 1, in
I agree that the issue of older versions not unpacking things made by
newer versions is not an important bug. I added that as an FYI.
I do think this bug qualifies as RC even though there is a workaround.
The workaround is non-trivial and requires Debian Developers to research
the issue for a
Your message dated Mon, 28 Jan 2019 11:55:28 +0100
with message-id <29610ccc-2e4e-33a3-485b-e8e4b6f81...@debian.org>
and subject line Re: Bug#920683: Cannot import gdbm module
has caused the Debian Bug report #920683,
regarding Cannot import gdbm module
to be marked as done.
This means that you
Your message dated Mon, 28 Jan 2019 11:48:43 +0100
with message-id <58f2c979-be53-df6a-6d2b-51cf1555d...@eds.org>
and subject line python3-asn1crypto is in stretch-backports
has caused the Debian Bug report #910064,
regarding androguard : Depends: python3-asn1crypto but it is not installable
to be
Package: python3-gdbm
Version: 3.7.2-3
Severity: grave
Hi,
It seems that the gdbm module cannot be imported in python 3
>>> import gdbm
Traceback (most recent call last):
File "", line 1, in
ModuleNotFoundError: No module named 'gdbm'
Kind regards,
Laurent Bigonville
-- System Information:
Package: src:astropy
Version: 3.1.1-1
Severity: serious
Tags: sid buster
atropy ftbfs with numpy 1.16
at least there are deprecation warnings popping up ...
> 'a.item() instead', DeprecationWarning, stacklevel=1)
E DeprecationWarning: np.asscalar(a) is deprecated
Your message dated Mon, 28 Jan 2019 10:19:34 +
with message-id
and subject line Bug#919763: fixed in adios 1.13.1-15
has caused the Debian Bug report #919763,
regarding adios: armhf FTBFS when built on arm64
to be marked as done.
This means that you claim that the problem has been dealt
close 920678 10.15.0~dfsg-10
thanks
This is canonically true that 10.15.0~dfsg-10 fixes this bug.
Processing commands for cont...@bugs.debian.org:
> close 920678 10.15.0~dfsg-10
Bug #920678 [src:nodejs] nodejs: FTBFS in Buster
Marked as fixed in versions nodejs/10.15.0~dfsg-10.
Bug #920678 [src:nodejs] nodejs: FTBFS in Buster
Marked Bug as done
> thanks
Stopping processing here.
Please
On Wed, 16 Jan 2019 at 21:51, Different55 wrote:
>
> Alright, not entirely sure if I did this right but I followed Debian's
> Building Tutorial to download and build wpa_supplicant with the changes you
> linked. One exception, I use wpa_supplicant through NetworkManager and could
> not work
Hi
Yes, thanka for this patch. I'm reluctant to consider that binaries
built on armhf failing on arm64 is an _RC Bug_, but its definitely
undesirable.
I'll forward the patch to upstream, and let them optimize it better.
regards
Alastair
On 25/01/2019 18:02, Steve Langasek wrote:
Package:
Le lun. 28 janv. 2019 à 10:42, Ritesh Raj Sarraf a écrit :
> Source: nodejs
> Version: 8.11.2~dfsg
> Severity: serious
> Justification: fails to build from source (but built successfully in the
> past)
>
> Dear Maintainer,
>
> I have been trying to build package nodejs from Buster but it fails
Control: tag -1 pending
Hello,
Bug #920536 in lintian 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 #920536 [src:lintian] lintian: fails to build because of test failure
Added tag(s) pending.
--
920536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920536
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Package: rainloop
Version: 1.11.1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
a test with piuparts revealed that your package uses files from
/usr/share/doc in its maintainer scripts which is a violation of
Policy 12.3: "Packages must not require the existence of
Hi,
On Monday, 28 January 2019, Lars Skovlund wrote:
> Hmm, moving the files out of the original directory structure and trying from
> there works.
> This gets weirder and weirder.
Indeed, indeed. Thanks for digging into this.
Mike
--
Sent from my Sailfish device
Your message dated Mon, 28 Jan 2019 09:30:47 +0100
with message-id
<1548664247.3149642.1645029560.44b17...@webmail.messagingengine.com>
and subject line
has caused the Debian Bug report #920672,
regarding netdata: Incomplete debian/copyright?
to be marked as done.
This means that you claim that
Processing commands for cont...@bugs.debian.org:
> severity 920639 grave
Bug #920639 [solfege] solfege: Does not start
Severity set to 'grave' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
920639:
Source: netdata
Version: 1.11.1+dfsg-5
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Daniel Baumann ,
ftpmas...@debian.org
Hi,
I just ACCEPTed netdata from NEW but noticed it was missing
attribution in debian/copyright for at least a bunch of embedded
code copies under
Source: netdata
Version: 1.11.1+dfsg-5
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Daniel Baumann ,
ftpmas...@debian.org
Hi,
I just ACCEPTed netdata from NEW but noticed it was missing
attribution in debian/copyright for at least a bunch of embedded
code copies under
Processing commands for cont...@bugs.debian.org:
> severity 920639 serious
Bug #920639 [solfege] solfege: Does not start
Severity set to 'serious' from 'grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
920639:
On Mon, 19 Nov 2018 16:42:35 -0800 Adam Lambert wrote:
> Ah, so I think you may have the winner. I set my temp directory to be
> something other than /tmp, and turned ClamAV back on, and it's been running
> for about an hour now with no obvious ill effects. I will report back if
> something
Processing commands for cont...@bugs.debian.org:
> severity 904111 important
Bug #904111 [clamav-daemon] clamav-daemon causing deadlocks/blocking I/O.
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
904111:
101 - 163 of 163 matches
Mail list logo
