Source: musicbrainzngs
Version: 0.5-2
Severity: serious
Justification: Policy 4.9
User: la...@debian.org
Usertags: network-access
Dear Maintainer,
Whilst musicbrainzngs builds successfully on unstable/amd64, according to
Debian Policy 4.9 packages may not attempt network access during
a build.
Hello Julian Wollrath!
On Sat, Jul 09, 2016 at 11:31:06AM +0200, Julian Wollrath wrote:
> Hi,
>
> I do not have the rights to change anything in collab-maint, therefore I
> attached two patches to update the packaging for 4.6.0.
Thanks for your help. I've done:
$ git fetch shemminger
$ gbp
found 830170 1.14.0-2
thanks
Am still seeing this in 1.14.0-2:
00:00:00.00 IP 6aa14ef749e2.46243 > dnscache.uct.ac.za.domain: 61838+ A?
dnspython.org. (31)
00:00:00.168510 IP dnscache.uct.ac.za.domain > 6aa14ef749e2.46243: 61838
1/4/2 A 54.231.131.132 (216)
00:00:06.271805 IP
Source: elib.intl
Version: 0.0.3~git20110809-3
Severity: serious
Justification: Policy 4.9
User: la...@debian.org
Usertags: network-access
Dear Maintainer,
Whilst elib.intl builds successfully on unstable/amd64, according to
Debian Policy 4.9 packages may not attempt network access during
a
Source: elasticsearch-curator
Version: 4.0.1-1
Severity: serious
Justification: Policy 4.9
User: la...@debian.org
Usertags: network-access
Dear Maintainer,
Whilst elasticsearch-curator builds successfully on unstable/amd64, according to
Debian Policy 4.9 packages may not attempt network access
Source: elib.intl
Version: 0.0.3~git20110809-3
Severity: serious
Justification: Policy 4.9
User: la...@debian.org
Usertags: network-access
Dear Maintainer,
Whilst elib.intl builds successfully on unstable/amd64, according to
Debian Policy 4.9 packages may not attempt network access during
a
Source: elib.intl
Version: 0.0.3~git20110809-3
Severity: serious
Justification: Policy 4.9
User: la...@debian.org
Usertags: network-access
Dear Maintainer,
Whilst elib.intl builds successfully on unstable/amd64, according to
Debian Policy 4.9 packages may not attempt network access during
a
Package: startpar
Version: 0.59-3
Tags: patch
Severity: serious
Hi
startpar build fails on current sid:
/usr/bin/make STARTPAR=/tmp/startpar/startpar-0.59/startpar -C testsuite check
make[3]: Entering directory '/tmp/startpar/startpar-0.59/testsuite'
On 2016-07-09 09:40 +, Niels Thykier wrote:
> Sven Joachim:
>> On 2016-07-08 09:53 +, Niels Thykier wrote:
>>
>>> [...]
>>>
>>> Thanks, I have applied it to master and it will be part of the next
>>> debhelper release. :)
>>
>> Unfortunately my patch breaks dh_installdocs in compat 11
Package: tracker.debian.org
Severity: wishlist
Hi,
Could you please add a link to Debian Maintainer Dashboard next to
maintainers and uploaders?
I would suggest something like "(dmd)" next to names, with "dmd" a link
pointing to e.g.
https://udd.debian.org/dmd/?hertzog%40debian.org#todo
-
On Sat, 9 Jul 2016 11:07, n...@walfield.org said:
> You can do this part using the new TOFU functionality. Specificaly,
> you just need to set the TOFU policy for the key to bad (gpg2
> --tofu-policy bad KEYID).
That was no Simon's question. He seems to want a tool to quickly change
the
Control: retitle -1 ITP trac-icalview, trac-icalviewdplugin replacement
Stop
If I did that correct, then has this BR now a better title then none. :-)
Cheers
Geert Stappers
Please, make /etc/skel/.bashrc and root's .bashrc identical. Yes, you may make
them both as empty as you want. But there is no any need in keeping them
different.
When I create new system, I edit this files using my scripts. This is part of
my scripts:
sed -i
Package: wnpp
Severity: wishlist
Owner: Al Nikolov
* Package name: trac-icalview
Version : 15654
Upstream Author : Xavier Péchoultres
* URL : http://trac-hacks.org/wiki/IcalViewPlugin
* License : GPL2
Package: tpm-tools
Version: 1.3.8-2+b1
Severity: normal
Dear Maintainer,
tpm-tools shouldn't depend on opencryptoki, or the package should be
split into the tools that do and don't depend on opencryptoki (most of
them don't). From what I can tell it seems only the tpmtoken_* commands
actually
Hi Peter!
Thanks for forwarding the bug.
* Peter Pentchev , 2016-07-09, 02:29:
in the worst case we may decide to carry this as a Debian-specific
patch for the benefit of compatibility with GNU tar, but, to be honest,
I see a couple of potential drawbacks with this approach,
Source: vim
Version: 2:7.4.1829-1
Severity: wishlist
Tags: patch
Hi!
The syntax highlighting in debian/control currently doesn't recognize
mips64el as a valid architecture.
The attached patch adds support for it.
Kind regards,
Reiner
diff --git a/debian/patches/debian_architectures.patch
severity 796604 important
thanks
On Thu, Jul 07, 2016 at 04:05:30PM +0200, Martin Pitt wrote:
> severity 796604 grave
>
> Then your package will most likely stop working properly under
> systemd.
Because console-setup is a standard for Debian now, the main function of
the package
Hi,
according to bug #827669 the current minetest-mod-mobf packaging is
buggy/incomplete with a debian/ directory shipped within and probably
missing directories ; in #830493 I pointed out that one of the missing
directories was really a missing package on which to depend.
After some more
Package: qa.debian.org
Severity: normal
User: qa.debian@packages.debian.org
Usertags: udd
Hi,
It would be nice to provide a way to receive TODO items about a set of
packages (as selected using DMD's selector) by email.
A design that could probably work for DSA would be a separate table to
¡Hola Éter!
El 2016-07-09 a las 10:14 +0200, Éter escribió:
Package: kactivitymanagerd
Version: 5.6.4-2
Severity: important
kactivitymanagerd does not work without libqt5sql5-sqlite or any other "database driver" recommended by the package libqt5sql5.
In the current state, kactivitymanagerd
Source: betamax
Version: 0.7.0-2
Severity: serious
Justification: Policy 4.9
User: la...@debian.org
Usertags: network-access
Dear Maintainer,
Whilst betamax builds successfully on unstable/amd64, according to
Debian Policy 4.9 packages may not attempt network access during
a build.
Sven Joachim:
> On 2016-07-08 09:53 +, Niels Thykier wrote:
>
>> [...]
>>
>> Thanks, I have applied it to master and it will be part of the next
>> debhelper release. :)
>
> Unfortunately my patch breaks dh_installdocs in compat 11 mode, as I
> have just discovered. :-/ Will look into it,
Hi,
I do not have the rights to change anything in collab-maint, therefore I
attached two patches to update the packaging for 4.6.0.
Cheers,
Julian>From 8962724984919e869e7df54b72a389f0ec1ed63e Mon Sep 17 00:00:00 2001
From: Julian Wollrath
Date: Sat, 9 Jul 2016 10:54:28
> > Interesting. Can't seem to reproduce here in latest sid. Do you
> > have limited memory or something like that..? Concurrency..?
>
> No, the machine has 8 GB of RAM. I also don't recall the machine
> being heavily loaded when I reran the test build to confirm. The
> first time, I used
Hi,
attached is a patch, that updates the packaging from svn for upstream
version 4.7.
Cheers,
Julian>From 3e75343efc415c32c45dbed736b68677051c943f Mon Sep 17 00:00:00 2001
From: Julian Wollrath
Date: Sat, 9 Jul 2016 11:13:21 +0200
Subject: [PATCH] New upstream release
---
Hi, I just discovered #638283, do you have any news on this issue?
In case I can fix fgrun instead, I already have the fix :p
thanks
G.
On 2016-07-08 09:53 +, Niels Thykier wrote:
> Sven Joachim:
>> Control: reassign -1 debhelper 9.20160702
>> Control: tags -1 + patch
>>
>> Am 08.07.2016 um 07:07 schrieb Helmut Grohne:
>>
>>> [...]
>>
>> It's a regression in debhelper 9.20160702 that is triggered if a package
>> symlinks
* Любен Каравелов [160709 09:11]:
[..]
> echo "export IMSM_NO_PLATFORM=1" >> /conf/param.conf
[..]
Note that the mdadm man page makes it quite clear that this is not
intended for normal operation, but rather mostly desaster recovery.
Putting this into param.conf and
Thanks so much!
Sure I will, every day learning something new...
On Fri, 08 Jul 2016 18:18:50 +0200,
Simon Richter wrote:
> On 08.07.2016 14:54, Werner Koch wrote:
> 2. mark the key as invalid/unusable.
>
> If someone I trust signs the fake key, that key is marked as "valid", so
> signatures will be accepted and the key becomes a candidate for
> encryption. As
Source: simgear
Severity: serious
Justification: breaks reverse dependencies, with underlink
Version: 1:2016.2.1+dfsg-6
Hi, while rebuilding fgrun I noticed a new FTBFS [1], many libraries missing,
e.g.
GL, pthread, expat and so on
root@Unimatrix04-Xenial:/fgrun# objdump -t
I had the same problem but upgrading the kf5 plasma libraries to 5.23
fixed it.
On 06/07/16 20:51, Diederik de Haas wrote:
On maandag 4 juli 2016 20:03:54 CEST Gard Spreemann wrote:
After upgrading plasma-workspace from 4:5.6.4-2 to 4:5.6.5.1-1 today,
krunner has stopped functioning
Source: gitit
Version: 0.12.1.1+dfsg-2
Severity: serious
Your package failed to build on arm64:
Erratum 843419 found and fixed at
"/usr/lib/ghc/ghc_0AG9TOjDEtx4Ji3wSwHOBe/libHSghc-7.10.3-0AG9TOjDEtx4Ji3wSwHOBe.a(Base.o)",
section 1, offset 0x00018890.
Erratum 843419 found and fixed at
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm
Dear Release Team,
please remove ruby-bdb from testing. It's a maintenance burden
and as such should go. There's an open RC bug against it, but
autoremoval is not picking it up so far.
Thanks,
* James Lu [160709 08:37]:
> Many few months ago, me and David prepared an upload of git-up 0.5.12-1,
> which can be found in the Debian Ruby Git repository at
> https://anonscm.debian.org/cgit/pkg-ruby-extras/git-up.git
[..]
> Upstream has not done anything so far to fix the
Package: wnpp
Severity: wishlist
Owner: Al Nikolov
* Package name: trac-datefield
Version : 14902
Upstream Author : Noah Kantrowitz
* URL : http://trac-hacks.org/wiki/DateFieldPlugin
* License : BSD
Programming Lang: Python
Description
Package: kactivitymanagerd
Version: 5.6.4-2
Severity: important
kactivitymanagerd does not work without libqt5sql5-sqlite or any other
"database driver" recommended by the package libqt5sql5.
In the current state, kactivitymanagerd does not depends nor recommends nor
suggests any of those
Package: partclone
Version: 0.2.88-1
partclone.xfs man page is included, but not the binary.
seems to be because configure.ac has `enable_xfs="yes"` commented out.
rebuilds OK and works fine with it uncommented.
--- configure.ac.orig 2016-07-09 14:27:47.477298030 +1000
+++ configure.ac
On Tue, 5 Jul 2016 10:54:02 +0100 Robie Basak
wrote:
> On Mon, Jul 04, 2016 at 07:42:32PM +0200, Michael Biebl wrote:
> > Hm, that repository is gone.
>
> We unified the repository into
> http://anonscm.debian.org/cgit/pkg-mysql/mysql.git/log/, yesterday which
> does
Control: tags 829176 + patch
Control: tags 829176 + pending
Dear maintainer,
I've prepared an NMU for libapache-htpasswd-perl (versioned as 1.8-1.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards.
--
.''`. Homepage https://info.comodo.priv.at/
Hi, I sponsored it, even if for a next time please do two things:
split the patch into two different files
one for armhf and one for BE failures.
"add-patch" is a good command to add single commits
wget github.com/project/commit.patch
(add the .patch)
and then add-patch of the file
but since
Package: gnome-pie
Version: 0.6.8-2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
gnome-pie package doesn't start anymore.
Error message :
[MESSAGE] Welcome to Gnome-Pie 0.6.8!
** (process:23086): CRITICAL (recursed) **: string_substring:
Package: installation-reports
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this
Package: ginac
Version: 1.7.0-1
Severity: serious
The uploaded amd64 package was built with gcc-6. But on other
architectures, it was built with gcc-5 -std=c++11. To avoid any ABI
breakage or yet anther soname bump, this package should not migrate to
testing.
A new package should be uploaded as
control: tags -1 + moreinfo
Hi Sean,
thanks for your bug report!
On Sat, Jul 09, 2016 at 03:29:56AM +, Sean Whitton wrote:
> piuparts considers package purge to have failed if the file
> /var/log/apt/eipp.log.xz remains, e.g.:
>
> 2m6.4s ERROR: FAIL: Package purging left files on
Package: wnpp
Severity: wishlist
Owner: Dmitry Smirnov
X-Debbugs-CC: debian-de...@lists.debian.org,
pkg-go-maintain...@lists.alioth.debian.org
Control: affects -1 docker-swarm
Package name: golang-github-docker-leadership
Version: 0.0~git20160208
Upstream Author:
Package: wnpp
Severity: wishlist
Owner: Dmitry Smirnov
X-Debbugs-CC: debian-de...@lists.debian.org,
pkg-go-maintain...@lists.alioth.debian.org
Control: affects -1 docker-swarm
Package name: golang-github-skarademir-naturalsort
Version: 0.0~git20150715
Upstream
Heh, yes. :)
- Josh Triplett
On Sat, Jul 09, 2016 at 05:53:35AM +, Craig Small wrote:
> I messed up the manual patch when it wouldn't apply. I put the return
> before the attrset() That'll do it!
>
> - Craig
>
>
> On Sat, Jul 9, 2016 at 3:38 PM Craig Small wrote:
>
>
Control: reopen -1
The new version still fails to build on the buildds.
Thanks,
Jeremy Bicha
This is probably not relevant any more, but it looks like the fsck could
be getting killed while trying to allocate memory. Taking into account
the size of the filesystems (2.5TB) the fsck might need several GB of RAM
to load the required metadata into memory. It is also quite possible this
is
201 - 251 of 251 matches
Mail list logo