Re: Bug#722950: ITP: ssh-agent-filter -- filtering proxy for ssh-agent

[Paul Wise]

On Sat, Sep 14, 2013 at 8:16 PM, Timo Weingärtner wrote:

> Packaging is prepared, an upload to mentors is waiting for the bug number.

FYI, ITP stands for *intent* to package. The ITP comes before the
package to prevent duplication of effort. If you make a package before
filing the ITP there is very little point in filing the ITP at all.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caktje6h42+d29uv8k-zc-mcsgrq64suevn3++kp4or5pvp1...@mail.gmail.com

Re: Considering dropping ssh-vulnkey from openssh-client

[Stephen Gran]

This one time, at band camp, Colin Watson said:
> I'm considering removing ssh-vulnkey in an upload of the Debian openssh
> package sometime soon, and would like feedback.

In my role as sysadmin for various places, I've used various wrappers
around your ssh-vulnkey code to check for weak keys and raise alerts and
so on.  I can't think of more than maybe one alert from those scripts,
after sorting out the initial mess of weak keys.  I won't mind if they
go away, and thank you for doing the work in the first place.

Cheers,
-- 
 -
|   ,''`.Stephen Gran |
|  : :' :sg...@debian.org |
|  `. `'Debian user, admin, and developer |
|`- http://www.debian.org |
 -


signature.asc
Description: Digital signature

Re: Bug#722950: ITP: ssh-agent-filter -- filtering proxy for ssh-agent

[Timo Weingärtner]

Hi,

On Sun, 2013-09-15 11:48:01 Paul Wise wrote:
> On Sat, Sep 14, 2013 at 8:16 PM, Timo Weingärtner wrote:
> > Packaging is prepared, an upload to mentors is waiting for the bug number.
> 
> FYI, ITP stands for *intent* to package. The ITP comes before the
> package to prevent duplication of effort. If you make a package before
> filing the ITP there is very little point in filing the ITP at all.

I know. I already had that package locally, so the ITP should really be an ITU 
(intent to upload).


Timo

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

Re: Bug#722950: ITP: ssh-agent-filter -- filtering proxy for ssh-agent

[Paul Gevers]

On 15-09-13 11:48, Paul Wise wrote:
> On Sat, Sep 14, 2013 at 8:16 PM, Timo Weingärtner wrote:
> 
>> Packaging is prepared, an upload to mentors is waiting for the bug number.
> 
> FYI, ITP stands for *intent* to package. The ITP comes before the
> package to prevent duplication of effort. If you make a package before
> filing the ITP there is very little point in filing the ITP at all.

Except that comments about the fitness of the package for Debian, or
comments about the description can still come from a large audience. But
yes, I agree that it makes more sense beforehand.

Paul




signature.asc
Description: OpenPGP digital signature

Bug#723017: ITP: python-xrayutilities -- Python package for xray data reduction and analysis

[Eugen Wintersberger]

Package: wnpp
Severity: wishlist
Owner: Eugen Wintersberger 

* Package name: python-xrayutilities
  Version : 1.0.1
  Upstream Author : Dominik Kriegner 
* URL : http://xrayutilities.sourceforge.net/
* License : GPL
  Programming Lang: C, Python
  Description : Python package for xray data reduction and analysis

xrayutilities is a collection of scripts used to reduce and analyze x-ray
diffraction data. It consists of a python package and several routines written
in C. It especially useful for the reciprocal space conversion of diffraction
data taken with linear and area detectors.


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130915122641.30737.53277.reportbug@amun

changes in python packaging

[Jay Berkenbilt]

I'm having problems with one of my packages that includes a python
module.  The package is vips.  I am not a python person, so this may be
simple.

The last time I built the package, there were several module binary
files that got installed appropriately.  For example:

% dpkg --listfiles python-vipscc| grep vmaskmodule.a
/usr/lib/python2.6/dist-packages/vipsCC/vmaskmodule.a
/usr/lib/python2.7/dist-packages/vipsCC/vmaskmodule.a

Now when I rebuild the package with no changes at all, I get something
like this:

% dpkg --contents python-vipscc_7.34.2-1_amd64.deb| grep vmaskmodule.a
-rw-r--r-- root/root   1127858 2013-09-15 09:33 
./usr/share/pyshared/vipsCC/vmaskmodule.a
lrwxrwxrwx root/root 0 2013-09-15 09:33 
./usr/lib/python2.7/dist-packages/vipsCC/vmaskmodule.a -> 
../../../../share/pyshared/vipsCC/vmaskmodule.a

Okay, this example shows a newer version of the package, but when I
rebuild the exact same version as before, I get the same result.

This looks like a bug to me, but I'm not even sure where to report the
bug.  What thing is responsible for having decided to move this module
to /usr/share and make a symlink, assuming that's what happened, even
though it's architecture-dependent?  Is this a problem with my
packaging, or is there a bug in whatever is doing this?

My best guess is that this is an issue with dh_python2, though I don't
know whether a change in dh_python2 is exposing a long-standing problem
with the upstream package, or whether this is a new bug, or whether this
is a difference because of fewer python versions being available or
what.

Thanks.  This is blocking me from uploading a new version of vips.

-- 
Jay Berkenbilt 


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130915094224.0521296614.qww314159@soup

Re: tlsa for smtp to @bugs.debian.org

[James Cloos]

> "KR" == Kurt Roeckx  writes:

KR> A self-signed cert's signature algorithm really isn't that
KR> important.  You either trust that cert or you don't.  Which
KR> is why openssl started to ignore this for root CAs.  I'm not
KR> sure what gnutls does with it.

Thanks.  That is most reasonable.

Empirically, the version of gnutls in wheezy does care about the self
sig on the root cert when presented with a tls client cert chain where
it (the tls server) is not configured to trust the chain's root, the
root's self sig is md5 and the ee cert's sig is sha256.

In this case, the tls server does not require a trusted client cert,
but notes the presence of such certs.

So, the ONLY think gnutls objected to in the case was that the presented
client cert chain had a root-self-sig using MD5.

I will send a note to gnutls-devel about it.

And one to postfix-devel suggesting that if the tls nego fails just
after offering a client cert, that it retry w/o the client cert.

I've worked around the problem locally by offering a different cert
when sending mail.

-JimC
-- 
James Cloos  OpenPGP: 1024D/ED7DAEA6


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/m3bo3u1940@carbon.jhcloos.org

Bug#723028: ITP: libnu-htmlparser-java -- HTML5 parsing algorithm in Java

[Andrew Ross]

Package: wnpp
Severity: wishlist
Owner: Andrew Ross 

* Package name: libnu-htmlparser-java
  Version : 1.4
  Upstream Author : Henri Sivonen 
* URL : http://about.validator.nu/htmlparser/
* License : MIT/X
  Programming Lang: Java
  Description : HTML5 parsing algorithm in Java

 The Validator.nu HTML Parser is an implementation of the HTML5 parsing
 algorithm in Java for applications. The parser is designed to work as a
 drop-in replacement for the XML parser in applications that already support
 XHTML 1.x content with an XML parser and use SAX, DOM or XOM to interface
 with the parser.


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130915145851.8754.83608.reportbug@sandstone

Accessing bug archives

[Dave Steele]

I was interested in doing some ongoing analysis of historical RFS
processing, and ran into trouble getting the archived bug information.

The bugs.debian.org web interface, by default, omits archived entries. When
including archives, the results are truncated. I don't see a way to work
around this by splitting up the results somehow. In aggregate, there
doesn't seem to be a way to get all of the bugs out of that web interface.

As a DM, the UDD db interface is not available to me. The UDD web interface
for bugs does not support the right query terms.

The Searching Bug Reports section on http://www.debian.org/Bugs/ identifies
a number of options that are broken or impractical.

What is the recommended strategy for me to get ongoing access of historical
bug stats, short of setting up a full UDD mirror? What am I missing here?


-- 
"Le mieux est l'ennemi du bien" - Voltaire

Re: Accessing bug archives

[Ansgar Burchardt]

Dave Steele  writes:
> As a DM, the UDD db interface is not available to me. The UDD web interface
> for bugs does not support the right query terms.

As far as I know anybody with an account on Alioth can access UDD:

$ ssh -t wagner.debian.org psql service=udd

There's also an unofficial public mirror on [1].

Ansgar

  [1] 


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/874n9mgksp@eisei.43-1.org

Re: Accessing bug archives

[Dave Steele]

> There's also an unofficial public mirror on [1].
>
> Ansgar
>
>   [1] 
>

Thanks, that should be perfect for me.

-- 
"Le mieux est l'ennemi du bien" - Voltaire

Re: Accessing bug archives

[Don Armstrong]

On Sun, 15 Sep 2013, Dave Steele wrote:
> The bugs.debian.org web interface, by default, omits archived entries.
> When including archives, the results are truncated.

Which searches are you doing? They should not (in general) be truncated.

-- 
Don Armstrong  http://www.donarmstrong.com

Frankly, if ignoring inane opinions and noisy people and not flaming
them to crisp is bad behavior, I have not yet achieved a state of
nirvana.
 -- Manoj Srivastava in 87n04pzhmh@glaurung.internal.golden-gryphon.com


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130915155908.gw6...@teltox.donarmstrong.com

Bug#723033: ITP: cigi-ccl -- the CIGI class library (CCL)

[Klee Dienes]

Package: wnpp
Severity: wishlist
Owner: Klee Dienes 

* Package name: cigi-ccl
  Version : 3.3.3a
  Upstream Author : Bill Phelps 
* URL : http://cigi.sourceforge.net
* License : LGPL-2.1+
  Programming Lang: C++
  Description : the CIGI class library (CCL)

 This package contains development libraries and headers for the CIGI
 class library (CCL).  The CCL is a C++ language library for
 implementing CIGI in both host and IG applications.
 .
 Some features of the CCL include:
 .
  * Handles packing, unpacking, and byte swapping automatically
  * Handles output buffer management
  * Can handle most of the input buffer management with simple calls
  * Can translate between different versions of CIGI


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20130915153949.9470.54134.report...@router.dienesfamily.org

Re: Bug#723019: ITP: squidanalyzer -- Squid proxy native log analyzer and reports generator with full statistics

[Andrei POPESCU]

Control: reassign -1 wnpp

On Du, 15 sep 13, 15:06:22, Jacques Serfontein wrote:
> Package: squidanalyzer
> Severity: wishlist
> URL: http://squidanalyzer.darold.net
> License: GPL v3

Could you add the long description as well?

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

Bug#723038: ITP: maven-indexer -- Indexer for Maven repositories

[Andrew Ross]

Package: wnpp
Severity: wishlist
Owner: Andrew Ross 

* Package name: maven-indexer
  Version : 5.1.1
  Upstream Author : The Apache Software Foundation
* URL : http://maven.apache.org/maven-indexer/
* License : Apache-2.0
  Programming Lang: Java
  Description : Indexer for Maven repositories

 Apache Maven Indexer (former Sonatype Nexus Indexer) is the defacto standard
 for producing indexes of Maven repositories. The Indexes are produced and
 consumed by all major tools in the ecosystem.


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130915171958.8868.23065.reportbug@sandstone

Re: Considering dropping ssh-vulnkey from openssh-client

[Ian Jackson]

Colin Watson writes ("Re: Considering dropping ssh-vulnkey from 
openssh-client"):
> That lists 53141 live hosts (0.52%) under the category "using Debian
> weak keys" (the percentage for TLS was 0.03%, close to your
> recollection).  From the context of the rest of the paper I understand
> that it is referring to SSH host keys.
> 
> This is indeed an alarming number.  However, I can only see a couple of
> possibilities here:

Another possibility is that the system was installed using a
vulnerable version of Debian, but has been running a distro which does
not contain ssh-vulnkey etc., and the administrator hasn't noticed.

(Perhaps the admin even deliberately switched away from Debian when
they heard about the vulnerability, without reading the details and
discovering that that didn't fix the problem.)

> Are there any other possibilities here where continuing to carry the
> vulnerability-checking code will actually help?  I'm particularly
> interested if anyone has experience dealing with cleaning up such a
> system they found under a rock.

My suggestion above is entirely hypothetical.

Ian.


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/21046.1532.455859.797...@chiark.greenend.org.uk

Re: Bug#723015: package four years out of date

[jidanni]

> "RA" == Russ Allbery  writes:
RA> David Bremner  writes:
>> jida...@jidanni.org writes:

>>> P.S., why can't all this CPAN <-> Debian updating be a little bit
>>> automated for all the packages on Debian?

>>> At least some queue that some team gets alerted to...

>> there is a queue

>> http://pet.debian.net/pkg-perl/pet.cgi

>> and libgedcom-perl is listed there. So such bug reports are not
>> especially needed.

RA> Well... it does provide information that someone actually cares about that
RA> module in particular, whereas the queue has everything that's out of date
RA> whether anyone cares about the new version or not.  So such bugs could, in
RA> theory, help with prioritization.  Provided, of course, that the bug is
RA> prompted by a desire for the new version as opposed to just noticing that
RA> there was a newer version available.  (Frequently, newer versions have
RA> only cosmetic changes and aren't necessarily worth packaging.)

RA> -- 
RA> Russ Allbery (r...@debian.org)   

Hmmm, looking at the entire equation, one notices the most energy is
concentrated at each ultimate author's end. He has added some brilliant
new revisions to his masterpiece. Perhaps he should be encouraged to
notify the certain Debian, Redhat etc. maintainers to get a new
version... Hmmm, doesn't seem likely though. Plus would cut down on his
creativity, being bogged down having to bother unrelated people...

Adding debian-devel to Reply-to, removing 723...@bugs.debian.org


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87wqmhg8ly@jidanni.org

Bug#723015: Info received (Bug#723015: package four years out of date)

[Debian Bug Tracking System]

Thank you for the additional information you have supplied regarding
this Bug report.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 Debian Perl Group 

If you wish to submit further information on this problem, please
send it to 723...@bugs.debian.org.

Please do not send mail to ow...@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.

-- 
723015: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723015
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.723015.b723015.13792751198268.acki...@bugs.debian.org

Re: Accessing bug archives

[Dave Steele]

On Sun, Sep 15, 2013 at 11:59 AM, Don Armstrong  wrote:

> On Sun, 15 Sep 2013, Dave Steele wrote:
> > The bugs.debian.org web interface, by default, omits archived entries.
> > When including archives, the results are truncated.
>
> Which searches are you doing? They should not (in general) be truncated.
>
>
http://bugs.debian.org/cgi-bin/pkgreport.cgi?package=sponsorship-requests&archive=yes

The newest bug, by number, from this request is 700361, archived 14 March
(the only one above 70). But the query ...

http://bugs.debian.org/cgi-bin/pkgreport.cgi?package=sponsorship-requests

... looks like it only shows Resolved bugs with last comment dates going
back a month (oldest based on 'last comment' is 720113, with a last comment
date of 19 August).

>From that information, I assumed that there must be some archived bugs that
I don't see. Looking a little harder, I see that there are a total of 2
reported archive bugs with newer comments than 700361, and older than
720113, covering the period between March and August. Going backwards in
the archive, there are at least a dozen archived bugs per month, based on
last comment date.

Not hard proof, but it sure seems like something is missing.

Re: changes in python packaging

[Steve Langasek]

Hi Jay,

On Sun, Sep 15, 2013 at 09:42:24AM -0400, Jay Berkenbilt wrote:
> I'm having problems with one of my packages that includes a python
> module.  The package is vips.  I am not a python person, so this may be
> simple.

> The last time I built the package, there were several module binary
> files that got installed appropriately.  For example:

> % dpkg --listfiles python-vipscc| grep vmaskmodule.a
> /usr/lib/python2.6/dist-packages/vipsCC/vmaskmodule.a
> /usr/lib/python2.7/dist-packages/vipsCC/vmaskmodule.a

Well, to start off, this doesn't look correct at all.  Python modules are
never .a files; these appear to be spurious static builds of the modules
because you're using a non-pythonic build system that assumes it's
appropriate to build both shared and static versions of "libraries".  But
these are not libraries, they're DSOs; you should not ship these .a files in
your package.

> Now when I rebuild the package with no changes at all, I get something
> like this:

> % dpkg --contents python-vipscc_7.34.2-1_amd64.deb| grep vmaskmodule.a
> -rw-r--r-- root/root   1127858 2013-09-15 09:33 
> ./usr/share/pyshared/vipsCC/vmaskmodule.a
> lrwxrwxrwx root/root 0 2013-09-15 09:33 
> ./usr/lib/python2.7/dist-packages/vipsCC/vmaskmodule.a -> 
> ../../../../share/pyshared/vipsCC/vmaskmodule.a

> Okay, this example shows a newer version of the package, but when I
> rebuild the exact same version as before, I get the same result.

This looks like a change in the python helpers, yes, probably to handle
moving/symlinking of files other than .py or .so that some python modules
include and expect to be present in their directory.  So this is a change
from whitelist handling of files with a .py extension, to blacklist handling
of files with a .so extension.  The .a files are ending up in the "wrong"
place because dh_python isn't treating them specially... because they're not
special for python, they're extraneous files to be deleted.

In sum, this is a preexisting bug in python-vips that is just manifesting
differently with the new version of dh_python2.

HTH,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: Digital signature

Re: using packages from sid on travis-ci.org

[Roger Leigh]

On Tue, Sep 10, 2013 at 10:42:09PM +0200, Daniel Pocock wrote:
> 
> 
> Some of the upstream projects I work on use travis-ci.org for continuous
> integration
> 
> In some cases I'd like to configure builds that depend on packages from
> Debian unstable, but I'm not sure of the Ubuntu or travis way of doing
> that, has anybody dealt with this before?  Or is there a Debian alternative?

You can configure travis to add additional apt sources and then install
packages from them, e.g.

before_install:
  - sudo add-apt-repository -y "deb http://archive.ubuntu.com/ubuntu/ raring 
main universe"
  - sudo apt-get -qq update
  - if [[ $BUILD != 'sphinx' ]]; then sudo apt-get install -qq python-genshi; fi
  - if [[ $BUILD == 'cppwrap' ]]; then sudo apt-get install -qq build-essential 
cmake libboost-all-dev; fi
  - if [[ $BUILD == 'sphinx' ]]; then sudo apt-get install -qq python-sphinx; fi
  - if [[ $BUILD == 'sphinx' ]]; then sudo apt-get -y install 
texlive-latex-base texlive-latex-recommended texlive-xetex; fi
  - if [[ $BUILD == 'sphinx' ]]; then sudo apt-get -y install 
texlive-latex-extra texlive-fonts-recommended tex-gyre; fi
  - if [[ $BUILD == 'sphinx' ]]; then sudo fc-cache -rsfv; fi

In this case, we're updating to a newer version of Ubuntu and installing
packages from it, but you can probably do exactly the same for unstable.


Regards,
Roger

-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linux http://people.debian.org/~rleigh/
 `. `'   Printing on GNU/Linux?   http://gutenprint.sourceforge.net/
   `-GPG Public Key: 0x25BFB848   Please GPG sign your mail.


signature.asc
Description: Digital signature

Re: [PATCH] netplug - Allow to specify custom script file via param '-s'

[Pali Rohár]

On Friday 26 July 2013 17:30:11 Pali Rohár wrote:
> On Sunday 21 April 2013 13:23:49 Paul Wise wrote:
> > On Sun, Apr 21, 2013 at 6:11 PM, Pali Rohár wrote:
> > > But why Debian cannot review and include this my patch?
> > 
> > Now is the time for fixing RC bugs, not for including
> > patches, please wait until wheezy is released and then give
> > the maintainer some time to review it and prepare a new
> > package.
> 
> Wheezy was already released. Can anybody look at my patch now?

Bump. Is there any problem?

-- 
Pali Rohár
pali.ro...@gmail.com


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

Re: [PATCH] netplug - Allow to specify custom script file via param '-s'

[Paul Tagliamonte]

On Mon, Sep 16, 2013 at 12:15:20AM +0200, Pali Rohár wrote:
> Bump. Is there any problem?

Hey there Pali,

First of all, thank you for your hard work and persistence - I admire
that a great deal! Keep that up!


One interesting thing with Debian is that DDs can't go into another
maintainer's package and change something (such as a new feature or
upstream release) without the maintainer's consent.

If you're able to get the maintainer of this package to sign off on the
patch, and ack a NMU against it, I'm sure any number of us would be more
than happy to sponsor the upload.

However, doing this is frowned upon without the coordination of the
current maintainer - so that's a pretty needed first step!


Thank you so much for your work! Let's get your changes in the archive!
  Paul

-- 
 .''`.  Paul Tagliamonte 
: :'  : Proud Debian Developer
`. `'`  4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
 `- http://people.debian.org/~paultag


signature.asc
Description: Digital signature

Bug#723062: ITP: ibus-kkc -- libkkc engine for IBus

[Osamu Aoki]

Package: wnpp
Severity: wishlist
Owner: Osamu Aoki 

* Package name: ibus-kkc
  Version : 1.5.18
  Upstream Author : Daiki Ueno 
* URL : https://gitorious.org/libkkc/ibus-kkc/
https://bitbucket.org/libkkc/ibus-kkc/downloads
* License : GPL-2+
  Programming Lang: C, C++, Perl, Python, Ruby
  Description : libkkc engine for IBus

 IBus is an Intelligent Input Bus. It is a new input framework for Linux
 OS. It provides full featured and user friendly input method user interface.
 It also may help developers to develop input method easily.
 .
 ibus-kkc is an input method (IM) for Japanese, based on IBus.

I would like to set this and related packages team maintained by pkg-ime
team.
  https://wiki.debian.org/Teams/IMEPackagingTeam

(The package itself exist in Mitsuya's PPA in Ubuntu.  So I plan to do 
minor editings and update from 1.5.15 to 1.5.18.)

Related packages are ITPed by Mitsuya Shibata .
 * http://bugs.debian.org/714453 marisa
 * http://bugs.debian.org/715233 libkkc-data
 * http://bugs.debian.org/715232 libkkc
 (I am thinking about sponsoring them)

Mitsuya's PPA in Ubuntu:
 https://launchpad.net/~cosmos-door/+archive/marisa

Osamu



signature.asc
Description: Digital signature

Re: Accessing bug archives

[Don Armstrong]

On Sun, 15 Sep 2013, Dave Steele wrote:
> On Sun, Sep 15, 2013 at 11:59 AM, Don Armstrong  wrote:
> > On Sun, 15 Sep 2013, Dave Steele wrote:
> > > The bugs.debian.org web interface, by default, omits archived
> > > entries. When including archives, the results are truncated.
> >
> > Which searches are you doing? They should not (in general) be
> > truncated.
>
> http://bugs.debian.org/cgi-bin/pkgreport.cgi?package=sponsorship-requests&archive=yes
> 
> The newest bug, by number, from this request is 700361, archived 14 March
> (the only one above 70). But the query ...

http://bugs.debian.org/cgi-bin/pkgreport.cgi?package=sponsorship-requests&archive=both
 
lists all of the bugs. The oldest being #657303, and newer ones.

If you give archive=yes, you only get archived bugs.


-- 
Don Armstrong  http://www.donarmstrong.com

I'm So Meta, Even This Acronym
-- xkcd http://xkcd.com/917/


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130916033023.gx6...@teltox.donarmstrong.com