Bug#4655: /\dobe |ndesign cs3 'save 2542'
symantec norton antivirus 10.1 for mac - 29 sonic scenarist 3.0 - 49 corel painter ix for mac - 39 softimage alienbrain 8 - 169 borland developer studio 2006 - 149 microsoft visio 2007 professional - 39 steinberg nuendo 3.1 - 99 parallels desktop 3.0 for mac - 29 cakewalk sonar 6 producer edition - 69 microsoft frontpage 2003 - 29 +ype 'getmicrosoftfast .com' !n your Internet Exp1orer Take off ' before you +ype !n your Internet Exp1orer creative suite 3 design premium for win - 269 symantec norton 360 - 29 mcafee desktop firewall 8.0.493 - 39 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#464907: dpkg seems not to check for broken versioned dependencies when upgrading
I haven't checked, but this sounds very similar to #20471. There's a patch in that bug. If you can take some time to verify if it also fixes this issue, it would be nice. I applied this patch on top of current git master (rev 98cdd8883f0661e24ff72d4c29d73554586eddf8), and have been using it today while doing whatever, and it seemed to cause this failure: [EMAIL PROTECTED]:/home/joey/tmp/xterm-231dpkg -i ../xterm_231-2boldmode1_i386.deb dpkg: ../../src/depcon.c:218: depisok: Assertion `dep-type == dep_depends || dep-type == dep_predepends || dep-type == dep_breaks || dep-type == dep_conflicts || dep-type == dep_recommends || dep-type == dep_suggests || dep-type == dep_enhances' failed. Other packages installed ok; I was able to downgrade to unstable's dpkg and then install xterm successfully. Here's the package's header, just in case: Package: xterm Version: 231-2boldmode1 Architecture: i386 Maintainer: Debian X Strike Force [EMAIL PROTECTED] Installed-Size: 1108 Depends: libc6 (= 2.7-1), libfontconfig1 (= 2.4.0), libice6 (= 1:1.0.0), libncurses5 (= 5.6+20071006-3), libsm6, libx11-6, libxaw7, libxext6, libxft2 ( 2.1.1), libxmu6, libxt6, xbitmaps Recommends: xutils Suggests: xfonts-cyrillic Provides: x-terminal-emulator Section: x11 Priority: optional -- see shy jo signature.asc Description: Digital signature
Bug#465282: dpkg-dev: Set a set of compiler flags for a build
On Mon, Feb 11, 2008 at 05:39:10PM +0100, Matthias Klose wrote:
Content-Description: message body text
Package: dpkg-dev
Severity: wishlist
Please find attached a patch which implements setting a set of
compiler flags for a build; this was first announced in
http://lists.debian.org/debian-devel/2007/12/msg00090.html
Now simpliefied to just use the CFLAGS/CFLAGS_APPEND naming by Colin
Watson.
Maybe more like this (still missing l10n, but a lot less code
duplication):
diff --git a/scripts/dpkg-buildpackage.pl b/scripts/dpkg-buildpackage.pl
index 72854dd..a550f4c 100755
--- a/scripts/dpkg-buildpackage.pl
+++ b/scripts/dpkg-buildpackage.pl
@@ -242,9 +242,8 @@ if ($signcommand) {
}
}
+my $build_opts = Dpkg::BuildOptions::parse();
if ($parallel) {
-my $build_opts = Dpkg::BuildOptions::parse();
-
$parallel = $build_opts-{parallel} if (defined $build_opts-{parallel});
$ENV{MAKEFLAGS} ||= '';
if ($parallel eq '-1') {
@@ -256,6 +255,26 @@ if ($parallel) {
Dpkg::BuildOptions::set($build_opts);
}
+my $default_flags = defined $build_opts-{noopt} ? -g -O0 : -g -O2;
+my %flags = ( CPPFLAGS = '',
+ CFLAGS = $default_flags,
+ CXXFLAGS = $default_flags,
+ FFLAGS = $default_flags,
+ LDFLAGS = -Wl,-Bsymbolic-functions,
+);
+
+foreach my $flag (keys %flags) {
+if ($ENV{${flag}}) {
+ print $progname: use ${flag} from environment: $ENV{${flag}}\n;
+} else {
+ $ENV{${flag}} = $flags{$flag};
+ print $progname: set ${flag} to default value: $ENV{${flag}}\n;
+}
+if ($ENV{${flag}_APPEND}) {
+ $ENV{${flag}} .= .$ENV{${flag}_APPEND};
+}
+}
+
my $cwd = cwd();
my $dir = basename($cwd);
Gruesse,
--
Frank Lichtenheld [EMAIL PROTECTED]
www: http://www.djpig.de/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#465340: dpkg: Broken call to open in Dpkg/Control.pm
Package: dpkg
Version: 1.14.16.6
Severity: important
Tags: patch
User: [EMAIL PROTECTED]
Usertags: origin-ubuntu hardy ubuntu-patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
In Ubuntu, we've applied the attached patch to achieve the following:
* Fix wrong call to open in Dpkg/Control.pm that makes using a different
control file than debian/control fail horribly.
We thought you might be interested in doing the same.
- -- System Information:
Debian Release: lenny/sid
APT prefers hardy
APT policy: (500, 'hardy'), (500, 'gutsy')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.24-6-generic (SMP w/2 CPU cores)
Locale: LANG=da_DK.UTF-8, LC_CTYPE=da_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHsNBxonjfXui9pOMRAtxZAJwOJGRnPBBVuxf+wyjj7heRPh6ldwCfYGKk
gnFO1f8OjTlKg6rp654onUk=
=u9ID
-END PGP SIGNATURE-
diff -Nru /tmp/63ah7FRjAl/dpkg-1.14.16.6ubuntu1/scripts/Dpkg/Control.pm
/tmp/fQCCS9NM6H/dpkg-1.14.16.6ubuntu2/scripts/Dpkg/Control.pm
--- dpkg-1.14.16.6ubuntu1/scripts/Dpkg/Control.pm 2008-01-18
11:12:53.0 +0100
+++ dpkg-1.14.16.6ubuntu2/scripts/Dpkg/Control.pm 2008-02-11
23:20:11.0 +0100
@@ -78,7 +78,7 @@
my ($self, $file) = @_;
$self-reset();
# Parse
-open(CDATA, , $file) || syserr(_g(cannot read %s), $file);
+open(CDATA, $file) || syserr(_g(cannot read %s), $file);
my $cdata = parsecdata(\*CDATA, $file);
return if not defined $cdata;
$self-{source} = $cdata;
Bug#464907: dpkg seems not to check for broken versioned dependencies when upgrading
On Sat, 09 Feb 2008, Joey Hess wrote: libzlui-gtk depends on libzlcore (= 0.8.12-3). I have both installed. If I tell dpkg to upgrade to a new 0.8.13 version of libzlcore, it does so, leaving libzlui-gtk with a broken dependency. At no point does dpkg complain about that dependency being broken. I haven't checked, but this sounds very similar to #20471. There's a patch in that bug. If you can take some time to verify if it also fixes this issue, it would be nice. Cheers, -- Raphaël Hertzog Le best-seller français mis à jour pour Debian Etch : http://www.ouaza.com/livre/admin-debian/
Processed: Re: Bug#465184: libdebian-package-make-perl: Dpkg modules are not yet a public API
Processing commands for [EMAIL PROTECTED]: clone 465184 -1 Bug#465184: libdebian-package-make-perl: Dpkg modules are not yet a public API Bug 465184 cloned as bug 465256. tag 465184 pending Bug#465184: libdebian-package-make-perl: Dpkg modules are not yet a public API There were no tags set. Tags added: pending retitle -1 Please add a $VERSION variable to the Perl modules. Bug#465256: libdebian-package-make-perl: Dpkg modules are not yet a public API Changed Bug title to `Please add a $VERSION variable to the Perl modules.' from `libdebian-package-make-perl: Dpkg modules are not yet a public API'. reassign -1 dpkg-dev Bug#465256: Please add a $VERSION variable to the Perl modules. Bug reassigned from package `libdebian-package-make-perl' to `dpkg-dev'. severity -1 wishlist Bug#465256: Please add a $VERSION variable to the Perl modules. Severity set to `wishlist' from `important' thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#465282: dpkg-dev: Set a set of compiler flags for a build
Package: dpkg-dev Severity: wishlist Please find attached a patch which implements setting a set of compiler flags for a build; this was first announced in http://lists.debian.org/debian-devel/2007/12/msg00090.html Now simpliefied to just use the CFLAGS/CFLAGS_APPEND naming by Colin Watson. Matthias dist-compiler-flags.diff Description: Binary data
