Hi!
On Mon, 2011-07-04 at 18:11:37 +0200, Christoph Berg wrote:
> We don't distinguish unstable and experimental anymore in the DEHS
> setup; the "up to date" messages is what uscan outputs when passed a
> version number (which we take from unstable). At the moment I don't
> think a separate setup
Hi,
On Wed, 08 Jun 2011, Christoph Berg wrote:
> * fix the PTS to use that
I just did that and I reused the same YAML file you exported for UDD.
Cheers,
--
Raphaël Hertzog ◈ Debian Developer
Follow my Debian News ▶ http://RaphaelHertzog.com (English)
▶ http://RaphaelHert
Hi Raphael,
On Mon, 04 Jul 2011, Raphael Geissert wrote:
> > I've set up a WIP version of a new DEHS instance that uses the watch
> > files from the lintian lab to submit uscan results to mole. The data
> > is then extracted as a .db file and presented in DDPO.
>
> I know I disappeared, but this
Christoph Berg wrote:
> Hi,
>
> I've set up a WIP version of a new DEHS instance that uses the watch
> files from the lintian lab to submit uscan results to mole. The data
> is then extracted as a .db file and presented in DDPO.
I know I disappeared, but this is... *sigh*
There is more to it th
Re: Lucas Nussbaum 2011-06-15 <20110615084236.ga13...@xanadu.blop.info>
> > > UDD was importing DEHS data from
> > > http://dehs.alioth.debian.org/udd_dump.txt
> yes, YAML would be perfect.
Hi,
sorry it took a while. There now yaml data at
http://qa.debian.org/cgi-bin/udd-dehs
Data is updated
On 15/06/11 at 10:32 +0200, Christoph Berg wrote:
> Re: Lucas Nussbaum 2011-06-14 <20110614172545.ga8...@xanadu.blop.info>
> > UDD was importing DEHS data from
> > http://dehs.alioth.debian.org/udd_dump.txt
>
> abi-compliance-checker|1.21.12||1.6-1||1.6-1||f||f||1970-01-01 00:00:00|
> abicheck|1.2
Re: Lucas Nussbaum 2011-06-14 <20110614172545.ga8...@xanadu.blop.info>
> UDD was importing DEHS data from
> http://dehs.alioth.debian.org/udd_dump.txt
abi-compliance-checker|1.21.12||1.6-1||1.6-1||f||f||1970-01-01 00:00:00|
abicheck|1.2||1.2-5||1.2-5||t||f||2011-05-04 06:15:58|
abind|1.3.0||1.3.0-
On 14/06/11 at 14:28 +0200, Christoph Berg wrote:
> Re: To debian-qa@lists.debian.org 2011-06-08
> <20110608094252.gc3...@msgid.df7cb.de>
> > I've set up a WIP version of a new DEHS instance that uses the watch
> > files from the lintian lab to submit uscan results to mole. The data
> > is then ex
Re: To debian-qa@lists.debian.org 2011-06-08
<20110608094252.gc3...@msgid.df7cb.de>
> I've set up a WIP version of a new DEHS instance that uses the watch
> files from the lintian lab to submit uscan results to mole. The data
> is then extracted as a .db file and presented in DDPO.
>
> Todo:
> *
Hello Neil,
Neil Williams wrote:
> However, the PTS gets the wrong data from
> http://dehs.alioth.debian.org/maintainer.php?name=gpe-soundserver
> and wrongly indicates that 0.4-1 is new.
>
> I know the mangling is a pain and upstream will probably sort it out at
> the next release but that isn't
Hi,
* Bluefuture <[EMAIL PROTECTED]> [2007-07-29 14:04]:
> After some code revision i think that dehs data now are regular update
> again.
> Anybody could list all update dehs/developer.php/watch column outdate
> bugs agains dehs and qa so we try to close it?
The DEHS user tagged bugs should be a
> Yes, sort of:
>
> function is_updated ($up_vers, $debian_vers) {
> if ($up_vers=='') return 0;
> if (!(($debian_vers =~ /\d+\.?/) && ($up_vers =~ /\d+\.?/))) return 0;
> ...
> }
>
> I did some tests and I think that the results of the regex match above
> are flexible enough to not break a
Bluefuture wrote:
Hi Gustavo,
(...)
Btw, I would like to suggest point out (or ommit) the packages where
version naming scheme don't match, like in a52dec. It's the easier
scenario: If the upstream part of the version (upstream or debian)
contains "[a-Z]" and the other doesn't, the version na
Hi Gustavo,
>
>
> What about the false positives like gdm and gnome-screensaver?
>
That page list debian package not in sync with upstream. So if a debian
package has not a well done watch file probably we could have a debian
version more new that the upstream one. I suggest to send a bug with a
Bluefuture wrote:
Hi,
after etch release this is a list of debian packages not in sync with
upstream version[1] with upstream news or changelog data where available
(click on the upstream version number). Packages are sorted with popcon
data.
Great stuff, thanks!
I have also set the dehs "li
> It is still nice to be able to see the live code with all temporary
> files etc. (An additional plus is that I can just 'cat .svn/entries'
> to see where the svn root is.) At the moment I can't do that.
>
> [0] [EMAIL PROTECTED]:/var/lib/gforge/chroot/home/users/evaso-guest $cd
> projects/
> -b
Il giorno mar, 14/03/2006 alle 16.17 +0100, Christoph Berg ha scritto:
>
> Could you chmod +rx the dehs code on haydn please? (Why is this
> running in your $HOME at all instead of the web root?)
>
The dehs code is already available to all on svn.debian.org.
The live program is running on my ho
Re: Bluefuture 2006-03-15 <[EMAIL PROTECTED]>
> > Could you chmod +rx the dehs code on haydn please? (Why is this
> > running in your $HOME at all instead of the web root?)
>
> The dehs code is already available to all on svn.debian.org.
> The live program is running on my home and the web pages
Re: Bluefuture 2006-03-14 <[EMAIL PROTECTED]>
> For any problem about dehs please contact me.
Could you chmod +rx the dehs code on haydn please? (Why is this
running in your $HOME at all instead of the web root?)
Christoph
--
[EMAIL PROTECTED] | http://www.df7cb.de/
signature.asc
Description:
> indeed, qa.d.o dehs data files are dated Jun 5 and the same applies for
> data on alioth, dated Jun 6
>
> this can be related to non-us becoming obsolete, the logs shows that
> dehs failed to fetch Release from non-us/unstable
Yes, non-us is the problem. I have tried to fix it quick as i can
Jamie Wilkinson wrote:
> The DEHS watch page looks like it hasn't been updated for several weeks,
> which makes the Upstream watch columns in the DDPO page pretty useless.
indeed, qa.d.o dehs data files are dated Jun 5 and the same applies for
data on alioth, dated Jun 6
this can be related to
On Wed, Mar 23, 2005 at 08:02:20PM +0100, Luk Claes wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi Justin
>
> Justin Pryzby wrote:
> [...]
> | 1. Assert that every .orig.tar.gz which does not extract to
> | foo_ver.orig/ is identical to the one provided by upstream.
> [...]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Justin
Justin Pryzby wrote:
[...]
| 1. Assert that every .orig.tar.gz which does not extract to
| foo_ver.orig/ is identical to the one provided by upstream.
[...]
| 1 is a safety measure. It prevents people from using a nonoriginal
| .orig, fo
Hmm. I quite like the dehs idea. Possibly there are no well-defined
goals so far, but this is an area Debian as a whole could improve in.
Here are some thoughts.
1. Assert that every .orig.tar.gz which does not extract to
foo_ver.orig/ is identical to the one provided by upstream.
2. Keep
On Sun, Mar 06, 2005 at 06:44:37PM +0100, Jeroen van Wolffelaar wrote:
> On Sun, Mar 06, 2005 at 10:49:47AM +0100, Martin Quinson wrote:
> >
> > On Mon, Feb 28, 2005 at 03:32:30AM +0100, Bluefuture wrote:
> >
> > > I'm not a debian developer, so i could not post on dda mailing list. I
> > > had o
Christoph Berg wrote:
> Re: Thiemo Seufer in <[EMAIL PROTECTED]>
> > > Do *not* file 6229 bugs about the same subject. Never.
> >
> > Why not? As wishlist bugs with patch this seems sensible to me.
>
> I assume that you will hand-check the patches in those 6229 bug
> reports that the watch files
Re: Thiemo Seufer in <[EMAIL PROTECTED]>
> > Do *not* file 6229 bugs about the same subject. Never.
>
> Why not? As wishlist bugs with patch this seems sensible to me.
I assume that you will hand-check the patches in those 6229 bug
reports that the watch files actually do the right thing before y
Jeroen van Wolffelaar wrote:
[snip]
> > > I had try to randomly submit wishlist bugs for 6 packages to bts with
> > > the tag "patch" pointing to the dehs site or attaching the watch file to
> > > the bug.
> > > Almost all of this bug was closed and the watch file was check (in some
> > > cases fix
On Sun, Mar 06, 2005 at 10:49:47AM +0100, Martin Quinson wrote:
> [Why to cc on policy? Cut]
>
> On Mon, Feb 28, 2005 at 03:32:30AM +0100, Bluefuture wrote:
>
> > >If people don't care as much about this as you think they should,
> > >perhaps it would be a good idea to try explaining why they *sh
[Why to cc on policy? Cut]
On Mon, Feb 28, 2005 at 03:32:30AM +0100, Bluefuture wrote:
> >If people don't care as much about this as you think they should,
> >perhaps it would be a good idea to try explaining why they *should*
> >care, instead of just lamenting their lack of a telepathic
> >under
Scripsit Bluefuture <[EMAIL PROTECTED]>
>>If people don't care as much about this as you think they should,
>>perhaps it would be a good idea to try explaining why they *should*
>>care, instead of just lamenting their lack of a telepathic
>>understanding of your intentions?
> This is not true.
Y
>The community might start considering it less useless if an
>explanation of what it is supposed to be good for was actually
>available. In particular, why should a maintainer care about watch
>files if he uses something else than uscan to keep track of upstream
>happenings?
>From time to time, th
Scripsit Bluefuture <[EMAIL PROTECTED]>
> There is no reason to put more work and effort on a community tool that
> community itself consider useless.
The community might start considering it less useless if an
explanation of what it is supposed to be good for was actually
available. In particula
Il mer, 2004-07-21 alle 11:13, Erik Schanze ha scritto:
> >
> @Stefano: Would you include the possibility of following links to download
> area
> into your script?
I don't think it is a good solution. The typology of "download area" url
is too various. But, also if we can standardize the typolog
On Tue, Jul 13, 2004 at 11:56:46PM +0200, Bluefuture wrote:
> In which way do u want to implement this? I prefer that this feature
> will be included in dehs instead of an off-site solution.
every now and then (rarely) go through all the packages that have
working watch files, download the upstrea
Il mar, 2004-07-13 alle 20:08, Robert Lemmen ha scritto:
> hi stefano,
>
> i really like dehs, i think it will become a very valuable tool in the
> future. i have some comments though:
>
> - is the code available anywhere?
Dehs source code is available here:
Browsable: http://svn.debian.org/vie
> Mind posting useful information and not a collection of letters and
> numbers stolen from lynx output of a table it can't render? Currently,
> there is less than little value in the mail.
[ a small amount of information was discarded in the reformatting]
(popular packages with newer upstream v
Mind posting useful information and not a collection of letters and
numbers stolen from lynx output of a table it can't render? Currently,
there is less than little value in the mail.
Regards,
Joey
--
If nothing changes, everything will remain the same. -- Barne's Law
Please always C
On Fri, Jun 11, 2004 at 08:58:42PM +0200, Bluefuture wrote:
> I had added to DEHS http://dehs.alioth.debian.org a new functionality
> about "by maintainer" dehs summary.
>
> Try it and make suggestion.
>
> Next step: dehs ovveride??
>
> Colud be need some access restriction features for enter an
On Fri, Jun 11, 2004 at 08:43:57PM +0200, Frank K?ster wrote:
> I don't understand why you need an overrides file. Why not just submit
> wishlist bugs, with a link to a QA page that explains why a watch file
> is a Good Thing[TM] even if it is of no use for the individual
> maintainer?
Because ma
Bluefuture <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I had added to DEHS http://dehs.alioth.debian.org a new functionality
> about "by maintainer" dehs summary.
>
> Try it and make suggestion.
>
> Next step: dehs ovveride??
>
> Colud be need some access restriction features for enter an overrided
> wat
Hi,
I had added to DEHS http://dehs.alioth.debian.org a new functionality
about "by maintainer" dehs summary.
Try it and make suggestion.
Next step: dehs ovveride??
Colud be need some access restriction features for enter an overrided
watch file (and test)? How Maintainer will integrate it in t
On Wed, 9 Jun 2004, Michael Bramer wrote:
> Because of this, I like to add/fix watch files to _all_ packages.
In general I like the idea of working watch files for all packages.
My personal experience showed in the past the following:
1. Upstream maintainers sometimes have a strange idea about
On Wed, Jun 09, 2004 at 05:02:49AM +0200, Bluefuture wrote:
> Il mar, 2004-06-08 alle 03:27, Michael Bramer ha scritto:
> > >
> > > http://lists.debian.org/debian-devel/2004/05/msg01624.html
> >
> > very good.
> >
> > I like to add watch files to any debian package. Can we add some
> > 'watchfil
>i have tried soemthing like that in the past too. you could add a test
>for a prdownloads.sf.net page with the projects' name, that will work
>for ~15% of all packages without watch files.
Now every "sf.net" "sourceforge.net" is composed as above. Dehs is now
restarted,
for generating outputs (n
On Wed, May 26, 2004 at 10:13:36PM +0200, Bluefuture wrote:
> i had tried to implement a Watch filler function for dehs that run daily
> on alioth[1].
> There are 6510 package without watch file[1].
> I had run "watch filler" on this packages for try to make an
> automatically generated Watch from
On Tue, 4 May 2004, Michael Stone wrote:
> On Wed, May 05, 2004 at 01:25:10AM +0200, Bluefuture wrote:
> >In all this cases, is it so hard for Mantainers to fill watch file in
> >their own packages for Qa pourposes?
>
> We've had this argument before and the problem remains that many
> devlopers d
> It's not that it's hard,
> it's that they're not interested.
Well, they doesn't want to think to a little regular expression for help Qa
Purposes?
Or the problem is that all the Debian developer think that Dehs is bootless for
helping
Debian-qa?
>Another reason why some packages don't have a
On Wed, May 05, 2004 at 01:25:10AM +0200, Bluefuture wrote:
In all this cases, is it so hard for Mantainers to fill watch file in
their own packages for Qa pourposes?
We've had this argument before and the problem remains that many
devlopers don't see a point to putting one in. It's not that it
>Did you consider the possiblity that many package maintainers don't
>find
>the Watch file useful? Such things as:
>
>Upstream is package maintainer.
>
>Upstream development is dead.
>
>Package maintainer on upstream mailing list.
Ok, well. So the Watch file rationale could be switche
(dropped -devel, this is not relevant for -devel)
On Tue, May 04, 2004 at 03:39:00AM +0200, Bluefuture wrote:
> Il sab, 2004-05-01 alle 16:18, Jeroen van Wolffelaar ha scritto:
>
> >
> > Bluefuture: The interface that is needed for DDPO and the PTS is like
> > this:
> >
> > : [ | "N/A" | "Erro
Il sab, 2004-05-01 alle 16:18, Jeroen van Wolffelaar ha scritto:
>
> Bluefuture: The interface that is needed for DDPO and the PTS is like
> this:
>
> : [ | "N/A" | "Error" ]
>
> For resp. upstream version, no watch file, and error processing
> watchfile.
>
> --Jeroen
It is very simple for m
On Sat, May 01, 2004 at 05:44:25PM +0200, Bluefuture wrote:
> The original Dehs announcement it was only some days old:
> Anybody had saw this messages? :)
> http://lists.debian.org/debian-qa/2004/debian-qa-200404/msg00172.html
> http://lists.debian.org/debian-devel/2004/debian-devel-200404/msg0192
The original Dehs announcement it was only some days old:
Anybody had saw this messages? :)
http://lists.debian.org/debian-qa/2004/debian-qa-200404/msg00172.html
http://lists.debian.org/debian-devel/2004/debian-devel-200404/msg01921.html
Il sab, 2004-05-01 alle 11:56, Mark Howard ha scritto:
> Hi,
54 matches
Mail list logo
