Your message dated Wed, 28 Aug 2019 07:40:32 +0200
with message-id <20190828054032.ga16...@hjemme.reinholdtsen.name>
and subject line Re: BD on texlive-generic-extra which isn't build anymore and
isn't in bullseye
has caused the Debian Bug report #933283,
regarding BD on texlive-generic-extra
This was fixed in upload 0.6, but the changelog had a typo failing
to close the bug:
hamradio-maintguide (0.6) unstable; urgency=medium
* Packaging:
- No longer talk about priority extra
- Add a subsection about the /var/ax25 directory and that it is
preferred over /var/lib/ax25
*
Your message dated Wed, 28 Aug 2019 05:20:26 +
with message-id
and subject line Bug#925849: fixed in varnish 6.1.1-2
has caused the Debian Bug report #925849,
regarding varnish: ftbfs with GCC-9
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Processing commands for cont...@bugs.debian.org:
> fixed 925777 1.0-1
Bug #925777 [src:mkl-dnn] mkl-dnn: ftbfs with GCC-9
Marked as fixed in versions mkl-dnn/1.0-1.
> close 925777
Bug #925777 [src:mkl-dnn] mkl-dnn: ftbfs with GCC-9
Marked Bug as done
> thanks
Stopping processing here.
Please
Hi Reiner,
> I think the problem is that assaultcube-data 1.2.0.2.1-2 was uploaded
> source-only. Someone needs to do a new upload including the arch:all
> binary package, as it is in non-free (which the buildds don't seem to
> build).
I suspected it was, so I added "Multi-Arch: Foreign". I
Your message dated Wed, 28 Aug 2019 01:35:01 +
with message-id
and subject line Bug#875141: fixed in qpxtool 0.7.2-5
has caused the Debian Bug report #875141,
regarding [qpxtool] Future Qt4 removal from Buster
to be marked as done.
This means that you claim that the problem has been dealt
Hi Simon,
> Alternatively, if it's legally and technically OK to build assaultcube-data
> on buildds, a maintainer can mark it to be autobuilt and do source uploads:
> https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#non-free-buildd
"XS-Autobuild: yes" is in debian/control[0]
Your message dated Tue, 27 Aug 2019 22:20:43 +
with message-id
and subject line Bug#931874: fixed in gnome-shell-extension-appindicator
29+really22-1
has caused the Debian Bug report #931874,
regarding not installable, broken dependencies
to be marked as done.
This means that you claim that
Dear Aaron,
Thanks for bringing this to my attention.
> I just installed the suricata-update package from the Debian buster repo.
> Before that, I used the github version which worked fine.
I see.
>
> The "suricata-update" command of the Debian package tries to execute a file
>
Your message dated Tue, 27 Aug 2019 21:23:43 +
with message-id
and subject line Bug#934962: fixed in syncthing 1.1.4~ds1-3
has caused the Debian Bug report #934962,
regarding syncthing: FTBFS with 'build cache is disabled by GOCACHE=off, but
required as of Go 1.12'
to be marked as done.
Control: tag -1 pending
Hello,
Bug #934962 in syncthing 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 #934962 [syncthing] syncthing: FTBFS with 'build cache is disabled by
GOCACHE=off, but required as of Go 1.12'
Ignoring request to alter tags of bug #934962 to the same tags previously set
--
934962:
Processing control commands:
> tag -1 pending
Bug #934962 [syncthing] syncthing: FTBFS with 'build cache is disabled by
GOCACHE=off, but required as of Go 1.12'
Added tag(s) pending.
--
934962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934962
Debian Bug Tracking System
Contact
Control: tag -1 pending
Hello,
Bug #934962 in syncthing 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:
On Mon, 26 Aug 2019 08:39:31 +0200 t3ChN0M4G3 wrote:
Hi, Bullseye - Official Snapshot amd64 NETINST.iso 20190819-10:57
Installation crashes with that message
"Fehler traten auf beim Bearbeiten von: fuse"
'Error while handling of: fuse'
Attach full /var/log/apt/history.log and
Control: reopen -1
On Tue, Aug 27, 2019 at 07:08:13AM +, Sylvestre Ledru wrote:
> rust-rle-decode-fast (1.0.1-2) unstable; urgency=medium
> .
>* Team upload.
>* Package rle-decode-fast 1.0.1 from crates.io using debcargo 2.4.0
> Hopefully, the rebuild will (Closes: #935671)
It
Processing control commands:
> reopen -1
Bug #935671 {Done: Sylvestre Ledru }
[src:rust-rle-decode-fast] librust-rle-decode-fast+bench-dev/amd64
unsatisfiable Depends: librust-criterion-0.2+default-dev
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions
Package: suricata-update
Version: 1.0.3-2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
I just installed the suricata-update package from the Debian buster repo.
Before that, I used the github version which worked fine.
The "suricata-update" command of the Debian
On Tue, 27 Aug 2019 at 16:13:10 +0200, Reiner Herrmann wrote:
> I think the problem is that assaultcube-data 1.2.0.2.1-2 was uploaded
> source-only. Someone needs to do a new upload including the arch:all
> binary package, as it is in non-free (which the buildds don't seem to
> build).
Your message dated Tue, 27 Aug 2019 17:49:59 +
with message-id
and subject line Bug#925767: fixed in linux-ftpd 0.17-36.2
has caused the Debian Bug report #925767,
regarding linux-ftpd: ftbfs with GCC-9
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Tue, 27 Aug 2019 17:50:04 +
with message-id
and subject line Bug#925768: fixed in linux-ftpd-ssl 0.17.36+0.3-2.2
has caused the Debian Bug report #925768,
regarding linux-ftpd-ssl: ftbfs with GCC-9
to be marked as done.
This means that you claim that the problem has been
On Sun, 25 Aug 2019 15:51:21 +0200 Francesco Poli wrote:
> On Sun, 25 Aug 2019 13:46:36 +0200 Florian Weimer wrote:
[...]
> > We provided a solution acceptable to the reporter. I do not think
> > further action is needed on the glibc side. The manual page needs to
> > be updated to reflect the
Processing commands for cont...@bugs.debian.org:
> tags 935794 + sid bullseye
Bug #935794 [src:xfce4-sntray-plugin] xfce4-sntray-plugin FTBFS
Added tag(s) sid and bullseye.
> tags 935822 + sid bullseye
Bug #935822 [src:gr-dab] gr-dab: FTBFS with latest gnuradio
Added tag(s) sid and bullseye.
>
OK. Many thanks for you response Bernhard.
Today I find some time for make this.
I installed the following packages:
ii amule 1:2.3.2-5+b1
ii amule-common 1:2.3.2-5
ii amule-daemon1:2.3.2-5+b1
ii amule-emc 0.5.2-4+b1
ii amule-gnome-support1:2.3.2-5 all
Source: rust-uuid
Version: 0.7.2-2
Severity: serious
Affects: src:rust-md5
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu eoan
The rust-uuid package depends on a newer rust-md5 than is available in the
Debian archive.
librust-uuid+md5-dev/amd64 unsatisfiable Depends:
On Tue, 27 Aug 2019 at 15:21, Dominique Dumont wrote:
>
> On Tuesday, 27 August 2019 10:04:23 CEST Dominique Dumont wrote:
> > Right.. This is the same error than the one showing in the FTBS issue.
> >
> > I guess we need to talk to upstream. They may not have seen this issue yet
> > if they use
Processing control commands:
> tags -1 - moreinfo
Bug #935887 [python3-mapproxy] python3-mapproxy: Change default template_dir
and fix capabilities for Python >= 3.6.7
Removed tag(s) moreinfo.
> severity -1 important
Bug #935887 [python3-mapproxy] python3-mapproxy: Change default template_dir
Control: tags -1 - moreinfo
Control: severity -1 important
I've installed mapproxy on a test server with stretch, it contains the
symlinks as well:
# find /usr/lib/python2.7/dist-packages/mapproxy/ -type l -exec ls -l {} \;
lrwxrwxrwx 1 root root 73 Jan 7 2018
On Tuesday, 27 August 2019 10:04:23 CEST Dominique Dumont wrote:
> Right.. This is the same error than the one showing in the FTBS issue.
>
> I guess we need to talk to upstream. They may not have seen this issue yet
> if they use an older version of libuv.
On the other hand, I'm able to build
Your message dated Tue, 27 Aug 2019 15:02:05 +
with message-id
and subject line Bug#935873: fixed in menhir 20190626-6
has caused the Debian Bug report #935873,
regarding Missing dependency on coq-$ABI
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Hi Carlos,
I think the problem is that assaultcube-data 1.2.0.2.1-2 was uploaded
source-only. Someone needs to do a new upload including the arch:all
binary package, as it is in non-free (which the buildds don't seem to
build).
I think this change [0] does not help, as you can't enforce a
Hi,
Sorry for the silence, I had missed this bug completely. I will work on
fixing this, meanwhile, I hope this email delays the AUTORM for a few
days...
--
Martina Ferrari (Tina, the artist formerly known as Tincho)
Processing control commands:
> tag -1 pending
Bug #935873 [libmenhir-coq] Missing dependency on coq-$ABI
Added tag(s) pending.
--
935873: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935873
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #935873 in menhir 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: block -1 by 929438
Control: tags -1 pending
This will be fixed with sunpy version 1.0.2. However, the upload is
delayed due to a dependency which is currently still in the NEW queue.
Processing control commands:
> block -1 by 929438
Bug #934959 [src:sunpy] python-mock breaks sunpy autopkgtest
934959 was not blocked by any bugs.
934959 was not blocking any bugs.
Added blocking bug(s) of 934959: 929438
> tags -1 pending
Bug #934959 [src:sunpy] python-mock breaks sunpy
Processing commands for cont...@bugs.debian.org:
> retitle 935702 Mapped devices of size ≥2TiB are truncated on 32-bits platforms
Bug #935702 {Done: Guilhem Moulin } [cryptsetup-bin] DM
device size ≥2³² 512-bits sectors is truncated on 32-bits platforms
Changed Bug title to 'Mapped devices of
Attached is my sample configuration file I created as subset of my
production configuration. So probably it looks, like I do coordinate system
translation from JTSK to JTSK, but in fact, I use many sources in different
systems (most of them are in GLOBAL_WEBMERCATOR), and all sources I crop to
I pushed more changes to Git. We could fix the NullPointerException in
insubstantial but now I get two different errors.
Failed to register bus name / null
and
NoClassDefFoundError: org/slf4j/LoggerFactory
I don't know why this class is suddenly missing from the classpath.
signature.asc
On 2019-08-27 12:39, Marek Lukács wrote:
Do you need to prepare sample configuration for you? I can do simple
copy
of my configuration with for example single layer/service.
A (minimal) sample config to get a service working to reproduce the
issues would be very helpful. Thanks in advance.
On Tue, Aug 27, 2019 at 12:23 PM Bas Couwenberg wrote:
> Control: tags -1 + moreinfo
> Control: tags -1 - d-i
>
> On 2019-08-27 11:52, Marek Lukács wrote:
> > MapProxy does not work on Python 3.7 installs. I figured out two
> > issues,
> > one related to Debian installation (directory structure)
Processing control commands:
> tags -1 + moreinfo
Bug #935887 [python3-mapproxy] python3-mapproxy: Change default template_dir
and fix capabilities for Python >= 3.6.7
Added tag(s) moreinfo.
> tags -1 - d-i
Bug #935887 [python3-mapproxy] python3-mapproxy: Change default template_dir
and fix
Control: tags -1 + moreinfo
Control: tags -1 - d-i
On 2019-08-27 11:52, Marek Lukács wrote:
MapProxy does not work on Python 3.7 installs. I figured out two
issues,
one related to Debian installation (directory structure) and other to
upstream known issue:
1. Directory structure
Debian moves
Your message dated Tue, 27 Aug 2019 10:25:04 +
with message-id
and subject line Bug#935324: fixed in qemu 1:4.1-1
has caused the Debian Bug report #935324,
regarding FTBFS: gluster API has changed
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Tue, 27 Aug 2019 10:25:04 +
with message-id
and subject line Bug#933741: fixed in qemu 1:4.1-1
has caused the Debian Bug report #933741,
regarding qemu: CVE-2019-14378: heap buffer overflow during packet reassembly
to be marked as done.
This means that you claim that the
Package: python3-mapproxy
Version: 1.11.0-3
Severity: grave
Tags: patch d-i upstream
Justification: renders package unusable
MapProxy does not work on Python 3.7 installs. I figured out two issues,
one related to Debian installation (directory structure) and other to
upstream known issue:
1.
Hi Andreas,
I'll try to take a look at the end of the week.
Tanya.
On Tue, Aug 27, 2019, 09:14 Andreas Tille wrote:
> Hi Tatiana,
>
> since some time one of the profnet tests is failing with
>
>Program received signal SIGSEGV: Segmentation fault - invalid memory
>reference.
>
> Do you
Package: libvirt-daemon-system
Version: 5.6.0-1
Severity: serious
Hello,
So apparently libvirtd socket activation has been disabled in this
release because it's "broken upstream" but the daemon is still started
with "--timeout 120" meaning that after 2 min the daemon become
unreachable without
Your message dated Tue, 27 Aug 2019 08:56:48 +
with message-id
and subject line Bug#925850: fixed in vdetelweb 1.2.1-3
has caused the Debian Bug report #925850,
regarding vdetelweb: ftbfs with GCC-9
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Tue, 27 Aug 2019 08:54:41 +
with message-id
and subject line Bug#935284: fixed in lwipv6 1.5a-5
has caused the Debian Bug report #935284,
regarding lwipv6: FTBFS on amd64
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Tue, 27 Aug 2019 08:55:31 +
with message-id
and subject line Bug#934644: fixed in openstack-meta-packages 0.26
has caused the Debian Bug report #934644,
regarding openstack-deploy: depends on cruft package.
to be marked as done.
This means that you claim that the problem
Processing control commands:
> tag -1 pending
Bug #934644 [openstack-deploy] openstack-deploy: depends on cruft package.
Added tag(s) pending.
--
934644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934644
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #934644 in openstack-meta-packages 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:
Source: ccdproc
Version: 1.3.0-7
Severity: grave
Tags: ftbfs upstream
Justification: renders package unusable
Dear maintainer,
ccdproc FTBFS with newer pytest 4.6.
autopkgtests fails too, see:
https://ci.debian.net/data/autopkgtest/testing/amd64/c/ccdproc/2822438/log.gz
Thanks.
-- System
On Tuesday, 27 August 2019 05:27:49 CEST M. Zhou wrote:
> I'm somehow
> stuck on a strange installation failure (likely permission issue):
Oops, I missed that part...
> '/home/lumin/Debian/perl6/rakudo/debian/rakudo/usr/lib/perl6/core'
> No writeable path found,
>
Package: libmenhir-coq
Version: 20190626-5
Severity: serious
Hello,
All libX-coq (e.g. libssreflect-coq) must have a dependency on
coq-$ABI. libmenhir-coq lacks one.
Cheers,
--
Stéphane
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (990, 'testing'),
Source: pytest-sugar
Version: 0.9.2-1
Severity: serious
Tags: upstream ftbfs
pytest-sugar FTBFS with newer pytest 4.6.
autopkgtests fails too, see:
https://ci.debian.net/data/autopkgtest/testing/amd64/p/pytest-sugar/2822790/log.gz
Thanks.
-- System Information:
Debian Release: bullseye/sid
Your message dated Tue, 27 Aug 2019 07:08:13 +
with message-id
and subject line Bug#935671: fixed in rust-rle-decode-fast 1.0.1-2
has caused the Debian Bug report #935671,
regarding librust-rle-decode-fast+bench-dev/amd64 unsatisfiable Depends:
librust-criterion-0.2+default-dev
to be marked
Source: rust-combine
Version: 3.6.7-1
Severity: serious
Affects: src:rust-regex
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu eoan
The rust-combine package is uninstallable, because it depends on a version
of rust-regex that is older than what's in unstable:
Hi Tatiana,
since some time one of the profnet tests is failing with
Program received signal SIGSEGV: Segmentation fault - invalid memory
reference.
Do you have time to do some debugging on this?
Kind regards
Andreas.
--
http://fam-tille.de
60 matches
Mail list logo
