Hi Debian Packagers,
I'm surprised that /usr/share/doc/gnome-pkg-tools/README.Debian.gz
contradicts with the good practices described in developers reference.
See /usr/share/doc/gnome-pkg-tools/README.Debian.gz :
Copy control to control.in so that it gets refreshed before each build
On Sat, Oct 20, 2007 at 09:02:02AM +0200, Bart Martens wrote:
> I think that the latter is very true. It feels better to me to only
> include names of maintainers really contributing to the packages, so
> that implies a different set of "Uploaders:" per package maintained by
> the team. It more a
pe, 2007-10-19 kello 18:29 +0200, Adrian von Bidder kirjoitti:
> Seriously: I think exactly this kind of "not really much new stuff going
> on, but here's what we're continuing to do" kind of information should be
> more visible, because it, too, is valuable information to somebody who is
> no
On Sat, Oct 20, 2007, Bart Martens wrote:
> I'm surprised that /usr/share/doc/gnome-pkg-tools/README.Debian.gz
> contradicts with the good practices described in developers reference.
[...]
>It feels better to me to only
> include names of maintainers really
How can I find out who sponsored a particular upload? (I only need to do
it by hand, not an automated lookup.)
I expected that I could locate the upload announcement on
debian-devel-changes, then verify the signature to get the key ID, and
look that up. I got a key ID, but can't find out whose it
On Sat, Oct 20, 2007, Hamish Moffatt wrote:
> How can I find out who sponsored a particular upload?
Check the who-uploads helper in devscripts.
--
Loïc Minier
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Hamish Moffatt wrote:
> How can I find out who sponsored a particular upload? (I only need to do
> it by hand, not an automated lookup.)
>
> I expected that I could locate the upload announcement on
> debian-devel-changes, then verify the signature to get the key ID, and
> look that up. I got a k
We encourage people to not file duplicate bug reports, and check the BTS
first. So I check the BTS, the bug is there, I don't file a new one (I
do send a "me too"). 6 weeks later, the bug is closed because the
submitter's email is bouncing and he's on vacation anyway.
It sounds like what is really
Hi,
> How can I find out who sponsored a particular upload? (I only need to do
> it by hand, not an automated lookup.)
My favorite way is to go to the maintainer's qa page,
http://qa.debian.org/developer.php?login=hamish for example, move the
mouse over the version number and look at the tooltip
Package: wnpp
Severity: normal
Hello,
I do not use bins anymore.
The co-maintainer, Martin Michlmayr, do not have time to maintain it
either.
Debian bugs have been formwared upstream at
https://gna.org/bugs/?group=bins but none were ever answered.
It looks like bins has been orphaned upstream.
On Sat, Oct 20, 2007 at 05:15:51PM +0100, peter green wrote:
> >We encourage people to not file duplicate bug reports, and check the BTS
> >first. So I check the BTS, the bug is there, I don't file a new one (I
> >do send a "me too"). 6 weeks later, the bug is closed because the
> >submitter's emai
On Tue, 9 Oct 2007, Bill Allombert wrote:
> Others changes:
> ===
>
> -- Menu support a new format called "menu-2" since 8 years.
Uhmmm, this is one of the strangest sentences I read on this list this
year. At which time scale you would regard eight years old as new (at
least in the
Hi all,
I am running on a MIPS machine, with my kernel and debian distribution
(file system).
The kernel messages are configured to get out from the serial
connection, i.e. serial console.
When the serial output of my MIPS is connected to my PC everything is
OK and I can see the outputs in the term
Hi,
I just got this message, and I don’t know what to do with it. I uploaded
haskell-x11-extras_0.4-1_i386.changes to NEW a while ago, and it’s still
there. Maybe some buildd? Or did someone try to sneak in a package?
Greetings,
Joachim
Am Samstag, den 20.10.2007, 00:22 + schrieb Archive Adm
On Sat Oct 20, 2007 at 12:00:23 +0300, Lars Wirzenius wrote:
>
> pe, 2007-10-19 kello 18:29 +0200, Adrian von Bidder kirjoitti:
> > Seriously: I think exactly this kind of "not really much new stuff going
> > on, but here's what we're continuing to do" kind of information should be
> > more vis
On Fri Oct 19, 2007 at 18:29:46 +0200, Adrian von Bidder wrote:
> That you like pies is important.
:)
> Though in the specific case of the security team, the flow of security
> updates is an indication that the team is working
Yes, this is what I think too.
> Could've cc:ed you at least.
hagit <[EMAIL PROTECTED]> writes:
> I am running on a MIPS machine, with my kernel and debian distribution
> (file system).
> The kernel messages are configured to get out from the serial
> connection, i.e. serial console.
> When the serial output of my MIPS is connected to my PC everything is
> O
Dear maintainers of xine-frontends,
You are receiving this email because you are maintaining a package that
build-depends on libxine-dev, a popular media player. In order to fix the RC
bug #439389, a reorganisation of the xine package has been made. This
reorganisation has effects on xine-lib's f
Thank you for the additional information you have supplied regarding
this problem report. It has been forwarded to the package maintainer(s)
and to other interested parties to accompany the original report.
Your message has been sent to the package maintainer(s):
Reinhard Tartler <[EMAIL PROTECT
Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org
Package name: libmowgli
Version: 0.5.0
Upstream Author: Atheme Project
URL: http://www.atheme-project.org/projects/mowgli.shtml
License: ISC
Description:
Mowgli is a development framework for C (like GLib), which provides
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
peter green wrote:
> It sounds like what is really required is the ability for a bug to have
> multiple "reporters" recorded. Then any queries about a bug can be sent to
> all the reporters not just the one who happened to submit the report
> first.
W
On Sat, Oct 20, 2007 at 01:17:36PM -0300, Felipe Sateler wrote:
> Hamish Moffatt wrote:
> > How can I find out who sponsored a particular upload? (I only need to do
> > it by hand, not an automated lookup.)
> >
> > I expected that I could locate the upload announcement on
> > debian-devel-changes,
On Sat, 20 Oct 2007, peter green wrote:
>> We encourage people to not file duplicate bug reports, and check the BTS
>> first. So I check the BTS, the bug is there, I don't file a new one (I
>> do send a "me too"). 6 weeks later, the bug is closed because the
>> submitter's email is bouncing and he'
Package: wnpp
Severity: wishlist
Owner: "Raúl Sánchez Siles" <[EMAIL PROTECTED]>
* Package name: filelight-i18n
Version : 1.0-1
Upstream Author : Max Howell <[EMAIL PROTECTED]>
* URL : http://www.methylblue.com/filelight/
* License : (GPL)
Programming Lang: (C
Hamish Moffatt wrote:
> On Sat, Oct 20, 2007 at 01:17:36PM -0300, Felipe Sateler wrote:
>
> Excellent. Thanks all for the information. The DDPO method is also
> useful (although it only reveals the login of the uploader, so a visit
> to db.d.o is often required).
Just query finger [EMAIL PROTECT
Reinhard Tartler wrote:
> This change is about to happen in xine-lib_1.1.8-2. Due to the addition
> of the new packages libxine1-x and libxine1-misc-plugins, the package
> will have to be approved by an ftp-master before acceptance into
> unstable. Please prepare yourself to reupload your package w
Quoting Raúl Sánchez Siles ([EMAIL PROTECTED]):
> Package: wnpp
> Severity: wishlist
> Owner: "Raúl Sánchez Siles" <[EMAIL PROTECTED]>
>
> * Package name: filelight-i18n
> Version : 1.0-1
> Upstream Author : Max Howell <[EMAIL PROTECTED]>
> * URL : http://www.methylblue
27 matches
Mail list logo
