Package: fpc
Version: 2.2.0-dfsg1-9
Version: 2.0.0-4
Severity: serious
Thanks
As can be read in the changelog of the latest version the old source of
fpc has a copyright infringment:
- Possible CodeGear Copyright infringements in the source were reworked
using cleanroom approach.
Following the
that they took it very seriously.
Paul
[1] https://bugs.launchpad.net/ubuntu/+source/fpc/+bug/275688
Original Message
Subject: Bug#506977: FPC: copyright infringement in pre 2.2.2 sources
Date: Wed, 26 Nov 2008 10:42:13 -0600
From: Paul Gevers
To: [EMAIL PROTECTED]
Package: fpc
Version
Dear FTP-masters,
Please have a look at bug 506977 (of which the last and most explaining
comment is below this email). The issue involved is a copyright
infringement in the source of fpc before version 2.2.2 (i.e. everything
version except for the one in unstable). I fear that we should either
Package: lazarus-ide
Version: 0.9.28.2-7
Severity: grave
fpc was updated two days ago. Now, lazarus is uninstallable because it
depends on the fpc-abi-2.2.4+fcl240 package which doesn't exist in
unstable anymore.
signature.asc
Description: OpenPGP digital signature
I am looking into creating a security update for Lenny for this bug.
However, the original patch is not available anymore (404 error: Not
Found). Does anybody know where to find the patch or an equivalent one?
Paul
signature.asc
Description: OpenPGP digital signature
This bug is not an issue in the binary build since 3.1.1-1, because the
prototype.js is not used. Instead the package depends on libjs-prototype
and replaces the file with a link. See bug 475286.
Paul
signature.asc
Description: OpenPGP digital signature
Package: lazarus
Version: 0.9.26.2
Severity: normal
*** Please type your report below this line ***
To test the next version of lazarus for this bug, I svn exported the
debian tree at http://bollin.googlecode.com/svn/lazarus/trunk and run
the debian/rules get-orig-source rule. After that I ran
Could you please test if the attached patch fixes your issue?
Tested with a new checkout and it worked. Although lots of lintian
warnings/errors etc.
I will supply a, possibly not very useful, patch tomorrow for some
spelling warnings.
Please note that you need to build/package FPC 2.2.4
In Ubuntu I checked that the following packages builddepend on FPC:
lazarus
imapcopy
hedgewars
libhdate
gearhead
m-tx
python-soappy
poker-network
I assume, but have not check yet, that the same goes for Debian.
Looks like quite a lot of packages seem to have go. The removal request
Severity: normal
Thanks
The problem is that you are using mplayer from unstable, with ffmpeg
from experimental. The experimental version of ffmpeg-debian creates
libavcodec52, where your mplayer should depend on if you want to use it.
But the ffmpeg in unstable builds/needs libavcodec51, so that
Hi,
Due this bug, and the migration of the packages to Ubuntu, I am not able
to build [1] my package WinFF anymore in Ubuntu (Ubuntu already removed
the GTK1.2 libs). Do the maintainers appreciate help with fixing this
issue? I could prepare a debdiff for the 0.9.26.2 version of lazarus, in
tags 577347 pending
thanks
The source of lazarus changed the packaging and moved the winff
build-dependency executable lazbuild into lcl-utils.
Thanks for reporting (looking into whether this was necessary was
planned shortly anyway).
Paul
signature.asc
Description: OpenPGP digital signature
Package: madplay
Version: 0.15.2b-7
Justification: renders package unusable
Severity: grave
libesd-alsa0 is replace by libesd0, AFAICT madplay just needs a rebuild
to create a proper dependency list
signature.asc
Description: OpenPGP digital signature
Package: winff
Version: 1.3.2-2
Severity: grave
Since lcl got updated to version 0.9.30-1, building winff fails
[1][2][3]. The bug is reported against lcl-utils-0.9.30 [4] and this bug
will be marked as blocking the fix for this bug.
[1] https://buildd.debian.org/status/package.php?p=winff
[2]
Package: madplay
Version: 0.15.2b-7build1
Severity: serious
Justification: fails to build from source
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Madplay doesn't seem to build on kfreebsd architectures [1]. Looking at build
log
and the wiki of debian/kfreebsd [2], it seems that the problem is
Madplay doesn't seem to build on kfreebsd architectures [1]. Looking at
build log
and the wiki of debian/kfreebsd [2], it seems that the problem is in
building with
ALSA support. Maybe it helps to build on those platforms without the ALSA
support.
madplay was never available on
tag 624516 pending
thanks
Date: Fri Jul 1 20:58:53 2011 +0200
Author: Paul Gevers p...@climbing.nl
Commit ID: 7a1fa4a2b1d0034fc4548d309d5bc6ae00c10d4a
Commit URL:
http://git.debian.org/?p=pkg-cacti/cacti.git;a=commitdiff;h=7a1fa4a2b1d0034fc4548d309d5bc6ae00c10d4a
Patch URL:
http
tags 665243 pending
retitle 665243 cacti: FTBFS: grepping on output of file needs change
thanks
I also noticed this before as can be seen in [1].
Freely quoted:
If I run
$ find debian/cacti/usr/share/cacti/cli -type f -print0 | xargs -0 file
manually, I get things like:
For the list of issues, see:
http://security-tracker.debian.org/tracker/source-package/cacti
under Open unimportant issues (it's a bug that they're listed there,
only the first issue is actually unimportant and may be ignored for lenny)
Are you in a position to check each of these and
On 07/03/11 19:35, Paul Gevers wrote:
As discussed below and in bug 624516, I prepared a patch for
CVE-2010-1644: cacti: XSS issues in host.php and data_sources.php in
lenny. The maintainer of cacti suggested to contact you for further
actions. I read [1] and prepared a .diff.gz and .dsc
Thanks for your help and sorry that we didn't get around to processing
this package earlier.
NP.
I have taken a look and the package looks fine. However, there are other
open Cacti issues in Lenny aswell, and I don't think it would make sense
to release an update that includes a fix for
severity 624369 normal
retitle 624369 winff should not depend on fp-utils
thanks
As a work around for the original bug, winff build depends on fp-utils
now. Once bug 624361 is solved, it should not.
signature.asc
Description: OpenPGP digital signature
Please find attached three patches against the pkg-cacti git branch
debian-lenny to fix this bug.
Feel free to use them.
Paul
From 4c6b9f2dc8af687f288218575388619c9528c346 Mon Sep 17 00:00:00 2001
From: Paul Gevers p...@climbing.nl
Date: Fri, 1 Jul 2011 20:30:53 +0200
Subject: [PATCH 1/3] Fix
02:09 AM, Paul Gevers wrote:
Please find attached three patches against the pkg-cacti git branch
debian-lenny to fix this bug.
Feel free to use them.
Paul
Thanks, it would to nice if we counsult with debian-security team. you
can find them at http://lists.debian.org/debian-security-tracker
Sorry about the additional delay on my end, then. You should be added now.
Go ahead and commit directly to the repo, if there are any questions or
you want some review we can work from that.
I uploaded the patches. At this moment I think the review is the main
thing. As I mentioned, I did my
i don't see the patches though, what branch did you put them in?
As this is a security update for lenny, I put them on the debian-lenny
branch.
Paul
signature.asc
Description: OpenPGP digital signature
Package: dbconfig-common
Followup-For: Bug #476946
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Discussing this bug on the BSP in Utrecht [1], we were wondering if this issue
could
not be fixed by parsing the configuration file if it exists (and using that
with higher)
priority than the
Package: emacs23
Tags: moreinfo
Followup-For: Bug #689522
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
As you clearly have installed ii emacs23-bin-common 23.4+1-4 which depends
on
emacs23-common which contains the directory /etc/emacs32, I can only image one
of
the following, all not
Hi Zigo,
As lastfmsubmitd is maintained by the Debian QA group, I will just go
ahead and upload a new version of lastfmsubmitd with your patch applied.
I will request an unblock after the upload.
Paul
signature.asc
Description: OpenPGP digital signature
Package: openslp-dfsg
Followup-For: Bug #687597
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
As far as I can tell, no solution known yet, on 17 October 2012, 15:28 +0200.
While going through Debian QA group owned RC bugs, I touched on this bug.
Hi all involved,
[This is a ping].
Reading through RC bug 538822 and 540512 (which were already RC during
Squeeze release in 2010) I have the feeling that it is known how these
bug could be fixed and changes are available in the git repository.
Shouldn't we discuss this with the release team and
On 30-10-12 07:24, Jonathan Nieder wrote:
Christian PERRIER wrote:
IMHO (not involved in any of these packages), now is bad time to fix
these bugs: too late in the release process.
Yes, I think we should try to fix the diversion mess in experimental,
ignoring the release cycle, and wait
Hi release team,
There has been a small discussion about dash RC bugs 538822 and 540512
in the bts and the general idea is to postpone the proper fix (again)
till after the release. Do you agree, and if so, can you tag this bug
appropriate as wheezy-ignore? If you do, these bugs should again
: The use of implicit split call has been removed from perl
in version 5.12 as it had been deprecated for 15 years
Author: Paul Gevers elb...@debian.org
Bug-Debian: http://bugs.debian.org/692342
Forwarded: no
--- a/move3
+++ b/move3
@@ -42,7 +42,7 @@
}
while () {
- split;
+ @_=split;
if ($_[0] eq
Package: gnuspool
Followup-For: Bug #664754
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
As bug 664754 is RC, I was wondering what the progress is on this bug [1]. If
you
still want this in wheezy, I propose you fix this quickly and request the
proper unblock or request the removal of
On 09-11-12 18:37, John Collins (Xi Software Ltd) wrote:
Sorry I've been unexpectedly in hospital with a PE I'll do my best
to attend to it in the next few days.
I hope you are recovering well. Any indication on when you want to
upload your changes? Make sure they are in line with the freeze
Control: tag 664754 - pending
On 22-11-12 23:27, John Collins (Xi Software Ltd) wrote:
All a bit fraught and the rat poison I have to take makes my head swim
a bit. Oh well better than dying I suppose.
I would say so.
I think it would be best to take it out of wheezy and we'll work to get
The previous patch was not good. But I am working on it. I think I have
a good patch now for upstream (see upstream bts).
Will try to get this properly done for Debian, and see if the
release-team can except my changes and adding of jstree (apart for
dsfg-ing the source tar ball).
Paul
Hi release team,
Cacti has a nearly 5 months old standing RC bug [1] filed against it
about files with a non-DFSG license (distribution is possible, but
others can not use the copy for other purposes, they need to get their
own free copy). I was hoping that cacti upstream would create the code
Package: cacti
Version: 0.8.4-1
Justification: Policy 2.2.1
Severity: serious
I spotted a license issue in cacti. The files in question are in the
include/treeview folder, i.e. ftiens4.js and ftiens4_export.js, and I am
sure the same issue is related to the icons in that folder. The
license for
ad 2) I am investigating the possibility to use other javascript source
code projects that have similar functionality, but with a DFSG-free
license. So far this seems hopeful, so I think this is the best solution
possible.
[2] http://bugs.cacti.net/view.php?id=2228
Cacti upstream promises
Hi,
I believe you have reverted the solution to bug #660794. As I was hit by
this bug #665263 as well, I solved it by changing the line in
dh_usrlocal from:
my $ebs = $bs x 2; # Escape the backslash from the shell
to
my $ebs = $bs; # Escape the backslash from the
I like to contribute to the description of this package, but don't have
the time to do that right now. Maybe I can have a look next week if the
review isn't finished by than.
Package: lcl-qt4${PACKAGESUFFIX}
[...]
This package contains the LCL and components Qt based backend.
Actually this is
Hi Lucas,
On 22-06-13 16:01, Lucas Nussbaum wrote:
WARNING: unable to create primary config directory
/sbuild-nonexistent/.lazarus
Error: invalid Lazarus directory : directory not found
Would you have any idea why the directory can not be created in
/sbuild-nonexistent? The name suggests it
fixed 700719 2.9.6-1
thanks
On 16-02-13 17:06, Bastian Blank wrote:
Package: postfix
Version: 2.9.3-2.1
Severity: serious
Postfix 2.9 = x 2.9.6 computes completely bogus public key
fingerprints for TLS checks. Please fix this for Wheezy.
Version 2.9.6-1 is already in unstable. So
On 14-02-13 18:30, Matthias Klumpp wrote:
Could you please all check if the issue is gone on your systems, using
the PackageKit packages which are available in Debian Sid since today?
If there are no regressions and this bug is fixed, I will request
inclusion into Wheezy. (Tested it the last
tags 679980 + confirmed pending
thanks
On 19-02-13 09:40, Chris Boot wrote:
It seems the Recommends in 0.8.8a+dfsg-2 are broken:
Recommends: [...] libjs-query, libjs-query-cookie [...]
Both of those should read 'libjs-jquery-*' not 'libjs-query-*'. This
results in not installing the
Source: lazarus
Version: 0.9.30.4
Severity: serious
Tags: upstream
Justification: Policy 2.1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The source file contains the following files which I don't believe have a free
license:
- - components/aggpas/arial.ttf
- - components/aggpas/times.ttf
- -
reassign 709923 uil
affects 709923 lesstif-bin
thanks
This bug has been filed against both packages. If you, the
maintainers of the two packages in question, have agreed on which of
the packages will resolve the problem please reassign the bug to that
package. You may then also register in
Hi Michael,
I do appreciate your time to look at these fpc bugs, but they were filed
by the currently most active maintainer of the package. I therefore
believe, rather than just closing the bug, you could ask Abou for more
clarification if his explanation is somewhat short.
@Abou, don't
Maybe we can leave with this for wheezy, but should be
fixed anyway. So please keep open to be fixed for next uploads.
I just had a conversation on IRC with the RT, and they like to fix this
in Wheezy if the patch can be small. Abou, I expect something similar to
Lazarus [1]? I will look into
tags 704252 +patch pending
thanks
On 10-04-13 22:45, Abou Al Montacir wrote:
I've already committed this on svn on branch 2.6.0.
I saw this after I sent the mail.
I'm attaching patches for info. If you agree I can upload to
mentors.
The RT agrees with the patch for this issue. I have not
Hi Abou,
On 11-04-13 00:17, Abou Al Montacir wrote:
Can you please take 2.6.0 branch head and upload. The other 2 items are
just a typo in translation file and a fix suggested by release team
themselves. I think we really conform to the freeze goals. However if
you don't like these two fixes,
1) You used dpkg-architecture -qDEB_BUILD_ARCH instead of
dpkg-architecture -qDEB_BUILD_GNU_CPU (you could simplify your rules
file as well with this).
Hmm, it seems like this was not a smart idea for i386. So the point is
that either we have to fix i486 to i386 or amd64 to x86_64...
Abou,
-12 18:49:54.0 +0200
@@ -1,3 +1,11 @@
+fpc (2.6.0-7.1) unstable; urgency=low
+
+ * NMU upload
+ * Removed auto-generation of debian/control during build process as required
+by policy. (Closes: Bug#704252)
+
+ -- Paul Gevers elb...@debian.org Fri, 12 Apr 2013 18:49:15 +0200
+
fpc
On 14-04-13 01:45, peter green wrote:
Sorry I could have been clearer in my last mail. I didn't intend to
blame you for most of the issues with the patch (you just took a
broken patch and made it differently broken) but I could see how it
could have come across that way.
Thanks for the
Hi,
[Ping to all who have an idea on how to solve this bug]
Wouldn't it be a great time now to try and fix this bug properly, before
we land in jessie freeze and see that we have this bug still open?
Paul
signature.asc
Description: OpenPGP digital signature
Package: xfce4-terminal
Version: 0.4.8-1+b1
Severity: serious
Justification: Policy 11.8.3
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
xfce4-terminal declares that it provide x-terminal-emulator, but it fails
to support the -e option in the way described in the policy (instead, the
- -x
On 04-08-13 00:11, Yves-Alexis Perez wrote:
That's because the alternative is /u/b/xfce4-terminal.wrapper which
does the same tricks as gnome-terminal to have proper behavior for -e/-x.
Oops, sorry for the noise. I should have investigated deeper. Thanks for
the explanation though.
Paul
Hi Rupert,
On 16-11-13 10:08, Rupert Swarbrick wrote:
This happens because of some faulty logic in the linux
detection. Basically, they had something hardcoded to check for new
linuxes, which meant version 2.x.y. Linux 3.x broke it.
Do you have any idea why then cmucl doesn't segfault on my
Package: gridengine-qmon
Version: 6.2u5-2
Severity: serious
Justification: Policy 11.8.5
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Policy paragraph 11.8.5 says the following:
If one or more of the fonts so packaged are necessary for proper operation
of the package with which they are
As mentioned before, I do not receive e-mails to this bug. Sorry for not
responding earlier.
On 16-11-13 02:50, Hamish wrote:
if [ `uname -m` = ia64 ] ; then
or is there a better way to do arch-specific lines with the aid of debhelper?
Yes (well, no actually):
{{{
# in Wheezy (and Jessie
On 09-12-13 22:06, Paul Gevers wrote:
I haven't tried ppc64 yet.
I can't find a ppc64 porterbox, so I can't test this for you.
Just for the heads up, this bug is currently the only reason why
lesstif2 can't be removed from Debian. Thus, I would appreciate an
upload (I can sponsor if needed
Hi
Currently the via package in Debian is one of the last package to block
the removal of lesstif2 [0]. This is due to a serious bug [1] in the
package which prevents if from migrating to testing.
This e-mail aims to recheck the use of the lip...@cbs.mpg.de address,
which caused bug [1] to be
with $(HARDENING_DISABLE_PIE_CFLAGS_FILTER) filtered for
+now (closes: #728150)
+ * Add patch fix_big-endian_issues which allows grass to build on s390x
+and ppc64 (closes: #672719)
+
+ -- Paul Gevers elb...@debian.org Sat, 14 Dec 2013 12:17:17 +0100
+
grass (6.4.3-2) unstable; urgency=low
Package: grass
Version: 6.4.3-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
In the latest upload of grass, the build dependency for libtiff has been
changed to
libtiff-dev ( 4.0.3-1~) |
On 21-09-13 19:39, Michael Hanke wrote:
It seems like a broken build-dependency spec is the reason -- it builds
on my laptop, but I can't get it to work in a clean chroot. I wonder
whether you could easily spot the problem and help me out?
I had a very similar bug reported against my package
(ignored)
dh_clean
make[1]: Leaving directory `/media/home/paul/tmp/mricron'
And lastly, it is of course possible that you hit a bug in the packaging
of lazarus. Maybe we find out here.
Paul
On Sat, Sep 21, 2013 at 7:50 PM, Paul Gevers elb...@debian.org
mailto:elb...@debian.org wrote
On 03-10-13 22:38, peter green wrote:
Moritz Muehlenhoff wrote:
Package: fpc
Severity: important
fp-units-gfx-2.6.2 uses svgalib, which is scheduled for removal
from the archive. Please disable it and drop the build-dep on
libsvga1-dev.
Sorry for not responding to this bug earlier
And
Control: tag -1 confirmed
This very same bug was indeed also in cacti, where I fixed it in one of
the latest uploads. We should apply the same logic in cacti-spine as well.
Paul
signature.asc
Description: OpenPGP digital signature
Just a short note. I tried to reproduce this failure, but it doesn't
fail for me.
Paul
paul@wollumbin ~ $ cmucl
;;; Hey: there is no /etc/lisp-config.lisp file, please run
dpkg-reconfigure common-lisp-controller as root
CMU Common Lisp Debian build debian/20c-2-1-g957a42a-dirty (20C
Unicode),
Package: eglibc
Version: 2.13-38
Severity: grave
Justification: leaves system unusable
[Sorry for not filing this bug with reportbug, but due to this bug that
doesn't work anymore. I am also unable to sign my mail at this moment,
due to this bug.]
For building an i386-only package I libc6-amd64
Seems this bug was indeed already reported: 699206 and 707185. However,
it is not clear to me how I can get my system working again. Obviously,
I can not remove or create symlinks to the right location as ln and
friends don't work anymore (not to mention that sudo and getty don't help).
Seems
So I was indeed able to recover my system by changing the symlink in
/lib64/ with an emergency USB key. For the record, after shutdown, the
system of course would not come up. I am afraid that people with less
patience than I would conclude that their system was hopelessly ruined.
However, I have
/1ZgLuSnUhXZ4rIBdVlrGw9x2UQZcn5VO4l8HPlvmEITsnon3TKyJUP0gIk42io=
=futo
-END PGP SIGNATURE-
Description: with the current tools, building the docs results in endless loop
Author: Paul Gevers elb...@debian.org
--- cmucl-20c.orig/src/docs/cmu-user/Makefile
+++ cmucl-20c/src/docs/cmu-user/Makefile
@@ -53,7
Just an important note for anybody ending up at this bug and wanting to
remove libc6-amd64. As long as you have root access to the system and
have not powered off yet, I believe you can fix this issue without
rescue CD/USB.
With root access (sudo does not work anymore, because the setguid fails)
building twice by touching build-*-stamp
+ * Prevent dublicate control entries by calling dh_builddeb only on the
+proper target
+
+ -- Paul Gevers elb...@debian.org Tue, 29 Oct 2013 22:10:09 +0100
+
cmucl (20c-2) unstable; urgency=low
* Actually reference the changelog for 20c, not 19d
by Paul Gevers elb...@debian.org
dpkg-source --before-build winff-git
dpkg-source: info: using options from winff-git/debian/source/local-options:
--abort-on-upstream-changes --unapply-patches
dpkg-source: info: applying Fix-up-the-symbols.patch
dpkg-source: info: applying add-default-pdf-laucher
Control: tags -1 confirmed
On 14-09-14 17:28, David Suárez wrote:
convert -geometry 32x32
/�BUILDDIR�/lazarus-1.2.4+dfsg/images/ide_icon48x48.png
/�BUILDDIR�/lazarus-1.2.4+dfsg/debian/tmp/usr/share/pixmaps/lazarus-1.2.4.xpm
convert: tRNS chunk not allowed with alpha channel
Control: tags -1 pending
On 29-09-14 06:39, Debian testing autoremoval watch wrote:
lazarus 1.2.4+dfsg-1 is marked for autoremoval from testing on 2014-10-13
It is affected by these RC bugs:
761536: lazarus: FTBFS: recipe for target 'install-arch-stamp' failed
As nobody replied to my
report before I upload the fix, I would
really appreciate a review of my proposal, so please leave your comments
here.
Paul
From 8dd932f823d8cb07b49766ba8462f2d3e64f454d Mon Sep 17 00:00:00 2001
From: Paul Gevers elb...@debian.org
Date: Sun, 5 Oct 2014 21:47:24 +0200
Subject: [PATCH] Only parse
On 24-08-13 20:12, Paul Gevers wrote:
On 23-08-13 00:07, Romain Coltel wrote:
The recent DSA about cacti arose a problem of owner/group being reset to
the defaults (root/www-data). My configuration (using PHP-FPM with a
specific group for cacti) needs /etc/cacti/debian.php to be
group
Control: tags -1 -patch
On 05-10-14 22:02, Paul Gevers wrote:
Control: tags -1 patch
For anybody reading this bug report before I upload the fix, I would
really appreciate a review of my proposal, so please leave your comments
here.
So I let this issue ponder a bit and I concluded that my
Hi,
I am looking into dbconfig-common RC bug 720517 [1] and I was wondering
what the general idea is of maintainer scripts changing the permissions
and/or owners of configuration files and the use of dpkg-statoverride. I
myself find it unacceptable that updating a package changes the
On 07-10-14 15:40, Ian Jackson wrote:
Also I don't see in your references an explanation from anyone as to
why dbconfig-common does this.
I you mean with why: why is it implemented this way than that is
exactly the question that I am asking myself looking at the code, if you
mean why does
Control: tags -1 patch
On 07-10-14 08:31, Paul Gevers wrote:
So the fix needs to be implemented otherwise. I have
ideas, but I have to figure it out.
So, try number two. If anybody wants to review the patch, please leave
your comments here.
Unfortunately, the code became difficult to read
On 08-10-14 13:58, Ian Jackson wrote:
Paul Gevers writes (Re: Bug#720517: configuration files, ownership and
dpkg-statoverride):
On 07-10-14 15:40, Ian Jackson wrote:
Also I don't see in your references an explanation from anyone as to
why dbconfig-common does this.
I you mean with why
On 09-10-14 02:17, Henrique de Moraes Holschuh wrote:
On Wed, 08 Oct 2014, Paul Gevers wrote:
Thanks for the careful response. And no, as mentioned above, I didn't
mean to use dpkg-statoverride itself. dbconfig-common uses debconf and
ufc to manage the configuration files. However, dbconfig
Hi dbconfig-common-devel followers,
You may have noticed that I have been discussing behavior of
dbconfig-common on debian-devel [1] related to bug 720517 [2].
I want to solve the bug, but I am unsure on how to handle the situation.
So lets discuss the issue:
dbconfig-common can receive the
Control: tags -1 pending
Control: owner -1 !
On 10-10-14 12:06, Paul Gevers wrote:
Investigate all packages to check for their behavior (does any
package query the admin about this?)?
With the aid of http://codesearch.debian.net this was trivial. Currently
no package is querying the admin
issues. Debconf translations:
+- Brazilian Portuguese (Adriano Rafael Gomes) (Closes: #764777)
+- Turkish (Atila KOÃ) (Closes: #662778)
+ * Leave ownership and permissions of configuration files as they were
+(Closes: #720517)
+
+ -- Paul Gevers elb...@debian.org Sat, 11 Oct 2014 19:35:05
Control: tags -1 moreinfo
Control: severity -1 normal
Hi David,
Thanks for your work on these rebuilds.
On 02-06-14 20:42, David Suárez wrote:
/usr/bin/make -C src clean
Makefile:19: *** recipe commences before first target. Stop.
make[1]: Entering directory '/«PKGBUILDDIR»/src'
make[1]:
On 07-06-14 07:15, Scott Kitterman wrote:
FTBFS on kfreebsd* during a binNMU as part of the transition to drop
python3.3.
Issue seems unrelated to python3.3 transition:
/usr/lib/jvm/default-java/include/jni.h:52:20: fatal error: jni_md.h: No
such file or directory
#include jni_md.h
My
On 07-06-14 09:28, Michalis Kamburelis wrote:
Try compiling the Castle Game Engine sources with -Ur to avoid this.
This is indeed the solution that I am going to upload in several
minutes/hours, see [1].
Paul
[1]
Hi Debian Java maintainers,
May I draw your attention to bug 750811 [1]? A rebuild of brltty fails
because it can't find jni_md.h on kfreebsd* archs. See below.
On 07-06-14 08:22, Paul Gevers wrote:
On 07-06-14 07:15, Scott Kitterman wrote:
FTBFS on kfreebsd* during a binNMU as part
/include/linux/jni_md.h
So, is the problem in brltty that it doesn't look in these multiarch
locations?
I am investigating the situation in a porterbox.
Paul
On 13-06-14 20:06, Paul Gevers wrote:
Hi Debian Java maintainers,
May I draw your attention to bug 750811 [1]? A rebuild of brltty fails
Control: clone -1 -2
Control: reassign -2 gcj-4.9-jdk
Control: retitle -2 including /usr/lib/jvm/default-java/include/jni.h
fails on kfreebsd*
Control: block -1 by -2
On 13-06-14 20:45, Paul Gevers wrote:
I am investigating the situation in a porterbox.
I think I found the issue. In debian
On 15-06-14 17:31, Samuel Thibault wrote:
This is most probably similar to #714559 which had the same issue.
Yes, I agree. But interestingly enough, building liblouisutdml already
failed in gcc-4.8 while brltty (and libbluray) only now start to fail
with gcc-4.9, so something must have changed.
Package: cacti
Version: 0.8.8b+dfsg-5
Severity: grave
Tags: security patch upstream pending
Justification: user security hole
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Cacti upstream's svn [1] has a fix for CVE-2014-4002. I couldn't find
any information yet elsewhere. I can only guess that
Control: tags -1 pending
On 29-06-14 19:24, David Suárez wrote:
Relevant part (hopefully):
dpkg-source: error: expected ^--- in line 10 of diff
`flite-1.4-release/debian/patches/CVE-2014-0027_unsafe_temporary_file.patch'
dpkg-source: info: applying CVE-2014-0027_unsafe_temporary_file.patch
1 - 100 of 4241 matches
Mail list logo
