Differences between revisions 20 and 22 (spanning 2 versions)
Revision 20 as of 2010-03-24 12:58:56
Size: 5714
Editor: HidekiYamane
Comment:
Revision 22 as of 2017-05-23 08:46:40
Size: 5691
Editor: PaulWise
Comment: typos
Deletions are marked like this. Additions are marked like this.
Line 127: Line 127:
  . modify debian/control, add status: field and upload it to repository (if it is an ITP package, that should be skelton package. no upstream source, no maintainer scripts should not be added).   . modify debian/control, add status: field and upload it to repository (if it is an ITP package, that should be skeleton package. no upstream source, no maintainer scripts should not be added).
Line 131: Line 131:
= How to make conrtib/non-free pacakge that goes into main = = How to make conrtib/non-free package that goes into main =
Line 135: Line 135:
Restriction: make delivatives, redistribute delivatives Restriction: make derivatives, redistribute derivatives
Line 140: Line 140:
DM-Upload-Allowed: yes

this is just an idea

stolen from Fedora ;)

NAME: GNOME 2.30


Summary


Include GNOME 2.30

Owner


Current status


The schedule for Gnome 2.30 looks as follows:

Mar 10

2.29.92 rc

Mar 31

2.30.0

Benefit to Debian


Stay in sync with upstream.

Scope


Test Plan


  • (how to check?)

User Experience


Largely unchanged. One noteworthy change is that nautilus defaults to browser mode now.

Dependencies


Depends on upstream Gnome, see the Gnome 2.30 schedule

  • (blockers, etc)

Contingency Plan


  • (When you can't achieve this, what we should do? rollback to older release, choose other ways or nothing to do) ship with 2.28, we already finished 2.28

Documentation


Release Notes


This release includes the latest version of the Gnome desktop, 2.30. For more information about what is new in Gnome, see the Gnome 2.30 release notes

  • (this article will be included to Release Notes)

Comments and Discussion


add Package "Status" to be enable to use through apt/aptitude

  • Pros
    • Everyone can search Orphaned/RFPed/ITPed packages with apt/aptitude interface. It's quite easier rather than using BTS. And it also can check with lintian or so.

    • So, it would be short time packages will go into Debian. Users can get fresh packages and its own status.
  • Cons
    • We need some hack infrastructure for this idea (dak, dpkg and apt/aptitude.

$ apt-cache search sample-application
sample-application (needs new maintainer package)

$ apt-cache show sample-application
Package: sample-application (needs new maintainer package)
Priority: optional
Section: net
Maintainer: Hideki Yamane (Debian-JP) <henrich@debian.or.jp>
Version: 1.0-1
Description: sample
 sample-application is useful for you.
Homepage: http://sample-application.example.org/
Status: orphan [needs new maintainer]

$ apt-cache search sample-application2
sample-application2 [not packaged yet, needs maintainer]

$ apt-cache show sample-application2
Package: sample-application2 [not packaged yet, needs maintainer]
Priority: optional
Section: net
Maintainer: [needs package maintainer]
Version: 1.0-1
Description: sample
 sample-application2 is useful for you.
Homepage: http://sample-application.example.org/
Status: RFP

$ apt-cache search sample-application3
sample-application3 [not in Debian yet, needs more packaging work]

$ apt-cache show sample-application3
Package: sample-application2 [not in Debian yet, needs more packaging work]
Priority: optional
Section: net
Maintainer: Hideki Yamane (Debian-JP) <henrich@debian.or.jp>
Version: 1.0-1
Description: sample
 sample-application3 is useful for you.
Homepage: http://sample-application.example.org/
Status: ITP [waiting for sponsor, in new queue, or so]
  • add Status: field, it shows ITP, RFP, RFH, ITA and Orphan.

  • Status message [foo bar] is added by apt/aptitude. It is NOT added by maintainer.

  • At "Package:" field, add more information what is needed for this package now.
  • flow
    • modify debian/control, add status: field and upload it to repository (if it is an ITP package, that should be skeleton package. no upstream source, no maintainer scripts should not be added).
    • -> report the bug to BTS

    • -> someone adapt the package and upload it to close Status:.

How to make conrtib/non-free package that goes into main

Source: poppler-data
Section: non-free/misc
Restriction: make derivatives, redistribute derivatives
Rights-holder: Adobe Inc.
Reference-Bug: #xxxxxxx
Priority: optional 
Maintainer: Hideki Yamane (Debian-JP) <henrich@debian.or.jp>
Build-Depends: debhelper (>= 5)
Standards-Version: 3.8.1
Homepage: http://poppler.freedesktop.org/
  • add Restriction:, Rights-holder:, Reference-Bug: fields to make license problem fix easier.

install

  • x86/x86-64 のみ、インストーラーが特殊でも構わないのでは?
  • デフォルトでは GUI インストールの方が良い。Live イメージを起動してさらにインストールする Ubuntu 方式が一番良いと思う。
  • インストールイメージを持っておいてそれをコピーして一部パッケージについて configuration する方が、逐一パッケージをダウンロードして設定を実施するよりも早く確実に終わるのではないか?
  • Fedora/OpenSUSE だとインストーラ時に weak なパスワードについて警告をしてくれた。これは欲しい。pam だと思うんだけど。
  • そもそもインストールの流れをもっとダイナミックに変更すべき。
  • 管理画面を yast を参考にもっとよくできない?
  • fedora のアップデートは「packagekit」の「update applet」らしい。
    • 管理用のメニューが階層化されているのがよい
  • opensuse のメインウィンドウ(メインメニュー)が windows like なのは好ましいと思う。使いたい。

PCI ID

Printer メーカー

  • brother
  • hp
  • nec (oem?
  • ricoh
  • canon
  • lexmark
  • alps
  • epson