Re: Bug#503712: the gs-common problem

[Thomas Viehmann]

Hi,

Niko Tyni wrote:
>> Maybe "configure script" is badly worded: It's most blatant abuse, but
>> I'd just stick it into a /var/lib/dpkg/info/ghostscript.config
>> unless there are apt-get-lookalikes that don't call that at the
>> beginning of an upgrade. If the user produces the bad situation with
>> dpkg by himself, well, who cares.
> 
> I see. It's blatant abuse indeed, but it might work.
> 
> The preconfiguration only happens if debconf and apt-utils are installed
> (see /etc/apt/apt.conf.d/70debconf and /usr/sbin/dpkg-preconfigure), but
> according to popcon more than 99.8% of all installations have them. 
> 
> If this is the chosen approach, the script could as well fix the etch
> gs-common.prerm script instead of removing it; I think something like
> 
> if md5sum --status --check < 1959479be1e513d94a22f6fad8227fa3  /var/lib/dpkg/info/gs-common.prerm
> EOF
> then
> sed -i 's/defoma-app -t \(purge\|clean\) gs$/& || true/' \
> /var/lib/dpkg/info/gs-common.prerm || true
> fi
> 
> should do.

Barring objections, I'll test things and NMU along the lines Niko
indicated on Sunday.
Thanks to everyone for weighing in on the bug report.

Kind regards

T.
-- 
Thomas Viehmann, http://thomas.viehmann.net/


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: Please unblock ctypes/1.0.2-6

[Adeodato Simó]

* Sandro Tosi [Thu, 25 Dec 2008 01:50:45 +0100]:

> Hello,
> that version (just uploaded) simply add 'binutils' to Depends (along
> with minor cosmetic adjustments to the packaging) to fix an RC bug:
> 509623

> So I'm kindly ask you to unblock it.

Unblocked by Neil.

-- 
Adeodato Simó dato at net.com.org.es
Debian Developer  adeodato at debian.org
 
Any life, no matter how long and complex it may be, is made up of a
single moment: the moment in which a man finds out, once and for all,
who he is.
-- Jorge Luis Borges


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: Bug#503712: the gs-common problem

[Niko Tyni]

On Tue, Dec 23, 2008 at 09:39:20PM +0100, Thomas Viehmann wrote:
> Niko Tyni wrote:
> > On Tue, Dec 23, 2008 at 02:15:22PM +0100, Thomas Viehmann wrote:

> >> immediately after I sent the last mail, Sune Vuorela pointed me to
> >> apache2's fix for #390823: They simply remove the problematic maintainer
> >> script.
 
> > I think it's too late to do it inside ghostscript, it would have to go
> > in perl-modules.
> Maybe "configure script" is badly worded: It's most blatant abuse, but
> I'd just stick it into a /var/lib/dpkg/info/ghostscript.config
> unless there are apt-get-lookalikes that don't call that at the
> beginning of an upgrade. If the user produces the bad situation with
> dpkg by himself, well, who cares.

I see. It's blatant abuse indeed, but it might work.

The preconfiguration only happens if debconf and apt-utils are installed
(see /etc/apt/apt.conf.d/70debconf and /usr/sbin/dpkg-preconfigure), but
according to popcon more than 99.8% of all installations have them. 

If this is the chosen approach, the script could as well fix the etch
gs-common.prerm script instead of removing it; I think something like

if md5sum --status --check <

Re: Bug#506353: lenny removal requests

[Marc 'HE' Brockschmidt]

Julian Field  writes:
> On 25/12/08 21:38, Nico Golde wrote:
>> I'm afraid this is too late, mailscanner has already been
>> removed from lenny.
> Shame you couldn't wait 6 days for the new stable release. I don't
> immediately release a new stable release after making lots of changes to
> ensure it has received some testing in the field first. Your loss.

It wouldn't have been included anyway. Making lots of changes is not
something the Debian elease team wants to see shortly before a release.

> -- 
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.

This signature is a bad idea.

Marc
-- 
Fachbegriffe der Informatik - Einfach erklärt
89: PSD
   Damit die Schriften nicht aussehen, als wären sie mit der
   Laubsäge bearbeitet. (Meikel Katzengreis)


pgpu7eNrFvRlE.pgp
Description: PGP signature

Re: Bug#506353: lenny removal requests

[Nico Golde]

Hi,
* Simon Walter  [2008-12-25 00:43]:
> "Gabor FUNK"  writes:
[...] 
> Current state of this work is: It works (MailScanner starts and scans
> a simple textmail) but it's not well tested.  There still need to be
> done some testing with TNEF attachment, virus removal and some other
> cases.
> 
> I currently don't Know when I will have the time to do this.
> 
> I have attached the diff against 4.68.8 debian package.

I'm afraid this is too late, mailscanner has already been 
removed from lenny.

Cheers
Nico
-- 
Nico Golde - http://www.ngolde.de - n...@jabber.ccc.de - GPG: 0x73647CFF
For security reasons, all text in this mail is double-rot13 encrypted.


pgpmDn2fiaUbz.pgp
Description: PGP signature

Bug#509777: RM: axel/testing-proposed-updates -- ROM; migrated to testing

[Y Giridhar Appaji Nag]

Package: ftp.debian.org
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

axel 1.1-3lenny1 has been pushed to testing from t-p-u after it was
built on all architectures.  Please remove it from t-p-u.

Thanks,

Giridhar

- -- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (800, 'unstable'), (700, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAklUSp0ACgkQ4eu+pR04mIcXhACgx7ygscowvR+b2NMWoeQlH5wP
hX4AoM9FutNlgykI/Ip4CpMjJy+EF93r
=xPGr
-END PGP SIGNATURE-



-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Please hint to unblock debian-reference 2.22

[Osamu Aoki]

Hi,

This is documentation package.

I have uploaded new 1.22 version.  Most importantly, it removes
references to removed packages.

Please hint to unblock this.

debian-reference (2.22) unstable; urgency=low

  * Updated to make this build smooth on Ubuntu. Closes: 509163
  * Updated screen related contents.
  * Fixed regex of gnupg script example.
  * Added section for "NetworkManager" and "Colorized shell echo".
  * Updated git command style and mentioned sort order w.r.t. locale.
  * Updated popcon and package size data and removed reference to
removed packages.

 -- Osamu Aoki   Sat, 27 Dec 2008 01:13:05 +0900




Osamu


signature.asc
Description: Digital signature

Re: asterisk t-p-u upload

[Ron]

Hi,

I'm happy to consider this grounds for requesting a freeze exception
for vpb-driver, the changes since 4.2.36 that affect Debian users are
all in the 'too minor to request one otherwise' category, so I hadn't
done so previously.  This code has been in freeze upstream for quite
some months, so the changes are all deliberately minimal and suitable
for propagation to production users.

I definitely should relax the -V with the next upload, this is an
oversight/bug on my part.  The strict versioning was appropriate when
the packages were first created, but that hasn't been true since the
first upload to the distro, it's just gone unnoticed until now.  I'll
hold off on an upload to do that until I hear how you'd like to deal
with this for Lenny.  vpb-driver already has enough time in unstable
and is eligible to migrate immediately if you choose to go that way.

Cheers,
Ron


On Fri, Dec 26, 2008 at 02:08:59AM +0200, Faidon Liambotis wrote:
> Hi,
> 
> I've prepared a fix for #507883, an RC bug for asterisk.
> 
> Unfortunately, one of its dependencies, libvpb0, had a new upload in
> unstable (v4.2.38-1 vs. v4.2.36-1 in lenny) and uses  "dh_makeshlibs -V"
> with no symbol files, which resulted in new shlibs for asterisk.
> 
> Those libvpb0 changes are minor -mostly fixing GCC 4.4 FTBFS due to
> missing headers- and do not change the ABI at all (verified both by
> looking at the source and by comparing the exported symbols).
> 
> So, I can see four solutions:
>   a) The obvious: upload asterisk to t-p-u.
>   b) Fix libvpb0's shlibs to state the reality (">= 4.2.36"), upload,
>  wait for it to build on all architectures and then upload asterisk.
>  Versioned build-dep is obviously not an option here.
>   c) Push vpb-driver 4.2.38-1 to lenny.
>  asterisk is the only rev-dep in Debian, Ron is also upstream.
>  But I can see how this can be a problem during our hard freeze :)
>   d) Override the shlibs with debian/shlibs.local.
> 
> If there's no real rush and Ron agrees, I'd say that (c) is the best
> solution. I have no real problem with (d) either, despite its uglyness.
> 
> What's the preferred way in your opinion?
> 
> Thanks and happy holidays,
> Faidon
> 


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: Bug#503712: the gs-common problem

[Asheesh Laroia]

On Tue, 23 Dec 2008, Thomas Viehmann wrote:


Niko Tyni wrote:

On Tue, Dec 23, 2008 at 02:15:22PM +0100, Thomas Viehmann wrote:


immediately after I sent the last mail, Sune Vuorela pointed me to
apache2's fix for #390823: They simply remove the problematic maintainer
script.
The question then is where to do this in so it is reliably done before
stuff happens.
In one of the perl packages (because the upgrade of perl triggers this)
is probably too ugly, maybe the configure script of ghostscript?



I think it's too late to do it inside ghostscript, it would have to go
in perl-modules.



Maybe "configure script" is badly worded: It's most blatant abuse, but
I'd just stick it into a /var/lib/dpkg/info/ghostscript.config
unless there are apt-get-lookalikes that don't call that at the
beginning of an upgrade. If the user produces the bad situation with
dpkg by himself, well, who cares.


I think this is the best strategy.  Better to hack related packages.

An alternative is to to add gs-common being added to apt's 01autoremove, 
but I think that the /var/lib/dpkg/info/ghostscript.config change is a 
better choice; it limits the number of source packages affected.


I left some more notes on the bug, but this is the crux of it.

-- Asheesh.

--
You never know how many friends you have until you rent a house on the beach.


--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: diffstat

[Neil McGovern]

On Wed, Dec 24, 2008 at 12:23:03AM -0500, Asheesh Laroia wrote:
> I have a feeling that the libwebkit currently in sid and lenny is pretty  
> broken, from the looks of this bug.
>

Unfortunately, we don't seem to be able to get much/any response from
the maintainers. It would have been really useful to have a comment
recently.

> Is there any way that this library can be permitted to enter testing with 
> all these changes?
>

Not really, no.

> * Find the fix for this issue and backport it on top of 1.0.1-4

This would be preferred.

> * Remove libwebkit-1.0-1 from lenny

Possible, but not something I'm too happy with given it's popcon.

> * Simply allow lenny to release with 1.0.1-4 that is this broken.
>

Could anyone confirm how broken this is? Is it all sites, or a
selection? Maintainers: do you have an opinion on this bug?

Thanks,
Neil
-- 
A. Because it breaks the logical sequence of discussion
Q. Why is top posting bad?
gpg key - http://www.halon.org.uk/pubkey.txt ; the.earth.li B345BDD3


signature.asc
Description: Digital signature

Re: Bug#502836: t-p-u push to lenny for axel

[Y Giridhar Appaji Nag]

Hi Neil,

On 08/12/25 11:42 +, Neil McGovern said ...
> On Sat, Dec 20, 2008 at 05:03:50PM +0530, Y Giridhar Appaji Nag wrote:
> > 
> > More info about my request for pushing 1.1-3lenny1 to lenny from t-p-u:
> 
> Could you please attach a debdiff?

Attached, but Luk has already unblocked and pushed it to testing.

Thanks

Giridhar

-- 
Y Giridhar Appaji Nag | http://appaji.net/
Index: debian/control
===
--- debian/control	(.../1.1-3)	(revision 12070)
+++ debian/control	(.../1.1-3lenny1)	(revision 12070)
@@ -1,13 +1,12 @@
 Source: axel
 Section: web
 Priority: optional
-Maintainer: Y Giridhar Appaji Nag 
-Standards-Version: 3.7.3
+Maintainer: Y Giridhar Appaji Nag 
+Standards-Version: 3.8.0
 Build-Depends: gettext, debhelper (>= 5), dpatch
 Homepage: http://axel.alioth.debian.org/
 Vcs-Svn: svn://svn.debian.org/svn/collab-maint/ext-maint/axel/unstable
 Vcs-Browser: http://svn.debian.org/wsvn/collab-maint/ext-maint/axel/unstable/?op=log
-DM-Upload-Allowed: yes
 
 Package: axel
 Architecture: any
Index: debian/changelog
===
--- debian/changelog	(.../1.1-3)	(revision 12070)
+++ debian/changelog	(.../1.1-3lenny1)	(revision 12070)
@@ -1,3 +1,14 @@
+axel (1.1-3lenny1) testing-proposed-updates; urgency=low
+
+  * Patch 04_http_overflow to fix buffer overflow while translating
+characters to hex.  Thanks Philipp Hagemeister 
+(Closes: #502836)
+  * Update Standards-Version to 3.8.0, add README.source
+  * Remove DM-Upload-Allowed: yes and update Maintainer: to official
+Debian ID
+
+ -- Y Giridhar Appaji Nag   Mon, 15 Dec 2008 14:29:19 +0530
+
 axel (1.1-3) unstable; urgency=low
 
   * Update 02_axelkapt to change Categories=Utility;Network;KDE; to
Index: debian/patches/04_http_overflow.dpatch
===
--- debian/patches/04_http_overflow.dpatch	(.../1.1-3)	(revision 0)
+++ debian/patches/04_http_overflow.dpatch	(.../1.1-3lenny1)	(revision 12070)
@@ -0,0 +1,31 @@
+#! /bin/sh /usr/share/dpatch/dpatch-run
+## 04_http_overflow.dpatch by Y Giridhar Appaji Nag 
+##
+## All lines beginning with `## DP:' are a description of the patch.
+## DP: Fix buffer overflow while translating characters to hex codes
+## DP: Patch thanks to Philipp Hagemeister 
+
+...@dpatch@
+diff -urNad axel-1.1~/http.c axel-1.1/http.c
+--- axel-1.1~/http.c	2008-01-16 12:03:01.0 +0530
 axel-1.1/http.c	2008-12-15 13:41:12.0 +0530
+@@ -236,9 +236,19 @@
+ 	
+ 	for( i = j = 0; s[i]; i ++, j ++ )
+ 	{
++		/* Fix buffer overflow */
++		if (j >= MAX_STRING - 1) {
++			break;
++		}
++		
+ 		t[j] = s[i];
+ 		if( s[i] == ' ' )
+ 		{
++			/* Fix buffer overflow */
++			if (j >= MAX_STRING - 3) {
++break;
++			}
++			
+ 			strcpy( t + j, "%20" );
+ 			j += 2;
+ 		}

Property changes on: debian/patches/04_http_overflow.dpatch
___
Added: svn:executable
   + *

Index: debian/patches/00list
===
--- debian/patches/00list	(.../1.1-3)	(revision 12070)
+++ debian/patches/00list	(.../1.1-3lenny1)	(revision 12070)
@@ -1,3 +1,4 @@
 01_bug_report
 02_axelkapt
 03_l10n_ru
+04_http_overflow
Index: debian/README.source
===
--- debian/README.source	(.../1.1-3)	(revision 0)
+++ debian/README.source	(.../1.1-3lenny1)	(revision 12070)
@@ -0,0 +1,2 @@
+Please read the README.source provided with the documentation of the
+dpatch package


signature.asc
Description: Digital signature

asterisk t-p-u upload

[Faidon Liambotis]

Hi,

I've prepared a fix for #507883, an RC bug for asterisk.

Unfortunately, one of its dependencies, libvpb0, had a new upload in
unstable (v4.2.38-1 vs. v4.2.36-1 in lenny) and uses  "dh_makeshlibs -V"
with no symbol files, which resulted in new shlibs for asterisk.

Those libvpb0 changes are minor -mostly fixing GCC 4.4 FTBFS due to
missing headers- and do not change the ABI at all (verified both by
looking at the source and by comparing the exported symbols).

So, I can see four solutions:
  a) The obvious: upload asterisk to t-p-u.
  b) Fix libvpb0's shlibs to state the reality (">= 4.2.36"), upload,
 wait for it to build on all architectures and then upload asterisk.
 Versioned build-dep is obviously not an option here.
  c) Push vpb-driver 4.2.38-1 to lenny.
 asterisk is the only rev-dep in Debian, Ron is also upstream.
 But I can see how this can be a problem during our hard freeze :)
  d) Override the shlibs with debian/shlibs.local.

If there's no real rush and Ron agrees, I'd say that (c) is the best
solution. I have no real problem with (d) either, despite its uglyness.

What's the preferred way in your opinion?

Thanks and happy holidays,
Faidon


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: Bug#506353: lenny removal requests

[Julian Field]

On 25/12/08 21:38, Nico Golde wrote:

Hi,
* Simon Walter  [2008-12-25 00:43]:
   

"Gabor FUNK"  writes:
 

[...]
   

Current state of this work is: It works (MailScanner starts and scans
a simple textmail) but it's not well tested.  There still need to be
done some testing with TNEF attachment, virus removal and some other
cases.

I currently don't Know when I will have the time to do this.

I have attached the diff against 4.68.8 debian package.
 


I'm afraid this is too late, mailscanner has already been
removed from lenny.
   
Shame you couldn't wait 6 days for the new stable release. I don't 
immediately release a new stable release after making lots of changes to 
ensure it has received some testing in the field first. Your loss.


Jules

--
Julian Field MEng CITP CEng
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store

MailScanner customisation, or any advanced system administration help?
Contact me at ju...@jules.fm

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
PGP public key: http://www.jules.fm/julesfm.asc


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: [Fwd: Bug#509184: bacula-director-pgsql: Director crashes with double free from jcr.c:343]

[Thiemo Seufer]

Teodor wrote:
> On Tue, Dec 23, 2008 at 2:28 PM, Thiemo Seufer  wrote:
> > Gerfried Fuchs wrote:
> >>  I can confirm that the package builds fine, started a build yesterday
> >> on a mipsel box I have access to. I did build it in an uptodate unstable
> >> cowbuilder chroot, the build log can be found here:
> >> 
> >
> > Thanks for testing, I started a retry on the buildd.
> 
> The current buildd status is "Built" [1], but no progress for more
> than one day. Does it need a manual intervention (e.g. to be uploaded
> somewhere) or everything is done automatically?

Like for any other package the buildd admin has to check the build log
and sign the changes file. This can take few days, especially in holiday
season.


Thiemo


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: [Fwd: Bug#509184: bacula-director-pgsql: Director crashes with double free from jcr.c:343]

[Adeodato Simó]

* Teodor [Wed, 24 Dec 2008 20:07:25 +0200]:

> On Tue, Dec 23, 2008 at 2:28 PM, Thiemo Seufer  wrote:
> > Gerfried Fuchs wrote:
> >>  I can confirm that the package builds fine, started a build yesterday
> >> on a mipsel box I have access to. I did build it in an uptodate unstable
> >> cowbuilder chroot, the build log can be found here:
> >> 

> > Thanks for testing, I started a retry on the buildd.

> The current buildd status is "Built" [1], but no progress for more
> than one day. Does it need a manual intervention (e.g. to be uploaded
> somewhere) or everything is done automatically?

It needs manual action, but it's Christmas (I guess it's that).

-- 
Adeodato Simó dato at net.com.org.es
Debian Developer  adeodato at debian.org
 
   Listening to: Anjani - Half The Perfect World


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org