Re: Chao ban ve may bay

[Chinh Chinh]

 
 
		Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls.  Great rates starting at 1¢/min.

Re: problem with packaging

[Adrian von Bidder]

On Friday 07 April 2006 15:43, jean wrote:
> hi,
> i'm trying to create a package for sarge (it is my first experience in
> packet creation ), i tried to do this from an existing packet, i have
> decompacted the packet, i modified some things, and i re-packaged the
> folder.

As others have said: you'd rarely create binary packages 'out of thin air' - 
usually you'd write/modify a Debian source package (this is a .tar.gz file, 
an optional .diff.gz file and a .dsc file) and use standard Debian tools 
(dpkg-buildpackage, debuild or some others) to create a new binary package.

Here are some URLs to get you started:


  (These are some slides - not very verbose, but might give you a quick 
idea)

  (This will get you started quite efficiently)

  (this is the definitive reference on Debian packages.  Probably not what 
you'd want to start with, though.)

greetings
-- vbi

-- 
featured product: the GNU Compiler Collection - http://gcc.gnu.org


pgpf7p8cK3x9d.pgp
Description: PGP signature

deb src

[krotics]

Добрый  день! Подскажите где можно найти diff.gz для сборки gcc 4.0.1, glibc 
2.3.5, MySQL 5.0.12 ?Существует такой ресурс где хранятся все  diff.gz  для 
всех версий исходников?

Re: deb src

[Andrew Donnellan]

This is an English language list - please post in English.

andrew

On 4/8/06, krotics <[EMAIL PROTECTED]> wrote:
> Добрый  день! Подскажите где можно найти diff.gz для сборки gcc 4.0.1, glibc
> 2.3.5, MySQL 5.0.12 ?Существует такой ресурс где хранятся все  diff.gz  для
> всех версий исходников?
>


--
Andrew Donnellan
http://andrewdonnellan.com
http://ajdlinux.blogspot.com
Jabber - [EMAIL PROTECTED]
---
Member of Linux Australia - http://linux.org.au
Debian user - http://debian.org
Get free rewards - http://ezyrewards.com/?id=23484
OpenNIC user - http://www.opennic.unrated.net

Re: deb src

[Linas Zvirblis]

> This is an English language list - please post in English.

>> Добрый  день! Подскажите где можно найти diff.gz для сборки gcc 4.0.1, glibc
>> 2.3.5, MySQL 5.0.12 ?Существует такой ресурс где хранятся все  diff.gz  для
>> всех версий исходников?

--- translation ---
Good afternoon! Could you please tell me where to find diff.gz for a
collection of gcc 4.0.1, glibc 2.3.5, MySQL 5.0.12? Is there such place
where all diff.gz, for all versions of source code, are kept?
---


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#361400: ITP: museek+ -- file-sharing application for the SoulSeek peer-to-peer network

[Le_Vert]

Package: wnpp
Severity: wishlist
Owner: "Adam Cécile (Le_Vert)" <[EMAIL PROTECTED]>

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


* Package name: museek+
  Version : 0.1.2
  Upstream Author : "Daelstorm" <[EMAIL PROTECTED]>
* URL : http://thegraveyard.org/daelstorm/
* License : GPL
  Description : file-sharing application for the SoulSeek peer-to-peer 
network

 Museek+ consists of museekd (daemon), museeq (QT gui), muscan (tool for
 scanning shared files), musetup (configuration script), museekchat (Curses
 chat client), and Python bindings.

- -- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (900, 'testing'), (400, 'stable'), (300, 'unstable'), (250, 
'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-k7
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.2 (GNU/Linux)

iD8DBQFEN7A/HNb/igTI5bsRAlH/AJ40r3je7Fasde2EzVHbdVgn+GTWYwCfZcZW
H5TTkaWYvLmbrSfhRgg5yH8=
=Bmp/
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#361418: [Proposal] new Debian menu structure

[Bill Allombert]

Package: debian-policy
Version: 3.6.2.2
Severity: wishlist

Background:
--
The menu structure define the list of sections and subsections of
the Debian menu system (which are displayed in window-managers menus).
The official list is part of the Debian menu subpolicy.  This list is a
bit outdated, so we are proposing an update.

Proposal:

Following discussion on debian-policy I am formally proposing the 
new Debian menu structure devised by Linas Zvirblis to be included
in the Debian menu subpolicy.

For transitionning from the old structure, the translate_menus system
will be reused.  

What should you do:
--
--- As a packages maintainer: check whether your menu entry fit in the
new structure.
--- As a translator: check whether the new names are easier to
understand and translate.
--- As a Debian user: check whether the new structure improve the Debian
menu system.

Thanks in advance for all your suggestions for improvement. Please send
them to this buglog so we find them.

Please find in attachment:
-
1) The proposed new menu structure

2) The translate_menus file. To experiment with the new menu structure,
copy this file to /etc/menu-methods/ and rerun update-menus, the new
menu structure will be in effect as far as renaming of section are 
concerned (this will not add/remove new sections by itself).  Note that
this is English only until menu is translated (which will happen as soon
as the new structure is finalised and official).

Summary of changes:
--

1) Removed section:
Apps/Tools
Games/Sports
Screen/Root-window

2) Renamed sections:
Applications [was:Apps]
  Educational [was:Education]
  HAM Radio [was:Hamradio]
  Mathematical [was:Math]
  Network [was:Net]
  Scientific [was:Science]
 System/Administration [was:Admin]
 System/Language Environment [was:Language-Environment]
  Terminal Emulators [was:XShells]
Games
  Blocks [was:Tetris-like]
Screen
  Saving [was:Save]
  Locking [was:Lock]

Window Managers [was:WindowManagers]
Modules [was:WindowManagers/Modules]

3) New sections:

Applications [was:Apps]
  Accessibility [new]
  Data Management [new]
  File Management [new]
  Mobile Devices [new]
  Network [was:Net]
 Network/Communication [new]
 Network/File Transfer [new]
 Network/Monitoring [new]
 Network/Web Browsing [new]
 Network/Web News [new]
  Office [new]
  Project Management [new]
  System
 System/Hardware [new]
 System/Monitoring [new]
 System/Package Management [new]
 System/Security [new]
  Technical
 Technical/Electronics [new]
 Technical/Engineering [new]

  TV and Radio [new]
  Video [new]
  Web Development [new]

Games
  Tools [new]

Acknowledgement:
---
This new structure was devised by Linas Zvirblis with input from the
debian-policy mailing list.

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 
Applications [was:Apps]
Normal applications. This is top level
section, do not put entries here.

  Accessibility [new]
  Tools to aid people with disabilities or
  on machines lacking usual input devices.
  gok, yasr, dasher

  Data Management [new]
  Interactive database programs, collection
  managers, bibliography tools etc.
  gaby, alexandria, mdbtools

  Editors
  Editors, other than office word processors,
  for text based information.
  ksubtile, nano, hexedit

  Educational [was:Education]
  Educational and training software.
  gtypist, gcompris, quiz

  Emulators
  Software that allows you to run non-native
  software or more than one OS at a time.
  wine, dosemu, qemu

  File Management [new]
  Tools for file management, archiving,
  searching, CD/DVD burning and backup.
  file-roller, mc, baobab

  Graphics
  2D and 3D graphics manipulation software.
  gimp, inkscape, imagemagick

  HAM Radio [was:Hamradio]
  Anything relating to HAM radio.
  baken, hamsoft, twlog

  Mathematical [was:Math]
  Mathematics related software.
  gcalctool, snapea, xeukleides

  Mobile Devices [new]
  Software that allows you to interface
  with mobile devices (phones, PDA's etc.).
  kandy, gnokii, gnome-pilot

  Network [was:Net]
  Network related software. This is three level
  menu, do not put entries in second (this) level.

 Network/Communication [new]
 Mail, USENET news, chat, instant messaging,
 IP telephony, video conferencing software.
 xchat, gaim, mutt

 Network/File Transfer [new]
 File transfer software such as download
 managers, FTP clients, P2P clients.
 amule, gftp, d4x

 Network/Monitoring [new]
 Network monitoring software.
 gip, ettercap, iptstate

 Network/Web Browsing [new]
 Web browsers, tools for offline browsing.
 elinks, epiphany-browser, webhttrack

 Network/Web News
 Web feed (RSS, Atom etc.)
 and podcast aggregators.
 akregator, kitty, liferea

  Office [new]
  Office suites, word processors, spreadsheets,
  address books, CRM, ERP, fina

Re: deb src

[Alexander Schmehl]

Hi!

* Linas Zvirblis <[EMAIL PROTECTED]> [060408 13:45]:
> --- translation ---
> Good afternoon! Could you please tell me where to find diff.gz for a
> collection of gcc 4.0.1, glibc 2.3.5, MySQL 5.0.12? Is there such place
> where all diff.gz, for all versions of source code, are kept?
> ---

Beside deb debian mirros (which don't have every package release),
there's snapshot.debian.net (which isn't complete).

Yours sincerely,
  Alexander

-- 
http://learn.to/quote/
http://www.catb.org/~esr/faqs/smart-questions.html


signature.asc
Description: Digital signature

Bug#361429: ITP: libtext-bibtex-perl -- Perl extension to read and parse BibTeX files

[Bas Zoetekouw]

Package: wnpp
Severity: wishlist
Owner: Bas Zoetekouw <[EMAIL PROTECTED]>

* Package name: libtext-bibtex-perl
  Version : 0.36
  Upstream Author : Greg Ward <[EMAIL PROTECTED]>
* URL : http://search.cpan.org/~ambs/Text-BibTeX-0.36/
* License : Artistic/GPL
  Description : Perl extension to read and parse BibTeX files

 The Text::bibTeX module provides functions to read, parse and write
 bibTeX files using perl.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15.4
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Final call for votes for the debian project leader election 2006

[Toni Mueller]

On Thu, 06.04.2006 at 18:40:04 -0500, Debian Project Secretary <[EMAIL 
PROTECTED]> wrote:
> - - -=-=-=-=-=- Don't Delete Anything Between These Lines =-=-=-=-=-=-=-=-
> 52717dc0-26e3-4337-a88b-cc2c260fcb51
> [   ] Choice 1: Jeroen van Wolffelaar
> [   ] Choice 2: Ari Pollak
> [ 3 ] Choice 3: Steve McIntyre
> [ 2 ] Choice 4: Anthony Towns 
> [   ] Choice 5: Andreas Schuldei
> [   ] Choice 6: Jonathan aka Ted Walther
> [ 1 ] Choice 7: Bill Allombert
> [   ] Choice 8: None Of The Above
> - - -=-=-=-=-=- Don't Delete Anything Between These Lines =-=-=-=-=-=-=-=-


pgpcbZBkutKd5.pgp
Description: PGP signature

RFH: Test swt-gtk (azureus) on ia64 and alpha

[Shaun Jackman]

It has been reported that swt-gtk -- and azureus, which depends on it
-- does not work on amd64. I suspect this is true of all 64-bit
architectures. If you have access to a 64-bit architecture besides
amd64, I would very much appreciate your help with this bug. The
version in Sarge (libswt-gtk3=3.0-6) as well as the version that was
in unstable (libswt-gtk-3.1=3.1.2-1) on 2006-02-07 both need testing.

libswt-gtk-3.1=3.1.2-1 has been removed from the Debian archive, but
is available from snapshot.debian.net:
http://snapshot.debian.net/archive/2006/02/07/debian/pool/main/s/swt-gtk/

Thank you very much for your help porting to your architecture!
Shaun

deb src

[krot]

Good afternoon! Prompt where it is possible to find diff.gz for assembly gcc 
4.0.1, glibc 2.3.5, MySQL 5.0.12? There Is such resource where are stored{kept} 
all diff.gz for all versions of source codes?







-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Final call for votes for the debian project leader election 2006

[Toni Mueller]

Hi
sorry for the mistake :-(

--Toni, not fully awake++


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: deb src

[Alexander Schmehl]

* krot <[EMAIL PROTECTED]> [060408 20:22]:

> Good afternoon! Prompt where it is possible to find diff.gz for
> assembly gcc 4.0.1, glibc 2.3.5, MySQL 5.0.12? There Is such resource
> where are stored{kept} all diff.gz for all versions of source codes?

http://lists.debian.org/debian-devel/2006/04/msg00134.html


Yours sincerely,
  Alexander

-- 
http://learn.to/quote/
http://www.catb.org/~esr/faqs/smart-questions.html


signature.asc
Description: Digital signature

Re: deb src

[Kevin Mark]

On Sun, Apr 09, 2006 at 12:22:25AM +0600, krot wrote:
> Good afternoon! Prompt where it is possible to find diff.gz for assembly gcc 
> 4.0.1, glibc 2.3.5, MySQL 5.0.12? There Is such resource where are 
> stored{kept} all diff.gz for all versions of source codes?
> 
Hi,
All binary packages have associated source packages which contain diffs. You 
can use go to
packages.debian.org to download all of these and the diff files.
Cheers,
Kev
-- 
|  .''`.  == Debian GNU/Linux == |   my web site:   |
| : :' :  The  Universal | debian.home.pipeline.com |
| `. `'  Operating System| go to counter.li.org and |
|   `-http://www.debian.org/ |be counted! #238656   |
| my keysever: pgp.mit.edu   | my NPO: cfsg.org |


signature.asc
Description: Digital signature

Re: Bug#361418: [Proposal] new Debian menu structure

[Hamish Moffatt]

On Sat, Apr 08, 2006 at 04:46:10PM +0200, Bill Allombert wrote:
> Package: debian-policy
> Version: 3.6.2.2
> Severity: wishlist
> 
> Background:
> --
> The menu structure define the list of sections and subsections of
> the Debian menu system (which are displayed in window-managers menus).
> The official list is part of the Debian menu subpolicy.  This list is a
> bit outdated, so we are proposing an update.
> 
[...]
> 2) Renamed sections:
> Applications [was:Apps]
>   Educational [was:Education]
>   HAM Radio [was:Hamradio]
[...]

Hi Bill,

"HAM" is not an acronym, so "Ham Radio" would be more appropriate.

Even better (IMHO) is the full term "Amateur Radio", but some may
disagree. I've CC'd debian-hams for their input also.


Thanks for the work on the new menu structure.

Hamish
-- 
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Results for Debian Project Leader 2006 Election Statistics

[devotee]

Greetings,

This message is an automated, unofficial publication of vote results.
 Official results shall follow, sent in by thesecretary.  This is just a
 convenience for the impatient.  I remain, gentle folks,

Your humble servant,
Devotee (on behalf of Debian Project Secretary)

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Starting results calculation at Sun Apr  9 00:00:16 2006

Option 1 "Jeroen van Wolffelaar"
Option 2 "Ari Pollak"
Option 3 "Steve McIntyre"
Option 4 "Anthony Towns"
Option 5 "Andreas Schuldei"
Option 6 "Jonathan aka Ted Walther"
Option 7 "Bill Allombert"
Option 8 "None of the Above"

In the following table, tally[row x][col y] represents the votes that
option x received over option y.

  Option
  1 2 3 4 5 6 7 8 
===   ===   ===   ===   ===   ===   ===   === 
Option 1  310   123   144   166   341   228   319 
Option 2 40  344645   24648   158 
Option 3230   332 184   233   354   278   344 
Option 4230   334   190 242   365   281   339 
Option 5166   320   124   135 352   240   321 
Option 6 2061161616  2173 
Option 7119   2756899   117   321 294 
Option 8 75   202537175   30187   



Looking at row 2, column 1, Ari Pollak
received 40 votes over Jeroen van Wolffelaar

Looking at row 1, column 2, Jeroen van Wolffelaar
received 310 votes over Ari Pollak.

Option 1 Reached quorum: 319 > 47.0531614240744
Option 2 Reached quorum: 158 > 47.0531614240744
Option 3 Reached quorum: 344 > 47.0531614240744
Option 4 Reached quorum: 339 > 47.0531614240744
Option 5 Reached quorum: 321 > 47.0531614240744
Option 6 Reached quorum: 73 > 47.0531614240744
Option 7 Reached quorum: 294 > 47.0531614240744


Option 1 passes Majority.   4.253 (319/75) > 1
Dropping Option 2 because of Majority.  0.782 (158/202) < 1
Option 3 passes Majority.   6.491 (344/53) > 1
Option 4 passes Majority.   4.775 (339/71) > 1
Option 5 passes Majority.   4.280 (321/75) > 1
Dropping Option 6 because of Majority.  0.243 (73/301) < 1
Option 7 passes Majority.   3.379 (294/87) > 1


  Option 3 defeats Option 1 by ( 230 -  123) =  107 votes.
  Option 4 defeats Option 1 by ( 230 -  144) =   86 votes.
  Option 1 defeats Option 7 by ( 228 -  119) =  109 votes.
  Option 1 defeats Option 8 by ( 319 -   75) =  244 votes.
  Option 4 defeats Option 3 by ( 190 -  184) =6 votes.
  Option 3 defeats Option 5 by ( 233 -  124) =  109 votes.
  Option 3 defeats Option 7 by ( 278 -   68) =  210 votes.
  Option 3 defeats Option 8 by ( 344 -   53) =  291 votes.
  Option 4 defeats Option 5 by ( 242 -  135) =  107 votes.
  Option 4 defeats Option 7 by ( 281 -   99) =  182 votes.
  Option 4 defeats Option 8 by ( 339 -   71) =  268 votes.
  Option 5 defeats Option 7 by ( 240 -  117) =  123 votes.
  Option 5 defeats Option 8 by ( 321 -   75) =  246 votes.
  Option 7 defeats Option 8 by ( 294 -   87) =  207 votes.


The Schwartz Set contains:
 Option 4 "Anthony Towns"



-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

The winners are:
 Option 4 "Anthony Towns"

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

-- 
The voters have spoken, the bastards... --unknown
DEbian VOTe EnginE
digraph Results {
  ranksep=0.25;
 "Jeroen van Wolffelaar\n4.25" [ style="filled" , fontname="Helvetica", 
fontsize=10  ];
 "Jeroen van Wolffelaar\n4.25" -> "Bill Allombert\n3.38" [ label="109" ];
 "Jeroen van Wolffelaar\n4.25" -> "None of the Above" [ label="244" ];
 "Ari Pollak\n0.78" [ style="filled" , color="pink", shape=octagon, 
fontname="Helvetica", fontsize=10  ];
 "None of the Above" -> "Ari Pollak\n0.78" [ label="44" ];
 "Steve McIntyre\n6.49" [ style="filled" , fontname="Helvetica", fontsize=10  ];
 "Steve McIntyre\n6.49" -> "Jeroen van Wolffelaar\n4.25" [ label="107" ];
 "Steve McIntyre\n6.49" -> "Andreas Schuldei\n4.28" [ label="109" ];
 "Steve McIntyre\n6.49" -> "Bill Allombert\n3.38" [ label="210" ];
 "Steve McIntyre\n6.49" -> "None of the Above" [ label="291" ];
 "Anthony Towns\n4.77" [ style="filled" , color="powderblue", shape=egg, 
fontcolor="Navy Blue", fontname="Helvetica", fontsize=10  ];
 "Anthony Towns\n4.77" -> "Jeroen van Wolffelaar\n4.25" [ label="86" ];
 "Anthony Towns\n4.77" -> "Steve McIntyre\n6.49" [ label="6" ];
 "Anthony Towns\n4.77" -> "Andreas Schuldei\n4.28" [ label="107" ];
 "Anthony Towns\n4.77" -> "Bill Allombert\n3.38" [ label="182" ];
 "Anthony Towns\n4.77" -> "None of the Above" [ label="268" ];
 "Andreas Schuldei\n4.28" [ style="filled" , fontname="Helvetica", fontsize=10  
];
 "Andreas Schuldei\n4.28" -> "Bill Allombert\n3.38" [ label="123" ];
 "Andreas Schul

Re: Bug#361418: [Proposal] new Debian menu structure

[Andrew M.A. Cater]

On Sun, Apr 09, 2006 at 09:48:48AM +1000, Hamish Moffatt wrote:
> On Sat, Apr 08, 2006 at 04:46:10PM +0200, Bill Allombert wrote:
> > Package: debian-policy
> > Version: 3.6.2.2
> > Severity: wishlist
> > 
> > Background:
> > --
> > The menu structure define the list of sections and subsections of
> > the Debian menu system (which are displayed in window-managers menus).
> > The official list is part of the Debian menu subpolicy.  This list is a
> > bit outdated, so we are proposing an update.
> > 
> [...]
> > 2) Renamed sections:
> > Applications [was:Apps]
> >   Educational [was:Education]
> >   HAM Radio [was:Hamradio]
> [...]
> 
> Hi Bill,
> 
> "HAM" is not an acronym, so "Ham Radio" would be more appropriate.
> 
> Even better (IMHO) is the full term "Amateur Radio", but some may
> disagree. I've CC'd debian-hams for their input also.
> 
Radio amateur / amateur radio : either would be fine IMHO.

Andy [Amateur radio callsign G0EVX]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Proper way of closing *old* bugs

[Adam Majer]

Hello everyone,

I've written an email to Cyril Bouthors that started as,


"In your 4.0.0-3 upload of gluplot, you've said in the changelog

 * This upload is aimed to take over the package and fix the easiest bugs
   first. I'll upload another version shortly that will take care of the
   oh-so-many opened bugs that look almost all fixed upstream and/or
   obsolete to me. One of them is 5 years and 160 days old! "Release
   early, release often".
"

The rest of the email and his response follows,

Cyril Bouthors wrote:
> On  3 Apr 2006, Adam Majer wrote:
>
>   
>> But the correct method of closing bugs is to send a message to
>> [EMAIL PROTECTED] with the explanation of the fix and not in
>> the changelog. Well, at least not in the way you seem to intend. The
>> bugs closed in changelogs are suppose to be bugs closed due to the
>> changes from the previous version to the current version. If you only
>> mean to do,
>>
>> * Close bugs that were fixed VERY long time ago (closes:
>> #123,#234,#345,#456,#567,#678,#789,)
>>
>> then I don't think that is appropriate use of the changelog.
>> 
>
> Closing bugs through the changelog is an officially supported method
> and most DDs close bugs that way. Submitters receive a detailed
> notification by email as soon as the package is uploaded.
>
> I have no special mean to close bugs without informing the submitters
> with a clear and detailed explanation as I always did with all my
> packages.
>   



My question is, is it now appropriate to use the changelog as a crutch
to close bugs that have nothing to do with the upload? I was always
under impression that *old* bugs should be closed by sending an email to
[EMAIL PROTECTED] saying that you are closing it because it was
fixed some time ago, etc.. etc..

The policy [1] states,

"If this upload resolves bugs recorded in the Bug Tracking System
(BTS), they may be automatically closed on the inclusion of this package
into the Debian archive by including the string: closes: Bug#n in
the change details."

Therefore, by my reading of the policy the changelog is not an
appropriate method of closing *old* bugs because they were not resolved
by the upload. They were resolved some time ago and should be closed by
a mail to the BTS.

- Adam

[1] http://www.debian.org/doc/debian-policy/ch-source.html#s-dpkgchangelog



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Proper way of closing *old* bugs

[Matthew Palmer]

On Sat, Apr 08, 2006 at 05:55:05PM -0500, Adam Majer wrote:
> Cyril Bouthors wrote:
> > On  3 Apr 2006, Adam Majer wrote:
> >
> >   
> >> But the correct method of closing bugs is to send a message to
> >> [EMAIL PROTECTED] with the explanation of the fix and not in
> >> the changelog. Well, at least not in the way you seem to intend. The
> >> bugs closed in changelogs are suppose to be bugs closed due to the
> >> changes from the previous version to the current version. If you only
> >> mean to do,
> >>
> >> * Close bugs that were fixed VERY long time ago (closes:
> >> #123,#234,#345,#456,#567,#678,#789,)
> >>
> >> then I don't think that is appropriate use of the changelog.
> >> 
> >
> > Closing bugs through the changelog is an officially supported method
> > and most DDs close bugs that way. Submitters receive a detailed
> > notification by email as soon as the package is uploaded.
> >
> > I have no special mean to close bugs without informing the submitters
> > with a clear and detailed explanation as I always did with all my
> > packages.

I'm stunned that anyone still thinks that closing unrelated bugs in a
changelog is a good idea.  [EMAIL PROTECTED] sends the detailed close message
to the submitter, and it doesn't make it look like the problem was fixed in
that version (which, of course, it wasn't).

> My question is, is it now appropriate to use the changelog as a crutch
> to close bugs that have nothing to do with the upload? I was always
> under impression that *old* bugs should be closed by sending an email to
> [EMAIL PROTECTED] saying that you are closing it because it was
> fixed some time ago, etc.. etc..

Absolutely.

There's some debate over whether closing upstream bugs in the changelog is
OK, like so:

  * New upstream version.  (Closes: #N)
- The bar is now frobbed correctly.  (Closes: #X)
- No longer trip over our shoelaces.  (Closes: #Y)
  * Random package installation failures stopped.  (Closes: #)

Some people think that it shouldn't be done ever, since it's not a change
that the maintainer explicitly made, but others think that it's OK when done
like that shown above, as it preserves all of the useful information.

But I can't think of *any* discussion which has ended with people claiming
that closing random bugs is OK in an upload.  How would you even describe it
in the changelog?

  * The bug has magically disappeared.  (Closes: #NNN)
  
Uhhh... I doubt it.

- Matt


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Results for Debian Project Leader 2006 Election Statistics

[Adam Borowski]

On Sat, 8 Apr 2006, [EMAIL PROTECTED] wrote:

Option 3 "Steve McIntyre"
Option 4 "Anthony Towns"


Take a look at these numbers:


Option 3 Reached quorum: 344 > 47.0531614240744
Option 4 Reached quorum: 339 > 47.0531614240744



Option 3 passes Majority.   6.491 (344/53) > 1
Option 4 passes Majority.   4.775 (339/71) > 1



 Option 3 defeats Option 1 by ( 230 -  123) =  107 votes.
 Option 4 defeats Option 1 by ( 230 -  144) =   86 votes.



 Option 3 defeats Option 5 by ( 233 -  124) =  109 votes.
 Option 4 defeats Option 5 by ( 242 -  135) =  107 votes.



 Option 3 defeats Option 7 by ( 278 -   68) =  210 votes.
 Option 4 defeats Option 7 by ( 281 -   99) =  182 votes.



 Option 3 defeats Option 8 by ( 344 -   53) =  291 votes.
 Option 4 defeats Option 8 by ( 339 -   71) =  268 votes.


So, 3 (Steve) clearly wins over 4 (aj) everywhere except:

 Option 4 defeats Option 3 by ( 190 -  184) =6 votes.


Nice close shave...


The Schwartz Set contains:
 Option 4 "Anthony Towns"


Congrats!


--
/---\ Shh, be vewy, vewy quiet,
| [EMAIL PROTECTED] | I'm hunting wuntime ewwows!
\---/
Segmentation fault (core dumped)


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Bug#361418: [Proposal] new Debian menu structure

[Christian Perrier]

> "HAM" is not an acronym, so "Ham Radio" would be more appropriate.
> 
> Even better (IMHO) is the full term "Amateur Radio", but some may
> disagree. I've CC'd debian-hams for their input also.


HAM is probably well known among the amateur radio community.

However, *outside* this community, the name is pretty cryptic (I have
not idea, actually, what this "H" letter stands for).

So, I would also second "Amateur radio"...



signature.asc
Description: Digital signature

Re: Proper way of closing *old* bugs

[Stephen Samuel]

It seems to me that, in this case (and correct me if I'm wrong), the 
package hasn't been updated from upstream for a long time, and so the 
difference between the old version and the new version fixes the stack 
of old bugs (( even though it wasn't _this specific version_ where the 
bug was fixed )).


Now, if the bug has been (contrary to my reading) fixed for a long time, 
and just not reported as fixed, then I can see it being misleading to 
fix the bug via the changelog.


If it's a case of being lazy, then you can just something like:

while read bug notes ; do
( echo bug $bug was fixed a long time ago ; echo " $notes" | fmt ) | 
Mail [EMAIL PROTECTED]

done << EOF
42 A mouse did it
31415 Used a circular log
42923 Mikie did it.
EOF

Matthew Palmer wrote:

On Sat, Apr 08, 2006 at 05:55:05PM -0500, Adam Majer wrote:
  

Cyril Bouthors wrote:


On  3 Apr 2006, Adam Majer wrote:

  
  

But the correct method of closing bugs is to send a message to
[EMAIL PROTECTED] with the explanation of the fix and not in
the changelog. Well, at least not in the way you seem to intend. The
bugs closed in changelogs are suppose to be bugs closed due to the
changes from the previous version to the current version. If you only
mean to do,

* Close bugs that were fixed VERY long time ago (closes:
#123,#234,#345,#456,#567,#678,#789,)

then I don't think that is appropriate use of the changelog.



Closing bugs through the changelog is an officially supported method
and most DDs close bugs that way. Submitters receive a detailed
notification by email as soon as the package is uploaded.

I have no special mean to close bugs without informing the submitters
with a clear and detailed explanation as I always did with all my
packages.
  


I'm stunned that anyone still thinks that closing unrelated bugs in a
changelog is a good idea.  [EMAIL PROTECTED] sends the detailed close message
to the submitter, and it doesn't make it look like the problem was fixed in
that version (which, of course, it wasn't).

  

My question is, is it now appropriate to use the changelog as a crutch
to close bugs that have nothing to do with the upload? I was always
under impression that *old* bugs should be closed by sending an email to
[EMAIL PROTECTED] saying that you are closing it because it was
fixed some time ago, etc.. etc..



Absolutely.

There's some debate over whether closing upstream bugs in the changelog is
OK, like so:

  * New upstream version.  (Closes: #N)
- The bar is now frobbed correctly.  (Closes: #X)
- No longer trip over our shoelaces.  (Closes: #Y)
  * Random package installation failures stopped.  (Closes: #)

Some people think that it shouldn't be done ever, since it's not a change
that the maintainer explicitly made, but others think that it's OK when done
like that shown above, as it preserves all of the useful information.

But I can't think of *any* discussion which has ended with people claiming
that closing random bugs is OK in an upload.  How would you even describe it
in the changelog?

  * The bug has magically disappeared.  (Closes: #NNN)
  
Uhhh... I doubt it.


- Matt


  



--
Stephen Samuel +1(778)861-7641 [EMAIL PROTECTED]
   http://www.bcgreen.com/
  Powerful committed communication. Transformation touching
the jewel within each person and bringing it to light.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]