arc_5.21q-1_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 27 Jun 2013 13:09:45 +1000 Source: arc Binary: arc Architecture: source amd64 Version: 5.21q-1 Distribution: unstable Urgency: low Maintainer: Debian QA Group Changed-By: Anibal Monsalve Salazar Description: ar

Bug#641449: marked as done (arc: Ambiguous copyright license information)

Your message dated Thu, 27 Jun 2013 04:17:58 + with message-id and subject line Bug#641449: fixed in arc 5.21q-1 has caused the Debian Bug report #641449, regarding arc: Ambiguous copyright license information to be marked as done. This means that you claim that the problem has been dealt wit

Processing of arc_5.21q-1_amd64.changes

arc_5.21q-1_amd64.changes uploaded successfully to localhost along with the files: arc_5.21q-1.dsc arc_5.21q.orig.tar.gz arc_5.21q-1.debian.tar.gz arc_5.21q-1_amd64.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-qa

Processed: tagging 713307

Processing commands for cont...@bugs.debian.org: > tags 713307 + pending Bug #713307 [src:vera] vera: FTBFS: texinfo errors Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 713307: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713307 Debian

Bug report on perl-byacc: pbyacc crashes with exit status 139

Hi, We found a crash in pbyacc contained in the perl-byacc package. You are being contacted because your are listed as one of the maintainer of perl-byacc. We are planning to submit the bug to the Debian bug tracking system in two weeks. We wanted to give you a heads-up, so that you some time to

Bug report on fte-xwindow: xfte crashes with exit status 139

Hi, We found a crash in xfte contained in the fte-xwindow package. You are being contacted because your are listed as one of the maintainer of fte-xwindow. We are planning to submit the bug to the Debian bug tracking system in two weeks. We wanted to give you a heads-up, so that you some time to

Bug report on yagiuda: optimise crashes with exit status 139

Hi, We found a crash in optimise contained in the yagiuda package. You are being contacted because your are listed as one of the maintainer of yagiuda. We are planning to submit the bug to the Debian bug tracking system in two weeks. We wanted to give you a heads-up, so that you some time to asse

Bug report on fte-console: vfte crashes with exit status 139

Hi, We found a crash in vfte contained in the fte-console package. You are being contacted because your are listed as one of the maintainer of fte-console. We are planning to submit the bug to the Debian bug tracking system in two weeks. We wanted to give you a heads-up, so that you some time to

Bug report on gnats: queue-pr crashes with exit status 139

Hi, We found a crash in queue-pr contained in the gnats package. You are being contacted because your are listed as one of the maintainer of gnats. We are planning to submit the bug to the Debian bug tracking system in two weeks. We wanted to give you a heads-up, so that you some time to assess t

Bug report on xtermset: xtermset crashes with exit status 139

Hi, We found a crash in xtermset contained in the xtermset package. You are being contacted because your are listed as one of the maintainer of xtermset. We are planning to submit the bug to the Debian bug tracking system in two weeks. We wanted to give you a heads-up, so that you some time to as

Bug report on mtink: mtinkc crashes with exit status 139

Hi, We found a crash in mtinkc contained in the mtink package. You are being contacted because your are listed as one of the maintainer of mtink. We are planning to submit the bug to the Debian bug tracking system in two weeks. We wanted to give you a heads-up, so that you some time to assess the

Bug report on xfishtank: xfishtank crashes with exit status 139

Hi, We found a crash in xfishtank contained in the xfishtank package. You are being contacted because your are listed as one of the maintainer of xfishtank. We are planning to submit the bug to the Debian bug tracking system in two weeks. We wanted to give you a heads-up, so that you some time to

Bug report on ccontrol: ccontrol crashes with exit status 139

Hi, We found a crash in ccontrol contained in the ccontrol package. You are being contacted because your are listed as one of the maintainer of ccontrol. We are planning to submit the bug to the Debian bug tracking system in two weeks. We wanted to give you a heads-up, so that you some time to as

Bug report on fte-terminal: sfte crashes with exit status 139

Hi, We found a crash in sfte contained in the fte-terminal package. You are being contacted because your are listed as one of the maintainer of fte-terminal. We are planning to submit the bug to the Debian bug tracking system in two weeks. We wanted to give you a heads-up, so that you some time t

Bug report on yudit: mytool crashes with exit status 139

Hi, We found a crash in mytool contained in the yudit package. You are being contacted because your are listed as one of the maintainer of yudit. We are planning to submit the bug to the Debian bug tracking system in two weeks. We wanted to give you a heads-up, so that you some time to assess the

Bug report on xchain: xchain crashes with exit status 139

Hi, We found a crash in xchain contained in the xchain package. You are being contacted because your are listed as one of the maintainer of xchain. We are planning to submit the bug to the Debian bug tracking system in two weeks. We wanted to give you a heads-up, so that you some time to assess t

Bug report on unadf: unadf crashes with exit status 139

Hi, We found a crash in unadf contained in the unadf package. You are being contacted because your are listed as one of the maintainer of unadf. We are planning to submit the bug to the Debian bug tracking system in two weeks. We wanted to give you a heads-up, so that you some time to assess the

Bug report on canna: dpxdic crashes with exit status 139

Hi, We found a crash in dpxdic contained in the canna package. You are being contacted because your are listed as one of the maintainer of canna. We are planning to submit the bug to the Debian bug tracking system in two weeks. We wanted to give you a heads-up, so that you some time to assess the

Bug report on mtink: mtink crashes with exit status 139

Hi, We found a crash in mtink contained in the mtink package. You are being contacted because your are listed as one of the maintainer of mtink. We are planning to submit the bug to the Debian bug tracking system in two weeks. We wanted to give you a heads-up, so that you some time to assess the

Bug report on pmidi: pmidi crashes with exit status 136

Hi, We found a crash in pmidi contained in the pmidi package. You are being contacted because your are listed as one of the maintainer of pmidi. We are planning to submit the bug to the Debian bug tracking system in two weeks. We wanted to give you a heads-up, so that you some time to assess the

Bug report on gnuift: gift-write-feature-descs crashes with exit status 139

Hi, We found a crash in gift-write-feature-descs contained in the gnuift package. You are being contacted because your are listed as one of the maintainer of gnuift. We are planning to submit the bug to the Debian bug tracking system in two weeks. We wanted to give you a heads-up, so that you so

Bug report on canna: canlisp crashes with exit status 139

Hi, We found a crash in canlisp contained in the canna package. You are being contacted because your are listed as one of the maintainer of canna. We are planning to submit the bug to the Debian bug tracking system in two weeks. We wanted to give you a heads-up, so that you some time to assess th

Bug report on gpsk31: gpsk31 crashes with exit status 139

Hi, We found a crash in gpsk31 contained in the gpsk31 package. You are being contacted because your are listed as one of the maintainer of gpsk31. We are planning to submit the bug to the Debian bug tracking system in two weeks. We wanted to give you a heads-up, so that you some time to assess t

Bug report on gcb: gcb crashes with exit status 139

Hi, We found a crash in gcb contained in the gcb package. You are being contacted because your are listed as one of the maintainer of gcb. We are planning to submit the bug to the Debian bug tracking system in two weeks. We wanted to give you a heads-up, so that you some time to assess the seriou

Bug report on fte: cfte crashes with exit status 139

Hi, We found a crash in cfte contained in the fte package. You are being contacted because your are listed as one of the maintainer of fte. We are planning to submit the bug to the Debian bug tracking system in two weeks. We wanted to give you a heads-up, so that you some time to assess the serio

Bug report on auto-apt: auto-apt-pkgcdb crashes with exit status 139

Hi, We found a crash in auto-apt-pkgcdb contained in the auto-apt package. You are being contacted because your are listed as one of the maintainer of auto-apt. We are planning to submit the bug to the Debian bug tracking system in two weeks. We wanted to give you a heads-up, so that you some ti

Bug report on gnats-user: getclose crashes with exit status 139

Hi, We found a crash in getclose contained in the gnats-user package. You are being contacted because your are listed as one of the maintainer of gnats-user. We are planning to submit the bug to the Debian bug tracking system in two weeks. We wanted to give you a heads-up, so that you some time t

Bug report on canna: dpromdic crashes with exit status 139

Hi, We found a crash in dpromdic contained in the canna package. You are being contacted because your are listed as one of the maintainer of canna. We are planning to submit the bug to the Debian bug tracking system in two weeks. We wanted to give you a heads-up, so that you some time to assess t

Bug report on bochs: bochs-bin crashes with exit status 139

Hi, We found a crash in bochs-bin contained in the bochs package. You are being contacted because your are listed as one of the maintainer of bochs. We are planning to submit the bug to the Debian bug tracking system in two weeks. We wanted to give you a heads-up, so that you some time to assess

Bug report on a56: a56 crashes with exit status 139

Hi, We found a crash in a56 contained in the a56 package. You are being contacted because your are listed as one of the maintainer of a56. We are planning to submit the bug to the Debian bug tracking system in two weeks. We wanted to give you a heads-up, so that you some time to assess the seriou

Bug report on a56: a56-keybld crashes with exit status 139

Hi, We found a crash in a56-keybld contained in the a56 package. You are being contacted because your are listed as one of the maintainer of a56. We are planning to submit the bug to the Debian bug tracking system in two weeks. We wanted to give you a heads-up, so that you some time to assess the

Bug#636195: marked as done (fortune-mod: Still need new fortunes webform hosting?)

Your message dated Wed, 26 Jun 2013 18:35:29 +0200 with message-id <20130626163529.GA25255@debian.WAG160N> and subject line Re: fortune-mod: Still need new fortunes webform hosting? has caused the Debian Bug report #636195, regarding fortune-mod: Still need new fortunes webform hosting? to be marke

Bug#522671: marked as done (fortune-mod: The fortune(6) man page gives the wrong path to data files)

Your message dated Wed, 26 Jun 2013 18:16:00 +0200 with message-id <20130626161600.GA24961@debian.WAG160N> and subject line Closing bug has caused the Debian Bug report #522671, regarding fortune-mod: The fortune(6) man page gives the wrong path to data files to be marked as done. This means that

Bug#514082: marked as done (man fortunes give wrong file locations)

Your message dated Wed, 26 Jun 2013 18:21:00 +0200 with message-id <20130626162100.GA25167@debian.WAG160N> and subject line Closing the bug has caused the Debian Bug report #514082, regarding man fortunes give wrong file locations to be marked as done. This means that you claim that the problem ha

python-socksipy_1.0-2_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 26 Jun 2013 16:58:19 +0200 Source: python-socksipy Binary: python-socksipy Architecture: source all Version: 1.0-2 Distribution: unstable Urgency: low Maintainer: Debian QA Group Changed-By: Sebastian Ramacher De

Bug#479062: fortune-mod: cannot select english fortunes having the non-English locale

tags 479062 - moreinfo tags 479062 - unreproducible tags 479062 confirmed stop On Tue, Jun 25, 2013 at 10:15:49PM +0300, Eugene V. Lyubimkin wrote: > The bug (wish?) is: in the case 2) there is no visible way to select an > English > fortune having German locale. Ah, I see the point now, and can

Processed: Re: fortune-mod: cannot select english fortunes having the non-English locale

Processing commands for cont...@bugs.debian.org: > tags 479062 - moreinfo Bug #479062 [fortune-mod] fortune-mod: cannot select english fortunes having the non-English locale Removed tag(s) moreinfo. > tags 479062 - unreproducible Bug #479062 [fortune-mod] fortune-mod: cannot select english fortun

Processing of python-socksipy_1.0-2_amd64.changes

python-socksipy_1.0-2_amd64.changes uploaded successfully to localhost along with the files: python-socksipy_1.0-2.dsc python-socksipy_1.0-2.diff.gz python-socksipy_1.0-2_all.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to d

Bug#578687: marked as done (Suggestion -- Ayn Rand quotes should be moved to fortunes-off)

Your message dated Wed, 26 Jun 2013 16:54:36 +0200 with message-id <20130626145436.GA5482@debian.WAG160N> and subject line Re: Suggestion -- Ayn Rand quotes should be moved to fortunes-off has caused the Debian Bug report #578687, regarding Suggestion -- Ayn Rand quotes should be moved to fortunes

H24INFO : Toutes les infos qu'il vous faut

Se désinscrire de la liste: http://link.h24info.ma/u/443/738cb0bbdfd56cc52d3f8bbee7ba3a6c5eb6508290db6da9