yaird (0.0.12-24ubuntu1) hardy; urgency=low
* Merge from Debian unstable. Remaining Ubuntu changes:
- debian/control:
+ changing maintainter to "Ubuntu MOTU Developers"
- debian/mkinitrd.yaird
+ update-initramfs compatibility
yaird (0.0.12-24) unstable; u
Uploaded, thanks for your contribution.
** Changed in: yaird (Ubuntu)
Assignee: Andrea Gasparini (gaspa) => (unassigned)
Status: Incomplete => Fix Committed
--
Merge with version 0.0.12-24 from Debian unstable
https://bugs.launchpad.net/bugs/156712
You received this bug notification
The build log is attached, here's the install through dpkg:
# dpkg -i yaird_0.0.12-24ubuntu1_i386.deb
(Reading database ... 26066 files and directories currently installed.)
Preparing to replace yaird 0.0.12-23ubuntu1 (using
yaird_0.0.12-24ubuntu1_i386.deb) ...
Unpacking replacement yaird ...
Looks good to me. Have you checked that it builds and installs correctly in an
hardy environment?
Please attach a build log and installation report.
--
Merge with version 0.0.12-24 from Debian unstable
https://bugs.launchpad.net/bugs/156712
You received this bug notification because you are a me
ok. let's do it. ;)
Cesare, take a look if now I done all and well... thanks. ;)
** Attachment added: "yaird_0.0.12-24ubuntu1.debdiff"
http://launchpadlibrarian.net/10196009/yaird_0.0.12-24ubuntu1.debdiff
--
Merge with version 0.0.12-24 from Debian unstable
https://bugs.launchpad.net/bugs/15
We better patch it then, because I have the impression that there is no
official support for yaird (at least this
https://bugs.edge.launchpad.net/ubuntu/+source/yaird/+bug/129828/comments/1
seems to imply so).
--
Merge with version 0.0.12-24 from Debian unstable
https://bugs.launchpad.net/bugs/15
Ok, i took the last version for the merge.
About the patch, it seems it's still needed, this is the output in Hardy
with installed the debian version 0.0.12-24:
[EMAIL PROTECTED]:/mnt/sorgenti/ubuntu/yaird$ sudo dpkg-reconfigure
linux-image-`uname -r`
Running depmod.
mkinitrd.yaird: opzione non
You shouldn't look at debian/rules. If you check your build log, you
should see something like:
make[2]: Entering directory `/tmp/buildd/yaird-0.0.12/doc'
/usr/bin/xmlto xhtml-nochunks yaird.xml
This is part of the upstream makefile, simply entering the doc directory and
executing the xmlto comm
Yes, i start the merge when was available versione 0.0.12-23.
So, I'll regain the sources and merging, asap.
For the xml issue, I'll take a look, perhaps I misunderstand the debian/rules.
Thanks.
--
Merge with version 0.0.12-24 from Debian unstable
https://bugs.launchpad.net/bugs/156712
You rece
I would like to add that I changed your bug description (was talking
about wesnoth) and the title. It seems you have been working on a
previous debian version, as most probably 0.0.12-24 was not available
when you first prepared your patch.
--
Merge with version 0.0.12-24 from Debian unstable
htt
** Summary changed:
- Merge with version 0.0.12-23 from Debian unstable
+ Merge with version 0.0.12-24 from Debian unstable
** Description changed:
Binary package hint: yaird
- Binary package hint: yaird
-
- Merge wesnoth 0.0.12-32 from Debian unstable.
+ Merge yaird 0.0.12-24 from Debian
11 matches
Mail list logo
