Package: wnpp
I'm orphaning dmachinemon. I don't need it and I don't use it anymore.
No active upstream, probably doesn't work.
Package: dmachinemon
Priority: optional
Section: admin
Installed-Size: 244
Maintainer: Junichi Uekawa <[EMAIL PROTECTED]>
Architecture: amd64
Package: wnpp
It doesn't work well and it's not maintained well in
upstream. Recently, it was just fighting against bit-rotting.
gnome-alsamixer etc. will work better.
Package: gamix
Priority: extra
Section: sound
Installed-Size: 196
Maintainer: Junichi Uekawa <[EMAIL PROTECTED]&
Hi,
> By default, the current version of nmudiff opens a new bug against the
> package and attaches the diff to it. I recently submitted wishlist
> #370056 against devscripts so nmudiff behaves like this only if --new is
> passed, and by default sends the patch to the bugs the NMU fixes.
I don't
> > I just a thought search debian/ include package.
> > I'd try the idea out, use gonzui.
> >
> > http://debian-src.devel.jp
>
> Nice idea.
>
> What exactly is included in the search? All source packages? All binary &
> source packages?
What's included in debian/ directory of source packag
Hi,
> > > what's a non-linear movie editor?
> >
> > http://en.wikipedia.org/wiki/Non-linear_editing_system
> >
> > The term is quite common for a video editing system.
>
> Actually, I was aware of that. When the description talks about an
> amateur target audience, I was simply questioning the
Hi
I've got hold of an intel mac that I'm interested in getting Debian
running. I've seen quite a few folks running Debian on MacBook Pro at
Debconf in Mexico, and I'm surprised that there aren't Debian
packages.
The things I'm planning on doing are follows:
Code packages
fix gnu-efi (b
Hi,
> > fix gnu-efi (bug: #376000)
>
> I'm sure this is a dupe of a bug I filed, but I can't find it right now.
Your bug is meant to be already fixed (#355252), but I see there are
some deviations between Debian and Ubuntu (which you seem to
maintain), I'm suspecting there might be problems
Hi,
> > Debian-installer:
> > elilo-installer is not built for ia32
> > (http://lists.debian.org/debian-boot/2006/06/msg00185.html)
> >
> > Anyone already working on these stuff?
>
> There has been some work done on the installer (including uploading elilo
> installer for i386 to the archive
Hi,
> > Your bug is meant to be already fixed (#355252), but I see there are
> > some deviations between Debian and Ubuntu (which you seem to
> > maintain), I'm suspecting there might be problems with Debian code
> > which is only updated about 3 months ago.
>
> Ok, that's a possibility - there w
Hi,
>
> Worst case: You have to abuse the firmware update released to facilitate
> Boot camp, and have that boot normal lilo.
> Perhaps not as nice as having EFI boot a bootload, or running a bootloader
> as an EFI application, but
> I think that is what most people are currently doing.
I've t
>
> Code packages
s/Code/Core/
> fix elilo (bug: #376002)
So far I had zero luck with using elilo for loading kernel.
elilo itself starts to be starting up and is doing something, but
the kernel does not look like it's booted up at all.
Has anyone got it working?
regards,
junic
retitle 376000 gnu-efi: efilib too old
thanks
Hi,
I'm now trying to build rEFIt against gnu-efi, and I'm having a
problem in that what's contained in gnu-efi is too old. From what I
can see, it contains efilib from 1998 or so. The current EFI spec is
at 1.1, which is released sometime around 200
Hi,
> ITP rEFIt (bug: #375999)
> (I've filed bugs to track their progress)
I've uploaded a package. There is a gptsync command in /sbin/gptsync,
which should be a good start. Including calls to gptsync in
debian-installer before calling lilo/grub should ease a few parts.
I've noticed afte
Hi,
> > -- Forwarded Message --
> > ...
> > ...
> > Current work around is to reboot into rEFIt and run gptsync, and
> > then run d-i from CDROM, and then configure the bootloader.
> >
>
> could you please give more details about this?
# apt-get install refit (when it ente
Hi,
> >
> > # apt-get install refit (when it enters past the NEW queue)
> > # gptsync /dev/sda
> >
> > I've temporarily put refit packages on:
> > http://www.netfort.gr.jp/~dancer/tmp/20060702/
>
> I chrooted into /target from the second console of d-i and
> copied the deb package I got from yo
> >> 1) compile docs pre-build-time; or
> >> 2) compile docs in build-time
> >
> > Definitely the latter. We build stuff at build time for a reason,
> > architecture-specific or -independent alike.
>
> That depends a bit on the stuff. A lot of maintainers think running
> auto* to generate conf
At 04 Jul 2006 17:57:29 +0200,
Paul Seelig wrote:
>
> [EMAIL PROTECTED] (Free Ekanayaka) writes:
>
> > This package contains a collection of drumkits for Hydrogen, a
> > sample based drum machine/step sequencer.
> >
> This is not a single package but actually a collection of various
> packages
Hi,
MacBook has a i945 integrated graphic device. To configure, I chose
'intelfb' (not imacfb driver, which seems only to garble the screen
for me) driver for the kernel.
For X, I managed to make a dual-screen setup, so that I can do
presentation on projector and stuff.
Here's my xorg.conf:
#
> > auto-apt update
> > Downloading http://ftp.jp.debian.org/debian//dists/unstable
> > Contents-amd64.gz ...
> > Warning: "+number" syntax is deprecated, please use "-n +number"
> >
> > put: 0 files, 0 entries done (0 sec)
>
> FWIW, this works for me, even though I get the same warnings (which
Hi,
> > MacBook has a i945 integrated graphic device. To configure, I chose
> > 'intelfb' (not imacfb driver, which seems only to garble the screen
> > for me) driver for the kernel.
> >
> > For X, I managed to make a dual-screen setup, so that I can do
> > presentation on projector and stuff.
>
Hi,
> > > It seems like it would be quite taxing on the autobuilders to have to pull
> > > something like docbook (and its chain of dependencies) into a pbuilder
> > > just
> > > to recompile a manpage that doesn't change between architectures.
> > >
> > AIUI, the autobuilders use sbuild and don
> by viper2.netfort.gr.jp with SMTP; 6 Jul 2006 22:53:24 -0000
> Date: Fri, 07 Jul 2006 07:53:24 +0900
> Message-ID: <[EMAIL PROTECTED]>
> From: Junichi Uekawa <[EMAIL PROTECTED]>
> To: "Steinar H. Gunderson" <[EMAIL PROTECTED]>
> Cc: Junichi Uekawa
reopen 368674
reassign 368674 fuse-utils
thanks
Hi,
>It works today. Now I remember I installed fuse-utils yesterday, which
>means the fuse group did not still exist when udev started. Restarting
>udev (or rebooting the system, obviously) fixes the issue.
>This behavior seems like the only one p
Hi,
I've been worried about this small bug where hwclock waits for timeout in while
booting,
with a message:
select() to /dev/rtc to wait for clock tick timed out.
The machine is a MacBook, and I see references to this message on
dual-core Intel processors, so it looks like a generic problem.
tfort.gr.jp.netfort.gr.jp) (127.0.0.1)
> by viper2.netfort.gr.jp with SMTP; 8 Jul 2006 16:27:16 -0000
> Date: Sun, 09 Jul 2006 01:27:18 +0900
> Message-ID: <[EMAIL PROTECTED]>
> From: Junichi Uekawa <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED] (Marco d'Itri)
&g
At Sun, 09 Jul 2006 09:43:49 +0900,
Junichi Uekawa wrote:
>
> Hi,
> The question I have is how to accomplish this. It looks like hotplug
> is loading stuff at boot-time, and it's not quite clear as how to make
> it not load rtc.
>
> I have tried not loading rtc with bl
Package: wnpp
Hi,
Package: linux-uvc-source
Upstream: svn checkout
http://svn.berlios.de/svnroot/repos/linux-uvc/linux-uvc/trunk
* Copyright (C) 2005-2006
* Laurent Pinchart ([EMAIL PROTECTED])
*
* This program is free software; you can redistribute it and/or modify
*
Hi,
> I've read in a blog that iSight is a standard USB video-class device:
> http://blogs.gnome.org/view/rbultje/2006/07/08/0
I've created a Debian package. I'm having trouble in that it doesn't
seem to work at all with any application I tried. Could people try
out and see if it's going to wo
Hi,
>
> I've created a Debian package. I'm having trouble in that it doesn't
> seem to work at all with any application I tried. Could people try
> out and see if it's going to work?
Actually, I managed to get it working on MacBook with Ekiga.
I'm looking for success/failure reports now.
>
>
Hi,
> > SVN does not track merges across branches, unless you do it in the
> > changelog.
>
> I know, it's a pain in the neck. But still it's a good step forward over
> CVS, and seems to be quite popular in Debian. I hope svn will improve in
> this area.
svn/cvs et cetera are quite linear; dpatc
At Sun, 23 Jul 2006 15:40:55 +0200,
zino wrote:
>
> [1 ]
> On Sun, Jul 23, 2006 at 01:10:59PM +0200, Eduard Bloch wrote:
> > > I installed the following:
> > > linux-uvc-source_0.1.0-1_i386.deb
> > > linux-uvc-tools_0.1.0-1_i386.deb
> >
> > How? Let me guess: you used dpkg --force-... because
Package: module-assistant
Version: 0.10.6
Hi,
> > #!/bin/sh
> > set -e
> >
> > SYSTEMMAP=/boot/System.map-_KVERS_
> >
> > if [ -f $SYSTEMMAP ] ; then
> > depmod -ae -F $SYSTEMMAP _KVERS_
> > elif [ "`uname -r`" = "_KVERS_" ] ; then
> > depmod -a &
> > fi
>
> As of debhe
Hi,
> I would like to ask about common practice in packaging libraries, especially
> their development files. There is a rather old tool like pkg-config.
> It gives standarized interface[1] for getting compiler and linker flags.
> What is your recomendation for adding a .pc files in -dev package?
Hi,
> Before asking here I went thru several mailing list archives. What I
> found was a general argument along the lines of "don't add _that_ hwcap
> because that will increase the size of the list of paths that you have
> to stat(2) in order to find the library and that's slow". In
> part
s half as secure
and one is not notified. And the person is trying to use a ssh.
---
dancer, a.k.a. Junichi Uekawa
Dept. of Knowledge Engineering and Computer Science, Doshisha University.
... Long Live Free Software, LIBERTAS OMNI VINCIT.
garabik> > COLOR:1:cyan:black
garabik> > COLOR:5:brightcyan:black
The same can be said about the default "ls" colors.
It shows directory names with blue on black.
--
dancer, a.k.a. Junichi Uekawa http://www.netfort.gr.jp/~dancer
Dept. of Knowledge Engineering and C
In Thu, 30 Mar 2000 11:10:20 +0100, de profundis "Oliver Elphick"
cum veritas scribat
Try from another user :
ps axu | grep root | wc
and see how many processes root is running ...
--
dancer, a.k.a. Junichi Uekawa http://www.netfort.gr.jp/~dancer
Dept. of Knowledge Engin
l.
Some people do not have sendmail. I use "imput" for internet mail,
and sendmail only reaches my local network.
Maybe I'm weird.
regards,
junichi
--
University: [EMAIL PROTECTED]Netfort: [EMAIL PROTECTED]
dancer, a.k.a. Junichi Uekawa http://www.netfort.gr.
k bugs. It's cosmetically annoying.
I really would love to remove it but there would be quite a lot of
trouble (and fear that legitimate info could be lost).
regards,
junichi
--
University: [EMAIL PROTECTED]Netfort: [EMAIL PROTECTED]
dancer, a.k.a. Junichi Uekawa http://www.n
k bugs. It's cosmetically annoying.
I really would love to remove it but there would be quite a lot of
trouble (and fear that legitimate info could be lost).
regards,
junichi
--
University: [EMAIL PROTECTED]Netfort: [EMAIL PROTECTED]
dancer, a.k.a. Junichi Uekawa http://www.n
rch silo.
Wasn't this the only method a linux on sparc would boot up?
It's rather an important package IMO, should not be removed
from the distribution unless an alternative is found...
regards,
junichi
--
University: [EMAIL PROTECTED]Netfort: [EMAIL PROTECTED]
te info could be lost).
>
> Tell me the bug number and I'll clean it out.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=62770&repeatmerged=yes
so it's 62770.
regards,
junichi
--
University: [EMAIL PROTECTED]Netfort: [EMAIL PROTECTED]
dancer, a.k.a. Junic
junichi
--
University: [EMAIL PROTECTED]Netfort: [EMAIL PROTECTED]
dancer, a.k.a. Junichi Uekawa http://www.netfort.gr.jp/~dancer
Dept. of Knowledge Engineering and Computer Science, Doshisha University.
... Long Live Free Software, LIBERTAS OMNI VINCIT.
hmm... I can't find the deb I thought I made through Google...
## I am still in the NM queue, and playing with Sponsorship makes me refrain
## from claiming any more package.
regards,
junichi
--
University: [EMAIL PROTECTED] Netfort: [EMAIL PROTECTED]
dancer, a.k.a. Junichi Uek
es are identical between releases.
No offence, but wouldn't it be a tad difficult to play around with it,
since deb packages are not just gzipped archives, but ar archive containing
gzipped tar archives?
regards,
junichi
--
University: [EMAIL PROTECTED] Netfort: [EMAIL PROT
The only action taken so far is to update the documentation to reflect
the change of "I" to "j"
regards,
junichi
--
University: [EMAIL PROTECTED]Netfort: [EMAIL PROTECTED]
dancer, a.k.a. Junichi Uekawa http://www.netfort.gr.jp/~dancer
Dept. of Knowledge Engineering and
Hi,
I've received several reports that debootstrap of sid has not been
possible recently due to sysvinit.
I guess the problem is that sysvinit related postinst
scripts are calling 'init' inside chroot, which fails,
failing the whole installation process.
The possible alternatives seem to be:
> I've received several reports that debootstrap of sid has not been
> possible recently due to sysvinit.
I've noticed that waldi already did a NMU.
I'm moved. It's free-software and cooperation at work.
excited,
junichi
> >> I've received several reports that debootstrap of sid has not been
> >> possible recently due to sysvinit.
> >
> >I've noticed that waldi already did a NMU.
> >I'm moved. It's free-software and cooperation at work.
>
> Yes, NMUing essential packages without bothering to contact the
> maintain
> Everything in csound was relicensed LGPL a couple of months ago. Now
> literally *everything* in csound is LGPL. The page above is old and
> obsolete, and should probably be changed. The funny part is that the
> only one that pushed hard enough to have a clear GPL statement (though
> with an exc
The 'standard process' that I know of is this:
> * On other side some people on #d-d says that the standard way is to add
> .1 to the number.
>
Thus, a package with a version number '1.5' will be versioned
'1.5.1'
Then, an exception follows that if the previous upload was a NMU,
in which ca
> >
> > my $temp="set -e\nset -- @ARGV\n" . << 'EOF';
> > if [ "$1" = "configure" ]; then
> > [ -x /usr/sbin/update-configlets ] && /usr/sbin/update-configlets
> > fi
> >
> > EOF
> > >>
At Mon, 04 Aug 2003 15:54:56 +0200,
Matthias Urlichs wrote:
>
> Hi, Nikita V. Youshchenko wrote:
>
> >> Guess how many hours it takes for the m68k buildd to rebuild
> >> kdegraphics. OVER 38 HOURS!
> >
> > By the way, isn't it a good time to rise up a discussion about package
> > cross-compi
At Mon, 04 Aug 2003 15:54:56 +0200,
Matthias Urlichs wrote:
>
> Hi, Nikita V. Youshchenko wrote:
>
> >> Guess how many hours it takes for the m68k buildd to rebuild
> >> kdegraphics. OVER 38 HOURS!
> >
> > By the way, isn't it a good time to rise up a discussion about package
> > cross-compi
I'm cc'ing PSG, maybe he'll be interested.
> * New upstream release .* (Closes: #1, #2, #3)
>
> to
>
> * New upstream release \1
> * fixed "BTS summary line of #1" Closes: #1
> * fixed "BTS summary line of #2" Closes: #2
> * fixed "BTS summary line of #3" Closes: #3
>
> in changelogs wo
ebian-bug-* (there's no debian-bug-to-buffer... hmm?)
> to parse the bugreport ?
Here is what the output looks like:
ecasound2.2 (2.3.0-1) UNRELEASED; urgency=low
* New upstream release
* Run autoconf-automae-libtool in build.
* jackd requires /proc/cpuinfo information not available o
> I'm not sure what the goal is?
> Why do you want the bug submitter named in the Closes entry?
> If its the title you want, then that is already available after the bug
> list has been fetched. I've been wanting to use the title as initial
> input to the close command for a wgile, but wasn't conv
> * Bug fix "debian-changelog mode to support fetching of bug to fill
>in changelog", Thanks to Junichi Uekawa <[EMAIL PROTECTED]>
>(Closes: #207852).
>
> But I've always thought listing the thitle didn't really say _what_ was
> fixed
> One big problem with this approach is that the same maintainers who are
> too lazy to write proper entries for bug-closers in their changelog
> entries are going to be too lazy to ensure that a bug report has a
> meaningful summary in the first place.
Maintainers who are lazy cannot be fixed, bu
> Which is what I will do, probably. It's just annoying... but
> a statement in README.Debian will do...
update-alternatives is usually used in managing multiple
manpages.
I don't know if it's a overkill, but it's somewhat friendlier than documenting
in README.Debian.
regards,
junich
ich is directly applied :
* Updated translation for ja.po
From: Junichi Uekawa (closes: #)
* Fix behavior of SIGSEGV handling
From: Junichi Uekawa (closes: #)
2. A user report that did not contain a patch or anything that helped
track down the problem, but at least the problem got fixed:
Hi,
> > >> Another bug I noticed is that in the ru_RU.UTF-8 locale, man won't
> > >> find the man pages under ru_RU.KOI8-R.
> > >Hm. Yes, that is a bug (although not a regression; I think man-db
> > >2.4.1 behaved the same way). I wonder how to solve that correctly
> > >and generally.
> >
>
Hi,
I'll just write a mail here to notify people using pbuilder, that
sid is a wild place.
My testsuite tells me that currently Debian sid/etch is not
debootstrap'able. This is due to several problems,
including g++ ABI transition breaking aptitude.
However, the good news is that you should b
Hi,
I'd like to propose, for new -dev packages, to
name -dev packages after their runtime library counterparts.
If the library package is named lib$NAME,
call the -dev package lib$NAME-dev.
For example,
libxxx0 will have
libxxx0-dev.
libfoobar-2.1-0 will have
libfoobar-2.1-0-dev.
This
Hi,
> > I'd like to propose, for new -dev packages, to
> > name -dev packages after their runtime library counterparts.
> >
> > If the library package is named lib$NAME,
> > call the -dev package lib$NAME-dev.
> [...]
>
> Hej,
> The obvious downside of this is that the name of dev-package will
Hi,
> * Junichi Uekawa ([EMAIL PROTECTED]) wrote:
> > I'd like to propose, for new -dev packages, to
> > name -dev packages after their runtime library counterparts.
>
> Uh, no? The -dev packages have no need to match to a specific runtime
> library and this
Hi,
> > There may be other showstoppers.
>
> What does doing this solve? What does it even help with?
Hmmm... we are talking about naming
Debian development shareed library package names based on
Debian runtime shared library package names.
>
> > I would really like this 10-year old non-reg
Hi,
> > I'd like to propose, for new -dev packages, to
> > name -dev packages after their runtime library counterparts.
>
> I personally found it very handy that the dev packages automatically
> selects the most recent API compatible version. Why do you want this
> switch by the way? You did not
Hi,
> You can (and it is often done) extend an api to include more
> functionality without breaking the existing api. Any program using one
> of the new functions must use a versioned depend on the libfoo-dev
> package introducing the function.
>
> The API can (and will) even stay compatibly acro
Hi,
> > 2. The information of -dev packages depending on other -dev packages
> > cannot be automatically determined currently;
> > it should be possible to obtain a minimal list by analyzing the
> > NEEDED field of the objdump output.
>
> Errr, -dev packages generally don't (and shouldn't) depe
Hi,
Thanks for the comments.
> Ideally there needs to be either
>
> * a login environment where changes are saved AND/OR
>
> * a hook that gets executed for an update operation, *before* apt-get
> is called.
Luckily, since pbuilder 0.118 which was released 31 Oct 2004,
there is a --save-aft
Hi,
> The aspell dictionary packages build-depend on aspell-bin (>> 0.60).
> aspell-bin is now a virtual package provided by aspell, but virtual
> packages cannot be versioned, so these build-dependency cannot be
> satisfied.
>
> There are fifteen such packages:
I'd see a benefit in filing mail
Hi,
> > BTW, having Build-Depends: libfoo-dev in
> > a library's build-deps, will allow the developer
> > to overlook a soname change in depending shared library.
> > Which is a bad idea in the QA standpoint.
>
> Yes and no.
>
> The programer can overlook the soname change for the source. The A
Hi,
Thanks for your input.
> > Having a solid naming scheme will allow me to
> >
> > ldd /usr/lib/libwhatever.so to track down its
> > shared library dependency, and appending "-dev"
> > to individual package to create the list of
> > requisite -dev packages.
>
> If this is actually necessa
Hi,
> > Having a solid naming scheme will allow me to
> >
> > ldd /usr/lib/libwhatever.so to track down its
> > shared library dependency, and appending "-dev"
> > to individual package to create the list of
> > requisite -dev packages.
>
> With the current scheme it is:
>
> ldd /usr/lib/libwh
> > > > libfoobar-2.1-0 will have
> > > > libfoobar-2.1-0-dev.
> > >
> > > Please distinguish between API and ABI!
> > >
> >
> > True. Indeed the proposed policy is already followed in case of ABI
> > changes. And any sane program would not compile when ever a library
> > change its _API_ in a
Hi,
Thanks for your time and feedback. I appreciate it very much.
> You could also suggest a policy for libs to have a libfoo.devname file
> similar to the libfoo.shlibs file but naming the needed -dev
> packages. If that is a good idea or not you have to think about. Just
> a wild idea.
Yes, t
Hi,
> is there a policy for bugs which are unreproducible?
> I mean how long this kind of bug should be open?
> There are bugs who are unreproducible for over a year and
> the version increased to a major version during the time.
I tend to request the user for more info with the new version;
so a
Hi,
Since I've started up this thread, I'd like to summarize what was
discussed in this thread.
1. Conclusion:
For the initial question of
'How does one decide which -dev package accompanies
runtime library package'
There is no answer, and we have not reached the consensus.
2. Methods to
compilation with libtool will break.
regards,
junichi
--
Junichi Uekawa, Debian Developer http://www.netfort.gr.jp/~dancer/
183A 70FC 4732 1B87 57A5 CE82 D837 7D4E E81E 55C1
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ork
with static linking.
However, it is still in policy 8.3. that if it exists, it will be
in -dev package.
Having an extra -static package is rather drastic change,
and I personally still do like the ability of being able to
do static linking.
regards,
junichi
--
Junichi Uekawa,
_ugettext(msgid).encode(gettext_encoding)
+_ = lgettext
Correct me if I'm missing something, since python is not
my best language.
regards,
junichi
--
Junichi Uekawa, Debian Developer http://www.netfort.gr.jp/~dancer/
183A 70FC 4732 1B87 57A5 CE82 D837 7D4E E81E 55C1
--
T
#x27;s invention of gettext which only
returns UTF-8; which you will have to call like:
print _("some string").encode(locale.nl_langinfo(CODESET))
as opposed to
print _("some string")
(if _ is bound to lgettext).
regards,
junichi
--
Junichi Uekawa, Debian Developer
,
junichi
--
Junichi Uekawa, Debian Developer http://www.netfort.gr.jp/~dancer/
183A 70FC 4732 1B87 57A5 CE82 D837 7D4E E81E 55C1
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ror
-> cleaning the build env
-> removing directory /var/cache/pbuilder/build//27924 and its
subdirectories
regards,
junichi
--
Junichi Uekawa, Debian Developer http://www.netfort.gr.jp/~dancer/
183A 70FC 4732 1B87 57A5 CE82 D837 7D4E E81E 55C1
--
To UNSUBSCRIBE, email to [EMAIL PROTE
s a Debian Developer.
The following is a text signed by Kenshi Muto:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Debian developer Junichi Uekawa <[EMAIL PROTECTED]> has lost his
previous key CD3756F4 and he is now using his new key E81E55C1
since 2005-5-22
pub 1024D/CD3756F4 2000-
create-etch-cdebootstrap
[OK] build-etch-dsh
[OK] pdebuild-etch-dsh
[OK] pdebuild-internal-etch-dsh
[OK] update-etch-sid.log
[OK] update-etch-sid-experimental.log
regards,
junichi
--
Junichi Uekawa, Debian Developer http://www.netfort.gr.jp/~dancer/
183A 70FC 4732 1B87 5
Hi,
> >I'm planning on getting a cdebootstrap supported version released somewhat
> >soonish.
> >
> >I'd be looking for sponsored upload, since if I'm not mistaken,
> >and finger [EMAIL PROTECTED] is telling me the correct thing,
> >my new gpg key is not in the keyring yet.
>
> I'll sponsor all
cer/tmp/20050820-jacktransition/
regards,
junichi
--
Junichi Uekawa, Debian Developer http://www.netfort.gr.jp/~dancer/
183A 70FC 4732 1B87 57A5 CE82 D837 7D4E E81E 55C1
pgpiDgWIuZcPo.pgp
Description: PGP signature
.99.p14.debian1-3_i386.changes: translation updates
update-cluster_0.41.5-1_i386.changes: translation updates
whizzytex_1.2.3-1_i386.changes: new upstream release
wysihtml_0.12-1_i386.changes: new upstream release
available: http://www.netfort.gr.jp/~dancer/tmp/20050821/
regards,
junic
onf5.
License: GPL
URL: http://www.netfort.gr.jp/~dancer/software/cowdancer.html
cowdancer_0.3_i386.deb
--
Package: cowdancer
Version: 0.3
Section: utils
Priority: optional
Architecture: i386
Depends: libc6 (>= 2.3.5-1)
Installed-Size: 84
Maintainer: Junichi Uekawa <[EMA
nfmtc
Version: 0.7-1
Section: utils
Priority: extra
Architecture: i386
Depends: libc6 (>= 2.3.2.ds1-21), gcc, binutils, g++, binfmt-support
Suggests: g77, gcj, libgcj4-dev, gpc
Installed-Size: 188
Maintainer: Junichi Uekawa <[EMAIL PROTECTED]>
Description: Execute C program as
led
output in a sane way (I'm currently eyeing bison; flex looks a bit
difficult).
Considering that there doesn't seem to be a similar project,
I'm going to upload the package.
regards,
junichi
--
Junichi Uekawa, Debian Developer http://www.netfort.gr.jp/~dancer/
183A
update-sarge-etch-sid.log
[OK] update-sarge-etch-sid-experimental.log
[OK] create-etch-cdebootstrap
[OK] build-etch-dsh
[OK] pdebuild-etch-dsh
[OK] pdebuild-internal-etch-dsh
[OK] update-etch-sid.log
[OK] update-etch-sid-experimental.log
regards,
junichi
--
Junichi Uekawa
Hi,
> > Of course I read debian-devel. But I fix bugs once they are
> > reported. I use the BTS to track needed work in this way.
>
> This is of course suprerior to running vi debian/control because
> beauracracy is fun.
I'm transitioning one of my packages to a potential new-maintainer;
and
Hi,
> Extracting source
> Password: su: Authentication failure
> Sorry.
> pbuilder: Failed extracting the source
> -> Aborting with an error
> -> unmounting dev/pts filesystem
> ...
>
>
> I guess I have to set a further sudo permission here but for what program?
> It is 'sudo su' ? I would
tags 330291 +patch
reassign 330291 login
severity 330291 serious
thanks
Hi,
> > Extracting source
> > Password: su: Authentication failure
> > Sorry.
> > pbuilder: Failed extracting the source
> > -> Aborting with an error
> > -> unmounting dev/pts filesystem
> > ...
> >
> >
> > I guess I h
oot.
And you were running sid inside chroot.
To summarize: today's sid was rather more unstable than usual
due to shadow.
regards,
junichi
--
Junichi Uekawa, Debian Developer http://www.netfort.gr.jp/~dancer/
183A 70FC 4732 1B87 57A5 CE82 D837 7D4E E81E 55C1
--
To UNSUBSC
for cdebootstrap; I guess.
It will probably soon be required to have the key checks
in pbuilder when I come around to adding those support to
pbuilder.
regards,
junichi
--
Junichi Uekawa, Debian Developer http://www.netfort.gr.jp/~dancer/
183A 70FC 4732 1B87 57A5 CE82 D837 7D4E E
Hi,
> > debootstrap test:
> > [FAIL] create-sid-debootstrap
> > [FAIL] build-sid-dsh
> > [FAIL] pdebuild-sid-dsh
> > [FAIL] pdebuild-internal-sid-dsh
> > [FAIL] create-etch-debootstrap
> > [FAIL] build-etch-dsh
> > [FAIL] pdebuild-etch-dsh
> > [FAIL] pdebuild-internal-etch-dsh
> > [FAIL] update-et
101 - 200 of 446 matches
Mail list logo
