Followup-For: Bug #892403
Control: reopen -1
Hi,
while trying to rebuild starpu-contrib for CUDA 9.2 it failed with some
errors related to gcc-6.
I successfully built the package with the attached patch that switched
to GCC 7, but since the build system is a bit special, I'm not going to
upload
Processing control commands:
> reopen -1
Bug #892403 {Done: Samuel Thibault } [src:starpu-contrib]
starpu-contrib: build-depends on GCC 6
'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
Package: cargo
Version: 0.31.1-1
Severity: grave
Any time I try to update the crates.io index with the currently packaged
version of cargo, I get a segfault:
$ cargo update
Updating crates.io index
Segmentation fault
I can reproduce this in a brand new project (`cargo new foo`) by adding
On Wed, 09 Jan 2019 21:08:51 +0100 Salvatore Bonaccorso
wrote:
> Source: systemd
> Version: 204-1
> Severity: grave
> Tags: security upstream
> Justification: user security hole
> Control: found -1 232-25+deb9u6
> Control: found -1 240-2
>
> Hi,
>
> The following vulnerability was published for
On 1/9/19 3:45 PM, Andreas Beckmann wrote:
> Package: neutron-fwaas-common
> Version: 1:13.0.1-3
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
>
> Hi,
>
> during a test with piuparts I noticed your package fails to remove.
>
>>From the attached log (scroll to the
Control: tags -1 pending
Control: tags 918771 pending
I intend to upload theano (also containing other changes - see Salsa
repo) either tonight or tomorrow night.
...or by calling numpy 1.16 a transition, are you implying you want this
minimal fix and nothing else?
Processing control commands:
> tags -1 pending
Bug #918090 [src:theano] theano: C-optimized ops fail with "module
'numpy.core.multiarray' has no attribute '_get_ndarray_c_version'"
Bug #918217 [src:theano] theano: autopkgtest fails with python-numpy
(1:1.16.0~rc1-3)
Added tag(s) pending.
Added
Processing commands for cont...@bugs.debian.org:
> tags 918823 + moreinfo
Bug #918823 [libc6] libc6: [24945.428485] libvirtd[12553]: segfault at 8 ip
7fb0f515ba63 sp 7fff86e08370 error 4 in ld-2.24.so[7fb0f514b000+23000]
Added tag(s) moreinfo.
> thanks
Stopping processing here.
Please
Processing commands for cont...@bugs.debian.org:
> tags 918823 - d-i
Bug #918823 [libc6] libc6: [24945.428485] libvirtd[12553]: segfault at 8 ip
7fb0f515ba63 sp 7fff86e08370 error 4 in ld-2.24.so[7fb0f514b000+23000]
Removed tag(s) d-i.
> thanks
Stopping processing here.
Please contact
Hi,
On 2019-01-09 16:25, leopoldotosi wrote:
>
> Package: libc6
> Version: 2.24-11+deb9u3
> Severity: critical
> Tags: d-i
> Justification: breaks unrelated software
>
> Dear Maintainer,
>
> I can not work libvirtd ?-:-(
I am sorry about that.
> Reading symbols from virsh...(no debugging
Package: debconf
Version: 1.5.69
Severity: serious
Hi.
I'm running a mostly-up-to-date Debian/sid system. I just tried updating
it, and it barf at me when I ask it to update debconf:
root@machine:~# aptitude install debconf
The following NEW packages will be installed:
Your message dated Thu, 10 Jan 2019 01:19:06 +
with message-id
and subject line Bug#912712: fixed in dlang-openssl 2.0.0+1.1.0h-0.1
has caused the Debian Bug report #912712,
regarding vibe.d FTBFS with ldc
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Thu, 10 Jan 2019 01:20:02 +
with message-id
and subject line Bug#918749: fixed in tpm2-tss 2.1.0-3
has caused the Debian Bug report #918749,
regarding libtss2-dev: missing Depends: libgcrypt20-dev, pkg-config --libs
tss2-esys lists -lgcrypt
to be marked as done.
This
Package:
python-meep-openmpi,python-meep-mpich2,python-meep-mpi-default,python-meep-lam4
Version: 1.7.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this
Your message dated Wed, 09 Jan 2019 22:40:12 +
with message-id
and subject line Bug#916292: fixed in pyfai 0.17.0+dfsg1-2
has caused the Debian Bug report #916292,
regarding pyfai FTBFS on i386: test failures
to be marked as done.
This means that you claim that the problem has been dealt
Processing commands for cont...@bugs.debian.org:
> severity 918749 serious
Bug #918749 [libtss2-dev] libtss2-dev: missing Depends: libgcrypt20-dev,
pkg-config --libs tss2-esys lists -lgcrypt
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need
Processing control commands:
> tag -1 pending
Bug #892388 [src:caffe-contrib] caffe-contrib: build-depends on GCC 6
Added tag(s) pending.
--
892388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892388
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Andreas Beckmann, le jeu. 10 janv. 2019 01:02:19 +0100, a ecrit:
> I successfully built the package with the attached patch that switched
> to GCC 7, but since the build system is a bit special, I'm not going to
> upload this myself.
I'll handle it once CUDA 9.2 is uploaded, yes. Thanks for
Control: fixed -1 0.9.15-1
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Processing control commands:
> fixed -1 0.9.15-1
Bug #918596 [src:ruby-acts-as-list] ruby-acts-as-list FTBFS with rails 5.2
Marked as fixed in versions ruby-acts-as-list/0.9.15-1.
--
918596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918596
Debian Bug Tracking System
Contact
Your message dated Thu, 10 Jan 2019 10:11:48 +0530
with message-id <37c526ff-638e-43b3-af99-bf23d97ec...@onenetbeyond.org>
and subject line Fixed with new upstream version in unstable
has caused the Debian Bug report #918596,
regarding ruby-acts-as-list FTBFS with rails 5.2
to be marked as done.
Your message dated Wed, 9 Jan 2019 22:06:32 +0100
with message-id <20190109210632.ga28...@seneca.home.org>
and subject line Re: morbig: FTBFS: unsatisfiable build-dependencies:
libppx-deriving-yojson-ocaml-dev, libppx-visitors-ocaml-dev
has caused the Debian Bug report #917701,
regarding morbig:
Followup-For: Bug #892388
Control: tag -1 pending
Hi,
I just pushed a (build-tested) commit to switch to CUDA 9.2 and GCC 7.
I don't plan to upload it immediately ... so you can update the package
if needed and upload yourself.
Andreas
Your message dated Wed, 09 Jan 2019 23:21:36 +
with message-id
and subject line Bug#918833: fixed in node-browserify-lite 0.5.0-3
has caused the Debian Bug report #918833,
regarding node-browserify-lite: autopkgtest regression
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 09 Jan 2019 23:49:53 +
with message-id
and subject line Bug#834915: fixed in node-temp 0.8.3-2
has caused the Debian Bug report #834915,
regarding node-temp: FTBFS (AssertionError: temp.createWriteStream did not
create a file)
to be marked as done.
This means that
For anyone looking at this bug (especially folks at bug squashing
parties): I've filed an Intent To Salvage for this package
(https://bugs.debian.org/917937), and assuming I don't hear from the
maintainer by January 21st, will be uploading a version of lsof that
fixes this bug.
Your message dated Thu, 10 Jan 2019 06:50:03 +
with message-id
and subject line Bug#918738: fixed in odb-api 0.18.1-4
has caused the Debian Bug report #918738,
regarding libodb-api-dev is not installable due to typo in the dependencies
to be marked as done.
This means that you claim that the
Processing commands for cont...@bugs.debian.org:
> tags 912077 - help
Bug #912077 [src:libbiod] libbiod FTBFS on i386: Error: cannot implicitly
convert expression
Removed tag(s) help.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
912077:
Control: forwarded -1 https://github.com/biod/BioD/issues/50
Control: tags -1 help upstream
Dear Matthias,
unfortunately there is another issue with libbiod and as usual I need
your help due to my total incompetence in D. :-(
I have reported the issue upstream as well.
Kind regards
Processing control commands:
> forwarded -1 https://github.com/biod/BioD/issues/50
Bug #917721 [src:libbiod] libbiod: FTBFS: dh_auto_test: cd obj-x86_64-linux-gnu
&& LC_ALL=C.UTF-8 MESON_TESTTHREADS=2 ninja test returned exit code 1
Set Bug forwarded-to-address to
Your message dated Thu, 10 Jan 2019 06:55:32 +0100
with message-id <20190110055520.gy1...@sym.noone.org>
and subject line Re: Bug#918764: udev: "udevadm control --reload-rules" kills
all processes except init
has caused the Debian Bug report #918764,
regarding udev: "udevadm control
Hi again Tobias,
On Sun, Nov 18, 2018 at 09:53:30AM +0100, Joost van Baal-Ilić wrote:
> On Sat, Nov 17, 2018 at 11:57:03PM +0100, Dr. Tobias Quathamer wrote:
> > Am 17.11.2018 um 09:04 schrieb Joost van Baal-Ilić:
> > > I plan to work on the Debian FAQ at
> > >
tags 918326 +patch +pending
tags 918645 +patch +pending
thanks
I just went ahead and uploaded a NMU fixing bugs 918326 (dependency on cruft
package) and 918645 (testsuite failure due to missing build-dependency) to
delayed/5. A debdiff is attatched, please tell me if you have any issues with
Processing commands for cont...@bugs.debian.org:
> tags 918326 +patch +pending
Bug #918326 [python3-dfwinreg] python-dfwinreg and python3-dfwinreg depend on
cruft package dtfabric
Added tag(s) patch.
Bug #918326 [python3-dfwinreg] python-dfwinreg and python3-dfwinreg depend on
cruft package
Hi Michael,
On Thu, Jan 10, 2019 at 01:41:17AM +0100, Michael Biebl wrote:
> On Wed, 09 Jan 2019 21:08:51 +0100 Salvatore Bonaccorso
> wrote:
> > Source: systemd
> > Version: 204-1
> > Severity: grave
> > Tags: security upstream
> > Justification: user security hole
> > Control: found -1
Your message dated Thu, 10 Jan 2019 09:12:11 +0200
with message-id <20190110071211.GK13260@localhost>
and subject line python-qpid-proton is back in buster
has caused the Debian Bug report #918280,
regarding koji build depends on python-qpid-proton that is currently not in
buster
to be marked as
Your message dated Thu, 10 Jan 2019 09:10:31 +0200
with message-id <20190110071031.GJ13260@localhost>
and subject line python3-factory-boy is back in buster
has caused the Debian Bug report #918340,
regarding pylint-django build depends on python3-factory-boy that is currently
not in buster
to be
Your message dated Wed, 09 Jan 2019 09:20:13 +
with message-id
and subject line Bug#916067: fixed in fuse-umfuse-ext2 0.4-1.2
has caused the Debian Bug report #916067,
regarding fuse-umfuse-ext2 FTBFS with glibc 2.28
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 09 Jan 2019 09:20:35 +
with message-id
and subject line Bug#899514: fixed in fuse-umfuse-iso9660 0.3-1.3
has caused the Debian Bug report #899514,
regarding fuse-umfuse-iso9660: Invalid maintainer address
pkg-vsquare-de...@lists.alioth.debian.org
to be marked as done.
Your message dated Wed, 09 Jan 2019 09:20:13 +
with message-id
and subject line Bug#899817: fixed in fuse-umfuse-ext2 0.4-1.2
has caused the Debian Bug report #899817,
regarding fuse-umfuse-ext2: Invalid maintainer address
pkg-vsquare-de...@lists.alioth.debian.org
to be marked as done.
This
Your message dated Wed, 09 Jan 2019 09:20:35 +
with message-id
and subject line Bug#901530: fixed in fuse-umfuse-iso9660 0.3-1.3
has caused the Debian Bug report #901530,
regarding fix build failure with libcdio-2.0
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 09 Jan 2019 09:20:24 +
with message-id
and subject line Bug#899516: fixed in fuse-umfuse-fat 0.1a-1.2
has caused the Debian Bug report #899516,
regarding fuse-umfuse-fat: Invalid maintainer address
pkg-vsquare-de...@lists.alioth.debian.org
to be marked as done.
This
Your message dated Wed, 09 Jan 2019 10:23:26 +
with message-id
and subject line Bug#899724: fixed in vdetelweb 1.2.1-2
has caused the Debian Bug report #899724,
regarding vdetelweb: Invalid maintainer address
pkg-vsquare-de...@lists.alioth.debian.org
to be marked as done.
This means that
Your message dated Wed, 09 Jan 2019 10:23:17 +
with message-id
and subject line Bug#899562: fixed in umview 0.8.2-1.2
has caused the Debian Bug report #899562,
regarding kernel-patch-viewos: Invalid maintainer address
pkg-vsquare-de...@lists.alioth.debian.org
to be marked as done.
This
Your message dated Wed, 09 Jan 2019 10:22:20 +
with message-id
and subject line Bug#899659: fixed in purelibc 0.4.1-2
has caused the Debian Bug report #899659,
regarding purelibc: Invalid maintainer address
pkg-vsquare-de...@lists.alioth.debian.org
to be marked as done.
This means that you
Hi,
On Wed, 9 Jan 2019 00:27:03 +0200 Faidon Liambotis wrote:
> So jemalloc 5.1.0-2 was recently uploaded to unstable. The build currently
> fails due to the explicit dependency on libjemalloc1 (cf. #918741), but as
> soon as this gets fixed, another issue is uncovered:
>
> While building this
Package: lintian
Version: 2.5.119
Severity: serious
X-Debbugs-CC: Felix Lechner
Hi Felix,
It appears like one of your recent changes has meant that a failing
test does not return an non-zero error code. For example:
$ debian/rules runtests onlyrun=01-critic
Processing control commands:
> title -1 FTBFS: dh_auto_test: numpy 1.16 arraysetops dtype error
Unknown command or malformed arguments to command.
> forwarded -1 https://github.com/PacificBiosciences/pbcore/issues/120
Bug #917670 [src:python-pbcore] python-pbcore: FTBFS: dh_auto_test: pybuild
Dear maintainers
If a patch providing Antonio's proposed stop-gap message is provided, is
it still possible for print-manager to get into buster? In that case, I
may possibly try to hack something like that.
Thanks for your work and consideration!
-Steven
Source: python-pbcore
Followup-For: Bug #917670
Control: title -1 FTBFS: dh_auto_test: numpy 1.16 arraysetops dtype error
Control: forwarded -1 https://github.com/PacificBiosciences/pbcore/issues/120
Confirmed, still occurs with pbcore 1.6.5.
Bug filed upstream.
Drew
Package: libc6
Version: 2.24-11+deb9u3
Severity: critical
Tags: d-i
Justification: breaks unrelated software
Dear Maintainer,
I can not work libvirtd ?-:-(
Reading symbols from virsh...(no debugging symbols found)...done.
(gdb) set pagination 8
"on" or "off" expected.
(gdb) run
Starting
Hello Ryan,
cmus is marked for autoremoval, the freeze is approaching (where no
removed packages are allowed to reenter testing) and I see no activity
from the cmus side.
Also at least the mpd developers are not very confident in the code
quality of libroar
Your message dated Wed, 09 Jan 2019 13:49:46 +
with message-id
and subject line Bug#918722: fixed in debootstrap 1.0.114
has caused the Debian Bug report #918722,
regarding debootstrap: says InRelease file expired
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 09 Jan 2019 13:50:20 +
with message-id
and subject line Bug#918511: fixed in golang-github-shopify-sarama 1.20.0-2
has caused the Debian Bug report #918511,
regarding golang-github-shopify-sarama-dev: missing dependency on
golang-github-datadog-zstd-dev
to be marked
Your message dated Wed, 09 Jan 2019 14:06:22 +
with message-id
and subject line Bug#917672: fixed in yp-svipc 0.16-3
has caused the Debian Bug report #917672,
regarding yp-svipc: FTBFS: python/svipc_module.c:869:28: error: expected
expression before ')' token
to be marked as done.
This
Package: neutron-fwaas-common
Version: 1:13.0.1-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to remove.
>From the attached log (scroll to the bottom...):
Removing neutron-fwaas-common (1:13.0.1-3) ...
On 1/8/19 7:46 PM, Michael Büsch wrote:
> Package: debootstrap
> Version: 1.0.113
> Severity: normal
>
> When bootstrapping Raspbian with debootstrap it fails since version 1.0.113:
>
> debootstrap --arch=armhf --foreign --verbose
> --keyring=raspbian.public.key.gpg stretch /my/directory
>
Control: tag -1 pending
Hello,
Bug #918511 in golang-github-shopify-sarama 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 Wed, 09 Jan 2019 11:36:12 +
with message-id
and subject line Bug#918780: fixed in koji 1.16.0-3
has caused the Debian Bug report #918780,
regarding koji-client: should depend on python-requests and python-dateutil
to be marked as done.
This means that you claim that the
Processing control commands:
> severity -1 serious
Bug #918722 [debootstrap] debootstrap: says InRelease file expired
Severity set to 'serious' from 'normal'
--
918722: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918722
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Processing commands for cont...@bugs.debian.org:
> reassign 915642 libcap-ng0 0.7.9-1
Bug #915642 [libapache2-mod-authnz-pam] AuthBasicProvider PAM crashes apache
Bug reassigned from package 'libapache2-mod-authnz-pam' to 'libcap-ng0'.
No longer marked as found in versions
Processing control commands:
> tag -1 pending
Bug #918054 [src:elkcode] elkcode: frequent test hangs
Ignoring request to alter tags of bug #918054 to the same tags previously set
--
918054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918054
Debian Bug Tracking System
Contact
Processing control commands:
> tag -1 pending
Bug #918054 [src:elkcode] elkcode: frequent test hangs
Added tag(s) pending.
--
918054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918054
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #918054 in elkcode 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 #918054 in elkcode 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 Wed, 09 Jan 2019 09:34:19 +
with message-id
and subject line Bug#899905: fixed in lwipv6 1.5a-3
has caused the Debian Bug report #899905,
regarding lwipv6: Invalid maintainer address
pkg-vsquare-de...@lists.alioth.debian.org
to be marked as done.
This means that you claim
Your message dated Wed, 9 Jan 2019 11:11:36 +0100
with message-id
and subject line Re: cross-toolchain-base: FTBFS: applying patches fails
has caused the Debian Bug report #917745,
regarding cross-toolchain-base: FTBFS: applying patches fails
to be marked as done.
This means that you claim that
Package: koji-client
Version: 1.16.0-2
Severity: serious
Justification: Policy 3.5
Hi,
Forwarding https://bugs.launchpad.net/ubuntu/+bug/1803423 which also happens
in Debian Buster. The koji command cannot be used without installing some
dependencies first.
$ koji help
Traceback (most recent
On Wed, Jan 9, 2019 at 3:46 PM, t...@schleuder.org wrote:
You probably mean a debian package? Unfortunately the maintainer is
traveling currently and the rest of us don't know enough to build
the package.
We could probably produce an unofficial gem once the change is
finished
if that also
Processing commands for cont...@bugs.debian.org:
> forwarded 917693 https://github.com/biocore/scikit-bio/issues/1648
Bug #917693 [src:python-skbio] python-skbio: FTBFS: dh_auto_test: pybuild
--test --test-nose -i python{version} -p 3.7 returned exit code 13
Set Bug forwarded-to-address to
Your message dated Wed, 9 Jan 2019 13:06:44 +
with message-id <20190109130644.gc18...@esaurito.net>
and subject line fix for wrong changelog entry
has caused the Debian Bug report #899892,
regarding umview: Invalid maintainer address
pkg-vsquare-de...@lists.alioth.debian.org
to be marked as
Processing commands for cont...@bugs.debian.org:
> reopen 899562
Bug #899562 {Done: Renzo Davoli } [src:kernel-patch-viewos]
kernel-patch-viewos: Invalid maintainer address
pkg-vsquare-de...@lists.alioth.debian.org
'reopen' may be inappropriate when a bug has been closed with a version;
all
Processing control commands:
> tag -1 pending
Bug #918511 [golang-github-shopify-sarama-dev]
golang-github-shopify-sarama-dev: missing dependency on
golang-github-datadog-zstd-dev
Added tag(s) pending.
--
918511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918511
Debian Bug Tracking
Processing commands for cont...@bugs.debian.org:
> forwarded 918670 https://github.com/floatdrop/duplexer3/issues/2
Bug #918670 [src:node-duplexer3] node-duplexer3 FTBFS with nodejs 10.15.0
Set Bug forwarded-to-address to
'https://github.com/floatdrop/duplexer3/issues/2'.
> thanks
Stopping
Processing commands for cont...@bugs.debian.org:
> tags 918670 + upstream
Bug #918670 [src:node-duplexer3] node-duplexer3 FTBFS with nodejs 10.15.0
Added tag(s) upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
918670:
On Wed, Jan 09, 2019 at 12:03:03AM +0100, Moritz Mühlenhoff wrote:
> On Wed, Dec 19, 2018 at 11:56:47PM +0100, Sebastian Andrzej Siewior wrote:
> > On 2018-12-06 22:52:32 [+0100], Moritz Muehlenhoff wrote:
> > > Source: cfengine2
> > > Severity: serious
> > >
> > > This is replaced by
Hi Rebecca,
On Thu, 3 Jan 2019 07:26:32 + "Rebecca N. Palmer"
wrote:
> Source: theano
> Version: 1.0.2+dfsg-1
> Severity: serious
> Control: tags -1 patch
>
> Many Theano operations include C code for speed; the compilation process
> uses an undocumented Numpy function to check ABI
What further information do you need? What do I do in the case when
"apt-cache depends" shows multiple package versions?
If I check what version of PHP is running, I get PHP Version => 7.3.0-2.
I inherited the system from the previous admin and admittedly it is in a
mess.
On Mon, 7 Jan 2019 at
Processing control commands:
> severity -1 important
Bug #918578 [gosa] gosa: GOsa web interface missing password field
Severity set to 'important' from 'serious'
--
918578: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918578
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
control: severity -1 important
thanks
On Mon, Jan 07, 2019 at 06:36:35PM +0100, Wolfgang Schweer wrote:
> On Mon, Jan 07, 2019 at 04:20:23PM +0200, Eliza wrote:
> > After some updates were applied, the password field disappeared from
> > GOsa. The text label "Password" exist, but the text box is
Processing control commands:
> tag -1 pending
Bug #918670 [src:node-duplexer3] node-duplexer3 FTBFS with nodejs 10.15.0
Added tag(s) pending.
--
918670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918670
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #918670 in node-duplexer3 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:
Hi,
I just had the what seems to be the same bug happen to me.
This is the relevant output form pstree:
,
| `-sudo,21446 apt dist-upgrade
| `-apt,21447 dist-upgrade
| `-dpkg,22875 --status-fd 39 --configure --pending
| `-ifupdown.postin,22876
Processing commands for cont...@bugs.debian.org:
> severity 852093 grave
Bug #852093 [src:hesiod] hesiod: CVE-2016-10152: Use of hard-coded DNS domain
if configuration file cannot be read
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need
Source: libvideo-info-perl
Version: 0.993-3
Severity: serious
https://tracker.debian.org/pkg/libvideo-info-perl
Long-term this might be fixable with
https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#non-free-buildd
Short-term this needs a binary uploaded
(feel free to close
Hi,
Axel Beckert wrote:
> I have no idea why this is happening, but several packages use "udevadm
> control --reload-rules" in their postinst (e.g. fuse) and if that's run,
> all process except init are instantly killed (reproducibly; the gettys
> seem to be respawned by init then, so I can login
Hi Piotr,
I recently NMU-ed fakechroot and now two more RC bugs popped up:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918741
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918741
is it okay if I NMU these again or do you want to take care of them?
I'm the maintainer of a reverse
Your message dated Wed, 09 Jan 2019 10:38:54 +
with message-id
and subject line Bug#918382: fixed in openexr 2.3.0-5
has caused the Debian Bug report #918382,
regarding trying to overwrite
'/usr/lib/x86_64-linux-gnu/libIlmImf-2_3.so.24.0.0', which is also in package
libopenexr23:amd64
Your message dated Wed, 09 Jan 2019 10:38:54 +
with message-id
and subject line Bug#917953: fixed in openexr 2.3.0-5
has caused the Debian Bug report #917953,
regarding openexr: Incomplete debian/copyright?
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Wed, 09 Jan 2019 10:22:20 +
with message-id
and subject line Bug#916165: fixed in purelibc 0.4.1-2
has caused the Debian Bug report #916165,
regarding purelibc FTBFS with glibc 2.28
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Wed, 09 Jan 2019 10:23:17 +
with message-id
and subject line Bug#916170: fixed in umview 0.8.2-1.2
has caused the Debian Bug report #916170,
regarding umview FTBFS with glibc 2.28
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Wed, 09 Jan 2019 10:42:29 +
with message-id
and subject line Bug#899726: fixed in vde2 2.3.2+r586-2.2
has caused the Debian Bug report #899726,
regarding vde2: Invalid maintainer address
pkg-vsquare-de...@lists.alioth.debian.org
to be marked as done.
This means that you
Processing commands for cont...@bugs.debian.org:
> severity 852094 grave
Bug #852094 [src:hesiod] hesiod: CVE-2016-10151: Weak SUID check allowing
privilege elevation
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Processing control commands:
> tags -1 upstream help
Bug #917693 [src:python-skbio] python-skbio: FTBFS: dh_auto_test: pybuild
--test --test-nose -i python{version} -p 3.7 returned exit code 13
Added tag(s) upstream and help.
> forward -1 https://github.com/biocore/scikit-bio/issues/1648
Unknown
Control: tags -1 upstream help
Control: forward -1 https://github.com/biocore/scikit-bio/issues/1648
I admit I wished python-numpy would do some transition procedure instead
of throwing RC candidates to unstable.
--
http://fam-tille.de
Hi Sandro,
python-numpy has a lot of rdepends and new numpy versions. In the past
every version bump of numpy has broken some of these. I'd propose to
use the well established transition procedure[1] for new numpy versions
specifically if you intend to upload RC candidates this should not just
Processing commands for cont...@bugs.debian.org:
> reassign 914680 src:plplot 5.13.0+dfsg-10
Bug #914680 {Done: Ole Streicher } [libplplotada3]
libplplotada3: missing Breaks+Replaces: libplplotada2
Bug reassigned from package 'libplplotada3' to 'src:plplot'.
No longer marked as found in versions
Any chance seeing this issue addressed or its severity lowered, so we can have
the package in Buster ?
Given its purpose - "extremely simple MTA [...]" - should this issue really be
considered "serious" (and Release Critical) ?
PS: ssmtp is extremely handy to forward machine-generated messages
On Thu, Dec 13, 2018 at 11:21:35PM +0100, Jonas Smedegaard wrote:
> Control: tags -1 help
>
> Quoting Guido Günther (2018-12-13 19:21:45)
> > On Thu, Dec 13, 2018 at 05:53:03PM +0100, Jonas Smedegaard wrote:
> > > @Guido, could you please have a fresh look at this bug to see if it
> > > can
Processing commands for cont...@bugs.debian.org:
> severity 914814 serious
Bug #914814 [src:spades] spades: FTBFS with jemalloc/experimental
Severity set to 'serious' from 'normal'
> retitle 914814 spades: FTBFS with jemalloc 5
Bug #914814 [src:spades] spades: FTBFS with jemalloc/experimental
1 - 100 of 153 matches
Mail list logo
