Search Results: "Hideki Yamane"

11 February 2013

Hideki Yamane: checking package with clang

Sylvestre Ledru wrote an article "Rebuild of Debian using clang 3.2". Probably package maintainers want to know about their package status with clang in PTS, Paul Wise has already posted to BTS#699936.

And, today I've hit upon an idea, then created a tiny patch for clang support for pbuilder. It may help you to check your package with clang.

10 February 2013

Hideki Yamane: license for MIBs

Unfortunately, most of MIBs doesn't meet DFSG since RFC is non-free. However, RFC5378 was released and it says "code components in RFCs are licensed under Simplified BSD license (BSD-3-clause)", See Trust Legal Provisions (TLP) Documents page.

Code components are

ABNF definitions, XML Schemas, XML DTDs, XML RelaxNG definitions, tables of values, MIBs, PIBs, ASN.1, and classical programming source code
So, recent MIBs can be included to Debian package :)

But it isn't enough because those RFCs are almost 30/260, 90% are not DFSG-free. And 190/260 RFCs are owned by ISOC and IETF trustee, I hope thay will release old MIBs code in RFCs under DFSG-free license as same as after RFC5378.

29 January 2013

Hideki Yamane: upstream and distro has a "same" goal


Tom Marble has a nice blog entry "Crowdsourcing Upstream Refactoring". It's interesting and I agree with most, but I want to say against one thing in "conclusion" in his presentation.

He said "upstreams and distros have different goals" but I don't think so. We distro and upstream has a same goal, "Deliver the value to users", but we distro have much criteria than upstream, like license, non-duplicate library, etc.

If we (distro and upstream) cannot share this view, then we would be failed, IMHO.

28 January 2013

Hideki Yamane: convention over configuration

" convention over configuration" is an approch for software design. Now I recognize why dh7 style is good.

24 January 2013

Hideki Yamane: net-snmp package

Current net-snmp package maintainers are busy, so now I'm trying to update it. One of maintainers Jochen Friedrich kindly checked my experimental package (thank!), and point MIB files should be removed to upload to Debian out (at least).

Anyway, current changelog is here (a little bit long). If you want to try it, get dsc file and build it.


net-snmp (5.7.2~dfsg-1~0.1) UNRELEASED; urgency=low
* Non-maintainer upload.
* New upstream version 5.7.2 (Closes: #557348, #631063, #684388, #599929,
#673197, #581185, #558356, #568550, #514842, #445608, #557186, #411858,
#428824, #611837)
* debian/control
- set "Standards-Version: 3.9.4"
- set "Build-Depends: debhelper (>= 9)" to enable hardening
- set "Build-Depends: automake", instead of automake1.9
- drop "Build-Depends: python-central", use dh_python2 by default, instead
- remove duplicational "Priority:" and "Section:" fields
- make it "Multi-Arch" enable
- add description for non-free snmp-mibs-downloader for users' convinience
(Closes: #561124)
- add "Build-Depends: libmysqld-dev" to support MySQL
- add "Build-Depends: dh-autoreconf"
- use python-all (2.6.6-3~) instead of python-all-dev (>= 2.5.4-1~), python
(>=2.3.5-7) for Build-Depends
- add "Build-Depends: python2.7-dev"
- s/libsnmp-python/python-netsnmp/ as Python Policy compliant (Closes: #661899)
* debian/compat
- set 9
* debian/*.install
- split into *.manpages
* debian/fixman: drop it.
* debian/*.manpages (Closes: #505149)
- remove unnecessary"snmp" from tail of all man pages
* debian/libsnmp-base.install
- move /usr/share/mibs to /usr/share/snmp/mibs (probably, previous setting
was just wrong...)
- install all mibs/*.txt
* debian/libsnmp-dev.install
- change from "usr/lib/*" to "usr/lib/*/*" to deal with Multi-Arch
* debian/libsnmp30.install
- change from "usr/lib/*.so" to "usr/lib/*/*.so" to deal with Multi-Arch
* debian/snmp.dirs: remove it since unnecessary
* debian/snmpd.dirs: remove lintian overrides direcotry, add /etc/snmp
* debian/libsnmp-dev.dirs: add it
* debian/libsnmp-perl.examples: add it since dh_installexamples target in
previous debian/rules doesn't work correctly.
* debian/patches
- remove all *.README files
- add fix_typo_in_snmpd.conf.patch (Closes: #603593)
Thanks to Slavko <linux@slavino.sk>
- add fix_logging_option.patch (Closes: #616437)
- add fix_snmpcheck_perl_path.patch to provide snmpcheck (Closes: #44373)
- add net-snmp-config_multi-arch.patch to enable Multi-Arch
- add fix_regular_expression.patch enable to build under Multi-Arch
- add to snmptranslate.1.patch fix lintian "hyphen-used-as-minus-sign"
warnings
- add fix_spelling_error.patch to fix typo
- adjust and refresh 03_makefiles.patch
- drop 25_duplicate_iftable.patch and 44_nlist_kvm.patch since it cannot be
applied to current code.
- drop 32_mnttab_path.patch since it was merged to upstream as
configure.d/config_os_misc4
- drop 56_manpage.patch since most of patches are merged, and others are
unnecessary because upstream files are disappeared.
- refresh 61_vacm_missing_dependency_check.patch
- drop 63_fix_shell.patch since it was merged to upstream
- reapplied 64_missing_lib.patch since upstream source has been changed.
- drop 65_CVE-2012-2141.patch since it was merged to upstream
- drop 66_formatstrings.patch since almost merged to upstream, some of
code are changed in upstream and become unnecessary.
- move 08_defaultconfig.patch to debian/snmptrapd.conf
* debian/rules
- enable hardening
(TODO: building perl module would be failed without -pie)
- specify LDFLAGS to enable hardening
- add "--with autotools-dev,autoreconf"
- export DEB_BUILD_MAINT_OPTIONS to enable hardening
- drop "dh --with python-central" (Closes: #616913)
- drop "include /usr/share/python/python.mk"
- remove "$(PYVERS:%=debian/python-install-stamp-%)"
- move exist python targets under override_dh_install
- remove unnecessary .PHONY lines
- enable tests by removing no instructions with dh_auto_test line
- set DEB_HOST_MULTIARCH to enable Multi-Arch
- enable install snmpcheck
- don't specify to copy files but install them by using .install file
(mostly)
- enable mysql support
- enable AES support (Closes: #447705)
- don't make symlink for /usr/share/doc/libsnmp-perl since other are okay
but it has examples files.
- snmpd doc files link to libsnmp (Closes: #453124)
- adjust dh_strip for dbg package.
- adjust dh_clean target
- remove override_dh_auto_build since LD_RUN_PATH is clearly specified
during building perl modules
- add mibII/mta_sendmail to build modules (Closes: #641608)
* debian/clean
- most listed files are cared by autotools-dev, so removed.
* debian/snmp.conf: fix typo (Closes: #623499, #647468)
* debian/snmpd.init
- force remove pid files (Closes: #528104)

-- Hideki Yamane <henrich@debian.org> Wed, 18 Jul 2012 13:39:41 +0900

And if I can put it to Debian, then I hope someone will maintain it...

20 January 2013

Hideki Yamane: digging CVEs

Sometimes I would check security-tracker to find problems that is already fixed but not tagged as so.

Today, I found problems that not in unstable package but not tagged as fixed for Eucalyptus, because it was removed from unstable once but re-introduced to archive again, then data in security-tracker was not updated as well. So update it (CVE-2010-3905 and CVE-2011-0730).

And also found vulnerablity in firebird2.5 was fixed in upstream svn, so pick it and made it as a patch, just report to BTS (for squeeze, too).

For isc-dhcp, it has a vulnerability from BIND9... I've been surprised but dhcp includes bind9 source since 4.2, so BIND9 vulnerability affects isc-dhcp. Pick a diff from bind9 for squeeze security update and made a patch (Bug#698597) .

10 January 2013

Hideki Yamane: 256 -> Debian

I had a cold, so couln't write anything (but back to be normal, almost).

I'm also Ubuntu LoCo team member as Ubuntu Japanese team. Some of team members write articles on gihyo.jp website during the years, and now our team leader Jun Kobayashi(*) celebrate 256 times(!) as Android Ubuntu Debian (Run Ubuntu Debian on Android)... Yes, Debian, you know :)

*) He also wrote very funny article ago, see this...

4 January 2013

Hideki Yamane: As tech writer

Sometimes I write articles for Japanese Tech Magazine, the recent one is for Software Design 2013/01. It's "Overview for 2013", of course I wrote about Debian :-)



And luckyly, editor requested the series (yeah!), so I'll do it for a while. I'm happy to get a chance to provide Debian information to readers, thanks!

... and I hope they'll be a media sponsor for DebConf in Japan (in some day :)

3 January 2013

Hideki Yamane: Hello New year, Hello Planet

This is first post to Planet Debian...

Hi, let me introduce myself a bit... I'm a Debian Developer living in Japan. I'm not a geek, programmer... but love Debian and enjoy to participate this project :-) I want to share something interesting related to Debian.


Recently, also I'm curious about Debian cloud computing service - AmazonEC2, Rackspace, WindowsAzure, Google Compute Engine and so on.
Recent two big topic for me is

Especially Aeolus is huge software stack and need to package a lot of Ruby gems, so I've joined Pkg-ruby-extras-maintainers and started packaging some gems. I'm newbie for Ruby, so please help if there's something wrong with my packaging.

30 December 2012

Hideki Yamane: put, put, put

put, put, put.

Just ITPed(dependency package is not satisfied yet).

28 December 2012

Hideki Yamane: How to associate with distribution


I know there is a reason why you rebuild/create your own packages.

  • Unfortunately, there's no official package that is necessary to provide service to your customers
  • distro package is not suitable for your purpose by default
    • maybe since its features
    • maybe since performance issue




However, I want to ask you one question.
Is it necessary that you'd maintain it in your private repository?
Because create custom package repository is a kind of "fork"


  • Of course, you can do folk. But if you don't want to be "upstream", every time you need to follow your upstream to fix bugs, vulnerabilities and introduce new features. Important: Merge cost would become larger and larger from the time you did folk.
  • It's best that if your system can be used "out of box", but you need to modify packages for some reason (as above).
    Then, what would you do? - minimize
    • minimize numbers of private package
      = reduce maintenance cost
    • minimize diff with distro package
      = minimize diff with upstream = reduce maintenance cost

If you could minimize diff with distro, you can update and introduce new attractive features from updated distro package easily (maybe you don't need to maintain your custom package since its feature is merged to upstream).

Yes, you can get Agility.


And, if you would put your package to Debian official repository, we Debian can give you below benefits

  • build daemon with many architectures
  • open bug tracking system
  • world wide mirror network
  • security vulnerabilities tracker
  • users

  1. We can provide build system, including non-x86 arch (none of you have thought arm* architecture become important, right?) You can deal with porting as daily job, no huge jump to support newer architectures. It also brings the view to build cleaner structures in your code.
    It is much work to setup such system, but you can use it without any trouble.
  2. You can get bug report/wishlist/patches from Debian BTS (without any pay for it! :-)
    It will help you to improve software packages, it cannot be sent to you if you would put packages to closed private repository.
  3. Package is mirrored to many repositories in world wide. Robust. You can get binary/source code immediately, anywhere. No need to backup your package source.
  4. Any CVE is tracked. You can analyze security status in your system easily (it means you don't need to pay much money to build such system)
  5. Debian has huge user base. It would work as good "showcase" test (of course, without any pay for it...)



Conclusion)

It's okay to create/modify package. It's FLOSS. As you like! :)

However, to maintain custom package, you need to pay its cost (someone should work for it. If it's in only your own repository, it means you should work, no one can help it).

To maintain packages in distro can reduce its cost, can get many benefit - Less cost, more benefit - why not? Let's get involved to distribution!

Hideki Yamane: maintain is not solely put new version

Sigh.

Some of people are complaining about Debian 7.0 uses linux 3.2. Hey... do you know which kernel version RHEL6 (and CentOS) uses? :-p

- If you want to use latest kernel, you can pull it from git repo
- If you want to use newer kernel version without loong compiling time, then you can pull it from experimental repo easily.
- If you want to make Debian's release kernel newer, then you should work for it - not just complain for it. To get something, someone must pay something for it

Maintain package is not solely put newer version to repo. If you put some package to repo, it should be maintained for 3 years (at least). Hey, you - can you do it? - pick patches to security vulnerabilities and apply it without any regressions 3 years, and maintain newer version for next release.

I know newer version is more attractive for you, but there's a reason to do so.

27 December 2012

Hideki Yamane: I don't want "emacsen-*.ex" files

Every time you run dh_make, you would remove "emacsen-*.ex" files. So I've made a patch for it.

28 November 2012

NOKUBI Takatsugu: BPS in Tokyo

I had attend to Debian Bug Squashing Party in Tokyo at 24th Nov. 2012. The place was provided by Plat Home Co., Ltd. The attendee was about 7 people, it s not so many men.
My big problem is unblocking file-mmagic package. I sent an unblocking request mail, but it has invalid From email address, so I couldn t trace the discussion.
My fault is changing source format to 3.0(quilt). It is a big change for testing.
Now I am making a new package for testing-proposed-update.
It seems about 10 RC bugs had closed by all attendees. Thank you the attendees, especially the cordinator Hideki Yamane.
The network in the place had provied by OpenBlocks, the product of Plat Home.

25 July 2012

Vincent Sanders: Travels with Mr. Brown

My return from Debconf12 has been tinged with a little wistfulness, I had a great time but wish I could have spent a little more time there to justify the seventeen hours travel each way. I took a lot of pictures which gave me a good record of my trip.

The talks, BOF and discussions were, as usual, very useful. The release team explaining what needed to be done for Wheezy was both informative and amusing.

The numerous BOF from Steve Mcintyre were a great source of discussion and ideas and appear to have generated progress on some quite contentious issues.

I especially enjoyed the Sylvestre Ledru talk on building the archive with clang and how this might be another useful tool in finding bugs.

Hideki Yamane gave a really useful talk "Let's shrink Debian package archive!" He gave a practical explanation on how Debian could benefit from using xz compression, where it is not appropriate and had a selection of real numbers to help the discussion. Given this was Hideki first talk at a Debconf I must congratulate him on doing an excellent job.

There were many other talks which I have not singled out here but that says nothing about their quality or usefulness, more about why I should blog immediately after an event and not leave it a week. Though the video team have managed to capture many of the talks so you can go and watch them too.

The event was well organised and the accommodation was pleasant, if a little crowded with three to a room. The hotel had a pool which was the centre for evening activities most days, though I did miss Neil McGovern (one of my room mates) unintentionally swimming in his kilt.
The lunch and dinner catering was outdoors which was novel. The food was generally good if a little limited for those of us with less straightforward dietary requirements.

Some of us did venture out to have dinner at the continental hotel on one evening for a change of scene.
There was of course the obligatory conference meal by the lakeside and an awesome day trip where I saw a mangrove swamp and (fortunately) no salt water crocodiles.
All in all I had a fabulous and productive time. I would like to thank Collabora for travel sponsorship to the event and to Neil who was a great travelling companion.

14 July 2012

Christian Perrier: My own personal "Best Talk Award" for Debconf12

After attending several talks and BOFs at Debconf12, I'll grant my personal "Best Talk Award" to Hideki Yamane's Let's shrink Debian package archive!. Despite it being his first ever Debconf talk/BOF, Yamane-san did an incredibly complete research work to bring arguments about ways to reduce the size of the archive by using xz compression. He triggerred a very live discussion (and for this we can also thank all participants) and the quality of his slides was really high. So, for this, as Tom Marble said after the talk. You definitely deserve it and I'm proud to have you as teammate in the pkg-fonts team.

19 February 2012

Gregor Herrmann: RC bugs 2012/07

thanks to the Paris BSP & other activities we're seeing a nice decline in RC bugs. here are my recent contributions:

8 January 2012

Gregor Herrmann: RC bugs 2012/01

new year, old hobby: trying to fix an RC bug per day, & reporting about it. here's the first episode of 2012:

1 June 2010

Debian News: New Debian Developers (May 2010)

The following developers got their Debian accounts in the last month: Congratulations!

20 December 2009

Christian Perrier: Font packages moved to source v3

Today, Hideki Yamane completed his work on the last four packages maintained by the Font packaging Team to make them switch to source v3. Along with these changes, we also moved all our packages to debhelper v7 and minimal rules files. We also dropped the dependency on the obsoleted defoma. The team maintains 77 source packages for fonts and has now built a quite solid experience in this. In the upcoming weeks, I'll try to get in touch with other people who maintain fonts, inviting them to join the team and maintain their packages in our SVN (we don't do very fancy things so SVN is very well suited for such work). The maingoals will be to continue dropping support for defoma (dropping defoma hints files: you can see good examples on how to do this properly in packages maintained by the team, such as ttf-dejavu). We also intend to drop useless Recommends or Suggests that appear in some font packages (often on "x-ttcidfontconf fontconfig" which is now completely useless) as well as harmonizing package naming schemes (with a "(ttf otf)-<foundry>-<fontname>" scheme). Feel free to join and share your advice and thoughts about The Right Way To Maintain Font Packages on our mailing list.

Next.

Previous.