Excerpts from Craig Sanders's message of 2016-10-26 15:22:27 +1100:
> On Wed, Oct 26, 2016 at 04:43:53AM +0200, Clint Byrum wrote:
> > > [ using /dev/tcp in bash ]
> >
> > That seems like a gross oversimplification of what works extremely well
> > today. mysqladmin actually understands mysql's
Hi Ben, hi Petra,
On Mon, Oct 24, 2016 at 02:35:07PM +0100, Ben Hutchings wrote:
> On Mon, 2016-10-24 at 11:49 +0200, Petra Ruebe-Pugliese wrote:
> [...]
> > Okay. So I've sacrificed the less important of the two
> > notebooks again and repeated the "apt-get dist-upgrade"
> > so that the
Package: wnpp
Severity: wishlist
Owner: Sruthi Chandran
X-Debbugs-CC: debian-de...@lists.debian.org
* Package name: node-spdx-license-ids
Version : 1.2.2
Upstream Author : Shinnosuke Watanabe (https://github.com/shinnn)
* URL :
Package: taglib
Version: 1.11.1-0.1
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu zesty ubuntu-patch
Hi Modestas,
The NMU of taglib 1.11.1 to unstable has included updates to the symbols
file. The changes that were made are incompatible with building
Excerpts from Craig Sanders's message of 2016-10-26 15:31:58 +1100:
> On Wed, Oct 26, 2016 at 04:52:38AM +0200, Clint Byrum wrote:
> > The point of the stable release is security updates with minimal impact.
>
> well, no. that's ONE of its points, not THE point.
>
> Another point is to refrain
Justin Coffman writes:
> I tried my hand at generating a patch, but the patched version didn't
> exhibit behavior any different than current. I guess my GnuTLS-fu is not
> strong enough.
> The gotcha (I think) is in the way GnuTLS shims the SSLv23_client_method
> in its
Control: retitle -1 ITP: simple-build-tool -- for scala and java
projects
Control: owner -1 !
Dear all,
In accordance with the Debian Java team (predominantly Emmanuel Bourg),
I started working on packaging SBT. As suggested before, I'll use a
strategy that involves the non-free archive because
retitle 610979 6tunnel: IPV4 option (-4) should warn if both addresses are
already IPV4
thanks
[Note to previous message] the commit to 1:0.12-1
debian/chnagelog where fix is recorded is:
Quoting Roger Shimizu (rogershim...@gmail.com):
> Dear Changzhuo,
>
> On Tue, Oct 25, 2016 at 7:46 PM, ChangZhuo Chen wrote:
> > On Sun, Mar 20, 2016 at 01:24:16AM +0800, ChangZhuo Chen (陳昌倬) wrote:
> >> Any progress for this patch?
> >
> > Could you help to review the patch
>> Justin Coffman writes:
>>
>> Package: tf5
>> Version: 5.0beta8-5+b1
>> Severity: important
>>
>> TinyFugue, when compiled from upstream source against OpenSSL, is
>> capable of the full set of expected ciphersuites (up to and including
>> TLSv1.2), such as those
Package: wnpp
Severity: wishlist
Owner: Pirate Praveen
X-Debbugs-CC: debian-de...@lists.debian.org
* Package name: node-currently-unhandled
Version : 0.4.1
Upstream Author : James Talmage
(github.com/jamestalmage)
* URL :
Package: wnpp
Severity: wishlist
Owner: "HIGUCHI Daisuke (VDR dai)"
* Package name: ruby-test-unit-notify
Version : 1.0.4
Upstream Author : Kouhei Sutou
* URL : https://github.com/test-unit/test-unit-notify
* License :
Package: wnpp
Severity: wishlist
Owner: Sruthi Chandran
X-Debbugs-CC: debian-de...@lists.debian.org
* Package name: node-is-builtin-module
Version : 1.0.0
Upstream Author : Sindre Sorhus
(sindresorhus.com)
* URL :
Control: tags -1 help
Justin Coffman writes:
> Package: tf5
> Version: 5.0beta8-5+b1
> Severity: important
> TinyFugue, when compiled from upstream source against OpenSSL, is
> capable of the full set of expected ciphersuites (up to and including
> TLSv1.2), such as those
On Monday, 24 October 2016, at 14:35 Ben Hutchings (b...@decadent.org.uk) wrote:
[...]
>
> OK, this is the same crash that someone else reported and I think I
> know which change triggered it (though not why).
>
> Does the attached patch fix the crash? (Instructions for rebuilding
> the package
On Wed, Oct 26, 2016 at 04:52:38AM +0200, Clint Byrum wrote:
> The point of the stable release is security updates with minimal impact.
well, no. that's ONE of its points, not THE point.
Another point is to refrain from breaking existing systems - that's at
least as important as security
Source: 389-ds-base
Version: 1.3.5.13-1
Severity: important
Tags: security upstream
Hi,
the following vulnerability was published for 389-ds-base. The
information though is very scarce, can you try to find more out about
upstream report and/or fix?
CVE-2016-5405[0]:
Password verification
Package: tf5
Version: 5.0beta8-5+b1
Severity: important
TinyFugue, when compiled from upstream source against OpenSSL, is capable of
the full set of expected
ciphersuites (up to and including TLSv1.2), such as those utilizing AES-GCM and
EC Diffie-Hellman. The
version packaged in Debian,
On Wed, Oct 26, 2016 at 04:43:53AM +0200, Clint Byrum wrote:
> > [ using /dev/tcp in bash ]
>
> That seems like a gross oversimplification of what works extremely well
> today. mysqladmin actually understands mysql's protocol, and can verify
> that it is up and fully functional. Listening doesn't
Package: how-can-i-help
Severity: wishlist
I would like to be able to list all issues that apply to my local
system in descending order of how much I care about them. The best
proxy of how much I care is probably how recently I used them.
For packages, this can be found in the popcon information
tag 842089 + pending
thanks
Some bugs in the libembperl-perl package are closed in revision
c54ff411fa580fd106b04f5d018fa2ccc858c9f4 in branch 'master' by gregor
herrmann
The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libembperl-perl.git/commit/?id=c54ff41
Commit
Hi!
On Wed, 2016-10-26 at 05:08:52 +0200, Guillem Jover wrote:
> On Wed, 2016-09-07 at 00:48:17 +0200, Bálint Réczey wrote:
> > 2016-09-04 3:03 GMT+02:00 Balint Reczey :
> > > Many packages fail to build due to gcc ... -shared -no-pie ... failing.
> > > I have reported the
Package: sponsorship-requests
Severity: important
Dear mentors,
Following #841876, I am looking for a sponsor for the package "ucommon":
gbp clone https://anonscm.debian.org/git/pkg-voip/ucommon.git
For verification, these are the current branch heads:
git show-ref --heads
tag 840980 + pending
thanks
Some bugs in the libperinci-sub-normalize-perl package are closed in
revision 0517f58fcb21a2775d5a1697539c6f61f533671c in branch 'master'
by gregor herrmann
The full diff can be seen at
Package: file
Severity: wishlist
Please detect MacWrite II documents:
Name: MacWrite II document
Sample: https://www.w3.org/History/1989/proposal
Info: http://fileformats.archiveteam.org/wiki/MacWrite
--
bye,
pabs
https://wiki.debian.org/PaulWise
signature.asc
Description: This is a
Hi!
On Wed, 2016-10-26 at 00:37:18 +0200, Andreas Cadhalpun wrote:
> On 25.10.2016 13:55, Guillem Jover wrote:
> > I don't think the reasoning there is sound (as I've mentioned
> > elsewhere), and the policy bug should be closed.
> >
> > Switching from no-PIE to PIE by default preserves our
On 2016-10-25 19:28, Simon McVittie wrote:
| On Tue, 25 Oct 2016 at 12:28:26 -0200, Joao Eriberto Mota Filho wrote:
| > Your package, recently uploaded to unstable, fails to build from source in
| > several architectures[1].
| >
| > The fail is being caused by some tests (in dh_auto_test target).
Control: tags + moreinfo
On Wednesday, October 26, 2016 12:12:05 AM CDT you wrote:
> Package: digikam
> Version: 4:5.2.0-2
> Severity: normal
>
> In the top menubar the Export dropbdown menu does not open. It gets selected
> as all the other menus, but nothing is shown. This also happens on a
Hi!
On Wed, 2016-09-07 at 00:48:17 +0200, Bálint Réczey wrote:
> 2016-09-04 3:03 GMT+02:00 Balint Reczey :
> > Many packages fail to build due to gcc ... -shared -no-pie ... failing.
> > I have reported the issue to GCC but they don't seem to fix that:
> >
Hi!
On Thu, 2016-10-20 at 03:20:59 +0200, Bálint Réczey wrote:
> For the record gcc-6/6.2.0-7 enabled bindnow for the architectures where
> PIE is enabled by default. I think enabling bindnow from dpkg would be
> better through the hardening flags because packages could disable it
> in a nicer
Excerpts from Craig Sanders's message of 2016-10-26 12:10:49 +1100:
> On Tue, Oct 25, 2016 at 01:09:23PM +0100, Robie Basak wrote:
> > I agree with you, but the release team have made their decision against our
> > wishes. There's no point arguing with us. We know.
>
> since when does the release
Excerpts from Craig Sanders's message of 2016-10-26 12:56:43 +1100:
> On Tue, Oct 25, 2016 at 06:42:11AM -0700, Lars Tangvald wrote:
>
> > SysV and upstart scripts use mysqladmin (which is in the client) to verify
> > that the server is running. 5.7 has some inbuilt support for systemd, so for
>
On Tue, 2016-10-25 at 22:39 +0900, Osamu Aoki wrote:
> I was thinking to bunch up all possible URL results by scanning all
> directory from low version to the high version. But you have a point.
> Scan from high version and pick page which has matching URL.
>
> This makes sense and not as bad
On Tue, Oct 25, 2016 at 06:42:11AM -0700, Lars Tangvald wrote:
> SysV and upstart scripts use mysqladmin (which is in the client) to verify
> that the server is running. 5.7 has some inbuilt support for systemd, so for
> systemd at least it's not needed.
pgrep (or even telnet to port 3306) would
On Sun, 23 Oct 2016 14:28:03 -0200 Joao Eriberto Mota Filho wrote:
> I have some UDD reports[1]
> [1] https://people.debian.org/~eriberto/udd/
Why not put these reports onto udd.d.o?
--
bye,
pabs
https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message
Hi Roger,
2016-10-26 8:09 GMT+08:00 Roger Shimizu :
> I'll fix this on next release.
> or you can fix it by yourself.
That determines on whether I could have access to collab-maint.
There are also some lintian errors, don't forget to get rid of them :p
> BTW. Have you
On Tue, Oct 25, 2016 at 01:09:23PM +0100, Robie Basak wrote:
> On Tue, Oct 25, 2016 at 10:00:32PM +1100, Craig Sanders wrote:
> > it still seems very surprising to me that a package called
> > default-MYSQL-client would force the removal of mysql-client* and
> > mysql-server*
>
> I agree this is
Hello Osamu,
here my watch file:
[quote]
version=4
#opts="dversionmangle=s/\+repack\d+$//"
http://www.argyllcms.com/downloadsrc.html Argyll_V(.*)_src\.zip
opts=dversionmangle=s/\+repack(.*)// \
http://www.argyllcms.com/downloadsrc.html Argyll_V(.*)_src\.zip debian
debian/repack.sh
[/quote]
Hi Simon,
Le mardi 25 octobre 2016 18:55:39 EDT, vous avez écrit :
> So while this seems to have migrated into unstable, when building in the
> Zesty proposed pocket, it failed to build.
>
> This FTBFS is only on ppc64el and seems to be caused by symbols
> problems. You can take a look for
On 2016-10-25 10:44:01 +0200, Marc Haber wrote:
> I have uploaded 2.2.4-1~exp1 to experimental. That version is a
> debugging release which has better logging. Can you please try to
> reproduce this issue?
I tried to upgrade, but it failed:
root@cventin:/home/vlefevre# apt install
On Tue, Oct 25, 2016 at 9:58 PM, Boyuan Yang <073p...@gmail.com> wrote:
>
> Currently the README.Debian file is packaged along with `libshadowsocks-libev-
> dev', which is not correct. This README file is meant to be read by the users
> of main package, `shadowsocks-libev'.
I got to know the
Package: lxqt-common
Version: 0.11.0-3
Severity: normal
'apt ugrade' upgraded this package today and it reported that the existing
/etc/xdg/lxqt/session.conf was different to the new version.
One change was an additional line:
dpi=96
My screen resolution is not 96, rather about 128 and that is
Package: src:linux
Version: 4.7.8-1~bpo8+1
Followup-For: Bug #839617
Dear Maintainer,
meanwhile I have found the following workaround:
booting with
i915.enable_psr=0
avoids the crashes.
Perhaps panel self refresh (psr) could be deactivated for intel broadwell until
upstream fixes this issue?
On 2016-10-25 17:40:03 -0400, Daniel Kahn Gillmor wrote:
> since each user has a single gpg-agent (thanks to the standard-socket),
> I see a few choices here:
>
> a) use pinentry-emacs where possible (this won't currently work within
> debian since none of our pinentry implementations are
So while this seems to have migrated into unstable, when building in the
Zesty proposed pocket, it failed to build.
This FTBFS is only on ppc64el and seems to be caused by symbols
problems. You can take a look for yourself here:
- https://launchpad.net/ubuntu/+source/taglib/1.11.1-0.1
-
On 2016-10-25 13:02:10 -0400, Daniel Kahn Gillmor wrote:
> It is not inherently a bug to run "gpg --no-tty" with no X display.
This is documented as:
Make sure that the TTY (terminal) is never used for any output.
But in my case (SSH without X forwarding), the tty was the *only* way
to
Silently bouncing messages mean messages can get lost. For example, when I
fetch manually, I can see this:
fetchmail: SMTP error: 550 maximum allowed line length is 998 octets, got 1006
fetchmail: mail from MAILER-DAEMON@ bounced to
fetchmail: SMTP listener refused delivery
If fetchmail is
I support the creation of the debian-riscv mailing list.
With regards,
Paul van der Vlis.
--
Paul van der Vlis Linux systeembeheer Groningen
https://www.vandervlis.nl/
Why is there a limitation at all? Bytes are just bytes; why does there have to
be a newline character every so often? I have lost mail because of this rule.
Please fix.
Fixed. Next steps would be:
adt-run --unbuilt-tree=limereg --- null
git tag -s -a debian/1.4.1-1 -m "Release 1.4.1-1"
git push --all
git push --tag
But I have a: WARNING: 'automake-1.15' is missing on your system, so I
cannot verify before creating the tag. Will move my development PC to
SID,
Source: partclone
Version: 0.2.88-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
partclone fails to build from source in unstable/amd64:
>> But does this generate the same output as without -enable-default-pie?
>> Some parts of the kernel do use -fpic or -fPIC. Which directive prevails?
If you call gcc with "-O3 -O0 -O1", only "-O1" option is make sence.
See attachments from recent build log (roughly speaking, Linux 4.8.4,
"make
Hi,
On 25.10.2016 13:55, Guillem Jover wrote:
> I don't think the reasoning there is sound (as I've mentioned
> elsewhere), and the policy bug should be closed.
>
> Switching from no-PIE to PIE by default preserves our current behavior
> WRT static libraries vs shared libraries.
The current
Package: wnpp
Severity: wishlist
Owner: Stephen Crowley
* Package name: arblib
Version : 2.8.1
Upstream Author : Fredrik Johansson
* URL : http://arblib.org/
* License : GNU Lesser General Public
Package: wnpp
Severity: wishlist
Owner: Raphael Enrici
* Package name: dynomite
Version : 0.5.8
Upstream Author : Netflix
* URL : https://github.com/Netflix/dynomite
* License : Apache License, version 2.0
On 10/25/2016 04:26 PM, Alf Gaida wrote:
On Tue, 25 Oct 2016 15:53:48 -0400
Jape Person wrote:
Do you suppose that my slightly odd system configuration could
be at fault? I do not have any of the regular desktop
No, not relly - that was my fault
Please let me know if
On Tue, Oct 25, 2016 at 11:35:42PM +0200, Hilmar Preuße wrote:
> > 3) configure done by dh_auto_configure
> >
> I'd simply replace
>
> ./configure $(shell dpkg-buildflags --export=configure) $(CONF_ARGS)
> --with-shared=$(DSOMODS1)$(DSOMODS2)$(DSOMODS3)$(DSOMODS4)
>
> by
>
> dh_auto_configure
Package: digikam
Version: 4:5.2.0-2
Severity: normal
In the top menubar the Export dropbdown menu does not open. It gets selected as
all the other menus, but nothing is shown. This also happens on a clean install
(no configuration). This is also present in 5.1.0-1, but was not present in
On Fri, 26 Aug 2016, Joseph Herlant wrote:
> Should we consider this one as a duplicate of #777177 as they both try
> to solve the reproducibility issues of asciidoc?
I think not: #777177 is about reproducibility of asciidoc itself, while
#782294 is about reproducibility of any packages using
The export functionality has been reshaped a lot in version 5. You can
choose the pictures to export in the main window, so all filtering
options (e.g. tags) can be used to display and select the desired items.
signature.asc
Description: OpenPGP digital signature
OK, I've added:
- a manpage
- patat to DHG's package-plan
I hope everything is good now...
signature.asc
Description: PGP signature
Package: wnpp
Severity: wishlist
Owner: Julian Gilbey
* Package name: jigsaw-generator
Version : 0.2.1
Upstream Author : Julian Gilbey
* URL : https://github.com/juliangilbey/jigsaw-generator.git
* License : GPL
Programming
On 25/10/16 11:28, Sebastien Delafond wrote:
> Source: brotli
> Version: 0.4.0+dfsg-1
> Severity: minor
>
> Hello,
>
> python-brotli version 0.6.0 is available upstream, and it turns out that
> "brotlipy<0.7,>=0.5.1" is a requirement for the new mitmproxy 0.18.1
> that I'm packaging up.
>
> Is
Control: tags 842015 - unreproducible moreinfo
Control: tags 842015 + upstream
Control: forwarded 842015 https://bugs.gnupg.org/gnupg/issue2818
Hi Vincent--
I think your analysis is correct:
On Tue 2016-10-25 14:35:49 -0400, Vincent Lefevre wrote:
> This happened when I was at my lab and
On 06.10.2016 22:20, Mattia Rizzolo wrote:
Hi,
> I can sponsor the upload if you want, but before I'd like to see more
> changes done, meaning:
>
>
> 3) configure done by dh_auto_configure
>
I'd simply replace
./configure $(shell dpkg-buildflags --export=configure) $(CONF_ARGS)
Source: bglibs
Version: 1.106-2.1
Severity: normal
PIE by default in gcc was enabled in unstable a week ago.
There has recently been some confusion regarding the changes required
for using PIE by default.
Static libraries do not have to be compiled with -fPIC for this change,
-fPIE is
Source: cmake
Version: 3.0.2-1+deb8u1
Severity: wishlist
Dear Maintainer,
It woud be great if you could backport cmake from unstable into
jessie-backports.
A bunch of projects I am using required cmake > 3.1. but jessie has only 3.0.2
Thanks for considering.
Frederic
-- System Information:
Hi Graham,
The new chemps2 version is released:
https://github.com/SebWouters/CheMPS2/releases/tag/v1.8.1
I'll try do to the debian repo tomorrow. I have to reinstall a couple of
things to test. If you want to merge the new release earlier based on the
github release, that's also fine with me.
Source: libctl
Version: 3.2.2-3
Severity: normal
PIE by default in gcc was enabled in unstable a week ago.
There has recently been some confusion regarding the changes required
for using PIE by default.
Static libraries do not have to be compiled with -fPIC for this change,
-fPIE is sufficient
On Mon 24 Oct 2016 at 22:58:06 +0100, Brian Potkin wrote:
> My print queue was set up (all on one line) with
>
> lpadmin -p wf2530 -v file:/home/brian/wf2530 -E
> -m
> escpr:/0/cups/model/epson-inkjet-printer-escpr/Epsom-WF-2530_Series-epson-escpr-en-ppd
>
> and I printed with
>
> lp
The problem according to your log is not libgphoto2 (it was before, but
is fixed since some releases), now it is a missing command: "gphoto2".
This command is part of a package with the same name "gphoto2". This
should probably be added as a manual dependency in control as shlib does
not seem to
On Tue, 25 Oct 2016 at 15:39:46 -0300, Ben Armstrong wrote:
> #5 0x557569f9 in gui_position_components (total_width=1) at
> gui.c:1355
> #6 0x5575982c in gui_resize_shell (pixel_width=,
> pixel_height=pixel_height@entry=1) at gui.c:1470
Well, that looks like bad news: you
Package: wnpp
Severity: wishlist
Owner: IOhannes m zmoelnig
* Package name: ableton-link
Version : 1.0.0
Upstream Author : Ableton AG, Berlin
* URL : https://www.ableton.com/en/link/
* License : GPL
Programming Lang: C++
Description
On Tue, Oct 11, 2016 at 10:44:28PM +0200, gregor herrmann wrote:
> On Mon, 10 Oct 2016 23:10:30 +0300, Niko Tyni wrote:
>
> > Help untangling this mess would be very welcome, as both Dominic and I
> > are rather short on time. Tagging and copying possible candidates :)
>
> Good news: I got the
Control: reopen -1
Control: affects -1 =
Control: severity -1 important
The main problem that libfl_pic.a is not compiled with -fPIC is still
not fixed.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for
Source: publib
Version: 0.40-3
Severity: normal
PIE by default in gcc was enabled in unstable a week ago.
There has recently been some confusion regarding the changes required
for using PIE by default.
Static libraries do not have to be compiled with -fPIC for this change,
-fPIE is sufficient
Source: cpputest
Version: 3.8-4
Severity: normal
PIE by default in gcc was enabled in unstable a week ago.
There has recently been some confusion regarding the changes required
for using PIE by default.
Static libraries do not have to be compiled with -fPIC for this change,
-fPIE is sufficient
Source: ctn
Version: 3.2.0~dfsg-3.1
Severity: normal
PIE by default in gcc was enabled in unstable a week ago.
There has recently been some confusion regarding the changes required
for using PIE by default.
Static libraries do not have to be compiled with -fPIC for this change,
-fPIE is
Hi,
IMO teamviewer is not DFSG[0] compliant.
DFSG:
* The license of a Debian component may not restrict any party from
selling or giving away the software as a component of an aggregate
software distribution containing programs from several different
sources. *The license may not
Source: portaudio19
Version: 19+svn20140130-1.1
Severity: normal
PIE by default in gcc was enabled in unstable a week ago.
There has recently been some confusion regarding the changes required
for using PIE by default.
Static libraries do not have to be compiled with -fPIC for this change,
Source: i2util
Version: 1.6-1
Severity: normal
PIE by default in gcc was enabled in unstable a week ago.
There has recently been some confusion regarding the changes required
for using PIE by default.
Static libraries do not have to be compiled with -fPIC for this change,
-fPIE is sufficient
Package: wnpp
Severity: wishlist
Owner: IOhannes m zmoelnig
* Package name: pd-lib-builder
Version : 0.2.7
Upstream Author : Katja Vetter
* URL : https://github.com/pure-data/pd-lib-builder
* License : Public Domain
Programming Lang:
Source: binpac
Version: 0.44-2
Severity: normal
PIE by default in gcc was enabled in unstable a week ago.
There has recently been some confusion regarding the changes required
for using PIE by default.
Static libraries do not have to be compiled with -fPIC for this change,
-fPIE is sufficient
Source: orbit2
Version: 1:2.14.19-2
Severity: normal
PIE by default in gcc was enabled in unstable a week ago.
There has recently been some confusion regarding the changes required
for using PIE by default.
Static libraries do not have to be compiled with -fPIC for this change,
-fPIE is
On Tue, Oct 25, 2016 at 03:03:59PM +0300, Ilias Tsitsimpis wrote:
> | Running ln -rs -T
> debian/libghc-shake-doc/usr/share/doc/libghc-shake-doc/html/CHANGES.txt
> debian/libghc-shake-doc/usr/share/doc/libghc-shake-doc/html/shake.txt
>
Source: unicon
Version: 3.0.4-15
Severity: important
PIE by default in gcc was enabled in unstable a week ago.
There has recently been some confusion regarding the changes required
for using PIE by default.
Static libraries do not have to be compiled with -fPIC for this change,
-fPIE is
Source: gadap
Version: 2.0-7
Severity: important
PIE by default in gcc was enabled in unstable a week ago.
There has recently been some confusion regarding the changes required
for using PIE by default.
Static libraries do not have to be compiled with -fPIC for this change,
-fPIE is sufficient
Hi,
I worked around the missing variables in the r-bioc-biocparallel
code by adding
debRreposname := $(shell dpkg-parsechangelog | awk '/^Source:/ {print $$2}' |
sed 's/r-\([a-z]\+\)-.*/\1/')
awkString := "'/^(Package|Bundle):/ {print $$2 }'"
cranNameOrig:= $(shell awk
Christian Seiler dixit:
>Yes, I fully intend to fix that - which is why I tagged the bug
>report "confirmed" when it was first reported, even while it
>was still of lower severity. I just had a lot of other stuff
>come up and didn't get to it yet. I had actually planned to
>take some time on
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "qspeakers"
* Package name: qspeakers
Version : 1.0-1
Upstream Author : Benoît Rouits
* URL : http://brouits.free.fr/qspeakers/
* License : GPL-3+
Package: file
Version: 1:5.29-1
Severity: normal
Tags: upstream
Starting from 1:5.29-1 on, many text files get mis-detected as
"Algol 68 source text". I plan to fix this soon; if all else
fails by disabling the entire algol68 magic.
Christoph
-- System Information:
Debian Release:
Package: digikam
Version: 4:5.2.0-2
Severity: important
Dear Maintainer,
digikam can't access my camera anymore, after upgrading to version 5.2.0-2. The
reason is that libgphoto2 support is missing in that version whereas it was
available in 5.1.0-2. This, or a similar problem, had occured a
On 2016-10-23 11:51-0700, Sean Whitton wrote:
> You should use "Forwarded: not-needed" (see DEP-3).
This does not seem to work with gbp-pq (see #785274), I propose to add this as
soon as gbp-pq supports DEP-3.
>>> 2. You can fix all of these Lintian tags, except possibly
>>>
control: tags -1 severity normal
control: tags -1 tags + help
On Tue, Oct 25, 2016 at 4:17 PM, Markus Wigge wrote:
> Package: freeradius-ldap
> Version: 2.2.5+dfsg-0.2
> Severity: important
> Tags: upstream
>
> Dear Maintainer,
>
> I encountered severe problems trying to
Source: libupnp
Version: 1:1.6.19+git20141001-1
Severity: grave
Tags: security upstream
Hi,
the following vulnerability was published for libupnp. The issue is
reproducible easily if libupnp compiled with ASAN and following the
reproducing steps in the upstream bugreport.
CVE-2016-8863[0]:
Quoting john.k...@vfemail.net:
Quoting Margarita Manterola :
Hola John Kirk!
Package: cinnamon
Version: 3.0.7-1
Followup-For: Bug #840348
If possible, it would be nice if you could just reply to the emails you
get, so
that they show up as part of the same conversation
On Tue, 25 Oct 2016 15:53:48 -0400
Jape Person wrote:
> Do you suppose that my slightly odd system configuration could
> be at fault? I do not have any of the regular desktop
No, not relly - that was my fault
> Please let me know if there's anything I might do from a
Package: dh-r
Severity: wishlist
Hi,
I'm starting to convert some of my R packages from cdbs helper to dh-r.
When converting r-bioc-biocparallel I wanted to turn the code to fix the
permissions of a file into
override_dh_fixperms:
dh_fixperms
chmod -x
Package: autopkgtest
Version: 4.1
Severity: wishlist
Tags: patch
A project I'm currently working on uses a read-only root filesystem
under normal circumstances, mounting it rw only when an upgrade is
desired. This makes autopkgtest fail horribly when testing our disk
images, which is (at least
I've only moved the mount2dir executable from the fai-nfsroot package
to the fai-client package. The fai-client does not replace
fai-nfsroot.
To fix this bug is it only possible by defining a breaks or replaces?
Which breaks do I have to define then?
BTW, fai-nfsroot is never installed on a
1 - 100 of 386 matches
Mail list logo