Bug#1021341: vmdb2: missing dependency on zerofree

[Lars Wirzenius]

On Sat, 2023-11-11 at 10:30 -0600, Gunnar Wolf wrote:
> I am adding a Recommends: on zerofree and will soon upload (and close
> thus bug). Michael: I understand your point, but given this is a
> design decision from our upstream author, I prefer adding a Cc: to
> Lars and ask him to consider switching from zerofree over to fstim,
> maybe he has reasons not to.
> 
> Greetings,
> 
>-Gunnar


vmdb2 uses zerofree by default so that the generated image will compress to
be smaller. This is important for my own use cases.

If this isn't great for other use cases, one can avoid the zerofree by
adding `zerofree: false` to the `mount` step. See
 for details.

I'm happy to consider a patch to use fstrim instead of zerofree, but I'm
not likely to make one myself any time soon, sorry.

Bug#945480: [PATCH 0/1] Drop remaining usage of python2

[Lars Wirzenius]

On Thu, 2019-11-28 at 10:40 -0600, Gunnar Wolf wrote:
> Lars Wirzenius dijo [Thu, Nov 28, 2019 at 11:27:54AM +0200]:
> > Thanks, I've applied the changes and pushed them to git.liw.fi and
> > gitlab.
> 
> Thanks for your prompt attention, Lars!
> 
> I am about to board a plane, but will try to work on this bug later
> today. Lars, do you want to tag a release? Or should I do again the
> "+git20191128" way?

If you could do the +git... thing this time, I'd appreciate it.

Safe travels.


signature.asc
Description: This is a digitally signed message part

Bug#945480: [PATCH 0/1] Drop remaining usage of python2

[Lars Wirzenius]

Thanks, I've applied the changes and pushed them to git.liw.fi and
gitlab.

On Mon, Nov 25, 2019 at 03:27:31PM -0300, Antonio Terceiro wrote:
> Hello,
> 
> The following patch drops the remaining usage of python2 in vmdb2, in
> the build system and test suite.
> 
> Gunnar: I just uploaded a cmdtest ported to python3, so without this
> vmdb2 will still fail to build because the test suite uses yarn
> internals which will not be available for python2 anymore.
> 
> Antonio Terceiro (1):
>   Remove remaining usage of python2
> 
>  check |  2 +-
>  setup.py  |  2 +-
>  yarns/900-implements.yarn | 10 +-
>  3 files changed, 7 insertions(+), 7 deletions(-)
> 
> -- 
> 2.24.0
> 

-- 
I want to build worthwhile things that might last. --joeyh


signature.asc
Description: PGP signature

Bug#910201: Processed: tagging 910201

[Lars Wirzenius]

On Wed, 2019-03-06 at 12:39 +0200, Jonathan Carter wrote:
> Hi Lars, I promise that we will stop using vmdebootstap as soon as
> humanly possible after buster. I'm just not sure it's safely and
> reasonably possible before then.

Good. If I get betterer, I may be able to help with that in, say, six months.
Feel free to ask me then, especially if you are willing to consider using
vmdb2 as a replacement.

Happy hacking!


signature.asc
Description: This is a digitally signed message part

Bug#910201: Processed: tagging 910201

[Lars Wirzenius]

On Wed, Mar 06, 2019 at 06:33:00AM +, Niels Thykier wrote:
> I am sorry to hear that you are sad by this.  To be honest, I had
> expected you were informed about this already.
> 
> This was requested in #922826 with the argument that our live image
> builds no longer worked and that it was too risky to rewrite it at this
> time in the release cycle (I remember some of this discussion from IRC,
> so it might not be visible in the bug).
> 
> I have CC'ed the people requesting/supporting this change as they are
> better suited for answering any questions you have in details but also
> figuring out where we go from here (even if that ends up being something
> as trivial as replacing you the maintainer field, so you are not listed
> at the direct contact point vmdebootstrap longer than you had anticipated).

Since I retired, I don't follow any Debian mailing lists, and I'm only
on one obscure Debian related IRC channel, which mostly doesn't even
talk about Debian. I feel better this way, as so much of Debian is bad
for my serenity and mental health. There's a lot of great people in
Debian, and a lot of great work happens in Debian, and I like the
distro, but there's also a number of people doing things that make me
really unhappy about being associated with the in any way. Which is
why I retired.

I made some very really incompetent, rookie mistakes when first
writing vmdebootstrap, and as a result it is one of the worst pieces
of software I've released in decades. It's so fundamentally bad that
it can't be fixed without rethinking and redesigning it from scratch.
That it sometimes mostly works is no excuse.

I've been trying to kill it off for a couple of years now.
Unfortunately, I've not been able to help those using it from
transitioning to something better. Specifically, Debian's live image
building.

When I retired from Debian last year I intentionally didn't upload a
version setting the maintainer to QA, since that carried the risk that
someone would adopt it. I don't want it adopted, I want it killed.

If it was my decision, I'd rather Debian release without a live image
than release one built with vmdebootstrap. However, I realise that
this would not be acceptable to most people and that live images are
used by enough people that Debian needs to provide them.

In a cruel twist of fate, I originally wrote vmdebootstrap because the
Debian live image building tools were buiding images that weren't
suitable for my needs, and also I found the tools to be written in way
thatI didn't want to even try to change them to suit my needs. Writing
my own tool from scratch seemed like it would be easy and an
interesting challenge. I'm paying for that hubris now.

I accept that buster will release with vmdebootstrap. If you could
make it so I don't get any emails about, taking me off as the package
maintainer, that would be nice and I would appreciate that. Thank you.

I'm afraid I won't be answering any bug reports, accept any patches,
or provide any help in keeping vmdebootstrap alive or working through
the life of the buster release.

-- 
I want to build worthwhile things that might last. --joeyh


signature.asc
Description: PGP signature

Bug#910201: Processed: tagging 910201

[Lars Wirzenius]

On Tue, Mar 05, 2019 at 07:24:03PM +, Debian Bug Tracking System wrote:
> Added tag(s) bullseye and sid.

Does this mean buster is going to be released with vmdebootstrap? This
would make me sad. Why is this? I'm not going to spend any time to fix
vmdebootstrap. I'd really rather nobody else did, either, and instead
spent the effort on fixing anything that still uses vmdebootstrap to
use something else.

-- 
I want to build worthwhile things that might last. --joeyh


signature.asc
Description: PGP signature

Bug#922020: gnome-shell: Keyboard layout not applied in programs using Xwayland

[Lars Wirzenius]

> What precisely do you mean by "not applied"? Does typing into Firefox
> and GTK2 apps behave as though you were using a USA keyboard
> (shift+2 -> @, shift+3 -> #, etc.)  or does it have some other
> behaviour?

In native GNOME applications, pressing the key that normally gives
me "-" (dash) gives me "-", which is appropriate for the Finnish
keyboard layout. In other programs, it gives me "/", which is US
layout, and other keys are also consistent with US layout (shift-3 is
# and not £ so it's not UK layout).

> What is in your /etc/default/keyboard?

XKBMODEL="pc105"
XKBLAYOUT="fi"
XKBVARIANT=""
XKBOPTIONS=""
BACKSPACE="guess"

> What does `gsettings list-recursively
> org.gnome.desktop.input-sources` say?

org.gnome.desktop.input-sources show-all-sources false
org.gnome.desktop.input-sources xkb-options @as []
org.gnome.desktop.input-sources per-window false
org.gnome.desktop.input-sources current uint32 0
org.gnome.desktop.input-sources mru-sources @a(ss) []
org.gnome.desktop.input-sources sources [('xkb', 'fi')]

(Under X, not Wayland. See below.)

> Are there any warnings in the systemd journal or syslog that look
> relevant?

I wouldn't know.

> Have you restarted gnome-shell (logged out and back in) since upgrading?
> (I don't expect that this would make any difference, but whether you
> did or not is an important data point in trying to reproduce the bug.)

I rebooted after dist-upgrading, yes.

> Does downgrading gnome-shell to the version in testing resolve this
> for you?

I didn't try, and it's not convenient for me to try.

> Other packages that might be relevant include mutter,
> gnome-settings-daemon, and anything else that /var/log/apt mentions as
> having been upgraded around the same time as gnome-shell.

I did two weeks' worth of dist-upgrade at once. There were lots of
packages. I haven't narrowed down what it was.

I worked around this problem by changing /etc/gdm3/daemon.conf have
WaylandEnable=false
instead of it being commented out, and rebooting. Now everything works.


signature.asc
Description: This is a digitally signed message part

Bug#911690: vmdb2 FTBFS: tests fail

[Lars Wirzenius]

On Tue, Oct 23, 2018 at 04:51:39PM +0200, Helmut Grohne wrote:
> Source: vmdb2
> Version: 0.13.2-1
> Severity: serious
> Tags: ftbfs
> 
> vmdb2 fails to build from source in unstable for multiple architectures,
> e.g. amd64:

Noting this for whoever looks at this again: the problem is that new
versions of pylint invent new reasons to be unhappy with code that it
was happy with before. The fix is to not use pylint.

-- 
I want to build worthwhile things that might last. --joeyh


signature.asc
Description: PGP signature

Bug#874421: python3-cliapp: fails to upgrade from 'stretch' - trying to overwrite /usr/share/man/man5/cliapp.5.gz

[Lars Wirzenius]

I've uploaded a version that should fix this.

On Sat, 2018-08-11 at 19:42 +, Niels Thykier wrote:
> On Thu, 05 Jul 2018 17:35:30 +0300 Lars Wirzenius  wrote:
> > On Thu, 2018-07-05 at 15:06 +0200, Andreas Beckmann wrote:
> > > But the upgrade path from stretch is not clean:
> > > 
> > >   Selecting previously unselected package python3-cliapp.
> > >   Preparing to unpack .../python3-cliapp_1.20170827-1_all.deb ...
> > >   Unpacking python3-cliapp (1.20170827-1) ...
> > >   dpkg: error processing archive 
> > > /var/cache/apt/archives/python3-cliapp_1.20170827-1_all.deb (--unpack):
> > >trying to overwrite '/usr/share/man/man5/cliapp.5.gz', which is also 
> > > in package python-cliapp 1.20160724-2
> > >   Errors were encountered while processing:
> > >/var/cache/apt/archives/python3-cliapp_1.20170827-1_all.deb
> > > 
> > > So you will need some Breaks and Replaces against the old
> > > package in stretch.
> > 
> > I see the problem now. I was confused by you calling it an upgrade problem,
> > when it isn't. It's a problem with one package containing the same file as
> > another package, and the two packages are only tangentially related.
> > 
> > It doesn't seem to me to be a particularly likely scenario, to me. A user
> > would need to change their sources.list to point from stretch to buster,
> > and then not upgrade anything else, but install python3-cliapp.
> > 
> > I'll add the Breaks and Replaces some day. Or have all of cliapp removed
> > from Debian.
> 
> Hi Lars,
> 
> Do you have an ETA on the upload fixing cliapp?  At the moment, cliapp
> is a key package and as such a potential blocker for the new Debian release.
> 
> If you are pondering a removal (per your last sentence), the following
> packages currently rely on cliapp in testing and would need to migrate
> away first:
> 
> """
> 
> Checking reverse dependencies...
> # Broken Depends:
> 
> cmdtest: cmdtest
> freedom-maker: freedom-maker
> live-wrapper: live-wrapper
> vmdb2: vmdb2
> vmdebootstrap: vmdebootstrap
> 
> # Broken Build-Depends:
> cmdtest: python-cliapp
> freedom-maker: python3-cliapp
> live-wrapper: python-cliapp
> vmdb2: python3-cliapp
> """
> 
> Thanks,
> ~Niels
> 


signature.asc
Description: This is a digitally signed message part

Bug#874421: python3-cliapp: fails to upgrade from 'stretch' - trying to overwrite /usr/share/man/man5/cliapp.5.gz

[Lars Wirzenius]

On Sat, 2018-08-11 at 19:42 +, Niels Thykier wrote:
> Do you have an ETA on the upload fixing cliapp?  At the moment, cliapp
> is a key package and as such a potential blocker for the new Debian release.

Key pacakge? I did not know that. What makes cliapp a key package?

I'll try to get this fixed soon. Sorry about the delay.



signature.asc
Description: This is a digitally signed message part

Bug#874421: python3-cliapp: fails to upgrade from 'stretch' - trying to overwrite /usr/share/man/man5/cliapp.5.gz

[Lars Wirzenius]

On Thu, 2018-07-05 at 15:06 +0200, Andreas Beckmann wrote:
> But the upgrade path from stretch is not clean:
> 
>   Selecting previously unselected package python3-cliapp.
>   Preparing to unpack .../python3-cliapp_1.20170827-1_all.deb ...
>   Unpacking python3-cliapp (1.20170827-1) ...
>   dpkg: error processing archive 
> /var/cache/apt/archives/python3-cliapp_1.20170827-1_all.deb (--unpack):
>trying to overwrite '/usr/share/man/man5/cliapp.5.gz', which is also in 
> package python-cliapp 1.20160724-2
>   Errors were encountered while processing:
>/var/cache/apt/archives/python3-cliapp_1.20170827-1_all.deb
> 
> So you will need some Breaks and Replaces against the old
> package in stretch.

I see the problem now. I was confused by you calling it an upgrade problem,
when it isn't. It's a problem with one package containing the same file as
another package, and the two packages are only tangentially related.

It doesn't seem to me to be a particularly likely scenario, to me. A user
would need to change their sources.list to point from stretch to buster,
and then not upgrade anything else, but install python3-cliapp.

I'll add the Breaks and Replaces some day. Or have all of cliapp removed
from Debian.


signature.asc
Description: This is a digitally signed message part

Bug#874421: python3-cliapp: fails to upgrade from 'stretch' - trying to overwrite /usr/share/man/man5/cliapp.5.gz

[Lars Wirzenius]

On Wed, Jul 04, 2018 at 06:34:41PM +0300, Lars Wirzenius wrote:
> (Also, the advice to use Replaces+Breaks is just wrong for this
> package. The bug is that the same file is in both the python2 and
> python3 versions of the package. The correct solution is to have it in
> at most one package. I will be making that fix eventually.)

In fact, it turns out I had already done this, in 1.20170827-1. Both
python-cliapp and python3-cliapp can now be installed at the same
time. I will close the bug. Thanks for reporting the issue, I must
have failed to close the bug in the changelog when uploading.

-- 
I want to build worthwhile things that might last. --joeyh


signature.asc
Description: PGP signature

Bug#874421: python3-cliapp: fails to upgrade from 'stretch' - trying to overwrite /usr/share/man/man5/cliapp.5.gz

[Lars Wirzenius]

On Wed, Sep 06, 2017 at 12:31:19AM +0200, Andreas Beckmann wrote:
> during a test with piuparts I noticed your package fails to upgrade from
> 'stretch'.
> It installed fine in 'stretch', then the upgrade to 'buster' fails
> because it tries to overwrite other packages files without declaring a
> Breaks+Replaces relation.
> 
> See policy 7.6 at
> https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

While it's true there's a bug, and I will fix that, I do not
understand why piuparts is installing python3-cliapp. That doesn't
seem like an obvious thing to do. The python3 version of the package
did not exist in stretch, and upgrading the python2 version from
stretch to buster seems to work just fine: I just tested that manually
in a chroot.

From the piuparts log I see that it is explicitly installing the
python3 version after upgrading to buster.

(Also, the advice to use Replaces+Breaks is just wrong for this
package. The bug is that the same file is in both the python2 and
python3 versions of the package. The correct solution is to have it in
at most one package. I will be making that fix eventually.)

-- 
I want to build worthwhile things that might last. --joeyh


signature.asc
Description: PGP signature

Bug#890628: vmdb2: Test fail with ImportError: No module named yarnutils

[Lars Wirzenius]

On Fri, 2018-02-16 at 23:19 +0100, Benjamin Drung wrote:
> Standard error from shell command:
> Traceback (most recent call last):
>   File "/tmp/tmpWTVTHk", line 7, in 
> from yarnutils import *
> ImportError: No module named yarnutils

I seem to have failed to upload to Debian a version of cmdtest with
yarnutils. I will fix this and add a versioned dependency on it to
vmdb2. Thanks for reporting.



signature.asc
Description: This is a digitally signed message part

Bug#852882: python-cliapp: FTBFS: Test failures

[Lars Wirzenius]

Thanks for the bug report, and for doing rebuild tests.

On Sat, Jan 28, 2017 at 09:27:24AM +0100, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
> 
> Relevant part (hopefully):
> > fi
> > * Module cliapp.app
> > C:346,30: Consider iterating the dictionary directly instead of calling 
> > .keys() (consider-iterating-dictionary)
> > C:364,30: Consider iterating the dictionary directly instead of calling 
> > .keys() (consider-iterating-dictionary)

These are errors from pylint. So what's happened is that pylint got
updated after my previous upload. When I uploaded the current version,
the version of pylint at that time didn't have these checks, and so
everything went fine. With the newer pylint, a rebuild fails.

I'll upload a new verison of python-cliapp once I'm back home from
travels, which will fix the code. At this stage of the Debian release,
I don't think pylint will change again, so I'll allow the tests to
still run pylint.

Or someone else can do an NMU to disable the pylint test, if they want
to fix the bug faster. I'm on the LowThresholdNmu list so you can just
do the upload.

-- 
I want to build worthwhile things that might last. --joeyh


signature.asc
Description: PGP signature

Bug#796950: NameError: global name 're' is not defined

[Lars Wirzenius]

On Tue, Aug 25, 2015 at 10:31:59PM -0700, Diane Trout wrote:
> packages/obnamlib/plugins/exclude_pathnames_plugin.py", line 97, in
> compile_regexps
> except re.error as e:
> NameError: global name 're' is not defined

Thank you, this is now fixed in git and the fix will be included in
the next upload to Debian. Unfortunately, I had fixed it before I got
to your patch, so I didn't apply yours. However, I've added a credit
in the NEWS file for you.

-- 
sic transit disci mundi, ergo obnam

Bug#770104: does seivot work on stable?

[Lars Wirzenius]

On Sun, Nov 23, 2014 at 05:00:01PM +0100, Holger Levsen wrote:
> Hi Lars, Antoine,
> 
> does seivot work on stable or should it be removed there as well? If it works 
> this bug should be tagged "sid"...

Seivot should work acceptably on stable. The bug's been closed by now,
so I don't think tagging's relevant anymore, but I'll keep the tagging
in mind for next time. Thanks!

-- 
http://gtdfh.branchable.com/ -- GTD for hackers
http://obnam.org/ -- HAVE YOU BACKED UP TODAY?


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

Bug#770104: seivot completely fails with "cannot run genbackupdata: No such file or directory"

[Lars Wirzenius]

On Tue, Nov 18, 2014 at 04:50:34PM -0500, Antoine Beaupré wrote:
> It seems there's a Depends on genbackupdata that is missing...

Yes, to say the least, and there seems to be other problems. seivot
has bit-rotted badly enough that it probably shouldn't be in Debian
anymore. I shall request it to be removed.

-- 
http://gtdfh.branchable.com/ -- GTD for hackers
http://obnam.org/ -- HAVE YOU BACKED UP TODAY?


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

Bug#741711: closing 741711

[Lars Wirzenius]

close 741711 
thanks

This was fixed by uploading the missing dependency. The BTS doesn't
like a bug being found and fixed in the same version, so I'm just
closing this now. Sorry for the confusion.

-- 
http://www.cafepress.com/trunktees -- geeky funny T-shirts
http://gtdfh.branchable.com/ -- GTD for hackers


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

Bug#741711: Unsatisfied dependencies on amd64/i386

[Lars Wirzenius]

On Sun, Mar 16, 2014 at 03:22:02AM +0100, Michael Biebl wrote:
> Package: obnam
> Version: 1.7-1
> Severity: serious
> 
> obnam depends on python-tracing (>= 0.8~) [amd64, i386] but that version
> is not available in unstable.
> Looks like a tainted build environment.

Uploading that version now. Thanks!

-- 
http://www.cafepress.com/trunktees -- geeky funny T-shirts
http://gtdfh.branchable.com/ -- GTD for hackers


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

Bug#735809: obnam: FTBFS: Tests failed

[Lars Wirzenius]

On Fri, Jan 17, 2014 at 08:12:28PM +0100, David Suárez wrote:
> > FAILURE: test_lgetxattr (vfs_local_tests.XAttrTests)
> > Traceback (most recent call last):
> >   File "./obnamlib/vfs_local_tests.py", line 74, in test_lgetxattr
> > self.assertEqual(_obnam.lgetxattr(self.filename, "user.hello"), "world")
> > AssertionError: 95 != 'world'
> > 
> > FAILURE: test_lsetxattr (vfs_local_tests.XAttrTests)
> > Traceback (most recent call last):
> >   File "./obnamlib/vfs_local_tests.py", line 69, in test_lsetxattr
> > ["user.hello", "user.key"])
> > AssertionError: Lists differ: [''] != ['user.hello', 'user.key']

Right, this is because the filesystem used by the builds for $TMPDIR
doesn't support user xattrs. I've fixed the code to skip these tests
in that circumstance.

Thank you for reporting this!

-- 
http://www.cafepress.com/trunktees -- geeky funny T-shirts
http://gtdfh.branchable.com/ -- GTD for hackers


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

Bug#680670: obnam: add_key doesn't encrypt symmetric key with new key

[Lars Wirzenius]

Hi, Mika,

my apologies for responding to this so slowly. I've been very busy
at work.

You are correct that the symmetric key should be re-encrypted when
a new key is added. It should also be re-encrypted when a key is
removed. Your analysis of the situation was spot-on. I didn't use
your patch directly, since I needed to re-encrypt in two places,
and that required a slightly different approach to the code. I've
fixed this now in bzr, and it will be included in the next release,
hopefully soon.

Thank you for your help.

-- 
I wrote a book on personal productivity: http://gtdfh.branchable.com/


signature.asc
Description: Digital signature

Bug#674834: FTBFS: test convert5to6 fails on FS w/o nanosecond resolution

[Lars Wirzenius]

On Mon, May 28, 2012 at 06:28:40AM +0200, Sven Hartge wrote:
> This took some time for me to debug since I first thought this was
> cowbuilders fault, but by comparing my build system to a different one
> I discovered the lack of support for nanosecond timestamps because it
> still uses ext3.

Thanks for reporting this. I already have code to deal with
this when the backup/restore happens over sftp, so I'll change things
so that happens when using filesystems that don't have reasonable time
stamps. I'll fix this for the next upload.

-- 
All my predictions will turn out to be false


signature.asc
Description: Digital signature

Bug#674832: FTBFS: xattr test fails if /tmp on tmpfs

[Lars Wirzenius]

On Mon, May 28, 2012 at 05:46:31AM +0200, Sven Hartge wrote:
> I had to move the tmp-dir to a different directory using $TMP and $TMPDIR
> to be able to complete the build.

Ah, yes. I need to change the test so it only runs if normal users can use
extended attributes. Thanks for the report, I'll fix that in the next upload.

-- 
All my predictions will turn out to be false


signature.asc
Description: Digital signature

Bug#641114: Soundconverter terminates at startup: TypeError: could not parse URI

[Lars Wirzenius]

I don't seem to be able to reproduce this. Does it still happen in
wheezy or sid with 1.5.4-1, recently uploaded? If so, could you
attach the /usr/share/soundconverter/soundconverter-logo.svg file
to the bug report, please? And, if possible, and strace of trying
to launch soundconverter? (Use the command "strace -o soundconverter.strace 
soundconverter" on the command line, then attach the soundconverter.strace
file to the bug report.)

Thanks.

-- 
Freedom-based blog/wiki/web hosting: http://www.branchable.com/


signature.asc
Description: Digital signature

Bug#496967: general: System completely blocks any input

[Lars Wirzenius]

pe, 2008-08-29 kello 19:51 +0200, Frank Küster kirjoitti:
> Any ideas how I can start debugging this?

My first suspicion would be about the hardware. You could run memtest86+
for at least 12 hours or until the first error.

Another idea: you could test the system with another version of Debian,
or with Ubuntu, Knoppix, or another live CD, and see if you can
reproduce the problem with that.





--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#497056: lsb-base: /lib/lsb/init-functions NON-DSFG Licence ?

[Lars Wirzenius]

pe, 2008-08-29 kello 11:20 -0500, William Pitcock kirjoitti:
> This is DFSG-free, and meets both requirements.

Since I agree with William, I'm closing the bug. If Jari disagrees,
he'll let us know.





-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#497056: lsb-base: /lib/lsb/init-functions NON-DSFG Licence ?

[Lars Wirzenius]

pe, 2008-08-29 kello 18:30 +0300, root kirjoitti:
> Please investigate if files included in lsb-base conform to DFSG. A lincense
> change to GPL would be better suited for Debian.

In what way do you think the lsb-base license does not conform to the
DFSG?

> Policy / 2.1. The Debian Free Software Guidelines:
> 
>  ...
>  Derived Works
>   The license must allow modifications and derived works, and must
>   allow them to be distributed under the same terms as the license
>   of the original software.

Derived works and distribution of them are allowed, as far as I can see.

>  Integrity of The Author's Source Code

This does not seem to be a problem, either.

I am missing something.





-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#493781: Can a package modify slapd.conf in its maintainer script?

[Lars Wirzenius]

su, 2008-08-10 kello 19:34 +0200, Fabio Tranchitella kirjoitti:
> Considering that slapd.conf is not (anymore) a conffile, in my opinion this
> behaviour is not forbidden from the Debian policy and thus the bug report
> could be closed without any change to the phamm-ldap package.
> 
> Of course, having an official way from the slapd package to add new schemas
> would be wonderful, but until this feature is added I think that this is
> the only possibility to automatically include a new schema in slapd.conf.

The policy (10.7.4, "Sharing configuration files"): 

The owning package should also provide a program that the other
packages may use to modify the configuration file.

The related packages must use the provided program to make any
desired modifications to the configuration file.

If I read that correctly, slapd should (but is not required to) provide
a program for programmatically modifying slapd.conf. All other packages
must, without exception, use that program. It seems that slapd does not
provide the program. My conclusion is that other package must not modify
slapd.conf at all in that case. (It does not matter whether slapd.conf
is a conffile or merely a configuration file.)

The best way forward is to write the slapd.conf modification program, or
modify slapd to support a slapd.conf.d directory in addition to the flat
file.





-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#442473: deluge-torrent: missing dependency on python-dbus

[Lars Wirzenius]

Package: deluge-torrent
Version: 0.5.5-1
Severity: serious
Justification: violates policy 3.5 "must specify the dependency"

I removed python-dbus from my system (since nothing depended on it), and
deluge-torrent stopped working. I installed it back (no other changes)
and it started working again .

  [EMAIL PROTECTED] deluge 
  Traceback (most recent call last):
File "/usr/bin/deluge", line 45, in ?
  import deluge._dbus as dbus
File "/var/lib/python-support/python2.4/deluge/_dbus.py", line 32, in ?
  from dbus import Interface, SessionBus, version
  ImportError: No module named dbus

  [EMAIL PROTECTED] dpkg --status deluge-torrent | grep dbus
  [status 1]
  [EMAIL PROTECTED] 

Fix should, of course, be very easy. :)

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

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

Versions of packages deluge-torrent depends on:
ii  libboost-date-time1.34. 1.34.1-2 set of date-time libraries based o
ii  libboost-filesystem1.34 1.34.1-2 filesystem operations (portable pa
ii  libboost-thread1.34.1   1.34.1-2 portable C++ multi-threading
ii  libc6   2.6.1-3  GNU C Library: Shared libraries
ii  libgcc1 1:4.2.1-5GCC support library
ii  libssl0.9.8 0.9.8e-8 SSL shared libraries
ii  libstdc++6  4.2.1-5  The GNU Standard C++ Library v3
ii  notification-daemon 0.3.7-1  a daemon that displays passive pop
ii  python  2.4.4-6  An interactive high-level object-o
ii  python-glade2   2.10.6-1 GTK+ bindings: Glade support
ii  python-gtk2 2.10.6-1 Python bindings for the GTK+ widge
ii  python-notify   0.1.1-1  Python bindings for libnotify
ii  python-support  0.6.4automated rebuilding support for p
ii  python-xdg  0.15-1.1 A python library to access freedes
ii  zlib1g  1:1.2.3.3.dfsg-5 compression library - runtime

deluge-torrent recommends no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#392940: NMU diff for RC bug

[Lars Wirzenius]

Attached is the diff for the NMU I intend to upload in a few minutes. It
works around the home-less build problem by setting HOME to a temporary
directory while waf is run. Upstreams suggestion of using WAF_HOME
didn't work, possibly the waf used by the package is too old.

-- 
Debian is a beast that speaks with many voices -- Richard Braakman
diff -ru kdissert-1.0.6.c.buggy/debian/changelog kdissert-1.0.6.c/debian/changelog
--- kdissert-1.0.6.c.buggy/debian/changelog	2007-01-04 23:41:28.0 +0200
+++ kdissert-1.0.6.c/debian/changelog	2007-01-04 23:42:08.0 +0200
@@ -1,3 +1,12 @@
+kdissert (1.0.6.c-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * debian/rules: Set HOME to a temporary directory for the build phase,
+so that waf works even when the read $HOME doesn't exist. 
+(Closes: #392940)
+
+ -- Lars Wirzenius <[EMAIL PROTECTED]>  Thu,  4 Jan 2007 23:35:09 +0200
+
 kdissert (1.0.6.c-1) unstable; urgency=low
 
   * New upstream release (really called "1.0.6c", but dpkg version ordering
diff -ru kdissert-1.0.6.c.buggy/debian/rules kdissert-1.0.6.c/debian/rules
--- kdissert-1.0.6.c.buggy/debian/rules	2007-01-04 23:41:28.0 +0200
+++ kdissert-1.0.6.c/debian/rules	2007-01-05 00:41:03.0 +0200
@@ -11,8 +11,9 @@
 
 common-build-arch:: build-stamp debian/kdissert.xpm debian/kdissert-16.xpm
 build-stamp:
-	$(WAF) configure --prefix=/usr --qtdir=/usr/share/qt3 --want-rpath=0
-	$(WAF)
+	mkdir -p debian/waftmp
+	env HOME=debian/waftmp $(WAF) configure --prefix=/usr --qtdir=/usr/share/qt3 --want-rpath=0
+	env HOME=debian/waftmp $(WAF)
 	touch $@
 
 
@@ -24,11 +25,12 @@
 
 
 common-install-arch::
-	$(WAF) install --destdir=$(DEB_DESTDIR)
+	env HOME=debian/waftmp $(WAF) install --destdir=$(DEB_DESTDIR)
 	rm -r $(DEB_DESTDIR)/usr/share/applnk
 
 
 clean::
 	rm -f build-stamp
-	-$(WAF) distclean
+	-env HOME=debian/waftmp $(WAF) distclean
 	rm -f debian/kdissert.xpm debian/kdissert-16.xpm
+	rm -rf debian/waftmp

Bug#395258: python-licosmamo is unsuitable for release, remove from etch

[Lars Wirzenius]

Package: python-licosmamo
Severity: serious
Justification: in the maintainer's opinion

I'm the maintainer of python-licosmamo. I've asked for it to be removed
(#390735) but since the removal request takes a while to be processed,
I'm filing this bug to ask for its removal from etch (which the release
managers can do quickly), so that it doesn't get included in the release
by mistake.

-- 
Programming should be fun, otherwise you're doing something wrong.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#392175: FTBFS: cannot find Python headers

[Lars Wirzenius]

On ti, 2006-10-10 at 17:04 +0100, Martin Michlmayr wrote:
> Package: lodju
> Version: 2.2-1
> Severity: serious
> 
> > Automatic build of lodju_2.2-1 on coconut0 by sbuild/ia64 0.49

I've asked for lodju to be removed from Debian (#390735), so I fear this
bug won't be fixed. Also, no-one please spend time fixing it, since the
package should be removed.

-- 
Fundamental truth #2: Attitude is usually more important than skills.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#387790: fillets-ng-data: broken symlinks

[Lars Wirzenius]

pe, 2006-09-22 kello 16:34 +0200, Alexander Schmehl kirjoitti:
> * Lars Wirzenius <[EMAIL PROTECTED]> [060916 20:01]:
> > Severity: minor
> 
> Hmmm... shouldn't broken symlinks due to missing dependencies be release
> critical?  Most likely they will render the package unusable, won't
> they?

Possibly they should be RC. However, I think that a package like
fillets-ng-data, which is useless without another package anyway, and
that other package (hopefully) provides the link targets, might as well
just get a non-RC bug. Of course, partly the problem is that I have
little time and there are so many packages...

Anyway, severity isn't relevant if the bug gets fixed. :)

-- 
(def (reverse items) (accumulate (fn (so-far x) (cons x so-far)) nil
items))



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#376501: Fix for "pxe: Trips over stray pid file."

[Lars Wirzenius]

mipsisa64sr71kel-* \
| mipstx39-* | mipstx39el-* \
| mmix-* \
-   | ms1-* \
+   | mt-* \
| msp430-* \
+   | nios-* | nios2-* \
| none-* | np1-* | ns16k-* | ns32k-* \
| orion-* \
| pdp10-* | pdp11-* | pj-* | pjl-* | pn-* | power-* \
@@ -696,6 +710,9 @@
basic_machine=i386-pc
os=-msdos
;;
+   ms1-*)
+   basic_machine=`echo $basic_machine | sed -e 's/ms1-/mt-/'`
+   ;;
mvs)
basic_machine=i370-ibm
os=-mvs
@@ -803,6 +820,12 @@
pc532 | pc532-*)
basic_machine=ns32k-pc532
;;
+   pc98)
+   basic_machine=i386-pc
+   ;;
+   pc98-*)
+   basic_machine=i386-`echo $basic_machine | sed 's/^[^-]*-//'`
+   ;;
pentium | p5 | k5 | k6 | nexgen | viac3)
basic_machine=i586-pc
;;
@@ -858,6 +881,10 @@
pw32)
basic_machine=i586-unknown
os=-pw32
+   ;;
+   rdos)
+   basic_machine=i386-pc
+   os=-rdos
;;
rom68k)
basic_machine=m68k-rom68k
@@ -1174,21 +1201,23 @@
  | -aos* \
  | -nindy* | -vxsim* | -vxworks* | -ebmon* | -hms* | -mvs* \
  | -clix* | -riscos* | -uniplus* | -iris* | -rtu* | -xenix* \
- | -hiux* | -386bsd* | -knetbsd* | -mirbsd* | -netbsd* | -openbsd* 
\
+ | -hiux* | -386bsd* | -knetbsd* | -mirbsd* | -netbsd* \
+ | -openbsd* | -solidbsd* \
  | -ekkobsd* | -kfreebsd* | -freebsd* | -riscix* | -lynxos* \
  | -bosx* | -nextstep* | -cxux* | -aout* | -elf* | -oabi* \
  | -ptx* | -coff* | -ecoff* | -winnt* | -domain* | -vsta* \
  | -udi* | -eabi* | -lites* | -ieee* | -go32* | -aux* \
  | -chorusos* | -chorusrdb* \
  | -cygwin* | -pe* | -psos* | -moss* | -proelf* | -rtems* \
- | -mingw32* | -linux-gnu* | -linux-uclibc* | -uxpv* | -beos* | 
-mpeix* | -udk* \
+ | -mingw32* | -linux-gnu* | -linux-newlib* | -linux-uclibc* \
+ | -uxpv* | -beos* | -mpeix* | -udk* \
  | -interix* | -uwin* | -mks* | -rhapsody* | -darwin* | -opened* \
  | -openstep* | -oskit* | -conix* | -pw32* | -nonstopux* \
  | -storm-chaos* | -tops10* | -tenex* | -tops20* | -its* \
  | -os2* | -vos* | -palmos* | -uclinux* | -nucleus* \
  | -morphos* | -superux* | -rtmk* | -rtmk-nova* | -windiss* \
  | -powermax* | -dnix* | -nx6 | -nx7 | -sei* | -dragonfly* \
- | -skyos* | -haiku*)
+ | -skyos* | -haiku* | -rdos*)
# Remember, each alternative MUST END IN *, to match a version number.
;;
-qnx*)

=== modified file 'debian/changelog'
--- debian/changelog
+++ debian/changelog
@@ -1,3 +1,27 @@
+pxe (1.4.2-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/postinst: Created. In addition to the usual stuff added by
+debhelper, we now create a Debian-pxe user.
+  * debian/prerm: Created. Handle a failed upgrade from a previous
+version by manually killing the daemon and removing the pid file.
+  * debian/postrm: Remove /var/run/pxe, /var/run/pxe/pxe.pid, and
+/var/run/pxe.pid.
+  * debian/init.d: Create /var/run/pxe before starting the daemon,
+and chown it to the Debian-pxe user. Also, wait for the pid file
+to disappear when stopping (or restarting), instead of blindly
+assuming that one second is enough. Further, allow start-stop-daemon
+to not do anything (--oknodo) when doing "start", "stop", or the
+stopping part of "restart".
+  * debian/rules: Tweak (with sed, since ./configure has no option) the
+LOCKFILE setting in autoconf.h to /var/run/pxe/pxe.pid, instead of
+the old value of /var/run/pxe.pid.
+  * Closes: #376501.
+  * debian/control: Updates Standards-Version to 3.7.2. No other changes
+required.
+
+ -- Lars Wirzenius <[EMAIL PROTECTED]>  Sat, 12 Aug 2006 23:25:49 +0300
+
 pxe (1.4.2-3) unstable; urgency=low
 
   * pxe.cc: Added patch to fix segfaulting (Closes: #330851).

=== modified file 'debian/control'
--- debian/control  
+++ debian/control  
@@ -3,12 +3,12 @@
 Priority: optional
 Maintainer: Daniel Baumann <[EMAIL PROTECTED]>
 Build-Depends: debhelper (>= 4.0.0), docbook-to-man
-Standards-Version: 3.6.2
+Standards-Version: 3.7.2
 
 Package: pxe
 Section: net
 Architecture: any
-Depends: ${shlibs:Depends}
+Depends: ${shlibs:Depends}, adduser
 Recommends: dhcp3-server, atftpd, syslinux
 Description: free PX daemon
  PXE is a specification to boot PCs from the net. Apart from BOOTP or DHCP for

=== modified file 'debian/init.d'
--- debian/init.d   
+++

Bug#382612: bzr: '~' in Version number violates policy 5.6.12

[Lars Wirzenius]

severity normal
thanks

la, 2006-08-12 kello 10:41 +0200, Jakob Bohm kirjoitti:
> Policy section 5.6.12 lists the permitted characters in package
> version numbers, '~' is NOT on the list, and until less than 14
> days ago all packages in the archive were compliant with that
> rule.  I know for certain that one of my own mirroring scripts
> will refuse to accept '~' in package file names, and others
> might do the same.

This is changing, see
http://lists.debian.org/debian-devel-announce/2006/08/msg6.html and
replies on debian-devel and debian-policy. Tilde is now de facto
allowed, and policy is going to be updated soon. When things affected by
policy change, it is common for policy updates to lag a bit, since the
policy is supposed to document existing practice. Before there is
existing practice, a policy change is (often) premature.

-- 
It's 1978! Things should be round by now -- Michael Kelso (That 70's
show)



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#378244: Bug #378244: enemies-of-carlotta: Mail with UTF-8 headers produces data-loss

[Lars Wirzenius]

tags 378244 unreproducible
thanks

I seem to not have noticed this bug earlier, oops. My apologies. (In
case it was due to my spam filter, I've now told my procmailrc to bypass
tha spam filter for anything with this bug number in the subject.)

> receiving a mail with a utf-8 header causes eoc to loose the mail.
> Unfortunatly I don't have a copy of the mail, but I have the python
> traceback:

I can't seem to be able to reproduce this, either with encoded or unencoded
UTF-8 text in the message headers, and not even with broken UTF-8.

However, as a quick workaround, you can add "pristine-headers = yes" to the 
list's config file, which should prevent the problematic code path from being 
entered. I'm reluctant to upload an untested fix until I can reproduce the 
problem (meaning: I can't be sure that my fix actually is a fix...).

If this happens again, could you do your best to retain the problematic 
mail and send me the relevant parts? Possibly using a procmail rule that
saves all incoming mail, or something similar, depending on your setup?

-- 
Fundamental truth #1: Complexity is the enemy.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#361377: xfingerd: missing dependency on inetd?

[Lars Wirzenius]

ke, 2006-06-14 kello 16:54 +0200, KELEMEN Peter kirjoitti:
> * Lars Wirzenius ([EMAIL PROTECTED]) [20060408 13:22]:
> 
> > [...] c) what happens if xinetd or some other inetd
> > implementation is installed instead of inetd?
> 
> Dunno.  Is there a generic framework for handling inetd/xinetd?

I don't know, but if there isn't, there seems to be a need for that.
Could you bring it up on debian-devel?

-- 
Päivät on kuin piikkilankaa, ne murjoo mua.

Bug#368289: Bug#364629: NMU broke configure script in s390 buildd

[Lars Wirzenius]

ma, 2006-05-22 kello 18:37 -0500, Gunnar Wolf kirjoitti:
> Thanks for taking care of my poor little package... I'm sure you
> understand why I haven't looked at it much lately :-( Anyway, it seems
> the patch you NMUed created some problems - As I'm still stuck with
> Debconf for a bit, and then have to catch up with at least one month
> of job I put away, could you take a dive into this again?

Yeah, I noticed that. I have no idea what the problem is -- I did build
the package with pbuilder before I uploaded it, so it should build
cleanly. Unfortunately, I'm travelling for another couple of weeks, so I
won't be able to work on this. Hopefully someone else notices the
problem and has time to fix things. My apologizes for messing things up.

-- 
There's a reason why "release manager" is abbreviated "rm".



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#366005: Debian package textopo maintainer address

[Lars Wirzenius]

Greetings, Steffen Moeller.

In Debian bug #366005
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=366005) it is claimed
that the address Steffen Moeller <[EMAIL PROTECTED]> does not
work, and indeed there is no DNS record for prz, but there is one for
pzr.uni-rostock.de. Is that the correct address? If so, would you like
to fix the bug by uploading a new package version?

-- 
I am a werehuman.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#364629: NMU diff

[Lars Wirzenius]

I have applied the patch from Roberto Sanchez and done an NMU of the
package. Attached is the exact diff; it differs from Roberto's only in
the changelog.

-- 
Latest nerd movie: Once were hackers
diff -u xosview-1.8.2/config/configure.in xosview-1.8.2/config/configure.in
--- xosview-1.8.2/config/configure.in
+++ xosview-1.8.2/config/configure.in
@@ -10,6 +10,74 @@
 ICE_CXX_LONG_LONG
 AC_PATH_X
 CXXFLAGS="$CXXFLAGS -I$x_includes"
+
+dnl
+dnl Added a proper check for the snprintf() function
+dnl
+
+AC_DEFUN([AC_FUNC_SNPRINTF],
+[AC_CHECK_FUNCS(snprintf vsnprintf)
+AC_MSG_CHECKING(for working snprintf)
+AC_CACHE_VAL(ac_cv_have_working_snprintf,
+[AC_TRY_RUN(
+[#include 
+
+int main(void)
+{
+char bufs[5] = { 'x', 'x', 'x', '\0', '\0' };
+char bufd[5] = { 'x', 'x', 'x', '\0', '\0' };
+int i;
+i = snprintf (bufs, 2, "%s", "111");
+if (strcmp (bufs, "1")) exit (1);
+if (i != 3) exit (1);
+i = snprintf (bufd, 2, "%d", 111);
+if (strcmp (bufd, "1")) exit (1);
+if (i != 3) exit (1);
+exit(0);
+}], ac_cv_have_working_snprintf=yes, ac_cv_have_working_snprintf=no, ac_cv_have_working_snprintf=cross)])
+AC_MSG_RESULT([$ac_cv_have_working_snprintf])
+AC_MSG_CHECKING(for working vsnprintf)
+AC_CACHE_VAL(ac_cv_have_working_vsnprintf,
+[AC_TRY_RUN(
+[#include 
+#include 
+
+int my_vsnprintf (char *buf, const char *tmpl, ...)
+{
+int i;
+va_list args;
+va_start (args, tmpl);
+i = vsnprintf (buf, 2, tmpl, args);
+va_end (args);
+return i;
+}
+
+int main(void)
+{
+char bufs[5] = { 'x', 'x', 'x', '\0', '\0' };
+char bufd[5] = { 'x', 'x', 'x', '\0', '\0' };
+int i;
+i = my_vsnprintf (bufs, "%s", "111");
+if (strcmp (bufs, "1")) exit (1);
+if (i != 3) exit (1);
+i = my_vsnprintf (bufd, "%d", 111);
+if (strcmp (bufd, "1")) exit (1);
+if (i != 3) exit (1);
+exit(0);
+}], ac_cv_have_working_vsnprintf=yes, ac_cv_have_working_vsnprintf=no, ac_cv_have_working_vsnprintf=cross)])
+AC_MSG_RESULT([$ac_cv_have_working_vsnprintf])
+if test x$ac_cv_have_working_snprintf$ac_cv_have_working_vsnprintf != "xyesyes"; then
+  AC_LIBOBJ(snprintf)
+  AC_MSG_WARN([Replacing missing/broken (v)snprintf() with version from http://www.ijs.si/software/snprintf/.])
+  AC_DEFINE(PREFER_PORTABLE_SNPRINTF, 1, "enable replacement (v)snprintf if system (v)snprintf is broken")
+fi])
+
+AC_FUNC_SNPRINTF
+
+dnl
+dnl End snprintf() check
+dnl
+
 case $host_os in
 linux*)
   LIBS="-L$x_libraries $LIBS"
diff -u xosview-1.8.2/debian/changelog xosview-1.8.2/debian/changelog
--- xosview-1.8.2/debian/changelog
+++ xosview-1.8.2/debian/changelog
@@ -1,3 +1,13 @@
+xosview (1.8.2-8.1) unstable; urgency=low
+
+  * Non-maintainer upload by Lars Wirzenius using patch by Roberto 
+C. Sanchez <[EMAIL PROTECTED]> from the bug tracking system.
+  * Added portable check for snprintf to configure.in using code from
+file:///usr/share/doc/autoconf-archive/htmldoc/ac_func_snprintf.html.
+(Closes: #364629)
+
+ -- Lars Wirzenius <[EMAIL PROTECTED]>  Sat, 21 May 2006 07:09:00 +0300
+
 xosview (1.8.2-8) unstable; urgency=low
 
   * Substituted build-dependency on xlibs-dev for its component packages

Bug#366827: NMU diff

[Lars Wirzenius]

Attached is the diff for the NMU I'm about to do for trac to fix bug
#366827 (trac: FTBFS: Clean rule fails on clean package).

-- 
When in doubt, use brute force.
diff -u trac-0.9.5/debian/control trac-0.9.5/debian/control
--- trac-0.9.5/debian/control
+++ trac-0.9.5/debian/control
@@ -1,7 +1,7 @@
 Source: trac
 Section: web
 Priority: optional
-Build-Depends-Indep: debhelper (>= 4.0.0), python2.3-dev, cdbs, python
+Build-Depends-Indep: debhelper (>= 4.1.0), python2.3-dev, cdbs, python
 Maintainer: Jesus Climent <[EMAIL PROTECTED]>
 Uploaders: Otavio Salvador <[EMAIL PROTECTED]>
 Standards-Version: 3.6.2
diff -u trac-0.9.5/debian/changelog trac-0.9.5/debian/changelog
--- trac-0.9.5/debian/changelog
+++ trac-0.9.5/debian/changelog
@@ -1,3 +1,14 @@
+trac (0.9.5-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Fix debian/rules clean target so it doesn't break by trying to remove
+files even when they don't exist. Closes: #366827.
+  * Updated build dependency for debhelper to be at leat 4.1.0, since that
+is required for cdbs's debhelper.mk to work (according to linda, at
+least).
+
+ -- Lars Wirzenius <[EMAIL PROTECTED]>  Sun, 21 May 2006 07:41:47 +0300
+
 trac (0.9.5-1) unstable; urgency=high
 
   * New upstream release.
diff -u trac-0.9.5/debian/rules trac-0.9.5/debian/rules
--- trac-0.9.5/debian/rules
+++ trac-0.9.5/debian/rules
@@ -7,7 +7,7 @@
 DEB_INSTALL_DOCS_ALL=$(filter-out $(DEB_INSTALL_CHANGELOGS_ALL),$(shell for f in contrib README RELEASE UPGRADE AUTHORS THANKS; do if test -s $(DEB_SRCDIR)/$$f; then echo $(DEB_SRCDIR)/$$f; fi; done))
 
 clean::
-	rm trac/__init__.pyc
+	rm -f trac/__init__.pyc
 
 binary-post-install/trac::
 	chmod 755 debian/trac/usr/lib/python2.3/site-packages/trac/test.py

Bug#358364: Notification of NMU of xml-core

[Lars Wirzenius]

Attached is the patch with which I intend to NMU xml-core in a little
while. The bug has been open for about three weeks now, and the fix is
simple enough. I didn't use Ghe Rivero's patch, but removed all use of
cd (since as far as I can determine, such use is useless). The package
as patched is relatively lintian and linda clean (a few warnings that
are harmelss and will be left for the maintainer to fix), and passes
piuparts testing (except for a warning about /etc/sgml, but that seems
to be due to a dependency, not this package).

=== modified file 'debian/changelog'
--- debian/changelog	
+++ debian/changelog	
@@ -1,3 +1,12 @@
+xml-core (0.09-0.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * debian/xml-core.postrm, debian/xml-core.preinst: Use absolute path
+names for files instead of doing a "cd /foo; mv plim plom; cd -" dance
+(especially since the dance if fragile, too). Closes: #358364.
+
+ -- Lars Wirzenius <[EMAIL PROTECTED]>  Thu, 13 Apr 2006 20:25:34 +
+
 xml-core (0.09) unstable; urgency=low
 
   * schemas/catalog: added official FPI for XML catalog DTD

=== modified file 'debian/xml-core.postrm'
--- debian/xml-core.postrm	
+++ debian/xml-core.postrm	
@@ -16,9 +16,7 @@
 
 ## --
 ## remove /var/lib/xml-core
-cd /var/lib
-rmdir --ignore-fail-on-non-empty xml-core
-cd - >/dev/null
+rmdir --ignore-fail-on-non-empty /var/lib/xml-core
 
 ## --
 ## remove root XML catalog
@@ -27,17 +25,13 @@
 
 ## --
 ## remove /etc/xml
-cd /etc
-rmdir --ignore-fail-on-non-empty xml
-cd - >/dev/null
+rmdir --ignore-fail-on-non-empty /etc/xml
 
 ## --
 ## restore legacy /etc/xml/catalog
 if [ -f /etc/xml/catalog.legacy ]
 then
-cd /etc/xml
-	mv catalog.legacy catalog
-cd - >/dev/null
+	mv /etc/xml/catalog.legacy /etc/xml/catalog
 fi
 
 fi

=== modified file 'debian/xml-core.preinst'
--- debian/xml-core.preinst	
+++ debian/xml-core.preinst	
@@ -34,9 +34,7 @@
 ## preserve legacy /etc/xml/catalog
 if [ -f /etc/xml/catalog ]
 then
-cd /etc/xml
-	mv catalog catalog.legacy
-cd - >/dev/null
+	mv /etc/xml/catalog /etc/xml/catalog.legacy
 fi
 
 fi

Bug#362476: yelp: does not display any help files

[Lars Wirzenius]

You wrote:
> yelp opens with an empty window: below the title "Help Topics" there 
> is nothing more. This happens when starting yelp from Desktop/Help (or F1) 
> as well as when trying to open the help-page of some application.
> (I had the same trouble with version 2.12.2-2)

Hi. This would seem to be the same bug as has been reported earlier and if so, 
it 
should be fixed by upgrading the scrollkeeper package to version 0.3.14-10.1, 
which 
has recently been uploaded to unstable. Could you try upgrading scrollkeeper and
see if that fixes it?




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#352714: scrollkeeper RC bug fixed

[Lars Wirzenius]

package scrollkeeper
tag 352714 fixed
tag 352628 fixed
tag 345563 fixed
thanks

Below is the change log entry that should have been in the binary
(version 0.3.14-10.1) that I uploaded, but because I forgot to rebuild
the binary package after changing the changelog (but after testing that
the fix actually fixes the bug) it wasn't included and also these three
bugs weren't closed. I'm marking them "fixed" with this message.

+scrollkeeper (0.3.14-10.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+Note that although #352714 against scrollkeeper is of severity
+"normal", #352628 and #345563 against yelp are release critical,
+which is justification for the NMU.
+  * Applied patch, with a modification to surround the addition with
+parentheses, from
+http://librarian.launchpad.net/1510562/scrollkeeper.patch (see also
+https://launchpad.net/distros/ubuntu/+source/yelp/+bug/18434). This
+fixes a memory allocation that is one array element too small. Note
+that the original patch only adds one byte, but we need enough for
+one char**. As it happens, adding just one byte will work, since
+malloc rounds up to the next suitable multiple of word size (or
+even larger unit), but it is not correct to rely on this.
+Closes: #352714, #352628, #345563.
+
+ -- Lars Wirzenius <[EMAIL PROTECTED]>  Sat,  8 Apr 2006 18:47:42 +
+

-- 
Comedy evolution: survival of the wittiest



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#345563: Notification of NMU

[Lars Wirzenius]

reassign 345563 scrollkeeper
reassign 352628 scrollkeeper
severity 352714 grave
merge 345563 352628 352714
thanks

There are two release critical bugs against yelp (352628 and 345563).
Based on comments to those bugs they are really bugs in scrollkeeper,
and I've verified this by testing. Thus I'm reassigning them. The same
bug is already reported as a normal-severity bug against scrollkeeper,
so I'm raising its severity and merging.

The bug logs also include a reference to a patch that fixes the problem.
I've verified the fix, both by code review and testing, and am including
the patch with which I intend to NMU to fix the bug.

=== added file 'debian/patches/08_libs_i18n_c_malloc_bug.diff'
--- /dev/null	
+++ debian/patches/08_libs_i18n_c_malloc_bug.diff	
@@ -0,0 +1,11 @@
+--- scrollkeeper-0.3.14.untouched/libs/i18n.c	2003-11-09 23:05:36.0 +
 scrollkeeper-0.3.14/libs/i18n.c	2006-04-08 18:48:09.0 +
+@@ -206,7 +206,7 @@
+ 		count++;
+ 	}
+ 	
+-	tab = (char ***)malloc(sizeof(char **) * count);
++	tab = (char ***)malloc(sizeof(char **) * (count + 1));
+ 	
+ 	str = strdup(lang);
+ 	check_ptr(str, "");

=== modified file 'debian/changelog'
--- debian/changelog	
+++ debian/changelog	
@@ -1,3 +1,22 @@
+scrollkeeper (0.3.14-10.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+Note that although #352714 against scrollkeeper is of severity
+"normal", #352628 and #345563 against yelp are release critical,
+which is justification for the NMU.
+  * Applied patch, with a modification to surround the addition with
+parentheses, from
+http://librarian.launchpad.net/1510562/scrollkeeper.patch (see also
+https://launchpad.net/distros/ubuntu/+source/yelp/+bug/18434). This
+fixes a memory allocation that is one array element too small. Note
+that the original patch only adds one byte, but we need enough for
+one char**. As it happens, adding just one byte will work, since
+malloc rounds up to the next suitable multiple of word size (or
+even larger unit), but it is not correct to rely on this.
+Closes: #352714, #352628, #345563.
+
+ -- Lars Wirzenius <[EMAIL PROTECTED]>  Sat,  8 Apr 2006 18:47:42 +
+
 scrollkeeper (0.3.14-10) unstable; urgency=medium
 
   * [debian/patches/00_updated_translations.diff] Reordered from

Bug#355045: Patch for 355045 (xqf fails to start)

[Lars Wirzenius]

package xqf
tag 355045 + patch
thanks

Attached is a patch to fix this release critical xqf bug. With this
patch, xqf again starts up properly (as far as I can see, at least).
Since xqf is not currently in testing, I won't bother to do a
non-maintainer upload.

The problem as far as I can see is that the code tries to load XPM
pictures into the executable, instead of having them as files, and then
tries weird dlopen magic to get the in-executable XPM files. Magic is
not as reliable as technology, and once again it fails. So the first
change was to install the XPM files into /usr/share/xqf.

This was not enough, however, since the source refers to the files with
the wrong names: using _ instead - in filenames. The second change was
to fix that.

I hope this is useful. Happy hacking.

-- 
Teaching: the proof is in the doing.
diff -ru xqf-1.0.4/debian/changelog xqf-fixed/debian/changelog
--- xqf-1.0.4/debian/changelog	2006-04-08 16:57:41.0 +
+++ xqf-fixed/debian/changelog	2006-04-08 16:17:02.0 +
@@ -1,3 +1,10 @@
+xqf (1.0.4-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Foo.
+
+ -- Lars Wirzenius <[EMAIL PROTECTED]>  Sat,  8 Apr 2006 16:16:55 +
+
 xqf (1.0.4-1) unstable; urgency=low
 
   * New upstream release.
diff -ru xqf-1.0.4/debian/rules xqf-fixed/debian/rules
--- xqf-1.0.4/debian/rules	2006-04-08 16:57:41.0 +
+++ xqf-fixed/debian/rules	2006-04-08 16:21:01.0 +
@@ -12,6 +12,7 @@
 
 binary-install/xqf::
 	install -m 644 -p $(CURDIR)/debian/xqf.xpm $(CURDIR)/debian/xqf/usr/share/pixmaps/xqf.xpm
+	install -m 644 -p $(CURDIR)/src/xpm/*.xpm $(CURDIR)/debian/xqf/usr/share/xqf
 
 clean::
 	rm -f config.h
diff -ru xqf-1.0.4/src/loadpixmap.c xqf-fixed/src/loadpixmap.c
--- xqf-1.0.4/src/loadpixmap.c	2005-07-03 17:51:08.0 +
+++ xqf-fixed/src/loadpixmap.c	2006-04-08 16:46:43.0 +
@@ -149,7 +149,7 @@
   g_return_val_if_fail(pix!=NULL,NULL);
 
   found_filename = find_pixmap_file(filename);
-  if(is_suffix(filename, ".xpm")) // try png instead
+  if(!found_filename && is_suffix(filename, ".xpm")) // try png instead
   {
 char* tmp = g_strdup(filename);
 strcpy(tmp+strlen(tmp)-3, "png");
@@ -159,6 +159,7 @@
 
   if(!found_filename)
   {
+#if 0
 // not file on disk maybe xpm compiled into binary
 if(is_suffix(filename, ".xpm"))
 {
@@ -191,6 +192,7 @@
 	pix->pix = gdk_pixmap_colormap_create_from_xpm_d (NULL, colormap, &pix->mask, NULL, xpm);
   }
 }
+#endif
   }
   else if(is_suffix(found_filename, ".xpm"))
   {
diff -ru xqf-1.0.4/src/pixmaps.c xqf-fixed/src/pixmaps.c
--- xqf-1.0.4/src/pixmaps.c	2005-10-07 12:55:15.0 +
+++ xqf-fixed/src/pixmaps.c	2006-04-08 16:55:40.0 +
@@ -327,31 +327,31 @@
   create_pixmap (window, "record.xpm", &record_pix);
 
   create_pixmap (window, "sfilter.xpm", &sfilter_pix);
-  create_pixmap (window, "sfilter_cfg.xpm", &sfilter_cfg_pix);
+  create_pixmap (window, "sfilter-cfg.xpm", &sfilter_cfg_pix);
 
   create_pixmap (window, "pfilter.xpm", &pfilter_pix);
-  create_pixmap (window, "pfilter_cfg.xpm", &pfilter_cfg_pix);
+  create_pixmap (window, "pfilter-cfg.xpm", &pfilter_cfg_pix);
 
   create_pixmap (window, "green_plus.xpm", &gplus_pix);
   create_pixmap (window, "red_minus.xpm", &rminus_pix);
 
-  create_pixmap (window, "man_black.xpm", &man_black_pix);
-  create_pixmap (window, "man_red.xpm", &man_red_pix);
-  create_pixmap (window, "man_yellow.xpm", &man_yellow_pix);
-
-  create_pixmap (window, "group_red.xpm", &group_pix[0]);
-  create_pixmap (window, "group_green.xpm", &group_pix[1]);
-  create_pixmap (window, "group_blue.xpm", &group_pix[2]);
-
-  create_pixmap (window, "buddy_red.xpm", &buddy_pix[1]);
-  create_pixmap (window, "buddy_green.xpm", &buddy_pix[2]);
-  create_pixmap (window, "buddy_blue.xpm", &buddy_pix[4]);
-
-  create_pixmap (window, "server_na.xpm", &server_status[0]);
-  create_pixmap (window, "server_up.xpm", &server_status[1]);
-  create_pixmap (window, "server_down.xpm", &server_status[2]);
-  create_pixmap (window, "server_to.xpm", &server_status[3]);
-  create_pixmap (window, "server_error.xpm", &server_status[4]);
+  create_pixmap (window, "man-black.xpm", &man_black_pix);
+  create_pixmap (window, "man-red.xpm", &man_red_pix);
+  create_pixmap (window, "man-yellow.xpm", &man_yellow_pix);
+
+  create_pixmap (window, "group-red.xpm", &group_pix[0]);
+  create_pixmap (window, "group-green.xpm", &group_pix[1]);
+  create_pixmap (window, "group-blue.xpm"

Bug#361377: xfingerd: missing dependency on inetd?

[Lars Wirzenius]

Package: xfingerd
Version: 0.6-4
Severity: serious
Justification: missing dependency

When testing xfingerd with piuparts, I get the following error:

  Unpacking xfingerd (from .../xfingerd_0.6-4_i386.deb) ...
  Setting up xfingerd (0.6-4) ...
  /var/lib/dpkg/info/xfingerd.postinst: line 8: /etc/init.d/inetd: No
such file
or directory
  dpkg: error processing xfingerd (--configure):
   subprocess post-installation script returned error exit status 127

xfingerd does not depend on inetd, but calls its init.d script directly.
This is wrong because a) it is missing a dependency on inetd, b) you
shouldn't be calling the init.d script directly anyway (see policy
9.3.3.2), and c) what happens if xinetd or some other inetd
implementation is installed instead of inetd?

-- 
Programming should be fun, otherwise you're doing something wrong.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#361372: statd: calls /etc/init.d/inetd directly from postinst

[Lars Wirzenius]

Package: statd
Version: 1.0.1-6.1
Severity: serious
Justification: missing dependency

When testing statd with piuparts, I get the following error:

  Setting up statd (1.0.1-6.1) ...
  /var/lib/dpkg/info/statd.postinst: line 5: /etc/init.d/inetd: No such
file or
directory
  dpkg: error processing statd (--configure):
   subprocess post-installation script returned error exit status 127

The chroot that piuparts builds for testing does not contain the inetd
program, and therefore also doesn't contain the /etc/init.d/inetd
script. This may indicate a missing dependency, but it might be that
calling the init.d script only if it is there is a better fix than
depending on inetd. We have, after all, several inetd implementations in
Debian.

Also, you shouldn't call the init.d script directly, but via
invoke-rc.d. See policy 9.3.3.2.




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#359940: set6x86: no useful files

[Lars Wirzenius]

Package: set6x86
Version: 1.5-12
Severity: grave
Justification: makes the package in question unusable

When testing set6x86 with piuparts, I got the following error:

1m51.7s ERROR: Package purging left files on system:
  /etc/init.d/set6x86
owned by: set6x86
  /etc/rcS.d/S38set6x86

This happens upon upgrade from sarge to etch to sid, and seems to be
because the current sid version does not contain any useful files:

[EMAIL PROTECTED] dpkg
--fsys-tarfile /xl/debian-mirror/pool/main/s/set6x86/set6x86_1.5-12_i386.deb | 
tar tf -
./
./usr/
./usr/share/
./usr/share/doc/
./usr/share/doc/set6x86/
./usr/share/doc/set6x86/examples/
./usr/share/doc/set6x86/examples/rc.cyrix
./usr/share/doc/set6x86/examples/rc.6x86MX
./usr/share/doc/set6x86/CHANGES
./usr/share/doc/set6x86/README
./usr/share/doc/set6x86/Doc-6x86.txt
./usr/share/doc/set6x86/copyright

I guess something went wrong in the conversion to debhelper.

-- 
It's 1978! Things should be round by now -- Michael Kelso (That 70's
show)



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#359936: ifplugd: assumes /etc/udev exists without depending on udev

[Lars Wirzenius]

Package: ifplugd
Version: 0.28-1
Severity: serious
Justification: missing dependency

When testing ifplugd with piuparts, I get the following error:

  Setting up ifplugd (0.28-1) ...
  ln: creating symbolic link `/etc/udev/rules.d/030_ifplugd.rules' to
`../ifplugd.rules': No such file or directory
  dpkg: error processing ifplugd (--configure):
   subprocess post-installation script returned error exit status 1

ifplugd does not depend on udev, which provides the /etc/udev/rules.d
directory, leading to this error situation. Since this situation is
explicitly mentioned in http://release.debian.org/etch_rc_policy.txt as
a release criterion, I'm putting the severity as "serious"; if you
disagree, please downgrade.

-- 
Päivät on kuin piikkilankaa, ne murjoo mua.

Bug#355045: xqf: Fails to run - segmentation fault

[Lars Wirzenius]

I looked at this bug for a while, and here's what I have found so far:

The crash happens because gtk gets a NULL pointer when it wants a
pointer to a GtkWidget. Specifically, this seems to happen in src/xqf.c,
about line 2860, in create_player_menu_item, where pixmap becomes NULL.

The reason for this is that src/loadpixmap.c, function
load_pixmap_as_pixmap, does complicated things to try to load a PNG
instead of an XPM, and then tries to use dlsym to find an XPM linked
into the executable. dlsym fails, returns NULL, and then everything else
fails until the crash happens.

The fix would seem to be to not play tricks with dlsym, but I'll look at
that later. For now I just want to report what I found. Hope this helps.

-- 
Yet another password: just say no.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#353851: Notification of NMU

[Lars Wirzenius]

Attached is the diff for the NMU which I'm going to upload in a little
while.

-- 
Close your mind to stress and pain, hack till you're no longer sane.
diff -u tdom-0.7.8/debian/changelog tdom-0.7.8/debian/changelog
--- tdom-0.7.8/debian/changelog
+++ tdom-0.7.8/debian/changelog
@@ -1,3 +1,11 @@
+tdom (0.7.8-4.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * tclconfig/tcl.m4, extensions/example/tcl.m4: Fixed shell syntax error.
+Closes: #353851.
+
+ -- Lars Wirzenius <[EMAIL PROTECTED]>  Sat, 18 Mar 2006 21:35:41 +
+
 tdom (0.7.8-4) unstable; urgency=low
 
   * Added tcl8.4-dev build depend.
only in patch2:
unchanged:
--- tdom-0.7.8.orig/configure
+++ tdom-0.7.8/configure
@@ -1516,7 +1516,7 @@
   if { (eval echo configure:1517: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; }; then
 for file in conftest.*; do
   case $file in
-  *.c | *.o | *.obj) ;;
+  *.$ac_ext | *.c | *.o | *.obj) ;;
   *) ac_cv_exeext=`echo $file | sed -e s/conftest//` ;;
   esac
 done
@@ -3029,7 +3029,7 @@
 	# results, and the version is kept in special file).
 	
 	if test -r /etc/.relid -a "X`uname -n`" = "X`uname -s`" ; then
-		system=MP-RAS-`awk '{print }' /etc/.relid'`
+		system=MP-RAS-`awk '{print }' /etc/.relid`
 	fi
 	if test "`uname -s`" = "AIX" ; then
 		system=AIX-`uname -v`.`uname -r`
only in patch2:
unchanged:
--- tdom-0.7.8.orig/tclconfig/tcl.m4
+++ tdom-0.7.8/tclconfig/tcl.m4
@@ -759,7 +759,7 @@
 	# results, and the version is kept in special file).
 	
 	if test -r /etc/.relid -a "X`uname -n`" = "X`uname -s`" ; then
-		system=MP-RAS-`awk '{print $3}' /etc/.relid'`
+		system=MP-RAS-`awk '{print $3}' /etc/.relid`
 	fi
 	if test "`uname -s`" = "AIX" ; then
 		system=AIX-`uname -v`.`uname -r`
@@ -2026,7 +2026,7 @@
 	# results, and the version is kept in special file).
 	
 	if test -r /etc/.relid -a "X`uname -n`" = "X`uname -s`" ; then
-		system=MP-RAS-`awk '{print $3}' /etc/.relid'`
+		system=MP-RAS-`awk '{print $3}' /etc/.relid`
 	fi
 	if test "`uname -s`" = "AIX" ; then
 		system=AIX-`uname -v`.`uname -r`
only in patch2:
unchanged:
--- tdom-0.7.8.orig/extensions/example/tcl.m4
+++ tdom-0.7.8/extensions/example/tcl.m4
@@ -586,7 +586,7 @@
 	# results, and the version is kept in special file).
 	
 	if test -r /etc/.relid -a "X`uname -n`" = "X`uname -s`" ; then
-		system=MP-RAS-`awk '{print $3}' /etc/.relid'`
+		system=MP-RAS-`awk '{print $3}' /etc/.relid`
 	fi
 	if test "`uname -s`" = "AIX" ; then
 		system=AIX-`uname -v`.`uname -r`
@@ -1452,7 +1452,7 @@
 	# results, and the version is kept in special file).
 	
 	if test -r /etc/.relid -a "X`uname -n`" = "X`uname -s`" ; then
-		system=MP-RAS-`awk '{print $3}' /etc/.relid'`
+		system=MP-RAS-`awk '{print $3}' /etc/.relid`
 	fi
 	if test "`uname -s`" = "AIX" ; then
 		system=AIX-`uname -v`.`uname -r`

Bug#353849: Notification of NMU

[Lars Wirzenius]

Attached is the diff for the NMU I'm going to be making in a short
while.

-- 
The road is wide and the sky is tall, before I die I will see it
all.--H.A.
diff -Nru /tmp/rRy47AHqCn/tclvfs-1.3/debian/changelog /tmp/6vUdAklP1m/tclvfs-1.3/debian/changelog
--- /tmp/rRy47AHqCn/tclvfs-1.3/debian/changelog	2004-12-09 19:33:40.0 +
+++ /tmp/6vUdAklP1m/tclvfs-1.3/debian/changelog	2006-03-18 21:15:27.0 +
@@ -1,3 +1,10 @@
+tclvfs (1.3-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * tclconfig/tcl.m4: Fixed shell syntax error. Closes: #353849.
+
+ -- Lars Wirzenius <[EMAIL PROTECTED]>  Sat, 18 Mar 2006 21:15:06 +
+
 tclvfs (1.3-1) unstable; urgency=low
 
   * New upstream release.
diff -Nru /tmp/rRy47AHqCn/tclvfs-1.3/tclconfig/tcl.m4 /tmp/6vUdAklP1m/tclvfs-1.3/tclconfig/tcl.m4
--- /tmp/rRy47AHqCn/tclvfs-1.3/tclconfig/tcl.m4	2004-12-09 19:30:59.0 +
+++ /tmp/6vUdAklP1m/tclvfs-1.3/tclconfig/tcl.m4	2006-03-18 21:12:35.0 +
@@ -770,7 +770,7 @@
 	# results, and the version is kept in special file).
 	
 	if test -r /etc/.relid -a "X`uname -n`" = "X`uname -s`" ; then
-		system=MP-RAS-`awk '{print $3}' /etc/.relid'`
+		system=MP-RAS-`awk '{print $3}' /etc/.relid`
 	fi
 	if test "`uname -s`" = "AIX" ; then
 		system=AIX-`uname -v`.`uname -r`
@@ -2142,7 +2142,7 @@
 	# results, and the version is kept in special file).
 	
 	if test -r /etc/.relid -a "X`uname -n`" = "X`uname -s`" ; then
-		system=MP-RAS-`awk '{print $3}' /etc/.relid'`
+		system=MP-RAS-`awk '{print $3}' /etc/.relid`
 	fi
 	if test "`uname -s`" = "AIX" ; then
 		system=AIX-`uname -v`.`uname -r`

Bug#347093: Notification of NMU

[Lars Wirzenius]

Attached is the diff for the NMU I'm planning on doing on sourcenav in a
few minutes. It closes two RC bugs in the package.

The actual .diff.gz of the source package is going to be bigger, because
I had to regenerate two configure scripts, and that changed lots of line
number, even if no actual interesting changes happened apart from the
ones in this diff.

-- 
/* The following line has been commented out */
diff -ru sourcenav-5.1.4/debian/changelog sourcenav-5.1.4.works/debian/changelog
--- sourcenav-5.1.4/debian/changelog	2006-03-18 20:08:27.0 +
+++ sourcenav-5.1.4.works/debian/changelog	2006-03-18 19:45:24.0 +
@@ -1,3 +1,13 @@
+sourcenav (5.1.4-2.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * tcl/unix/tcl.m4, tk/unix/tcl.m4, tk/unix/configure, tcl/unix/configure:
+Fix shell syntax error. Closes: #349875.
+  * debian/control: Changed Build-Depends from xlibs-dev to 
+what Nelson A. de Oliveira suggested. Closes: #347093. 
+
+ -- Lars Wirzenius <[EMAIL PROTECTED]>  Sat, 18 Mar 2006 19:43:42 +
+
 sourcenav (5.1.4-2) unstable; urgency=low
 
   * applied portabiliy patch for amd64 from Andreas Jochens, closes: #303692
diff -ru sourcenav-5.1.4/debian/control sourcenav-5.1.4.works/debian/control
--- sourcenav-5.1.4/debian/control	2006-03-18 20:08:27.0 +
+++ sourcenav-5.1.4.works/debian/control	2006-03-18 19:39:28.0 +
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Torsten Werner <[EMAIL PROTECTED]>
 Standards-Version: 3.1.1
-Build-Depends: debhelper (>= 2), gettext, flex-old, bison, xlibs-dev
+Build-Depends: debhelper (>= 2), gettext, flex-old, bison, libx11-dev, libxt-dev, x-dev
 
 Package: sourcenav
 Architecture: any
diff -ru sourcenav-5.1.4/tcl/unix/tcl.m4 sourcenav-5.1.4.works/tcl/unix/tcl.m4
--- sourcenav-5.1.4/tcl/unix/tcl.m4	2001-09-09 23:56:09.0 +
+++ sourcenav-5.1.4.works/tcl/unix/tcl.m4	2006-03-18 19:35:42.0 +
@@ -558,7 +558,7 @@
 	# results, and the version is kept in special file).
 	
 	if test -r /etc/.relid -a "X`uname -n`" = "X`uname -s`" ; then
-		system=MP-RAS-`awk '{print $3}' /etc/.relid'`
+		system=MP-RAS-`awk '{print $3}' /etc/.relid`
 	fi
 	if test "`uname -s`" = "AIX" ; then
 		system=AIX-`uname -v`.`uname -r`
@@ -1483,7 +1483,7 @@
 	# results, and the version is kept in special file).
 	
 	if test -r /etc/.relid -a "X`uname -n`" = "X`uname -s`" ; then
-		system=MP-RAS-`awk '{print $3}' /etc/.relid'`
+		system=MP-RAS-`awk '{print $3}' /etc/.relid`
 	fi
 	if test "`uname -s`" = "AIX" ; then
 		system=AIX-`uname -v`.`uname -r`
Only in sourcenav-5.1.4/tk/generic: tkInt.h.orig
diff -ru sourcenav-5.1.4/tk/unix/tcl.m4 sourcenav-5.1.4.works/tk/unix/tcl.m4
--- sourcenav-5.1.4/tk/unix/tcl.m4	2001-09-10 01:16:54.0 +
+++ sourcenav-5.1.4.works/tk/unix/tcl.m4	2006-03-18 19:36:31.0 +
@@ -558,7 +558,7 @@
 	# results, and the version is kept in special file).
 	
 	if test -r /etc/.relid -a "X`uname -n`" = "X`uname -s`" ; then
-		system=MP-RAS-`awk '{print $3}' /etc/.relid'`
+		system=MP-RAS-`awk '{print $3}' /etc/.relid`
 	fi
 	if test "`uname -s`" = "AIX" ; then
 		system=AIX-`uname -v`.`uname -r`
@@ -1483,7 +1483,7 @@
 	# results, and the version is kept in special file).
 	
 	if test -r /etc/.relid -a "X`uname -n`" = "X`uname -s`" ; then
-		system=MP-RAS-`awk '{print $3}' /etc/.relid'`
+		system=MP-RAS-`awk '{print $3}' /etc/.relid`
 	fi
 	if test "`uname -s`" = "AIX" ; then
 		system=AIX-`uname -v`.`uname -r`

Bug#353823: NMU diff

[Lars Wirzenius]

Attached is the diff with which I'm about to an NMU in a moment to fix
#353823 (Port 8080 needs to be configurable). It is very simple, so
should be safe. I've tested it, obviously, but only the part that I
changed, as I don't have a way to test asterisk and such stuff myself.

-- 
Talk is cheap. Whining is actually free.
diff -u destar-0.1.1/debian/changelog destar-0.1.1/debian/changelog
--- destar-0.1.1/debian/changelog
+++ destar-0.1.1/debian/changelog
@@ -1,3 +1,14 @@
+destar (0.1.1-3.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * debian/patches/30_add_port_option.dpatch: Made the port number
+configurable. Closes: #353823.
+  * debian/init.d: Added --port=8080 to the default options. This doesn't
+change the default port number, but nicely points out where the port
+number is to be changed, if it needs to be changed.
+
+ -- Lars Wirzenius <[EMAIL PROTECTED]>  Thu, 16 Mar 2006 22:35:00 +0200
+
 destar (0.1.1-3) unstable; urgency=low
 
   * Asterisk removed from build-depends. 
diff -u destar-0.1.1/debian/init.d destar-0.1.1/debian/init.d
--- destar-0.1.1/debian/init.d
+++ destar-0.1.1/debian/init.d
@@ -7,7 +7,7 @@
 NAME=destar
 DESC="Asterisk Web GUI DeStar"
 PIDFILE=/var/run/$NAME/$NAME.pid
-DAEMON_OPTS="--daemonize --pid=$PIDFILE"
+DAEMON_OPTS="--daemonize --pid=$PIDFILE --port=8080"
 
 test -x $DAEMON || exit 0
 
diff -u destar-0.1.1/debian/patches/00list destar-0.1.1/debian/patches/00list
--- destar-0.1.1/debian/patches/00list
+++ destar-0.1.1/debian/patches/00list
@@ -5,0 +6 @@
+30_add_port_option.dpatch
only in patch2:
unchanged:
--- destar-0.1.1.orig/debian/patches/30_add_port_option.dpatch
+++ destar-0.1.1/debian/patches/30_add_port_option.dpatch
@@ -0,0 +1,50 @@
+#! /bin/sh /usr/share/dpatch/dpatch-run
+## 30_add_port_option.dpatch by  <[EMAIL PROTECTED]>
+##
+## All lines beginning with `## DP:' are a description of the patch.
+## DP: Add -P|--port option to destar.
+
[EMAIL PROTECTED]@
+
+--- destar-0.1.1.unchanged/destar	2005-11-13 04:00:41.0 +0200
 destar-0.1.1/destar	2006-03-16 22:59:48.0 +0200
+@@ -33,6 +33,7 @@
+ import daemonize
+ be_daemon = False
+ pid_file = '/var/run/destar.pid'
++port = 8080
+ 
+ 
+ def print_version():
+@@ -57,8 +58,8 @@
+ 
+ 
+ try:
+-	opts,args = getopt.getopt(sys.argv[1:],'dhp:v', 
+-		['daemonize','help','pid=', 'version'])
++	opts,args = getopt.getopt(sys.argv[1:],'dhp:vP:', 
++		['daemonize','help','pid=', 'version', 'port='])
+ except getopt.GetoptError:
+ 	print "DeStar: Command-line parsing error. Aborting."
+ 	print_usage()
+@@ -75,6 +76,11 @@
+ 	if opt in ('-v', '--version'):
+ 		print_version()
+ 		sys.exit(0)
++	if opt in ('-P', '--port'):
++		try:
++			port = int(val)
++		except ValueError:
++			pass
+ 
+ 
+ print_version()
+@@ -100,7 +106,7 @@
+ # 'Publisher.py' contains our session management, 'page_main' contains
+ # the start page.
+ import Server, Publisher
+-pub = Server.Server("page_main", port=8080, publisher=Publisher.DeStarPublisher)
++pub = Server.Server("page_main", port=port, publisher=Publisher.DeStarPublisher)
+ 
+ 
+ 

Bug#357037: itrans-fonts: missing dependency?

[Lars Wirzenius]

Package: itrans-fonts
Version: 5.3-3
Severity: serious
Justification: installation fails

When testing itrans-fonts with piuparts, I get the following error:

  Setting up itrans-fonts (5.3-3) ...
  /var/lib/dpkg/info/itrans-fonts.postinst: line 7: mktexlsr: command
not found
  dpkg: error processing itrans-fonts (--configure):
   subprocess post-installation script returned error exit status 127

That command seems to be in tetex-bin in sid. If it moved from
tex-common, it might be a problem with the tex packages to have changed
in an incompatible manner, and in that case, please reassign the bug
there.

-- 
Mulla on halu häkätä ja mulla on siihen taito

Bug#357036: cjk-latex: missing or incorrect dependency?

[Lars Wirzenius]

Package: cjk-latex
Version: 4.5.1-4.1
Severity: serious
Justification: installation fails

When testing cjk-latex with piuparts, I got the following error:

  Setting up cjk-latex (4.5.1-4.1) ...
  /var/lib/dpkg/info/cjk-latex.postinst: line 13: /usr/bin/kpsewhich: No
such file or directory
  dpkg: error processing cjk-latex (--configure):
   subprocess post-installation script returned error exit status 1

kpsewhich seems to be in tetex-bin in sid, but the Depends header is
such that tex-common is sufficient, and then installation fails.

-- 
Programming should be fun, otherwise you're doing something wrong.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#356796: dict-wn: postinst failure with serpento

[Lars Wirzenius]

ti, 2006-03-14 kello 08:32 +0100, Andreas Tille kirjoitti:
> My concern is that such a quick fix does not realy fix the root
> of the problem that as a package maintainer I can't know all
> alternatives for a dependant package.  If there is a further package
> that provides a dict server I have to change the postinst again.
> 
> I wonder whether serpento (as every package that provides a dictd
> server) should include a /etc/init.d/dictd and conflict to dict-server.

I think this sounds like a reasonable solution.

> (BTW, what's the advantage of serpendot - perhaps I want to use it myself.)
> 
> Lars, I just found out that the packages
>dict-devil, dict-elements, dict-foldoc, dict-gcide, dict-jargon,
>dict-misc, dict-moby-thesaurus 
> (and probably others I did not have on my mirror) all suffer from the
> problem you reported as #348262.

I've already reported similar bugs against those. Some of the dict
packages take a lot of time to get fixed, though.

-- 
Comedy evolution: survival of the wittiest



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#353189: NMU patch

[Lars Wirzenius]

Attached is the patch for the NMU I'm going to be uploading in a little
while. It fixes two bugs, one which is is currently release critical
(failure to build from source), and which is a policy violation and
therefore at least technically RC (leaves log files on disk after
purged), although the damage it does is minor, and isn't marked with an
RC severity. I filed the latter bug myself earlier today.

I hope this helps. Happy hacking.

-- 
It's 1978! Things should be round by now -- Michael Kelso (That 70's
show)
diff -u yaws-1.58/debian/changelog yaws-1.58/debian/changelog
--- yaws-1.58/debian/changelog
+++ yaws-1.58/debian/changelog
@@ -1,3 +1,13 @@
+yaws (1.58-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * debian/control: Removed the build dependency on erlang-src, which doesn't
+exist. Added a build dependency on libpam0g-dev. Closes: #353189.
+  * debian/yaws.postrm: Added. Now removes /var/log/yaws on purge
+(see policy 10.8, Log files, last paragraph). Closes: #356272.
+
+ -- Lars Wirzenius <[EMAIL PROTECTED]>  Fri, 10 Mar 2006 18:35:58 +
+
 yaws (1.58-1) unstable; urgency=low
 
   * New upstream release.
diff -u yaws-1.58/debian/control yaws-1.58/debian/control
--- yaws-1.58/debian/control
+++ yaws-1.58/debian/control
@@ -2,7 +2,7 @@
 Section: web
 Priority: optional
 Maintainer: Will Newton <[EMAIL PROTECTED]>
-Build-Depends: debhelper (>= 5.0.0), autotools-dev, erlang, erlang-src, mime-support
+Build-Depends: debhelper (>= 5.0.0), autotools-dev, erlang, mime-support, libpam0g-dev
 Standards-Version: 3.6.2
 
 Package: yaws
only in patch2:
unchanged:
--- yaws-1.58.orig/debian/yaws.postrm
+++ yaws-1.58/debian/yaws.postrm
@@ -0,0 +1,9 @@
+#!/bin/sh
+
+set -e
+
+case "$1" in
+purge) rm -rf /var/log/yaws ;;
+esac
+
+#DEBHELPER#

Bug#351958: NMU patch

[Lars Wirzenius]

I'm about to NMU this with the attached patch.

-- 
Yet another password: just say no.
diff -u xtel-3.3.0/debian/control xtel-3.3.0/debian/control
--- xtel-3.3.0/debian/control
+++ xtel-3.3.0/debian/control
@@ -2,8 +2,8 @@
 Section: comm
 Priority: extra
 Maintainer: Eric Delaunay <[EMAIL PROTECTED]>
-Standards-Version: 3.6.1
-Build-Depends: lesstif-dev,libx11-dev,libxmu-dev,libxpm-dev,libxt-dev,x-dev,xlibs-data,libxaw7-dev,debhelper (>= 4.1.16),gif2png,xbase-clients,xutils,libjpeg-dev, doc-base, mime-codecs
+Standards-Version: 3.6.2
+Build-Depends: lesstif-dev,libx11-dev,libxmu-dev,libxpm-dev,libxt-dev,x-dev,xlibs-data,libxaw7-dev,debhelper (>= 4.1.16),gif2png,xbase-clients,xutils,libjpeg-dev, doc-base
 
 Package: xtel
 Architecture: any
diff -u xtel-3.3.0/debian/changelog xtel-3.3.0/debian/changelog
--- xtel-3.3.0/debian/changelog
+++ xtel-3.3.0/debian/changelog
@@ -1,3 +1,14 @@
+xtel (3.3.0-5.2) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Use perl's base64 decoding instead of mime-codecs, which no longer
+seems to exist. debian/rules has the change, and debian/control
+drops build-dependency on mime-codecs. Patch from Andreas Jochens.
+Closes: #351958. 
+  * debian/control: Bumbed Standards-Version to 3.6.2. No changes needed.
+
+ -- Lars Wirzenius <[EMAIL PROTECTED]>  Thu,  9 Mar 2006 19:43:55 +
+
 xtel (3.3.0-5.1) unstable; urgency=high
 
   * Non-maintainer upload.
diff -u xtel-3.3.0/debian/rules xtel-3.3.0/debian/rules
--- xtel-3.3.0/debian/rules
+++ xtel-3.3.0/debian/rules
@@ -54,7 +54,7 @@
 	rm -rf debian/tmp/usr/X11R6/lib/X11/fonts/xtel
 	# Install french documentation in the french docs directory
 	install -m 644 debian/index-fr.html debian/tmp/usr/share/doc/LANG/fr/xtel/index.html
-	base64-decode < debian/bullet.gif.base64 > debian/tmp/usr/share/doc/LANG/fr/xtel/bullet.gif
+	perl -MMIME::Base64  -ne 'print decode_base64($$_)' < debian/bullet.gif.base64 > debian/tmp/usr/share/doc/LANG/fr/xtel/bullet.gif
 	install -m 644 HISTOIRE.txt debian/tmp/usr/share/doc/LANG/fr/xtel/
 	install -m 644 LISEZMOI.txt debian/tmp/usr/share/doc/LANG/fr/xtel/
 	install -m 644 FAQ.txt debian/tmp/usr/share/doc/LANG/fr/xtel/

Bug#347937: tar truncates file >4GB to zero size when having large sparse region

[Lars Wirzenius]

Some further information for your consideration.

I can replicate the bug with the current version in sid (1.15.1-4). I
tested with version 1.15.90, found on ftp://alpha.gnu.org/gnu/tar/, with
the following results.

Create tarball as per instructions by Scott Edwards, using 1.15.1-4,
then extract it using same version. Result: win98/drivec.img is zero
bytes. Extraction with 1.15.90 also results in a zero byte file.

Creating the tarball with 1.15.90 and extracting it with the same
version works (file is identical to the original file created with dd).
Extracting with 1.15.1-4 also works.

Thus I assume the problem is in the code that creates the file in
1.15.1-4 (and the other versions that are affected), and also that it
has since been fixed in upstream. I didn't find out what the actual
change was, in order to backport it, however.

-- 
Wolfen one, you are my midday moon and I your midnight sun.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#347663: sfs-common: failure to remove, trying to deregister inexistent document

[Lars Wirzenius]

Yann Dirson <[EMAIL PROTECTED]>:
> Removing sfs-common ...
> /usr/share/doc-base/sfs-manual: cannot open control file for reading: No such 
> file or directory
> dpkg: error processing sfs-common (--remove):
>  subprocess pre-removal script returned error exit status 2

I can't actually reproduce this properly: I get the following error message:

> [EMAIL PROTECTED]:/# dpkg --purge sfs-common
> (Reading database ... 10890 files and directories currently installed.)
> Removing sfs-common ...
> Document `sfs-manual' is not installed, cannot remove.
> Purging configuration files for sfs-common ...
> removing sfs system account...
> ls: /var/lib/sfs/sockets/: No such file or directory
> [EMAIL PROTECTED]:/# echo $?
> 0
> [EMAIL PROTECTED]:/#

In other words, the error message is different, and the removal doesn't crash 
on it.
I don't know what causes this.

Still, the attached patch should fix it. I'm hesitant to actually do an NMU 
before I can
reproduce. Jaakko, do you have a comment?

-- 
Fundamental truth #1: Complexity is the enemy.
diff -u sfs-0.8-0+pre20050819.1/debian/changelog sfs-0.8-0+pre20050819.1/debian/changelog
--- sfs-0.8-0+pre20050819.1/debian/changelog
+++ sfs-0.8-0+pre20050819.1/debian/changelog
@@ -1,3 +1,11 @@
+sfs (1:0.8-0+pre20050819.1-2.2) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * debian/sfs-common.prerm: Removed call to install-doc, since no
+    documentation is actually installed by the package.
+
+ -- Lars Wirzenius <[EMAIL PROTECTED]>  Wed,  8 Mar 2006 16:31:15 +0200
+
 sfs (1:0.8-0+pre20050819.1-2.1) unstable; urgency=low
 
   * NMU to fix FTBFS bug (Closes: #338532), thanks to Damian Viano:
diff -u sfs-0.8-0+pre20050819.1/debian/sfs-common.prerm sfs-0.8-0+pre20050819.1/debian/sfs-common.prerm
--- sfs-0.8-0+pre20050819.1/debian/sfs-common.prerm
+++ sfs-0.8-0+pre20050819.1/debian/sfs-common.prerm
@@ -6,10 +6,6 @@
 install-info --quiet --remove /usr/share/info/sfs.info.gz
 install-info --quiet --remove /usr/share/info/sfs.info-1.gz
 install-info --quiet --remove /usr/share/info/sfs.info-2.gz
-#doc-base
-if command -v install-docs >/dev/null 2>&1; then
-	install-docs -r sfs-manual
-fi
 if [ -L /usr/doc/sfs ]; then
 rm -f /usr/doc/sfs
 fi

Bug#353852: Notification of NMU to fix FTBFS bug

[Lars Wirzenius]

ke, 2006-03-08 kello 14:19 +0200, Lars Wirzenius kirjoitti:
> Attached is the diff for the NMU I'm going to make in a little while
> (we're in 0-day NMU mode for bugs that have been open for over a week).

Ah, I was a bit late with my announcement. by all of fifteen minutes, I
obviously won't do the upload, since Matej already did. rcbugs-- anyway,
that's the good thing.

-- 
Rule #13 for successful communication: don't do Latin quotations



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#353852: Notification of NMU to fix FTBFS bug

[Lars Wirzenius]

Attached is the diff for the NMU I'm going to make in a little while
(we're in 0-day NMU mode for bugs that have been open for over a week).

-- 
Those who do, decide.
diff -u wyg-1.1.3.0.debian.1/debian/control wyg-1.1.3.0.debian.1/debian/control
--- wyg-1.1.3.0.debian.1/debian/control
+++ wyg-1.1.3.0.debian.1/debian/control
@@ -7,7 +7,7 @@
 
 Package: wyg
 Architecture: any
-Depends: ${shlibs:Depends} perl, bison, flex
+Depends: ${shlibs:Depends}, perl, bison, flex
 Description: (Where's Your Grammar?) command line parser generator
  WYG (Where's Your Grammar?) is a tool that automates the use of lex,
  yacc, and getopt_long to create a front-end for your projects that can
diff -u wyg-1.1.3.0.debian.1/debian/changelog wyg-1.1.3.0.debian.1/debian/changelog
--- wyg-1.1.3.0.debian.1/debian/changelog
+++ wyg-1.1.3.0.debian.1/debian/changelog
@@ -1,3 +1,11 @@
+wyg (1.1.3.0.debian.1-4.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * debian/control: added missing comma in Depends line. Package now
+builds from source again. Closes: #353852.
+
+ -- Lars Wirzenius <[EMAIL PROTECTED]>  Wed,  8 Mar 2006 13:49:54 +0200
+
 wyg (1.1.3.0.debian.1-4) unstable; urgency=low
 
   * Adopted package (Closes: #266460).

Bug#347744: dpkg - FTBFS: undefined reference to `sepol_genbools'

[Lars Wirzenius]

> Attached the correct patch snippet.
> 
> We'll be fixing this on next upload once we've sorted out the
> transition. ;)

For what it's worth, I couldn't build dpkg with these patches under pbuilder, 
the error is the same.

(This means, Bart, that I can't test your patch for #318825, but as soon as I 
can
build dpkg, I will test your patch by running piuparts on all successfully 
tested
packages to see if the patch works. Can't see why it wouldn't, of course.)

-- 
Mike, if loving you were any more painful, priests would assign it as
penance.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#336503: Can't reproduce: fp-compiler: /usr/share/man/man1/pc.1.gz duplicated still persists

[Lars Wirzenius]

package fp-compiler
severity normal
thanks

ma, 2006-01-09 kello 18:52 +0100, Lukas Ruf kirjoitti:
> > Lars Wirzenius <[EMAIL PROTECTED]> [2006-01-06 18:45]:
> >
> thanks for your answer.

You're welcome.

> > Lukas, do you still have the problem? You reported the bug two
> > months ago, so it may be that your system has been fixed since.
> >
> Today, I retried again -- now it worked.  Unfortunately, I have not
> investigated the problem any further then.
> 
> Thanks again for your answer and efforts!

Thanks for your quick reply. In this circumstance, I'll downgrade the
severity of the bug report to "normal". It hasn't been fixed, so I'm not
closing it, but since it doesn't seem to affect most people, it
shouldn't be of a higher severity. This way, the package won't be
removed from "testing", meaning it will get into the next Debian
release.

-- 
It doesn't matter who you are, it's what you do that takes you far.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#338327: Bug#340076: Patch for several xmltex bugs

[Lars Wirzenius]

ma, 2006-01-09 kello 01:07 +0100, Norbert Preining kirjoitti:
> Hi Frank!
> 
> On Fre, 30 Dez 2005, Frank Küster wrote:
> > One thing is missing in the patch, and that is to remove the files from
> > /etc/texmf that are now in /usr/share/texmf;  this must either be done
> > unconditionally (in this case don't remove them, but move them to
> > /etc/texmf/oldstuff_unused (creating it if it doesn't exist)), or by
> > checking with known md5sums whether they have changed.  Note that the
> > ini files won't be found at their old places in /etc/texmf/xmltex.
> 
> There is one problem with the upload you did, or it was intended: 
> dpkg: warning - unable to delete old file `/etc/texmf/xmltex': Directory
> not empty

Actually, I did the upload, as an NMU. See changelog.

For some reason, when I tested the package, I did not run into this
problem. Oops. And sorry. I'll have a look at this after I've slept,
unless someone beats me to it. 

Bug#335842: hmake: FTBFS: Makefile error in lib/debian/config

[Lars Wirzenius]

Attached is the diff for the NMU I'm going to upload in a little while.
It consists of the two patches mailed by Stefan Potyra to this bug. I've
done my best to verify that they work: the package builds, no new
lintian/linda warnings happen, and no (new) failures found with
piuparts.

-- 
Policy is your friend. Trust the Policy. Love the Policy. Obey the
Policy.
diff -ru hmake-3.10.untouched/debian/changelog hmake-3.10/debian/changelog
--- hmake-3.10.untouched/debian/changelog	2006-01-06 17:23:37.0 +
+++ hmake-3.10/debian/changelog	2006-01-06 17:31:31.0 +
@@ -1,3 +1,15 @@
+hmake (3.10-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Applied patches from Stefan Potyra to fix bug reported by Daniel
+Schepler to adapt to output changes in new ghc6 version that make
+"__GLASGOW_HASKELL__" be expanded into many lines instead of one.
+scripts/confhc uses the output to create lib/debian/config, and
+makes assumptions about the format. Similarly for 
+src/interpreter/HInteractive.hs. Closes: #335842.
+
+ -- Lars Wirzenius <[EMAIL PROTECTED]>  Fri,  6 Jan 2006 19:30:00 +0200
+
 hmake (3.10-1) unstable; urgency=low
 
   * New upstream version. Closes: #309837.
diff -ru hmake-3.10.untouched/script/confhc hmake-3.10/script/confhc
--- hmake-3.10.untouched/script/confhc	2005-03-10 17:45:32.0 +
+++ hmake-3.10/script/confhc	2006-01-06 17:27:17.0 +
@@ -78,7 +78,7 @@
 ghcsym () {
   echo __GLASGOW_HASKELL__ >ghcsym.hs;
   $1 -E -cpp -optP-P ghcsym.hs -o ghcsym.out;
-  grep -v '^#' ghcsym.out > $2;
+  grep -E '[0-9]+' ghcsym.out | grep -v '#' > $2;
   rm -f ghcsym.hs ghcsym.out;
 }
 echo -n "  Looking for ghc...   "
Only in hmake-3.10.untouched/src/hmake: Makefile~
diff -ru hmake-3.10.untouched/src/interpreter/HInteractive.hs hmake-3.10/src/interpreter/HInteractive.hs
--- hmake-3.10.untouched/src/interpreter/HInteractive.hs	2005-03-02 17:14:28.0 +
+++ hmake-3.10/src/interpreter/HInteractive.hs	2006-01-06 17:27:22.0 +
@@ -348,39 +348,39 @@
 help   = "hi - help command does not work in hbc < 0..5"
 
 #else
-banner = "\ 
-\__   __ __ _\n\ 
-\||   ||  _____  || _   hmake interactive (hi):\n\ 
-\||___|| || || ||  ___|| ||/  ||__||  Copyright (c) May 2000\n\ 
-\||---|| || || || ||__|| ||\\_ ||__http://www.cs.york.ac.uk/fp/hmake/\n\ 
-\||   ||Report bugs to: [EMAIL PROTECTED] 
-\||   || Version: "++hmakeVersion++"-"
+banner = "\
+__   __ __ _\n\
+||   ||  _____  || _   hmake interactive (hi):\n\
+||___|| || || ||  ___|| ||/  ||__||  Copyright (c) May 2000\n\
+||---|| || || || ||__|| ||\\_ ||__http://www.cs.york.ac.uk/fp/hmake/\n\
+||   ||Report bugs to: [EMAIL PROTECTED]
+||   || Version: "++hmakeVersion++"-"
 
 
-help = "\ 
-\Commands (can be abbreviated to first letter):\n\ 
-\ evaluate expression\n\ 
-\  :type  show type of expression [nhc98 only]\n\ 
-\  :quitquit\n\ 
-\  :Quitquit\n\ 
-\  :load mod [mod...]   load modules (note, not filenames)\n\ 
-\  :loadclear all modules\n\ 
-\  :also mod [mod...]   load additional modules (note, not filenames)\n\ 
-\  :reload  repeat last load command\n\ 
-\  :freshen remove, recompile, and reload all current modules\n\ 
-\  :module mod  set module scope for evaluating expressions\n\ 
-\  :edit file   edit filename\n\ 
-\  :editedit current module\n\ 
-\  :cd dir  change directory\n\ 
-\  :cd  show current directory\n\ 
-\  :dir list current directory\n\ 
-\  :hc compiler set Haskell compiler to use\n\ 
-\  :hc  show current compiler and other available compilers\n\ 
-\  :set options set hmake/compiler options\n\ 
-\  :unset options   remove hmake/compiler options\n\ 
-\  :observe namedebug function 'name' with 'Hood' [coming soon]\n\ 
-\  :trace [on|off]  switch on/off debugging with 'Hat' [nhc98 only]\n\ 
-\  :!commandshell escape\n\ 
-\  :version show hmake version\n\ 
-\  :?   display this list of commands"
+help = "\
+Commands (can be abbreviated to first letter):\n\
+ evaluate expression\n\
+  :type  show type of expression [nhc98 only]\n\
+  :quitquit\n\
+  :Quitquit\n\
+  :load mod [mod...]   load modules (note, not filenames)\n\
+  :loadclear all modules\n

Bug#338327: Going to NMU xmltex (Re: xmltex: Package fails to install (and also tells me to report a bug for using fmtutil))

[Lars Wirzenius]

I'm about to NMU xmltex with the attached patch (actually made by Frank
Küster), since Steve Langasek tells me it is urgent because other
release critical bugs are depending on this.

-- 
Fundamental truth #4: Typing URLs always introduces errors. Always copy
+paste.
diff -ru xmltex-1.9.untouched/Makefile xmltex-1.9/Makefile
--- xmltex-1.9.untouched/Makefile	2006-01-06 18:10:22.0 +
+++ xmltex-1.9/Makefile	2006-01-06 18:30:30.0 +
@@ -7,7 +7,8 @@
 
 ## --
 prefix		= 
-confdir		= $(prefix)/etc/texmf/$(package)
+etctexmf	= $(prefix)/etc/texmf
+confdir		= $(etctexmf)/$(package)
 sharedir	= $(prefix)/usr/share/texmf/tex/$(package)
 
 ## --
@@ -16,12 +17,15 @@
 		dvips -o manual.ps manual
 
 install:
-		install -m 0755 -d $(confdir)
-		install -m 0644 *.ini xmltex.cfg $(confdir)
+		install -m 0755 -d $(etctexmf)/texmf.d
+		install -m 0755 -d $(etctexmf)/fmt.d
+		install -m 0644 debian/20xmltex.cnf $(etctexmf)/texmf.d
+		install -m 0644 debian/40xmltex.cnf $(etctexmf)/fmt.d
 		install -m 0755 -d $(sharedir)/base
 		install -m 0644 *.xmt xmltex.tex $(sharedir)/base
-		install -m 0755 -d $(sharedir)/templates
-		install -m 0644 debian/*.cnf $(sharedir)/templates
+		install -m 0755 -d $(sharedir)/config
+		install -m 0644 xmltex.cfg $(sharedir)/config
+		install -m 0644 *.ini $(sharedir)/config
 
 distclean:
 		rm -f $(addprefix manual.,toc log aux dvi ps)
diff -ru xmltex-1.9.untouched/debian/changelog xmltex-1.9/debian/changelog
--- xmltex-1.9.untouched/debian/changelog	2006-01-06 18:10:22.0 +
+++ xmltex-1.9/debian/changelog	2006-01-06 19:19:58.0 +
@@ -1,3 +1,23 @@
+xmltex (1.9-11.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * All the changes are actually by Frank Kuster <[EMAIL PROTECTED]>
+from mail sent to the #338327 bug. I'm doing the NMU because
+Steve Langasek indicated it is urgent to get this fixed, since other
+RC bugs wait for this to be fixed. I've done my best to test it (i.e.,
+package builds and installs, and packages depending on it install
+without trouble).
+  * Drop special handling of the configuration files in texmf.d and
+fmt.d, and make them conffiles (since they don't seem to have changed
+for long, this should be safe) (closes: #340076)
+  * Move ini files to /usr/share/texmf/tex/xmltex/config, in accordance
+with TeX Policy on configuration files, and to allow the fmtutil
+configuration snippet to be treated as a conffile; drop dh_link
+(closes: #345223)
+  * Call fmtutil-sys if it is available (closes: #338327)
+
+ -- Lars Wirzenius <[EMAIL PROTECTED]>  Fri,  6 Jan 2006 21:19:00 +0200
+
 xmltex (1.9-11) unstable; urgency=low
 
   * debian/postinst: Do not check for the created format files, because
diff -ru xmltex-1.9.untouched/debian/rules xmltex-1.9/debian/rules
--- xmltex-1.9.untouched/debian/rules	2006-01-06 18:10:22.0 +
+++ xmltex-1.9/debian/rules	2006-01-06 18:30:30.0 +
@@ -45,7 +45,7 @@
 		dh_installchangelogs
 		dh_installexamples
 		dh_installman
-		dh_link
+#		dh_link
 		dh_compress
 		dh_fixperms
 		dh_installdeb
Only in xmltex-1.9.untouched/debian: xmltex.links
diff -ru xmltex-1.9.untouched/debian/xmltex.postinst xmltex-1.9/debian/xmltex.postinst
--- xmltex-1.9.untouched/debian/xmltex.postinst	2006-01-06 18:10:22.0 +
+++ xmltex-1.9/debian/xmltex.postinst	2006-01-06 18:30:30.0 +
@@ -7,6 +7,9 @@
 
 set -e
 
+fmtutil=fmtutil
+if [ -x /usr/bin/fmtutil-sys ]; then fmtutil=fmtutil-sys; fi
+
 # summary of how this script can be called:
 #*  `configure' 
 #*  `abort-upgrade' 
@@ -33,43 +36,43 @@
echo $* 1>&2
 }
 
-installconf () {
-# mv on disable file or copy template
-while [ $# -gt 0 ]; do
-conffile=$1
-shift
-if [ -f $conffile ] ; then
-   :
-elif [ -f $conffile.disable ]; then
-mv $conffile.disable $conffile
-else
-cp $TMPLDIR/`basename $conffile` $conffile
-fi
-done
-}
-
-checkconf ( ) {
-# Treat old conffiles
-if [ -f $TEXMFDIR/20xmltex ] ; then
-mv $TEXMFDIR/20xmltex $TEXMFDIR/20xmltex.cnf
-fi
-
-if [ -f /etc/texmf/xmltex.cfg ] ; then
-mv -f /etc/texmf/xmltex.cfg /etc/texmf/xmltex/xmltex.cfg
-fi
+# installconf () {
+# # mv on disable file or copy template
+# while [ $# -gt 0 ]; do
+# conffile=$1
+# shift
+# if [ -f $conffile ] ; then
+#:
+# elif [ -f $conffile.disable ]; then
+# mv $conffile.disable $conffile
+# else
+# cp $TMPLDIR/`basename $conffile` $conffile
+# fi
+# done
+# }
+
+# checkconf ( ) {
+# # Treat old conffiles
+# if [ -f $TEXMFDIR/20xmltex ] ; then
+# mv $TEXMFDIR/20xmltex $TEXM

Bug#336503: Can't reproduce: fp-compiler: /usr/share/man/man1/pc.1.gz duplicated still persists

[Lars Wirzenius]

Lukas Ruf wrote:
> the problem still persists in 2.0.0-4:
> 
> Setting up fp-compiler (2.0.0-4) ...
> update-alternatives: slave link name /usr/share/man/man1/pc.1.gz duplicated

I looked at reproducing this bug (not being the maintainer, merely working on 
release critical bugs in general). I created four identical clean sid chroots 
with
just the base system in them.

In the first chroot I installed fp-compiler 2.0.0-1 and upgraded that to 2.0.0-4
(the version currently in testing and unstable). This worked perfectly.

In the second chroot I installed fp-compiler 2.0.0-2 and upgraded that to 
2.0.0-4.
This worked perfectly.

In the third chroot I installed fp-compiler 2.0.0-1, and upgraded that to 
2.0.0-2.
This failed, as expected. I then removed the pc alternative 
("update-alternatives 
--remove pc /usr/bin/fpc"), installed 2.0.0-2 again, which now worked. The 
upgrade
to 2.0.0-4 worked perfectly.

In the fourth chroot I installed fp-compiler 2.0.0-1, tried to upgrade to 
2.0.0-2
(which failed) and then upgraded directly to 2.0.0-4, which worked perfectly.

I also tested the package with piuparts, both simple installation and removal,
and upgrades from sarge to etch and sid, and that worked perfectly.

Lukas, do you still have the problem? You reported the bug two months ago, so it
may be that your system has been fixed since. I suspect that you had trouble 
because
of something you tried to do after installing the 2.0.0-1 or -2 versions and 
that
that made things such that the problem still occurs with -4, but I couldn't find
a scenario where I could reproduce this. Any hints as to how to reproduce it 
would
be most welcome.

I did not investigate how the fpc packages may interact with the gpc packages. 
Lukas,
do you (or did you) have gpc packages also installed when the problem occurred?

If this bug can't be reproduced, I think it would be appropriate to at least 
lower 
the severity to normal, since the package does seem to be usable for most 
people.

-- 
Good news at once. Bad news never in the evening or on Friday.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#340960: Patch for Bug #340960: --delete-input-file ate my data

[Lars Wirzenius]

package flac
tags 340960 + patch
thanks

Attached is flac.diff, which turns the warnings about unexpected EOF
into errors, so that --delete-input-file doesn't delete the input file
if there is something suspicious going on.

I'm not going to NMU this immediately, but I may do that later.

-- 
Fundamental truth #2: Attitude is usually more important than skills.
diff -ru flac-1.1.2/src/flac/encode.c flac-1.1.2.patched/src/flac/encode.c
--- flac-1.1.2/src/flac/encode.c	2005-01-25 04:13:52.0 +
+++ flac-1.1.2.patched/src/flac/encode.c	2006-01-05 15:50:34.822506736 +
@@ -397,8 +397,8 @@
 		return EncoderSession_finish_error(&encoder_session);
 	}
 	else if(feof(infile)) {
-		flac__utils_printf(stderr, 1, "%s: WARNING: unexpected EOF; expected %u samples, got %u samples\n", encoder_session.inbasefilename, (unsigned int)encoder_session.total_samples_to_encode, (unsigned int)encoder_session.samples_written);
-		data_bytes= 0;
+		flac__utils_printf(stderr, 1, "%s: ERROR: unexpected EOF; expected %u samples, got %u samples\n", encoder_session.inbasefilename, (unsigned int)encoder_session.total_samples_to_encode, (unsigned int)encoder_session.samples_written);
+		return EncoderSession_finish_error(&encoder_session);
 	}
 }
 else {
@@ -456,7 +456,8 @@
 			return EncoderSession_finish_error(&encoder_session);
 		}
 		else if(bytes_read != (*options.common.align_reservoir_samples) * bytes_per_frame) {
-			flac__utils_printf(stderr, 1, "%s: WARNING: unexpected EOF; read %u bytes; expected %u samples, got %u samples\n", encoder_session.inbasefilename, (unsigned int)bytes_read, (unsigned int)encoder_session.total_samples_to_encode, (unsigned int)encoder_session.samples_written);
+			flac__utils_printf(stderr, 1, "%s: ERROR: unexpected EOF; read %u bytes; expected %u samples, got %u samples\n", encoder_session.inbasefilename, (unsigned int)bytes_read, (unsigned int)encoder_session.total_samples_to_encode, (unsigned int)encoder_session.samples_written);
+			return EncoderSession_finish_error(&encoder_session);
 		}
 		else {
 			info_align_carry= *options.common.align_reservoir_samples;
@@ -735,8 +736,8 @@
 		return EncoderSession_finish_error(&encoder_session);
 	}
 	else if(feof(infile)) {
-		flac__utils_printf(stderr, 1, "%s: WARNING: unexpected EOF; expected %u samples, got %u samples\n", encoder_session.inbasefilename, (unsigned)encoder_session.total_samples_to_encode, (unsigned)encoder_session.samples_written);
-		data_bytes = 0;
+		flac__utils_printf(stderr, 1, "%s: ERROR: unexpected EOF; expected %u samples, got %u samples\n", encoder_session.inbasefilename, (unsigned)encoder_session.total_samples_to_encode, (unsigned)encoder_session.samples_written);
+		return EncoderSession_finish_error(&encoder_session);
 	}
 }
 else {
@@ -794,8 +795,8 @@
 			return EncoderSession_finish_error(&encoder_session);
 		}
 		else if(bytes_read != (*options.common.align_reservoir_samples) * bytes_per_wide_sample) {
-			flac__utils_printf(stderr, 1, "%s: WARNING: unexpected EOF; read %u bytes; expected %u samples, got %u samples\n", encoder_session.inbasefilename, (unsigned)bytes_read, (unsigned)encoder_session.total_samples_to_encode, (unsigned)encoder_session.samples_written);
-			data_bytes = 0;
+			flac__utils_printf(stderr, 1, "%s: ERROR: unexpected EOF; read %u bytes; expected %u samples, got %u samples\n", encoder_session.inbasefilename, (unsigned)bytes_read, (unsigned)encoder_session.total_samples_to_encode, (unsigned)encoder_session.samples_written);
+			return EncoderSession_finish_error(&encoder_session);
 		}
 		else {
 			info_align_carry = *options.common.align_reservoir_samples;
@@ -1046,8 +1047,8 @@
 	return EncoderSession_finish_error(&encoder_session);
 }
 else if(feof(infile)) {
-	flac__utils_printf(stderr, 1, "%s: WARNING: unexpected EOF; expected %u samples, got %u samples\n", encoder_session.inbasefilename, (unsigned)encoder_session.total_samples_to_encode, (unsigned)encoder_session.samples_written);
-	total_input_bytes_read = max_input_bytes;
+	flac__utils_printf(stderr, 1, "%s: ERROR: unexpected EOF; expected %u samples, got %u samples\n", encoder_session.inbasefilename, (unsigned)encoder_session.total_samples_to_encode, (unsigned)encoder_session.samples_written);
+	return EncoderSession_finish_error(&encoder_session);
 }
 			}
 			else {
@@ -1098,7 +1099,8 @@
 	return EncoderSession_finish_error(&encoder_session);
 }
 else if(bytes_read != (*options.common.align_reservoir_samples) * bytes_per_wide_sample) {
-	flac__utils_printf(stderr, 1, "%s: WARNING: unexpected EOF; read %u bytes; expected %u samples, got %u samples\n", encoder_session.inbasefilename, (unsigned)bytes_read, (unsigned)encoder_session.total_samples_to_encode, (unsigned)encoder_session.samples_written);
+	flac__utils_printf(stde

Bug#340119: About coreutils bug #340119

[Lars Wirzenius]

Wouter Verhelst wrote:
> Just to tell you that after doing an install of etch (using the beta1
> installer) yesterday, and immediately upgrading that to sid, I've got
> the same problem. If you'd want to test that, it should be easy :-)

A data point: I tried this with an etch chroot, and also with piuparts 
from sarge to etch to sid. These tests didn't trigger the bug.

-- 
There's a reason why "release manager" is abbreviated "rm".



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#344229: Patch for: am-utils: Contains file in /usr/man

[Lars Wirzenius]

package am-utils
tags 344229 + patch
thanks

Nathanael Nerode wrote:
> This package violates the FHS by shipping a file in /usr/man.

I've attached a patch to fix this. Since I can't test the package, I
won't do an NMU. I know the package builds, and lintian and linda don't
give any errors/warnings related to my changes, but I don't know if the
package as built my me works, since I don't have an automounter setup
and I don't want to build one just for this package.

I hope this is useful. Happy hacking.

-- 
Talk is cheap. Whining is actually free.
--- am-utils-6.1.3/debian/changelog	2006-01-04 17:55:48.573040469 +
+++ am-utils-6.1.3.patched/debian/changelog	2006-01-04 17:53:22.159901747 +
@@ -1,3 +1,11 @@
+am-utils (6.1.3-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Moved manpages from /usr/man to /usr/share/man. Closes: #344229
+(by Nathanael Nerode), a release critical bug.
+
+ -- Lars Wirzenius <[EMAIL PROTECTED]>  Wed,  4 Jan 2006 19:53:00 +0200
+
 am-utils (6.1.3-1) unstable; urgency=low
 
   * New upstream version (Closes: #331566)
--- am-utils-6.1.3/debian/am-utils.install	2006-01-04 17:55:48.578039654 +
+++ am-utils-6.1.3.patched/debian/am-utils.install	2006-01-04 17:35:29.0 +
@@ -1,8 +1,8 @@
 debian/tmp/usr/sbin
 debian/tmp/usr/bin
-debian/tmp/usr/man usr/share
+debian/tmp/usr/share/man usr/share
 debian/amd.conf etc/am-utils
 debian/amq-check-wrap usr/sbin
-debian/amq-check-wrap.8 usr/man/man8
+debian/amq-check-wrap.8 usr/share/man/man8
 debian/a_master usr/share/doc/am-utils/examples
 debian/*.diff usr/share/doc/am-utils/kernel-patches
--- am-utils-6.1.3/debian/rules	2006-01-04 17:55:48.577039817 +
+++ am-utils-6.1.3.patched/debian/rules	2006-01-04 17:29:16.0 +
@@ -85,20 +85,21 @@
 	dh_clean -k
 	dh_installdirs
 
-	$(MAKE) prefix=`pwd`/debian/tmp/usr install
+	$(MAKE) prefix=`pwd`/debian/tmp/usr \
+		mandir=`pwd`/debian/tmp/usr/share/man install
 	rm -fr debian/tmp/usr/etc
 	rm debian/tmp/usr/sbin/lostaltmail
 	rm debian/tmp/usr/bin/expn
-	rm debian/tmp/usr/man/man1/expn.1
+	rm debian/tmp/usr/share/man/man1/expn.1
 	rm debian/tmp/usr/sbin/mk-amd-map
-	rm debian/tmp/usr/man/man8/mk-amd-map.8
+	rm debian/tmp/usr/share/man/man8/mk-amd-map.8
 	rm debian/tmp/usr/sbin/am-eject
 	rm debian/tmp/usr/sbin/ctl-* debian/tmp/usr/sbin/wait* \
 	   debian/tmp/usr/sbin/fix-amd-map \
 	   debian/tmp/usr/sbin/fixrmtab
 	mv debian/tmp/usr/sbin/fsinfo debian/tmp/usr/sbin/amd-fsinfo
-	mv debian/tmp/usr/man/man8/fsinfo.8 \
-	   debian/tmp/usr/man/man8/amd-fsinfo.8
+	mv debian/tmp/usr/share/man/man8/fsinfo.8 \
+	   debian/tmp/usr/share/man/man8/amd-fsinfo.8
 
 	dh_install --fail-missing -a -i
 

Bug#337269: gatos: FTBFS: invalid lvalue in assignment

[Lars Wirzenius]

If I change src/i2c.c, line 398 to be like this:

  if (loop) (N1) ? (N2=N) : (N1 = N) ; if (N2) loop = 0 ; }

Then the build continues, but fails later with this error:

g++ -Wall -pipe -O -o .libs/xatitv xatitv.o
xutils.o .libs/xatitvS.o  ./.libs/libgatos.so
-L/usr/lib /usr/lib/libibtk.so -L/usr/X11R6/lib -lstdc++ -lX11
-lXxf86dga -lXxf86vm -lXext -lm
/usr/bin/ld: warning: type and size of dynamic symbol `__do_delay' are
not defined
/usr/bin/ld: dynamic variable `__do_delay' is zero size
/usr/bin/ld: .libs/xatitvS.o(.rodata+0x14c4): unresolvable R_386_32
relocation against symbol `__do_delay'
/usr/bin/ld: final link failed: Nonrepresentable section on output

I don't know how to fix that.

-- 
Good news at once. Bad news never in the evening or on Friday.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#338930: gambas - FTBFS: creating symbolic link: Permission denied

[Lars Wirzenius]

The patch below allows the package to be built. A quick glance at it
doesn't indicate any huge problems, but since I don't the package at
all, I didn't test it. Hopefully this is helpful in gettinga fixed
upload done anyway.

Happy hacking.

--- gambas-1.0.12/debian/rules  2005-12-16 21:13:24.0 +
+++ gambas-1.0.12.modified/debian/rules 2005-12-16 21:07:42.0
+
@@ -54,7 +54,8 @@
dh_testroot
dh_clean -k
dh_installdirs
-   $(MAKE) install DESTDIR=$(CURDIR)/debian/tmp
+   $(MAKE) install DESTDIR=$(CURDIR)/debian/tmp \
+   ROOT="$(CURDIR)/debian/tmp"
cp $(CURDIR)/debian/gambas.lintian-overrides
$(CURDIR)/debian/gambas/usr/share/lintian/overrides/gambas
cp $(CURDIR)/debian/gambas-doc.lintian-overrides
$(CURDIR)/debian/gambas-doc/usr/share/lintian/overrides/gambas-doc


-- 
Fundamental truth #5: Always ask the simple troubleshooting questions
first.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#337870: FTBFS (alpha): conflicting types for 'strlen'

[Lars Wirzenius]

Attached please find two patches. patch-1.txt is minimal, just enough to
make the build succeed. It modified fvwm/alpha_header.h so that it uses
the proper (standardized!) headers instead of declaring things itself.
This is, I hope, sufficient to fix the bug in question.

patch-2.txt includes the minimal fix, but includes fixes for several
other changes as well to silence some warnings. Mostly fixes for wrongly
defined main functions, but also a fix to switch from using mktemp
(which causes a warning and is potentially risky from a security
perspective) to mkstemp (which is not risky, and is simpler to use as
well).

I don't have an alpha machine to test with, so I have only tested that
the build succeeds. In fact, since the chroot in which I was doing this
didn't have all necessary packages, I didn't even test the full build.

Under these circumstances I won't even consider making an NMU to fix the
package, but I hope the patches (at least the small one, but preferably
the big one) is useful to the maintainer or to a bug squashing party.

Happy hacking.

-- 
Though spring is here, to me it is still September
Only in fvwm1-1.24r.original: .message~
diff -ru fvwm1-1.24r.original/fvwm/alpha_header.h fvwm1-1.24r/fvwm/alpha_header.h
--- fvwm1-1.24r.original/fvwm/alpha_header.h	2005-12-16 19:27:28.0 +
+++ fvwm1-1.24r/fvwm/alpha_header.h	2005-12-16 19:28:31.0 +
@@ -3,14 +3,17 @@
  * alpha's */
 #include 
 #include 
+#include 
+#include 
 
-
+#if 0
 extern int select(int, fd_set *, fd_set *, fd_set *, struct timeval *);
 
 /* string manipulation */
 #ifdef __GNUC__
 extern size_t strlen(char *);
 #endif
+#endif
 
 /* The following already exist on Debian GNU/Linux alpha systems */
 /* extern int bzero(char *, int);
Only in fvwm1-1.24r.original: .message~
diff -ru fvwm1-1.24r.original/fvwm/alpha_header.h fvwm1-1.24r.modified/fvwm/alpha_header.h
--- fvwm1-1.24r.original/fvwm/alpha_header.h	2005-12-16 19:27:28.0 +
+++ fvwm1-1.24r.modified/fvwm/alpha_header.h	2005-12-16 19:04:56.0 +
@@ -3,14 +3,18 @@
  * alpha's */
 #include 
 #include 
+#include 
+#include 
 
 
+#if 0
 extern int select(int, fd_set *, fd_set *, fd_set *, struct timeval *);
 
 /* string manipulation */
 #ifdef __GNUC__
 extern size_t strlen(char *);
 #endif
+#endif
 
 /* The following already exist on Debian GNU/Linux alpha systems */
 /* extern int bzero(char *, int);
diff -ru fvwm1-1.24r.original/libs/SendInfo.c fvwm1-1.24r.modified/libs/SendInfo.c
--- fvwm1-1.24r.original/libs/SendInfo.c	1994-09-13 18:53:14.0 +
+++ fvwm1-1.24r.modified/libs/SendInfo.c	2005-12-16 19:05:37.0 +
@@ -1,5 +1,6 @@
 #include 
 #include 
+#include 
 
 /***
  *
diff -ru fvwm1-1.24r.original/libs/SendText.c fvwm1-1.24r.modified/libs/SendText.c
--- fvwm1-1.24r.original/libs/SendText.c	1994-09-13 18:53:12.0 +
+++ fvwm1-1.24r.modified/libs/SendText.c	2005-12-16 19:05:50.0 +
@@ -1,5 +1,6 @@
 #include 
 #include 
+#include 
 /
  *
  * Sends arbitrary text to fvwm
diff -ru fvwm1-1.24r.original/libs/hostname.c fvwm1-1.24r.modified/libs/hostname.c
--- fvwm1-1.24r.original/libs/hostname.c	1994-09-22 12:37:18.0 +
+++ fvwm1-1.24r.modified/libs/hostname.c	2005-12-16 19:06:47.0 +
@@ -1,4 +1,5 @@
 #include "../configure.h"
+#include 
 
 #if HAVE_UNAME
 /* define mygethostname() by using uname() */
diff -ru fvwm1-1.24r.original/libs/mystrcasecmp.c fvwm1-1.24r.modified/libs/mystrcasecmp.c
--- fvwm1-1.24r.original/libs/mystrcasecmp.c	1994-09-14 15:55:20.0 +
+++ fvwm1-1.24r.modified/libs/mystrcasecmp.c	2005-12-16 19:06:30.0 +
@@ -1,6 +1,7 @@
 #include 
 #include 
 #include 
+#include 
 
 int mystrcasecmp(char *s1,char *s2)
 {
diff -ru fvwm1-1.24r.original/modules/FvwmAudio/FvwmAudio.c fvwm1-1.24r.modified/modules/FvwmAudio/FvwmAudio.c
--- fvwm1-1.24r.original/modules/FvwmAudio/FvwmAudio.c	1994-09-14 14:28:53.0 +
+++ fvwm1-1.24r.modified/modules/FvwmAudio/FvwmAudio.c	2005-12-16 20:04:48.0 +
@@ -138,7 +138,7 @@
 RPLAY	*rplay_table[MAX_MESSAGES+MAX_BUILTIN];
 #endif
 
-main(int argc, char **argv)
+int main(int argc, char **argv)
 {
 	char *temp, *s;
 
@@ -179,6 +179,7 @@
 	audio_play(BUILTIN_STARTUP);
 	SendText(fd,"Nop",0);
 	Loop(fd);
+	return 0;
 }
 
 /***
diff -ru fvwm1-1.24r.original/modules/FvwmAuto/FvwmAuto.c fvwm1-1.24r.modified/modules/FvwmAuto/FvwmAuto.c
--- fvwm1-1.24r.original/modules/FvwmAuto/FvwmAuto.c	1994-12-02 19:04:02.0 +
+++ fvwm1-1.24r.modified/modules/FvwmAuto/FvwmAuto.c	2005-12-16 19:54:04.0 +
@@ -57,7 +57,7 @@
  *	main - start of module
  *
  ***/
-void main(int argc, char **argv)
+int main(int argc, char **argv)

Bug#339972: phalanx: /var/games doesn't exist

[Lars Wirzenius]

Package: phalanx
Version: 22-15
Severity: serious
Justification: uninstallable in some circumstances

While testing phalanx with piuparts, I get the following error:

  Unpacking phalanx (from .../phalanx_22-15_i386.deb) ...
  Setting up phalanx (22-15) ...
  dd: opening `/var/games/phalanx.learn': No such file or directory
  dpkg: error processing phalanx (--configure):
   subprocess post-installation script returned error exit status 1
  Errors were encountered while processing:
   phalanx
  E: Sub-process /usr/bin/dpkg returned an error code (1)

This would seem to be because the postinst script assumes /var/games
exists, but it is not part of base-files, so the package needs to create
it if it doesn't exist, and remove when the package is removed (unless
it's still being used by others). For example the gnome-games package
does this (the first package I found).

-- 
On a clear disk, you seek forever.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#339961: rsplib-dev: file conflict with rsplib1

[Lars Wirzenius]

Package: rsplib-dev
Version: 1.0.0-1
Severity: serious
Justification: upgrades from sarge to etch fail

When testing rsplib-dev with piuparts, specifically upgrades from sarge
via etch to sid, I get the following error:

  Unpacking replacement rsplib-dev ...
  dpkg: error
processing /var/cache/apt/archives/rsplib-dev_1.0.0-1_i386.deb
(--unpack):
   trying to overwrite `/usr/lib/librsplib.so', which is also in package
rsplib1

This happened during the upgrade from sarge to etch. An installation
directly into a clean sid chroot does work. I assume the librsplib.so
file shouldn't be in both packages. In case it helps, dpkg or apt-get
decided to upgrade rsplib1 only after rsplib-dev. The whole piuparts log
file is about 185 kilobytes, so I won't attach it, but I'd be glad to
mail it on request.

-- 
Happiness isn't happiness without a violin-playing goat. -- Notting Hill



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#338537: mffm-fftw: file conflict between mffm-fftw1c2 and mffm-fftw1

[Lars Wirzenius]

Package: mffm-fftw1c2
Version: 1.6-1
Severity: serious
Justification: breaks upgrades

When testing mffm-fftw-dev with piuparts, specifically upgrades from
sarge via etch to sid, I get the following error:

  Selecting previously deselected package mffm-fftw1c2.
  Unpacking mffm-fftw1c2 (from .../mffm-fftw1c2_1.6-1_i386.deb) ...
  dpkg: error
processing /var/cache/apt/archives/mffm-fftw1c2_1.6-1_i386.deb
(--unpack):
   trying to overwrite `/usr/lib/lib2Dfft.so.1', which is also in
package mffm-fftw1

mffm-fftw1 was installed in sarge, then remains on the system (or the
chroot that is used for this test) as it is upgraded to etch and sid.
The sid version of mffm-fftw-dev pulls in mffm-fftw1c2, and this results
in a file conflict, which needs to be resolved. I don't know what the
proper way of resolving it is.

The entire piuparts log file is around 170 kilobytes, so I won't attach
it to this bug report, but I'd be happy to send it on request. For
reference, the command line used was:

sudo piuparts -ab sarge.tar.gz -d sarge -d etch -d sid mffm-fftw-dev

where sarge.tar.gz was created with

sudo piuparts -as sarge.tar.gz -d sarge hello

-- 
Do, or do not. There is no angst.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#338393: sbcl: installation fails, register-common-lisp-implementation not found

[Lars Wirzenius]

Package: sbcl
Version: 1:0.9.6.0-7
Severity: serious
Justification: package doesn't install without common-lisp-controller

Testing sbcl with piuparts, I find that installation fails:

0m9.6s ERROR: Command failed (status=25600): "chroot /tmp/tmpUMtHi0
apt-get -y install 'sbcl'"
  Reading package lists...
  Building dependency tree...
  Suggested packages:
sbcl-common slime
  Recommended packages:
binfmt-support
  The following NEW packages will be installed:
sbcl
  0 upgraded, 1 newly installed, 0 to remove and 9 not upgraded.
  Need to get 9141kB of archives.
  After unpacking 32.3MB of additional disk space will be used.
  Get:1 http://liw.iki.fi sid/main sbcl 1:0.9.6.0-7 [9141kB]
  Fetched 9141kB in 0s (10.8MB/s)
  Selecting previously deselected package sbcl.
  (Reading database ... 7532 files and directories currently installed.)
  Unpacking sbcl (from .../sbcl_1%3a0.9.6.0-7_i386.deb) ...
  Setting up sbcl (0.9.6.0-7) ...
  /var/lib/dpkg/info/sbcl.postinst: line
22: /usr/sbin/register-common-lisp-implementation: No such file or
directory
  dpkg: error processing sbcl (--configure):
   subprocess post-installation script returned error exit status 1
  Errors were encountered while processing:
   sbcl
  E: Sub-process /usr/bin/dpkg returned an error code (1)

At first glance, this would indicate a missing dependency on
common-lisp-controller, but looking at the postinst script, it seems
more likely that the bug is here:

if [ -x /usr/lib/common-lisp/bin/sbcl.sh ]; then
/usr/sbin/register-common-lisp-implementation sbcl
fi

The "if" tests for the wrong file, I think.


-- 
Crappy tools are not worth it. Find or make better ones.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#338255: wzdftpd: missing ucf dependency breaks upgrade from sarge

[Lars Wirzenius]

Package: wzdftpd
Version: 0.5.5-3
Severity: serious
Justification: breaks upgrades

wzdftpd has one use of ucf in its maintainer scripts (postinst), so it
should have a dependency on ucf. This comes up when testing upgrades
from sarge to etch to sid (with piuparts), although the test only gets
to the upgrade to etch before failing. From the log file:

  Setting up wzdftpd (0.5.5-1) ...
  Installing new version of config file /etc/wzdftpd/file_ginfo.txt ...
  Installing new version of config file /etc/wzdftpd/file_help.txt ...
  Installing new version of config file /etc/wzdftpd/file_swho.txt ...
  Installing new version of config file /etc/wzdftpd/file_user.txt ...
  Installing new version of config file /etc/wzdftpd/file_group.txt ...
  Installing new version of config file /etc/wzdftpd/file_rules.txt ...
  Installing new version of config file /etc/wzdftpd/file_users.txt ...
  Installing new version of config file /etc/wzdftpd/file_who.txt ...
  Installing new version of config file /etc/wzdftpd/file_groups.txt ...
  Installing new version of config file /etc/wzdftpd/file_vfs.txt ...
  /var/lib/dpkg/info/wzdftpd.postinst: line 16: ucf: command not found
  dpkg: error processing wzdftpd (--configure):
   subprocess post-installation script returned error exit status 127

The entire log file is about 180 kilobytes, so I'm not attaching it, but
I'd be glad to mail on request.

The command I used was: "sudo piuparts -ab sarge.tar.gz -d sarge -d etch
-d sid wzdftpd" where sarge.tar.gz was created via "sudo piuparts -as
sarge.tar.gz -d sarge hello". The sarge.tar.gz is not necessary, but it
speeds things up quite a bit if one needs to run the test many times.


-- 
Close your mind to stress and pain, hack till you're no longer sane.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#338253: wims-common: postinst doesn't check errors, assumes "wims" user, and purge leaves cruft

[Lars Wirzenius]

Package: wims-common
Version: 3.28-6.1
Severity: serious
Justification: violates a "must" in policy

When testing wims-common with piuparts, I see several problems. To begin
with, it assumes that the "wims" user and group exists and is dedicated
for its use, yet does not even try to create the user. The piuparts log
file snippet:

0m14.8s DUMP:   Setting up wims-common (3.28-6.1) ...
0m14.8s DUMP:   chown: `wims.wims': invalid user

Further, the postinst script does not notice this failure and continues
as if everything was correct. This is in violation of Debian Policy,
3.10. Maintainer scripts, which says (in part): "Errors which occur
during the execution of an installation script must be checked and the
installation must not continue after an error."

Finally, after the package is purged, the package leaves files behind on
the system:

0m16.7s ERROR: Package purging left files on system:
  /usr/lib/wims
  /usr/lib/wims/public_html
  /usr/lib/wims/public_html/bases
  /usr/lib/wims/public_html/gifs
  /usr/lib/wims/public_html/html
  /usr/lib/wims/public_html/images
  /usr/lib/wims/public_html/java
  /usr/lib/wims/public_html/mathfonts
  /usr/lib/wims/public_html/modules
  /usr/lib/wims/public_html/msg
  /usr/lib/wims/public_html/scripts
  /usr/lib/wims/public_html/sessions
  /usr/lib/wims/public_html/units
  /var/lib/wims
owned by: wims-common
  /var/lib/wims/bases

This is "just cruft", but still shouldn't happen.

-- 
Just GNU it!



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#338243: vrms: uses diagnostics.pm, needs to depend on perl

[Lars Wirzenius]

Package: vrms
Version: 1.10
Severity: serious
Justification: package is uninstallable (unless you happen to have perl)

vrms has no explicit dependencies, but it seems it tries to use the
module diagnostics.pm, which is not included perl-base, so a dependency
on perl would seem to be in order (or else the code might have to be
modified). Without this dependency, if you don't happen to already have
perl (and not just perl-base) installed, installation fails, as shown by
the piuparts log file snippet below. This is admittedly an unusual
scenario, but it is possible, and violates a release criterion (see
http://release.debian.org/etch_rc_policy.txt, point 2, "Dependencies").

0m9.3s ERROR: Command failed (status=25600): "chroot /tmp/tmpak7UFJ
apt-get -y install 'vrms'"
  Reading package lists...
  Building dependency tree...
  The following NEW packages will be installed:
vrms
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 9792B of archives.
  After unpacking 94.2kB of additional disk space will be used.
  Get:1 http://liw.iki.fi sid/main vrms 1.10 [9792B]
  Fetched 9792B in 0s (234kB/s)
  Selecting previously deselected package vrms.
  (Reading database ... 7550 files and directories currently installed.)
  Unpacking vrms (from .../apt/archives/vrms_1.10_all.deb) ...
  Setting up vrms (1.10) ...

  An invocation of vrms has been added to the set of cron jobs run on a
  monthly basis, so that you will get a periodic reminder of non-free
  packages which are installed on your system.  Here is the current
list:

  Can't locate diagnostics.pm in @INC (@INC
contains: /etc/perl /usr/local/lib/perl/5.8.7 /usr/local/share/perl/5.8.7 
/usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 
/usr/local/lib/site_perl .) at /usr/bin/vrms line 4.  BEGIN failed--compilation 
aborted at /usr/bin/vrms line 4.
  dpkg: error processing vrms (--configure):
   subprocess post-installation script returned error exit status 2
  Errors were encountered while processing:
   vrms
  E: Sub-process /usr/bin/dpkg returned an error code (1)


-- 
You need fewer comments, if you choose your names carefully.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#334651: FTBFS: Missing build-dependency on texinfo

[Lars Wirzenius]

I'm about to do a non-maintainer upload of jlint with the attached
patch, as part of the bug squashing party going on this weekend. The bug
has been open for about 10 days now, the fix is trivial, there aren't
any lintian or linda errors related to the change (there are some
warnings about missing manpages and an old FSF address, but I'd like to
keep the patch minimal), and so I'll upload directly, not via a delayed
queue.

-- 
I'm a Luddite with neophilia
diff -u jlint-3.0/debian/changelog jlint-3.0/debian/changelog
--- jlint-3.0/debian/changelog
+++ jlint-3.0/debian/changelog
@@ -1,3 +1,11 @@
+jlint (3.0-4.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Added build-dependency on texinfo, suggested by Matt Kraai.
+    Closes: #334651.
+
+ -- Lars Wirzenius <[EMAIL PROTECTED]>  Sat, 29 Oct 2005 00:31:00 +0300
+
 jlint (3.0-4) unstable; urgency=low
 
   * Fix another "cast from 'const void*' to 'int' loses precision" error.
diff -u jlint-3.0/debian/control jlint-3.0/debian/control
--- jlint-3.0/debian/control
+++ jlint-3.0/debian/control
@@ -2,7 +2,7 @@
 Section: devel
 Priority: optional
 Maintainer: Ganesan Rajagopal <[EMAIL PROTECTED]>
-Build-Depends: debhelper (>> 3.0.0), texi2html, tetex-extra, zlib1g-dev
+Build-Depends: debhelper (>> 3.0.0), texi2html, tetex-extra, zlib1g-dev, texinfo
 Standards-Version: 3.6.2
 
 Package: jlint

Bug#306123: syslinux: FTBFS: undefined reference to `memcpy' and static declaration of 'crc_32_tab' follows non-static declaration)

[Lars Wirzenius]

Hi,

this bug caught my eye when browsing the list of release critical bugs
to find things I could help fix (possibly by doing an NMU). 

Andreas Jochens, I'd like to ask for clarification for a point about the
patch you included:

--- ../tmp-orig/syslinux-2.11/memdisk/Makefile  2004-01-24
21:37:22.0 +
+++ ./memdisk/Makefile  2005-04-24 11:55:47.371139174 +
@@ -39,7 +39,7 @@
 SSRC = init.S16
 NASMSRC  = memdisk.asm init32.asm
 
-all: memdisk e820test
+all: memdisk
 
 # tidy, clean removes everything except the final binary
 tidy:

You disable building of e820test. The package builds for me without this 
change, 
so I wonder, is it necessary?

Juan Cespedes, if you oppose me (or someone) doing an NMU on syslinux, please 
say 
so within a couple of day, thanks.

-- 
Rule #13 for successful communication: don't do Latin quotations


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#331109: libcsv-ruby1.8: uninstallable due to file conflict with libruby1.8

[Lars Wirzenius]

Package: libcsv-ruby1.8
Version: 1.2.2-1
Severity: grave
Justification: cannot be installed

It doesn't seem to be possible to install libcsv-ruby1.8 because of a
file conflict with libruby1.8, which it depends on. See transcript
below.

[EMAIL PROTECTED]:/# apt-get install libcsv-ruby1.8
Reading package lists... Done
Building dependency tree... Done
The following extra packages will be installed:
  libruby1.8
The following NEW packages will be installed:
  libcsv-ruby1.8 libruby1.8
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 1417kB of archives.
After unpacking 5681kB of additional disk space will be used.
Do you want to continue [Y/n]?
Get:1 http://liw.iki.fi sid/main libruby1.8 1.8.3-1 [1407kB]
Get:2 http://liw.iki.fi sid/main libcsv-ruby1.8 1.2.2-1 [10.4kB]
Fetched 1417kB in 0s (7845kB/s)
Selecting previously deselected package libruby1.8.
(Reading database ... 7538 files and directories currently installed.)
Unpacking libruby1.8 (from .../libruby1.8_1.8.3-1_i386.deb) ...
Selecting previously deselected package libcsv-ruby1.8.
Unpacking libcsv-ruby1.8 (from .../libcsv-ruby1.8_1.2.2-1_all.deb) ...
dpkg: error
processing /var/cache/apt/archives/libcsv-ruby1.8_1.2.2-1_all.deb
(--unpack):
 trying to overwrite `/usr/lib/ruby/1.8/csv.rb', which is also in
package libruby1.8
Errors were encountered while processing:
 /var/cache/apt/archives/libcsv-ruby1.8_1.2.2-1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
[EMAIL PROTECTED]:/#




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#330373: dvbtune: creates /dvb

[Lars Wirzenius]

Package: dvbtune
Version: 0.5-4
Severity: serious

>From the postinst:

if [ -e /sbin/MAKEDEV ]
then
/sbin/MAKEDEV dvb
fi

MAKEDEV *must* be run from within /dev (i.e., it creates files in the
current working directory). Because the postinst doesn't do so, it
inadvertently creates /dvb and device files in there, and thus violates
policy 9.1.1 (hence the severity).



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#328327: libdb2: doesn't have postrm with ldconfig

[Lars Wirzenius]

Package: libdb2-dev
Version: 2:2.7.7.0-10
Severity: serious
Justification: Clint said it's serious on irc 

libdb2 doesn't seem to have a postrm script that would run ldconfig,
meaning that after libdb2-dev is installed, and libdb2, libdb2-util, and
libdb2-dev are removed, there is a /usr/lib/libdb2.so.2 dangling symlink
on the filesystem. Running ldconfig manually fixes this.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#318693: FTBFS: Missing Build-Depends (patch)

[Lars Wirzenius]

pe, 2005-08-12 kello 11:37 +0200, Jerome Warnier kirjoitti:
> tags 318693 patch
> thank
> 
> Please find here a very simple patch to fix this (hope it helps fixing
> it faster).

Thanks. I'm on vacation until the end of the week. I'll fix it when I
get back.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#276172: logrotate: Pre/post rotate scripts don't get the log filenames as argument

[Lars Wirzenius]

su, 2005-05-15 kello 23:59 +0100, Paul Martin kirjoitti:
> On Mon, May 16, 2005 at 12:51:48AM +0300, Lars Wirzenius wrote:
> > I've verified that Brice Figureau's bug is valid, and that his patch
> > fixes it. Attached is a patch complete with an updated debian/changelog
> > as well. I will NMU it shortly (since we're in a 0-day NMU period) and
> > release managers to accept the change for sarge.
> 
> If you'd read the bug, you'd notice that I'd noted the bug, considered 
> it minor (very few scripts rely on this undocumented feature), and noted 
> that logrotate was already frozen.

I disagree with you about the severity of the bug. I agree with Alex
Owen that breaking log rotation scripts written by sysadmins is bad and
can cause data loss. It doesn't matter that no Debian packages rely on
it.

The behavior does indeed seem to be undocumented. However, it has worked
like that for many years now (since before woody), and so I'd say it is
a documentation bug and it is not unreasonable to expect the behavior to
continue.

That a package is frozen does not prevent fixing of release critical
bugs.

> Fixing a bug that's only just THIS DAY had its priority changed to 
> critical, and not at least giving the maintainer time to look at it is 
> downright unfriendly behaviour. This is the second time you've done this 
> to me. Take time to read the dates and times on the bug reports.

I did notice the dates. I ignored the fact that the bug had just been
upgraded. A large part of the reason for this was your decision to
downgrade it from important to normal.

The fact that we are, in fact, in a 0-day NMU mode, helped my decision,
of course. That it was going to make you angry again did not deter me.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#276172: logrotate: Pre/post rotate scripts don't get the log filenames as argument

[Lars Wirzenius]

I've verified that Brice Figureau's bug is valid, and that his patch
fixes it. Attached is a patch complete with an updated debian/changelog
as well. I will NMU it shortly (since we're in a 0-day NMU period) and
release managers to accept the change for sarge.

diff -ruN old/debian/changelog logrotate-3.7/debian/changelog
--- old/debian/changelog	2005-05-15 23:50:43.0 +0300
+++ logrotate-3.7/debian/changelog	2005-05-16 00:43:15.0 +0300
@@ -1,3 +1,12 @@
+logrotate (3.7-2.1) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * When calling execlp to run scripts, give execlp all the arguments it
+needs. This way, it doesn't eat the first actual command line 
+argument (argv[1]). Fix by Brice Figureau. Closes: #276172.
+
+ -- Lars Wirzenius <[EMAIL PROTECTED]>  Mon, 16 May 2005 00:40:00 +0300
+
 logrotate (3.7-2) unstable; urgency=high
 
   * Added commented out stuff in debian/rules to build a 
diff -ruN old/logrotate.c logrotate-3.7/logrotate.c
--- old/logrotate.c	2004-02-05 20:42:13.0 +0200
+++ logrotate-3.7/logrotate.c	2005-05-16 00:40:14.0 +0300
@@ -110,7 +110,7 @@
 close(fd);
 
 if (!fork()) {
-	execlp(filespec, logfn, NULL);
+	execlp(filespec, filespec, logfn, NULL);
 	exit(1);
 }
 

Bug#308398: irmp3: missing dependency on adduser and wrong assumptions in postrm

[Lars Wirzenius]

pe, 2005-05-13 kello 11:42 -0600, Roberto Mello kirjoitti:
> On Fri, May 13, 2005 at 07:52:26PM +0300, Lars Wirzenius wrote:
> > Unless there are objections, I will NMU irmp3 using Russ's patch (full
> > diff with changelog entry attached) tomorrow, with an upload to unstable
> > and a request to debian-release@lists.debian.org for the release
> > managers to consider letting the new version into testing.
> 
> Yes, please do (and thanks!).
> 
> My irmp3 package is fairly out-of-synch with upstream. I'll try to remedy
> that in the near future.
> 
> Sorry about the bug in the package.

The release managers decided that it is better to remove the package
from sarge, so I'll refrain from doing the NMU, since there is much less
hurry to fix the problem in sid.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#308398: irmp3: missing dependency on adduser and wrong assumptions in postrm

[Lars Wirzenius]

Unless there are objections, I will NMU irmp3 using Russ's patch (full
diff with changelog entry attached) tomorrow, with an upload to unstable
and a request to debian-release@lists.debian.org for the release
managers to consider letting the new version into testing.

diff -ruN old/debian/changelog irmp3-0.4.3pre6/debian/changelog
--- old/debian/changelog	2002-04-30 07:13:47.0 +0300
+++ irmp3-0.4.3pre6/debian/changelog	2005-05-13 19:27:41.0 +0300
@@ -1,3 +1,12 @@
+irmp3 (0.4.3pre6-3.1) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * Applied patch from Russ Allbery ([EMAIL PROTECTED]): add depend on
+adduser and move postrm to prerm (since deluser can't be used in
+postrm, since it is non-essential). Closes: #308398.
+
+ -- Lars Wirzenius <[EMAIL PROTECTED]>  Fri, 13 May 2005 18:47:00 +0300
+
 irmp3 (0.4.3pre6-3) unstable; urgency=low
 
   * The oh-crap-there-are-so-many-details release
diff -ruN old/debian/control irmp3-0.4.3pre6/debian/control
--- old/debian/control	2002-04-30 07:11:04.0 +0300
+++ irmp3-0.4.3pre6/debian/control	2005-05-13 18:47:13.0 +0300
@@ -7,7 +7,7 @@
 
 Package: irmp3
 Architecture: any
-Depends: ${shlibs:Depends}, mpg321 | mpg123
+Depends: ${shlibs:Depends}, adduser, mpg321 | mpg123
 Suggests: lirc (>= 0.6), lcdproc
 Description: A Multimedia Audio Jukebox application.
  With irmp3 you can control mpg321 (currently, other players are
diff -ruN old/debian/postrm irmp3-0.4.3pre6/debian/postrm
--- old/debian/postrm	2002-04-30 06:08:59.0 +0300
+++ irmp3-0.4.3pre6/debian/postrm	1970-01-01 02:00:00.0 +0200
@@ -1,10 +0,0 @@
-#!/bin/sh
-
-set -e
-
-# Clean up the irmp3 user if it exists.
-if test -n "`getent passwd irmp3`"; then
-	deluser --remove-home irmp3
-fi
-
-#DEBHELPER#
diff -ruN old/debian/prerm irmp3-0.4.3pre6/debian/prerm
--- old/debian/prerm	1970-01-01 02:00:00.0 +0200
+++ irmp3-0.4.3pre6/debian/prerm	2005-05-13 18:47:13.0 +0300
@@ -0,0 +1,10 @@
+#!/bin/sh
+
+set -e
+
+# Clean up the irmp3 user if it exists.
+if test -n "`getent passwd irmp3`"; then
+	deluser --remove-home irmp3
+fi
+
+#DEBHELPER#

Bug#306838: jargon-text: FTBFS: ERROR at cmdline.c:96: Unknown option -no-references

[Lars Wirzenius]

ti, 2005-05-03 kello 01:27 +0100, Paul Martin kirjoitti:
> This FTBFS will go away when elinks 0.10.4-3 reaches "testing"... but 
> your patch means that there's going to be a bug raised because it will 
> then FTBFS into a nice-looking text file.
> Filing an FTBFS on an "architecture: all" package that contains only a 
> plain text file, and then doing a zero-day NMU within 48 hours is not a 
> nice thing to do. It's not that important a package to warrant such 
> urgency.

Andreas opened the bug. I did the NMU. I meant to help things, not make
them worse. Sorry about any confusion.

Since this bug is release critical, one of two things needs to happen
before sarge can release: either the bug is fixed or jargon-text is
removed from sarge. I think the former is the better option. This is why
I made the NMU. I uploaded it immediately because we are very close to
freezing sarge, and this means that release critical bugs should be
closed as quickly as possible. That is why the project is in a 0-day NMU
period until the freeze.

Removing the option that causes the build to fail with the version of
jargon-text in sarge was the faster way to get the fixed jargon-text
into sarge.

I compared the versions before making the upload. I did not find the new
version (the one in my NMU) to be terribly formatted, but I guess that
is a matter of taste.

> The correct long-term fix for this bug is to build-depend on the right 
> version of elinks (which ought to enter testing in a few days). If 
> elinks 0.10.4 doesn't enter testing, your NMU package will be the one in 
> sarge.

Steve Langasek told me on IRC that it is unlikely that the new elinks
will get into sarge in time. With my NMU, jargon-text could still stay
in sarge (whether the formatting is good or not). With your MU, as far
as I understand, jargon-text needs to be removed from sarge, since it
can't be built with sarge tools.

Since my NMU is not yet in sarge, your MU will overwrite my NMU at about
22:00 UTC today, when the next dinstall run happens. This means the bug
won't be fixed in sarge. If you prefer my NMU over removal from sarge,
you could mail debian-release today (well in advance of 22:00 UTC).

Note that anything I say about package removal in this mail is based on
my own understanding, it is not advice from release managers.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#304124: unison: FTBFS: missing build-depends

[Lars Wirzenius]

su, 2005-05-01 kello 01:12 +0200, Sylvain LE GALL kirjoitti:
> On Sat, Apr 30, 2005 at 05:31:55PM +0300, Lars Wirzenius wrote:
> > I've checked that the unison package will build with the
> > build-dependency change suggested by Aurelien Jarno. The attached patch
> > also fixes debian/unison-doc-base, and I propose to make a
> > non-maintainer upload with it later today (since we're in a 0-day NMU
> > period).
> > 
> > Hopefully this is helpful. Happy hacking.
> 
> Happy unuseful upload

It seems to fix the bug. Does it not?

> Please remove your upload. You should have asked me about this, packages
> are prepared to correct most of the bugs of unison. 

We are very, very close to a freeze (see debian-devel-announce mail from
today) and in a 0-day NMU period. This means that it is important to fix
bugs, especially release critical bugs, and one of the ways this is
dealt with is by not waiting the usual week or so for the maintainer to
react before doing an NMU. Anyway, an NMU is not a criticism of you, it
is an attempt to make sure the package is as good as possible, and
therefore Debian is as good as possible.

If you want to make a maintainer upload, go right ahead. Nothing in my
NMU stops you from doing that.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#304663: ximian-connector: FTBFS: Cannot find evolution libs

[Lars Wirzenius]

Daniel Schepler <[EMAIL PROTECTED]>:
> checking for gawk... no
> checking for mawk... mawk
> checking whether make sets $(MAKE)... yes
> checking Evolution version... configure: error: Evolution development 
> libraries not installed
> make: *** [config.status] Error 1

Hm. This is one more FTBFS I can't reproduce in a sid or sarge pbuilder
environment. Same version of ximian-connector. In both cases, the test
succeeds:

> checking Evolution version... 2.0.4

The package then continues to build successfully to the end. Either something 
got fixed or there's something weird going on.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#306248: statdataml: FTBFS: Build-Depends cannot be fulfilled in sarge

[Lars Wirzenius]

Andreas Jochens <[EMAIL PROTECTED]>:
> Building statdataml testing main amd64...
> Reading Package Lists...
> Building Dependency Tree...
> E: Build-dependencies for statdataml could not be satisfied.

I don't seem to be able to reproduce this with sarge or sid pbuilder
setups, or in a sarge or sid chroot, all on i386. For me, the package 
builds without problems.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#304124: unison: FTBFS: missing build-depends

[Lars Wirzenius]

I've checked that the unison package will build with the
build-dependency change suggested by Aurelien Jarno. The attached patch
also fixes debian/unison-doc-base, and I propose to make a
non-maintainer upload with it later today (since we're in a 0-day NMU
period).

Hopefully this is helpful. Happy hacking.

diff -u unison-2.9.1/debian/control unison-2.9.1/debian/control
--- unison-2.9.1/debian/control
+++ unison-2.9.1/debian/control
@@ -2,7 +2,7 @@
 Section: net
 Priority: optional
 Maintainer: Sylvain Le Gall <[EMAIL PROTECTED]>
-Build-Depends: debhelper (>= 4.0.0), ocaml-nox-3.08, liblablgtk-ocaml-dev, dpatch, chrpath
+Build-Depends: debhelper (>= 4.0.0), ocaml-nox-3.08.3, liblablgtk-ocaml-dev, dpatch, chrpath
 Standards-Version: 3.6.1.0
 
 Package: unison
diff -u unison-2.9.1/debian/changelog unison-2.9.1/debian/changelog
--- unison-2.9.1/debian/changelog
+++ unison-2.9.1/debian/changelog
@@ -1,3 +1,14 @@
+unison (2.9.1-2.1) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * Updated build-dependency from ocaml-nox-3.08 to ocaml-nox-3.08.3
+as suggested by Aurelien Jarno. Closes: #304124 (which is release
+critical, hence the high urgency).
+  * Changed debian/unison.doc-base to refer to unison-manual.txt instead
+of unison-manual.text.
+
+ -- Lars Wirzenius <[EMAIL PROTECTED]>  Sat, 30 Apr 2005 17:13:00 +0300
+
 unison (2.9.1-2) unstable; urgency=medium
 
   * Version to fix maintainer fields
diff -u unison-2.9.1/debian/unison.doc-base unison-2.9.1/debian/unison.doc-base
--- unison-2.9.1/debian/unison.doc-base
+++ unison-2.9.1/debian/unison.doc-base
@@ -13,7 +13,7 @@
 Files: /usr/share/doc/unison/unison-manual.ps.gz
 
 Format: text
-Files: /usr/share/doc/unison/unison-manual.text.gz
+Files: /usr/share/doc/unison/unison-manual.txt.gz
 
 Format: HTML
 Index: /usr/share/doc/unison/unison-manual.html

Bug#305411: cal3d: FTBFS: cp: cannot stat `debian/tmp//usr/share/doc/libcal3d-doc/html/functions_rela.html': No such file or directory

[Lars Wirzenius]

la, 2005-04-30 kello 13:03 +0200, Michael Koch kirjoitti:
> On Sat, Apr 30, 2005 at 02:32:07PM +0300, Lars Wirzenius wrote:
> > I've verified the build failure and tested the fix. Attached is a patch
> > for an NMU I intend to make later today (since we're in a 0-day NMU
> > period), unless there are objections.
> > 
> > Hopefully this is helpful. Happy hacking.
> 
> I'm happy with this patch. Are you okay when I prepare a -2 and you 
> sponsor it for me?

I'm okay with that. Thanks for the quick response.




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]