Ah, never mind me. It was the very last change I made that seems to have
tickled this problem. Uploading shortly.
On Mon, 12 Aug 2019 at 22:19, Brendan O'Dea wrote:
> This is due to a sanity check that I've added to ensure that everything is
> prepared for an "upstream&qu
This is due to a sanity check that I've added to ensure that everything is
prepared for an "upstream" release to both Debian and GNU. This is the
first time in ~16 years of the package containing an arch-specific binary
that I've come across a case where a bin-NMU has been required for
help2man.
On Fri, Mar 22, 2019 at 05:42:37PM +0100, Sven Joachim wrote:
>On 2019-03-21 20:45 +1100, Brendan O'Dea wrote:
>> I suspect that it is related to reproducible builds, [...]
>There has indeed been such a change in dpkg-source:
>
>,
>| - Generate reproducible source
On Wed, Mar 20, 2019 at 10:21:39AM +0100, Gianfranco Costamagna wrote:
>Looks like README needs a newer timestamp wrt help2man.PL file?
[...]
>dpkg-buildpackage: info: host architecture amd64
> fakeroot debian/rules clean
>test README -nt help2man.PL # maintainer sanity check
>make: *** [debian/ru
On Sat, May 07, 2011 at 02:20:33PM +0200, Julien Cristau wrote:
>See https://buildd.debian.org/status/package.php?p=vile
The configure failed at different points for both armel and s390, but there is
nothing particularly exceptional about either test, moreover this exact source
package has compile
On Wed, Oct 28, 2009 at 7:13 PM, Niko Tyni wrote:
> http://git.debian.org/?p=perl/perl.git;a=commitdiff;h=063f225d0fdeca563c7906927fc30171c3684f70
"This makes sure the script runs with the system perl and not the new one."
Note that one of the reasons why perl has a slightly eccentric rules
fil
On Mon, Aug 17, 2009 at 7:01 AM, Niko Tyni wrote:
>> There are ways around that, have the perl package provide a name which
>> maps to the debian version less NMUs (either by manually updating
>> debian/control, or an automated process which removes bin NMUs from
>> the version).
>
> As binNMUs get
On Mon, Jul 13, 2009 at 6:12 AM, Niko Tyni wrote:
> On Fri, Jul 10, 2009 at 11:15:17PM +1000, Brendan O'Dea wrote:
>> I vote that we fix this "problem" by simply nailing the dependencies
>> between perl-base/perl/perl-modules to an exact equivalence. [...]
>
>
On Fri, Jul 10, 2009 at 1:23 AM, Adrian Bunk wrote:
> /usr/share/doc/perl-modules is a symlink to /usr/share/doc/perl,
> and /usr/share/doc/perl/changelog.Debian.gz is shipped in the
> perl-base package.
> [...]
> "the Debian source tree" of perl-modules 5.10.0-24 is hardly the
> 5.10.0-1 or 5.10.0
On Wed, Jul 30, 2008 at 7:55 AM, Marc Lehmann <[EMAIL PROTECTED]> wrote:
> (I really wonder when debian maintainers learn to do their job properly
> and stop trying to act like bignosed idiots who know everything better -
> wasn't the we-know-better-than-openssl incident enough?).
> Sorry, but you
On Wed, Jul 30, 2008 at 7:52 AM, Marc Lehmann <[EMAIL PROTECTED]> wrote:
> On Tue, Jul 29, 2008 at 11:17:33PM +1000, Brendan O'Dea <[EMAIL PROTECTED]>
> wrote:
>> I think that you have some other problem. -L -lperl will search
>> at compile time for li
On Tue, Jul 29, 2008 at 10:44 AM, Marc Lehmann
<[EMAIL PROTECTED]> wrote:
> debian makes it impossible to install perls in other prefixes by forcing
> libperl.so (a private library that should not be in the default search
> path) into /usr/lib, where it clashes with every other libperl.
Impossible
On Wed, Jul 9, 2008 at 5:53 AM, gregor herrmann <[EMAIL PROTECTED]> wrote:
> On Tue, 08 Jul 2008 20:47:48 +0200, Ralf Treinen wrote:
> Possible solutions include:
> * make libcgi-pm-perl conflict (and maybe provide) with
> libcgi-fast-perl; that would mean changing the Priority to extra
> (also o
On Fri, Feb 15, 2008 at 09:39:42AM +0100, Raphael Hertzog wrote:
>On Thu, 14 Feb 2008, Niko Tyni wrote:
>> I run a few greps on debian/rules of the source packages of all the
>> binary packages matching '-perl' in unstable. Results: at least 398
>> arch:all and 38 arch:any packages apparently do an
On Mon, Jan 21, 2008 at 11:52:21AM +0100, Marc 'HE' Brockschmidt wrote:
>|
>ext/IO/t/io_sock..FAILED--expected
>test 11, saw test 12
That's puzzling. Is the build tree still around? If so, does the test
fail consistently? Run:
cd t; ./perl ../lib
On Tue, Dec 25, 2007 at 01:26:11PM +0100, Marc 'HE' Brockschmidt wrote:
>Package: perl
>Version: 5.10.0-1
>Severity: serious
>Tags: experimental
>
>Heya,
>
>Building perl 5.10 failed on all my buildds due to the same test suite
>failure:
>
>| ext/Sys/Syslog/t/syslog.
On Sat, Nov 10, 2007 at 07:00:17PM +0100, Nico Golde wrote:
>the following CVE (Common Vulnerabilities & Exposures) id was
>published for perl.
Upload is waiting for ftp-master to come back.
--bod
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact
On Thu, Nov 08, 2007 at 12:09:30AM +1100, Steffen Joeris wrote:
>Package: perl
>The patch used for this update is below. The CVE number is
>CVE-2007-5116. Please mention it in your changelog, when you fix this
>bug.
Thanks,
will apply and build tonight.
--bod
--
To UNSUBSCRIBE, email to [EMA
On Tue, Jul 24, 2007 at 09:01:51PM +0100, Marcos Marado wrote:
>OK, the "working" machine outputs nothing, but the "non-working" says:
>
>$ perl -e "use Scalar::Util 'weaken'"
>Weak references are not implemented in the version of perl at -e line 1
>BEGIN failed--compilation aborted at -e line 1.
>
merge 334958 429017
thanks
On Fri, Jun 15, 2007 at 03:08:40PM +0200, Andrea Cavaglieri wrote:
>I can't install the package in subject because the virtual package
>libapt-pkg-libc6.3-6-3.11 isn't installable (or better, package apt
>provides libapt-pkg-libc6.5-6-4.4 but not libapt-pkg-libc6.3-6-3.1
On Mon, Jul 24, 2006 at 05:44:22PM +0200, Sven Mueller wrote:
>Is there any chance to get this fixed within the next week or two? It's
>already blocking something like 60 packages from entering testing.
Not a whole lot that I can do about it.
Ryan believes that the problem with MIPS is a kernel i
reassign 335105 kernel
close 335105 2.6.5
thanks
On Sun, Dec 11, 2005 at 10:24:56AM +, Andrew Suffield wrote:
>My bet is that it's this kernel bug:
>
> I don't know if you've been following, but it was recently discoverd that on
> smp, if multiple processes read from /dev/urandom at the same
On Mon, Apr 12, 2004 at 03:31:35PM -0700, Peter Sebastian Masny wrote:
>I have what I believe is the same problem using working postfix and
>procmail. In detail:
>
>apt-get install spamassassin librazor-perl
>enable spamd in /etc/default/spamassassin
>/etc/init.d/spamassasin restart
>
>then in my
On Tue, Feb 21, 2006 at 10:54:08AM +0100, Ulrich Fürst wrote:
>Steve Langasek <[EMAIL PROTECTED]> wrote:
>> Please forward the output of ls -ld /usr/lib/perl/5.8 to this bug.
>
>ls -ld /usr/lib/perl/5.8
>drwxr-xr-x 27 root root 4096 2006-02-20 15:02 /usr/lib/perl/5.8/
>
>> This should be a symlink
tags 325528 - unreproducible
tags 325528 + patch
found 325528 1.2.0-5
thanks
On Tue, Aug 30, 2005 at 04:22:36AM +0900, Hidetaka Iwai wrote:
>Marc Dequènes (Duck) <[EMAIL PROTECTED]> wrote:
>> Using any sample file provided with mgp resulted in a segfault after
>> rendering background, so i guess w
On Thu, Dec 08, 2005 at 12:41:02PM -0800, Charles Stevenson wrote:
>[EMAIL PROTECTED]:~$ perl -e 'printf("%2918905856\$vs")'
>Segmentation fault
>
>I haven't had time yet but I imagine it might be possible to gain root
>through perl-suid.
This is not a buffer overflow.
You're causing a SEGV by at
On Fri, Dec 02, 2005 at 10:55:56AM +0100, Martin Pitt wrote:
>The CVE number CVE-2005-3962 has been assigned to this. Please mention
>this number in the changelog when you fix this.
Yes, Fedora quoted that number in their advisory. Oddly, cve.mitre.org
doesn't appear to have that have a match for
On Mon, Nov 21, 2005 at 09:34:11AM +0100, Thomas Hood wrote:
>Brendan O'Dea wrote:
>> Note: I believe that "return" should work to exit from a script both
>> when sourced and when executed but perhaps someone with a copy of POSIX
>> could confirm.
>
>
>
On Mon, Nov 21, 2005 at 09:55:22AM +0100, Thomas Hood wrote:
>Brendan O'Dea wrote:
>> there are quite a few instances in /etc/init.d/*.sh scripts where "exit" is
>> called.
>
>All the exit commands are either (1) at the end of usage exception sections,
>
On Sat, Nov 19, 2005 at 11:33:44PM +0100, Petter Reinholdtsen wrote:
>[Brendan O'Dea]
>> Debian Policy states (§9.3.1):
>>
>>"Also, if the script name ends `.sh', the script will be sourced
>>in runlevel `S' rather that being run in a forked
Package: sysv-rc
Version: 2.86.ds1-5
Severity: serious
Debian Policy states (§9.3.1):
"Also, if the script name ends `.sh', the script will be sourced in
runlevel `S' rather that being run in a forked subprocess, but will
be explicitly run by `sh' in all other runlevels".
This could p
On Fri, Oct 14, 2005 at 12:44:33PM +0200, [EMAIL PROTECTED] wrote:
>Package: perl
>Version: 5.8.7-6
>Severity: serious
>
>There was an error while trying to autobuild your package:
>
>> Automatic build of perl_5.8.7-6 on ska by sbuild/m68k 69
>> Build started at 20051013-0833
>
>[...]
>
>> ** Using
reopen 333510
thanks
On Thu, Oct 13, 2005 at 01:49:45PM +1000, Brendan O'Dea wrote:
>Building a new package now. I've dropped the optimisation on only the
>following files (which proved to be the source of the problem on other
>architectures): pp_ctl.c, pp_hot.c and pp_
On Wed, Oct 12, 2005 at 12:01:03PM +0300, Riku Voipio wrote:
>Perl fails to build on arm/armeb with -O2 optimization and current gcc4.
>with -01, perl compiled fine and pass testsuites withoout a problem. By
>using the following patch instead of the current 63_debian_ppc_opt..
>patch, this (gcc) is
reassign 326090 cpio
retitle 326090 cpio -p does not copy dangling symlinks
thanks
On Thu, Sep 01, 2005 at 08:33:08PM +0200, Andreas Jochens wrote:
>Without 'libperl.so' some packages which Build-Depend on
>'libperl-dev' will FTBFS.
This build worked fine when originally run. It appears that the
On Thu, Aug 18, 2005 at 10:19:48PM +0200, martin f krafft wrote:
>Is there any progress being made on this bug? I can't install any
>more debconf-using packages on my system, or packages uses perl for
>maintainer scripts, and this is quite bad.
I haven't been able to replicate the problem.
debcon
On Fri, Apr 08, 2005 at 08:36:05AM +0200, Henning Glawe wrote:
>it could be "fixed" by introducing a versioned pre-dependency of
>perl-modules on perl-base while letting perl-base conflict with too old
>perl-modules, which forces apt to update both packages together; this
>combination may be highl
On Thu, Mar 17, 2005 at 11:37:48PM -0600, Micah Anderson wrote:
>#286905 fixes CAN-2005-0448 for testing's perl (5.8.4-7), however it
>leaves it unfixed in stable's version (5.6.1-8.8), which is also
>affected (according to http://www.securityfocus.com/bid/12767), so
>this bug should not be closed.
On Fri, Feb 04, 2005 at 03:32:05PM +0100, Thierry Carrez wrote:
>Brendan O'Dea wrote:
>
>> Seems a pretty clean fix, I've applied this to Debian's 5.8.4-5 package.
>
>Paul Szabo brought to our attention that the fix for CAN-2004-0452 does
>not handle all race
On Wed, Jan 12, 2005 at 05:02:41PM -0500, Aaron Sherman wrote:
>> [p5p:] If anyone had a cleaner (and cross-platform) fix, I'd love to
>> hear of it.
>
>Well, certainly relying on rm (and you assumed a "-v" option which,
>AFAIK implies GNU rm specifically) is right out. I'm sure others will
>say th
On Thu, Dec 23, 2004 at 09:10:31AM +1100, Paul Szabo wrote:
>Package: perl-modules
>Version: 5.6.1-8.7
>Severity: critical
>File: /usr/share/perl/5.6.1/File/Path.pm
>Tags: security
>Justification: root security hole
>Example of attack: suppose we know that root uses rmtree to clean up
>/tmp direct
41 matches
Mail list logo
