Source: libcommons-codec-java
Version: 1.10-1
Severity: serious
Justification: Policy 4.9
User: la...@debian.org
Usertags: network-access
Dear Maintainer,
Whilst libcommons-codec-java builds successfully on unstable/amd64, according to
Debian Policy 4.9 packages may not attempt network access dur
> Well, you don't edit shipped files. Neither conffiles nor normal files.
> Instead, you put these values into a new file (not a shipped file!,
> maybe ship a template in /usr/share/$pkg) in either /etc or /var (with a
> symlink in /usr pointing to it) that is solely managed by the maintainer
> scr
Processing commands for cont...@bugs.debian.org:
> severity 831918 serious
Bug #831918 [src:bglibs] bglibs: FTBFS with dpkg-buildpackage -A: make: *** No
rule to make target 'build-indep'. Stop.
Severity set to 'serious' from 'important'
> severity 831921 serious
Bug #831921 [src:daemontools] da
Le 21/07/2016 à 09:12, Chris Lamb a écrit :
> Whilst libcommons-codec-java builds successfully on unstable/amd64, according
> to
> Debian Policy 4.9 packages may not attempt network access during
> a build.
Hi Chris,
Thank you for reporting this issue. This happens because the Javadoc is
linked
> Something like the attached patch? (Untested)
Had more time than I thought; updated and (quickly) tested patch
attached.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
diff --git a/debian/rules b/debian/rules
index f4a187f..
Processing commands for cont...@bugs.debian.org:
> severity 830955 normal
Bug #830955 [keepalived] keepalived: Segfault - keepalived doesn't work without
CONFIG_IP_VS
Severity set to 'normal' from 'critical'
> merge 830955 544700
Bug #830955 [keepalived] keepalived: Segfault - keepalived doesn't
severity 830955 normal
merge 830955 544700
thanks
On Wed, 13 Jul 2016, Mathieu Ruellan wrote:
> Package: keepalived
> Version: 1.2.20-1
> Severity: critical
> Justification: causes serious data loss
>
> Dear Maintainer,
>
> Could you please update the keepalived to fix this issue?
>
>
> https
> the javadoc tool merely checks the existence of the remote
> documentation to add href links in the generated files.
Mm. This also happens with Python's "Sphinx" documentation framework.
> This is optional and doesn't break the build if it doesn't work.
Builds may not even _attempt_ access IM
On 2016-07-21 10:05, Chris Lamb wrote:
>> Something like the attached patch? (Untested)
>
> Had more time than I thought; updated and (quickly) tested patch
> attached.
postrm purge should delete /etc/zm/core.php, shouldn't it?
What should happen if core.php.default changes its content? There ar
> postrm purge should delete /etc/zm/core.php, shouldn't it?
Probably. Patches are proof of concept, am not the maintainer/user
here. :)
> What should happen if core.php.default changes its content? There are a
> lot of options, maybe a new one is added some day ...
Good point. So maybe the mai
On Thu, 21 Jul 2016 10:00:06 +0200, Emmanuel Bourg wrote:
> My understanding of the "no network access" rule was that the build must
> not require a network connection to complete, nor pull into the package
> external elements not found in the source tarball at build time. I guess
> the intent is
> PS1: I can't say that I'm 100% convinced by this policy change.
This may not be the appropriate venue for a protracted discussion as
it's liable to get hidden but can you briefly outline why?
> PS2: I'm surprised that it took so long after the release of policy
> 3.9.7 before someone start
> Interesting, thank you for the reference. libcommons-codec-java
> currently declares a compliance to the version 3.9.6 of the policy. Does
> it mean the new rule doesn't apply to it yet? :)
Oh, now /that's/ a very cute argument :)
Regards,
--
,''`.
: :' : Chris Lamb
`. `
Le 21/07/2016 à 10:24, gregor herrmann a écrit :
> In my understanding, this has changed in 3.9.7 (emphasis mine):
>
> * Policy: [4.9] debian/rules: required targets _must not attempt_ network
> [..]
> Closes: #770016
Interesting, thank you for the reference. libcommons-codec-java
currently
On Thursday, 21 July 2016 9:31:47 AM AEST Chris Lamb wrote:
> This seems an odd.attitude to have as the maintainer.. :)
Sorry if I didn't make it clear: I'm not blaming anyone, it was a oversight
on my side which will be fixed. Chris, since I applied your patch I wanted
you to get a feedback of
Le 21/07/2016 à 10:41, Chris Lamb a écrit :
> Oh, now /that's/ a very cute argument :)
I'm fine with fixing the package so I won't defend this argument too
much, but I'd be curious to know. Because if the compliance level
declared by the package doesn't matter, it would mean the
Standards-Version
> I won't defend this argument too much, but I'd be curious to know.
Same here. Alas I'm not a Policy "wonk" (and try to avoid being one as
it tends to devolve technical discussions into ones of intepretative
legal-like arguments that focus on the minutae of language rather than
on, well, what is
On Thu, 21 Jul 2016 10:33:35 +0200, Chris Lamb wrote:
> > PS1: I can't say that I'm 100% convinced by this policy change.
> This may not be the appropriate venue for a protracted discussion as
> it's liable to get hidden but can you briefly outline why?
My experience with perl packages shows that
Thanks :)
> - by disabling them, even if they fail gracefully, in order to follow
> policy, we effectively castrate the tests, which doesn't seem right
> from a QA POV.
Mm, agreed. Moving these tests to the autopkgtest infrastructure is one
fix but it's not "that" clean a solution..
Regard
Your message dated Thu, 21 Jul 2016 11:16:28 +0200
with message-id <20160721091628.gc10...@xanadu.blop.info>
and subject line Re: Bug#831240: google-perftools: FTBFS: Running death test 0
hangs
has caused the Debian Bug report #831240,
regarding google-perftools: FTBFS: Running death test 0 hangs
On Thu, 21 Jul 2016 11:19:46 +0200, Chris Lamb wrote:
> > - by disabling them, even if they fail gracefully, in order to follow
> > policy, we effectively castrate the tests, which doesn't seem right
> > from a QA POV.
> Mm, agreed. Moving these tests to the autopkgtest infrastructure is one
>
Processing commands for cont...@bugs.debian.org:
> tags 831067 pending
Bug #831067 [src:openvdb] openvdb: FTBFS with GCC 6: cstdlib:75:25: fatal
error: stdlib.h: No such file or directory
Added tag(s) pending.
>
End of message, stopping processing here.
Please contact me if you need assistance.
I believe there is a control field for autopkgtest for this purpose.
gregor herrmann wrote:
> On Thu, 21 Jul 2016 11:19:46 +0200, Chris Lamb wrote:
>
> > > - by disabling them, even if they fail gracefully, in order to follow
> > > policy, we effectively castrate the tests, which doesn't seem
Your message dated Thu, 21 Jul 2016 09:56:24 +
with message-id
and subject line Bug#831181: fixed in odin 2.0.2-0.2
has caused the Debian Bug report #831181,
regarding odin: FTBFS with GCC 6: odinpulse.cpp:659:35: error: call of
overloaded 'sqrt(funcMode&)' is ambiguous
to be marked as done.
severity 831240 important
reopen 831240
On Thu, 21 Jul 2016, Lucas Nussbaum wrote:
> I recently discovered that the official Debian images on AWS EC2 include
> some sysctl tunings (see
> https://github.com/andsens/bootstrap-vz/pull/256/commits/06da309895f69573996a4c1ff027f999155b876b#diff-43081b5
Processing commands for cont...@bugs.debian.org:
> severity 831240 important
Bug #831240 {Done: Lucas Nussbaum } [src:google-perftools]
google-perftools: FTBFS: Running death test 0 hangs
Severity set to 'important' from 'serious'
> reopen 831240
Bug #831240 {Done: Lucas Nussbaum } [src:google-pe
Processing control commands:
> tags -1 + patch
Bug #412185 [atftpd] Upgrade overwrites /etc/default/atftpd, inetd.conf
Added tag(s) patch.
--
412185: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=412185
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 + patch
[Ludovic Drolez]
> Yes proper auto-configuration of this package is a nightmare, maybe the
> better is to drop all auto-config and suggest people to manually
> configure it.
Probably not. Here is a draft patch (untested) which make sure the
atftpd.config script load the
Processing commands for cont...@bugs.debian.org:
> close 831994
Bug #831994 [sponsorship-requests] RFS: python-prompt-toolkit/1.0.3-1 (ITP)
Marked Bug as done
> close 821990
Bug #821990 [gworldclock] gworldclock: Build arch:all+arch:any but is missing
build-{arch,indep} targets
Marked Bug as done
Processing control commands:
> severity -1 critical
Bug #814905 [liblog4cplus-1.1-9] liblog4cplus-1.1-9: C++11 methods missing from
the binary
Severity set to 'critical' from 'normal'
> block 831118 by -1
Bug #831118 [src:openalpr] openalpr: FTBFS with GCC 6: daemon.cpp:153:
undefined reference
[Petter Reinholdtsen]
> As far as I can see, this can not be fixed in openalpr, but must be fixed in
> liblog4cplus. Perhaps this bug should be reassigned?
No need, as it is already reported as bug #814905.
--
Happy hacking
Petter Reinholdtsen
tag 825095 pending
thanks
Hello,
Bug #825095 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:
http://git.debian.org/?p=python-modules/packages/python-backports-shutil-get-terminal-size.git;a=commitdiff;h=3dacd27
Processing commands for cont...@bugs.debian.org:
> tag 825095 pending
Bug #825095 [python-backports-shutil-get-terminal-size]
python-backports-shutil-get-terminal-size: clashes over backports/__init__.py
with python-backports.ssl-match-hostname
Added tag(s) pending.
> thanks
Stopping processing
Your message dated Thu, 21 Jul 2016 11:19:21 +
with message-id
and subject line Bug#811717: fixed in ivtools 1.2.11a1-7
has caused the Debian Bug report #811717,
regarding ivtools: FTBFS with GCC 6: narrowing conversion
to be marked as done.
This means that you claim that the problem has been
Your message dated Thu, 21 Jul 2016 11:48:34 +
with message-id
and subject line Bug#825095: fixed in python-backports-shutil-get-terminal-size
1.0.0-2
has caused the Debian Bug report #825095,
regarding python-backports-shutil-get-terminal-size: clashes over
backports/__init__.py with python
On Wed, 20 Jul 2016 22:06:05 +0300 Faidon Liambotis wrote:
> Stack trace of thread 4122:
> #0 0x7fa47ae7f1c8 raise (libc.so.6)
> #1 0x7fa47ae8064a abort (libc.so.6)
> #2 0x7fa4719b8f5b n/a (libavcodec.so.57)
>
Your message dated Thu, 21 Jul 2016 12:05:30 +
with message-id
and subject line Bug#811620: fixed in xml-security-c 1.7.3-2
has caused the Debian Bug report #811620,
regarding FTBFS with GCC 6: cannot convert x to y
to be marked as done.
This means that you claim that the problem has been dea
Processing commands for cont...@bugs.debian.org:
> tags 826197 + fixed-upstream patch
Bug #826197 [src:discount] discount: FTBFS on many architectures: 1 test failed
Added tag(s) fixed-upstream and patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
826197: htt
tags 826197 + fixed-upstream patch
thanks
This issue was fixed upstream (and the bug is actually on those arches
where the tests did NOT fail...):
https://github.com/Orc/discount/commit/0d71ce77859c44aad7379d70c9024d5047577100
https://github.com/Orc/discount/commit/aa9a54bddb3211204625c1eb6a26
Your message dated Thu, 21 Jul 2016 12:18:28 +
with message-id
and subject line Bug#831804: fixed in apcupsd 3.14.14-0.2
has caused the Debian Bug report #831804,
regarding Fails to build on arch:all buildd
to be marked as done.
This means that you claim that the problem has been dealt with.
If the issue is reproducible, please someone test if it disappears once you
recompile GStreamer against the installed libavcodec headers.
Your message dated Thu, 21 Jul 2016 13:03:39 +
with message-id
and subject line Bug#831741: fixed in pdns 4.0.0-5
has caused the Debian Bug report #831741,
regarding pdns-backend-pgsql: new pdns spams postgres log until disk fills up
to be marked as done.
This means that you claim that the pr
resteasy has been updated and I triaged the remaining tomcat6 bugs.
I think we can proceed with the removal now.
Your message dated Thu, 21 Jul 2016 13:36:44 +
with message-id
and subject line Bug#831067: fixed in openvdb 3.1.0-4
has caused the Debian Bug report #831067,
regarding openvdb: FTBFS with GCC 6: cstdlib:75:25: fatal error: stdlib.h: No
such file or directory
to be marked as done.
This means
Your message dated Thu, 21 Jul 2016 13:48:33 +
with message-id
and subject line Bug#812040: fixed in gelemental 1.2.0-10
has caused the Debian Bug report #812040,
regarding gelemental: FTBFS with GCC 6: operands to ?: have different
to be marked as done.
This means that you claim that the pro
Tracked upstream in
https://github.com/alastair/python-musicbrainzngs/issues/201
However, this is rather a debian packaging issue than an issue upstream.
The internet access is needed for the docs (sphinx/intersphinx)
see also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830186
The solutio
Martyn,
On 20/07/16 19:31, Martyn Smith wrote:
> Yeah, I'm not sure if anyone uses it, but it seems pretty pointless now,
> I'd be quite happy for it to just disappear :-)
Thanks for replying.
I will make mtail conclict on monkeytail, so the bug can be closed.
Would you file the removal bug wit
tag 831863 + pending
thanks
Some bugs in the mtail package are closed in revision
870c98c509101470bd90710abc26c5afa1aa3c22 in branch 'debian/sid' by
Martín Ferrari
The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/mtail.git/commit/?id=870c98c
Commit message:
Confl
Processing commands for cont...@bugs.debian.org:
> tag 831863 + pending
Bug #831863 [monkeytail,mtail] monkeytail,mtail: both ship /usr/bin/mtail
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
831863: http://bugs.debian.org/cgi-bin/bugreport
Your message dated Thu, 21 Jul 2016 16:21:29 +
with message-id
and subject line Bug#831176: fixed in gazebo 7.3.0+dfsg-2
has caused the Debian Bug report #831176,
regarding gazebo: FTBFS with GCC 6: physics/libgazebo_physics.so.7.0.0:
undefined reference to
`boost::re_detail::cpp_regex_trait
reassign 830227 debhelper 9.20160702
forcemerge 830309 830227
affects 830227 src:xdffileio
thanks
The build fails because of debhelper because xdffileio use
dh_installdocs --link-doc
The bug has already been fixed in debhelper 9.20160709
This should close the bug
Cheers,
Nicolas Bourdaud
Processing commands for cont...@bugs.debian.org:
> reassign 830227 debhelper 9.20160702
Bug #830227 [src:xdffileio] xdffileio: FTBFS: install: cannot change
permissions of 'debian/libxdffileio-dev/usr/share/doc/libxdffileio-dev': No
such file or directory
Bug reassigned from package 'src:xdffile
Your message dated Thu, 21 Jul 2016 16:29:04 +
with message-id
and subject line Bug#830681: fixed in trilinos 12.6.3-2
has caused the Debian Bug report #830681,
regarding trilinos-all-dev: Updating binutils breaks trilinos
to be marked as done.
This means that you claim that the problem has b
Processing control commands:
> tags 817586 + patch
Bug #817586 [src:most] most: Removal of debhelper compat 4
Added tag(s) patch.
> tags 817586 + pending
Bug #817586 [src:most] most: Removal of debhelper compat 4
Added tag(s) pending.
--
817586: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=8
Control: tags 817586 + patch
Control: tags 817586 + pending
Dear maintainer,
I've prepared an NMU for most (versioned as 5.0.0a-2.4) 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/ - OpenPGP key 0x
Your message dated Thu, 21 Jul 2016 16:53:24 +
with message-id
and subject line Bug#829360: fixed in dq 20160720-1
has caused the Debian Bug report #829360,
regarding dqcache-run: priority is standard but depends on optional packages
to be marked as done.
This means that you claim that the pr
Your message dated Thu, 21 Jul 2016 16:55:45 +
with message-id
and subject line Bug#831863: fixed in mtail 0.0+git20160716.f911b02-1
has caused the Debian Bug report #831863,
regarding monkeytail,mtail: both ship /usr/bin/mtail
to be marked as done.
This means that you claim that the problem
On Thu, 09 Jun 2016 10:29:23 +0200 "Mathieu Malaterre" wrote:
> This is a continued operation since src:jasper removal for stretch
> release.
>
> src:openjpeg will be removed from Debian for the stretch release (and
> following that, the archive in general). For more information see:
> http://bug
On Thu, 09 Jun 2016 10:30:01 +0200 "Mathieu Malaterre" wrote:
> This is a continued operation since src:jasper removal for stretch
> release.
>
> src:openjpeg will be removed from Debian for the stretch release (and
> following that, the archive in general). For more information see:
> http://bug
Your message dated Thu, 21 Jul 2016 17:22:19 +
with message-id
and subject line Bug#830333: fixed in topal 75-2.1
has caused the Debian Bug report #830333,
regarding topal: FTBFS: build-dependency not installable: gnat-4.9
to be marked as done.
This means that you claim that the problem has b
Processing control commands:
> block -1 by 829178 829409
Bug #832045 [ftp.debian.org] RM: tidy -- RoQA; abandoned; superseded by
tidy-html5
832045 was not blocked by any bugs.
832045 was not blocking any bugs.
Added blocking bug(s) of 832045: 829409 and 829178
--
832045: http://bugs.debian.org/
Control: tag -1 + pending patch
Hi Logan and Uwe,
Logan Rosen wrote:
> In Ubuntu, the attached patch was applied to achieve the following:
Logan: Thanks!
> * debian/compat: Bump to 9.
> * debian/control:
> - Build-depend on debhelper (>= 9).
> - Depend on ${misc:Depends}.
> * debi
Processing control commands:
> tag -1 + pending patch
Bug #817373 [src:bb] bb: Removal of debhelper compat 4
Added tag(s) patch and pending.
--
817373: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817373
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
This test failure seems to be caused by a new libarchive version.
According to ci.debian.net this test started first failing on
2016-06-01. The difference between this test run and the previous one
(where this specific test still passed) is the version of libarchive13:
3.1.2-11.1 vs. 3.2.0-2.
s
Processing commands for cont...@bugs.debian.org:
> forwarded 829022 https://github.com/Changaco/python-libarchive-c/issues/34
Bug #829022 [src:python-libarchive-c] python-libarchive-c: FTBFS:
tests/test_entry.py::test_check_archiveentry_with_unicode_and_binary_entries_zip2
FAILED
Set Bug forward
On Thu, 16 Jun 2016 16:00:02 -0300 Herbert Fortes wrote:
> We have to wait a next release:
>
> https://github.com/jazzband/django-authority/issues/50#issuecomment-226319945
>
>
About Django 1.9.
It seems that one will do a 'Pull Request' and the
upstream will do the merge .
regards,
-- Her
Hi,
Firstly thanks for your report.
Could you provide what is your radiostream? and send please the complete
log again.
Are you using gnome 3 shell? if so, there's a bug about it #687007.
Best regards.
Elías Alejandro
On Tue, Jul 19, 2016 at 5:06 AM, Jörg Frings-Fürst
wrote:
> Package: radiot
To be honest, I don't even know how to go about doing it.
If you could file it that'd be great!
Thanks,
Martyn Smith
On Fri, 22 Jul 2016 at 3:50 AM "Martín Ferrari"
<
mailto:
> wrote:
Martyn,
On 20/07/16 19:31, Martyn Smith wrote:
> Yeah, I'm not sure if anyone uses it, but it seems pretty
On 21/07/16 19:35, Martyn Smith wrote:
> To be honest, I don't even know how to go about doing it.
>
> If you could file it that'd be great!
The simplest way is to run reportbug "ftp.debian.org" and follow the
instructions. I can do it for you :)
--
Martín Ferrari (Tincho)
Processing commands for cont...@bugs.debian.org:
> tag 830555 pending
Bug #830555 [src:foolscap] foolscap: accesses the internet during build
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
830555: http://bugs.debian.org/cgi-bin/bugreport.cgi
tag 830555 pending
thanks
Hello,
Bug #830555 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:
http://git.debian.org/?p=python-modules/packages/foolscap.git;a=commitdiff;h=6bae4dc
---
commit 6bae4dc17b96e0619e4f
On 21.07.2016 05:00, Brian Warner wrote:
I've just released foolscap-0.12.0 to PyPI, which should fix this. We've
deprecated a function that talks to the root nameservers, and this
release removes the test that used to exercise that function. I think
that was the only place which should be doing
Your message dated Thu, 21 Jul 2016 18:53:52 +
with message-id
and subject line Bug#812046: fixed in open-vm-tools 2:10.0.7-3227872-4.1
has caused the Debian Bug report #812046,
regarding open-vm-tools: FTBFS with GCC 6: dereferencing pointer
to be marked as done.
This means that you claim th
Your message dated Thu, 21 Jul 2016 19:36:38 +
with message-id
and subject line Bug#831221: fixed in sqlobject 3.0.0+dfsg-2
has caused the Debian Bug report #831221,
regarding sqlobject-admin: fails to upgrade from 'testing' - trying to
overwrite /usr/bin/sqlobject-admin
to be marked as done.
Processing commands for cont...@bugs.debian.org:
> reopen 821990
Bug #821990 {Done: Julien Puydt } [gworldclock]
gworldclock: Build arch:all+arch:any but is missing build-{arch,indep} targets
Bug reopened
Ignoring request to alter fixed versions of bug #821990 to the same values
previously set
>
Source: supertuxkart
Version: 0.9.2-1
Severity: serious
Justification: does not include source code of GPL licensed work
Supertuxkart contains a song called "Boom boom boom" in Ogg Vorbis
format. According to the credits and debian/copyright, this song is
created by Matt Thomas, and is licensed un
Processing commands for cont...@bugs.debian.org:
> tags 831192 + pending
Bug #831192 [src:icedove] icedove: FTBFS with GCC 6:
../../dist/include/mozilla/mozalloc.h:192:28: error: 'malloc' was not declared
in this scope
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me i
Package: intel-microcode
Followup-For: Bug #828819
Dear Maintainer,
thanks for clearing this up so quickly :). Just as a follow up, Tuxedo released
a new BIOS version including microcode 0x8a and I tested that 3.20160607.1
doesn't fail with that anymore.
Cheers Jochen
Your message dated Thu, 21 Jul 2016 22:05:47 +
with message-id
and subject line Bug#828883: fixed in dh-python 2.20160721
has caused the Debian Bug report #828883,
regarding zope.interface: FTBFS: E: Please add apropriate interpreter package
to Build-Depends, see pybuild(1) for details
to be
Your message dated Thu, 21 Jul 2016 22:11:34 +
with message-id
and subject line Bug#831868: fixed in pyjwt 1.4.1-1
has caused the Debian Bug report #831868,
regarding python-jwt: ships /usr/lib/python2.7/dist-packages/.coverage
to be marked as done.
This means that you claim that the problem
Processing commands for cont...@bugs.debian.org:
> tag 831768 moreinfo
Bug #831768 [radiotray] radiotray stops at start a radiostream
Added tag(s) moreinfo.
> tag 831768 = moreinfo
Bug #831768 [radiotray] radiotray stops at start a radiostream
Ignoring request to alter tags of bug #831768 to the s
Hi Mako,
I've prepared an NMU for most (versioned as 5.0.0a-2.4) and
uploaded it to DELAYED/10.
This is not a minimal bugfix NMU, as this package has not been touched
by the maintainer since 2010 and could clearly do with an update, so
I've updated it. Mako - if you want to keep it all old and
Your message dated Fri, 22 Jul 2016 01:19:18 +
with message-id
and subject line Bug#832023: Removed package(s) from unstable
has caused the Debian Bug report #831733,
regarding tomcat6: Don't include in Stretch
to be marked as done.
This means that you claim that the problem has been dealt wi
Your message dated Fri, 22 Jul 2016 01:20:54 +
with message-id
and subject line Bug#832065: Removed package(s) from unstable
has caused the Debian Bug report #817316,
regarding clean-crypto: Mandatory debian/compat for debhelper
to be marked as done.
This means that you claim that the problem
Processing commands for cont...@bugs.debian.org:
> tags 831878 pending
Bug #831878 [cyphesis-cpp] cyphesis-cpp: fails to install in chroot:
update-rc.d: error: no runlevel symlinks to modify, aborting!
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assista
On Fri, 22 Jul 2016 02:09:52 +0100, Wookey wrote:
> Hi Mako,
Hi Wookey and Mako,
> I've prepared an NMU for most (versioned as 5.0.0a-2.4) and
> uploaded it to DELAYED/10.
Good to see so much interest in most; I did an NMU (to DELAYED/2) a
couple of hours before :)
> This is not a minimal bu
On Fri, 22 Jul 2016 03:24:45 +0200, gregor herrmann wrote:
> I'd love to see your NMU with all those fixes get into the archive
> (compared to my minimal "just bump debhelper compat level"), so I've
> reschedule my NMU to DELAYED/12 (as a hopefully not needed fallback).
Or did I reschedule your N
On Tue, Jul 19, 2016 at 07:48:33PM +0200, Salvatore Bonaccorso wrote:
> Source: lepton
> Version: 1.0-2
> Severity: grave
> Tags: security upstream
> Justification: user security hole
>
> Hi,
>
> Multiple issues were found in lepton. The CVE request was at
> http://www.openwall.com/lists/oss-secu
Hi Andreas,
On 07/20/2016 08:50 AM, Andreas Beckmann wrote:
Package: cyphesis-cpp
Version: 0.6.0-4
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 makes th
Source: libsvm
Version: 3.21+ds-1
Severity: serious
Justification: renders package unusable
Hi!
While updating libsvm from 3.12-1.1 to 3.21+ds-1:
=
Preparing to unpack .../libsvm3_3.21+ds-1_amd64.deb ...
dpkg: error processing archive
/var/cache/apt/archives/libsvm3_3.21+ds-1_amd64.deb (--u
On Fri, 22 Jul 2016, Jochen Sprickerhof wrote:
> thanks for clearing this up so quickly :). Just as a follow up, Tuxedo
> released
> a new BIOS version including microcode 0x8a and I tested that 3.20160607.1
> doesn't fail with that anymore.
Yeah, information about their BIOS update was forwarded
Processing commands for cont...@bugs.debian.org:
> forwarded 832062 https://github.com/supertuxkart/stk-code/issues/2577
Bug #832062 [src:supertuxkart] supertuxkart: source for GPL song
Boom_boom_boom.ogg missing
Set Bug forwarded-to-address to
'https://github.com/supertuxkart/stk-code/issues/25
Processing commands for cont...@bugs.debian.org:
> found 831145 5.22.0-1
Bug #831145 [src:kjsembed] kjsembed: FTBFS with GCC 6: dh_makeshlibs: failing
due to earlier errors
Marked as found in versions kjsembed/5.22.0-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
tag 830727 + pending
thanks
Some bugs in the golang-github-magiconair-properties package are
closed in revision 190f7cf864eda22eda8e652c3f7c9569acbc1c1a in branch
'master' by Dmitry Smirnov
The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-magiconair-prope
Processing commands for cont...@bugs.debian.org:
> tag 830727 + pending
Bug #830727 [src:golang-github-magiconair-properties]
golang-github-magiconair-properties: FTBFS: go test -v
github.com/magiconair/properties [..] circular reference
Added tag(s) pending.
> thanks
Stopping processing here.
Your message dated Fri, 22 Jul 2016 05:18:31 +
with message-id
and subject line Bug#830727: fixed in golang-github-magiconair-properties
1.7.0-2
has caused the Debian Bug report #830727,
regarding golang-github-magiconair-properties: FTBFS: go test -v
github.com/magiconair/properties [..] ci
Package: mps-youtube
Version: 0.01.46-3
Severity: serious
Justification: 3
Dear Maintainer,
I installed mps-youtube and tried to run it:
$ mpsyt
Traceback (most recent call last):
File "/usr/bin/mpsyt", line 5, in
from pkg_resources import load_entry_point
ImportError: No module named pkg_
97 matches
Mail list logo
