On Tue, Apr 15 2014, David Suárez wrote:
> Manoj, Im planning to do a GCC and a normal archive rebuild soon.
> Maybe I could mix your "make 4 rebuild" at the same time
> (normal+gcc+make4) or do it in another step, have to look at it...
I am hoping that it does not require a build by
rchive rebuild with the version of
> > >> make in
> > >> experimental (4.0) ?
> > >
> > > Sounds like a good idea to me. Some info about the archive rebuilds is
> > > here:
> > >
> > > https://lists.debian.org/debian-qa/2013/05/
r builds, it is perhaps
> >> wise to know how much work needs be done before we can upgrade make. How
> >> does one go about asking for an archive rebuild with the version of make in
> >> experimental (4.0) ?
> >
> > Sounds like a good idea to me. Some info abou
make. How
>> does one go about asking for an archive rebuild with the version of make in
>> experimental (4.0) ?
>
> Sounds like a good idea to me. Some info about the archive rebuilds is
> here:
> https://lists.debian.org/debian-qa/2013/05/msg00034.html
> https:/
imental (4.0) ?
Sounds like a good idea to me. Some info about the archive rebuilds is here:
https://lists.debian.org/debian-qa/2013/05/msg00034.html
https://wiki.debian.org/qa.debian.org/ArchiveTesting
--
bye,
pabs
http://wiki.debian.org/PaulWise
--
To UNSUBSCRIBE, email to de
Hi,
[Please do keep me in the CC:, I am not subscribed to this
list]
Some time ago, I had uploaded the version 3.82 of make
into
experimental, since there were known backward incompatibilities
in an
under-specified part of the rules. From the NEWS file:
Backward-
Le Fri, Jan 24, 2014 at 01:03:28AM +0100, Andreas Beckmann a écrit :
>
> After building a source package successfully, a binary debdiff should be
> done with the binary packages currently in the archive.
> (What else could be done with the packages? Maybe a lintian run.)
>
> I see three groups of
On 24/01/14 at 01:03 +0100, Andreas Beckmann wrote:
> Hi,
>
> the problem discovered in http://bugs.debian.org/736426 can probably
> checked for automatically. But I don't know enough about the
> full-archive rebuilds (nor do I have time to dig into them ... as least
&g
* Andreas Beckmann , 2014-01-24, 01:03:
the problem discovered in http://bugs.debian.org/736426 can probably
checked for automatically. But I don't know enough about the
full-archive rebuilds (nor do I have time to dig into them ... as least
as long as there are failures discovered
Hi,
the problem discovered in http://bugs.debian.org/736426 can probably
checked for automatically. But I don't know enough about the
full-archive rebuilds (nor do I have time to dig into them ... as least
as long as there are failures discovered with piuparts) to see how this
can be accompl
Hi,
On 02/06/13 at 15:30 +0200, David Suárez wrote:
> Hi,
>
> On Viernes, 17 de mayo de 2013 08:49:14 Lucas Nussbaum escribió:
> > Now, real work. We need to:
> > - do another full archive rebuild, and process all the results
> > - do a gcc4.8 rebuild. the contact for that is d...@debian.org. He
Hi,
On Viernes, 17 de mayo de 2013 08:49:14 Lucas Nussbaum escribió:
> Now, real work. We need to:
> - do another full archive rebuild, and process all the results
> - do a gcc4.8 rebuild. the contact for that is d...@debian.org. He told
> that he would like to be notified before we start the rebu
On 21/05/13 at 14:44 +0200, Lucas Nussbaum wrote:
> Hi,
>
> Someone terminated the master node (by mistake). I've restarted it, and
> re-added the SSH keys.
>
> The new master node address is ec2-107-22-58-191.compute-1.amazonaws.com
>
> If you had logs on it, they are lost, unfortunately.
Gah,
Hi,
Someone terminated the master node (by mistake). I've restarted it, and
re-added the SSH keys.
The new master node address is ec2-107-22-58-191.compute-1.amazonaws.com
If you had logs on it, they are lost, unfortunately.
Lucas
signature.asc
Description: Digital signature
On Viernes, 17 de mayo de 2013 09:04:19 Lucas Nussbaum escribió:
> On 17/05/13 at 08:49 +0200, Lucas Nussbaum wrote:
> > Now, real work. We need to:
> > - do another full archive rebuild, and process all the results
> > - do a gcc4.8 rebuild. the contact for that is d...@debian.org. He told
> > tha
On Martes, 14 de mayo de 2013 18:05:28 Lucas Nussbaum escribió:
>
> When you are done filing bugs, you can replace all those NNN by actual bug
> numbers. For that, you need to use e.g.: cqa-importbugnumbers
> debian-qa@lists.debian.org qa-ftbfs-20130509 < $TODOFILE > tmp the two
> parameters are b
On Viernes, 17 de mayo de 2013 08:49:14 Lucas Nussbaum escribió:
> Hi,
>
> Please pick up one of the tasks, and coordinate here!
>
> Lucas
Hi,
I send a patch to add support for specifying output directory. Now, we can
work at same time.
The script on ec2 masternode is modified while the patc
Hi,
Thanks Nathan. If i can help you later Ill ask you.
David
El 17/05/2013 13:55, "Nathan Handler" escribió:
> On Fri, May 17, 2013 at 5:21 AM, david suarez
> wrote:
> >>Forgot something:
> >>during my last archive rebuild, two packages's build hang, which is
> >>rather painful to handle. Tho
On Fri, May 17, 2013 at 5:21 AM, david suarez wrote:
>>Forgot something:
>>during my last archive rebuild, two packages's build hang, which is
>>rather painful to handle. Those were ns3 and gcc-snapshot.
>>Someone should try to reproduce that, investigate that, and file a
>>proper bug report.
>
>
Hi,
>Forgot something:
>during my last archive rebuild, two packages's build hang, which is
>rather painful to handle. Those were ns3 and gcc-snapshot.
>Someone should try to reproduce that, investigate that, and file a
>proper bug report.
I'm still doing step3, so if Nathan wants to take the wor
On 17/05/13 at 08:49 +0200, Lucas Nussbaum wrote:
> Now, real work. We need to:
> - do another full archive rebuild, and process all the results
> - do a gcc4.8 rebuild. the contact for that is d...@debian.org. He told
> that he would like to be notified before we start the rebuild, so that
> he ca
Hi,
When you have done all three steps successfully, I will send you an
archive with the Debian QA EC2 account key. Using it, you can reserve
and terminate instances.
We use "spot instances" (instances at a lower price that can be
terminated by Amazon if the "market price" becomes higher than the
I used it :)
El 16/05/2013 20:16, "Lucas Nussbaum" escribió:
> On 12/05/13 at 11:01 +0200, Lucas Nussbaum wrote:
> > In order to make your life slightly easier (and to reduce a bit the
> risks in
> > case of mistakes :) ), I've already reserved 5 "medium" instances for
> you. So
> > you don't nee
On 12/05/13 at 11:01 +0200, Lucas Nussbaum wrote:
> In order to make your life slightly easier (and to reduce a bit the risks in
> case of mistakes :) ), I've already reserved 5 "medium" instances for you. So
> you don't need to do the resources reservation steps of README. The list of
> those node
On 15/05/13 at 15:33 -0500, Nathan Handler wrote:
> On Tue, May 14, 2013 at 11:05 AM, Lucas Nussbaum wrote:
> > You mission this time:
> > - pick up ~100 random packages from the list of packages that failed to
> > build on
> > 2013-05-09 and are still marked TODO. it's a good idea to ignore th
Hi Nathan,
> I have successfully filed my 10 bugs (relevant files at [1]). I will
> commit the bug numbers to the list for 20130509 as soon as my request
> to join collab-qa on alioth is approved.
>
> [1] http://people.debian.org/~nhandler/.ec2/
Please remove all strings with error [2] from your
On Tue, May 14, 2013 at 11:05 AM, Lucas Nussbaum wrote:
> You mission this time:
> - pick up ~100 random packages from the list of packages that failed to build
> on
> 2013-05-09 and are still marked TODO. it's a good idea to ignore the
> remaining
> GCC_ERROR bugs: those don't need to be fi
On 15/05/13 at 00:52 +0800, Thomas Goirand wrote:
> On 05/12/2013 05:01 PM, Lucas Nussbaum wrote:
> > Hi!
> >
> > First, thanks all for volunteering!
> >
> > >From now on, let's use the debian-qa@ list for coordination (so, please
> > subscribe, if not done already)
> >
> > I'll try to walk you thr
On 14/05/13 at 18:05 +0200, Lucas Nussbaum wrote:
> You mission this time:
> - pick up ~100 random packages from the list of packages that failed to build
> on
> 2013-05-09 and are still marked TODO. it's a good idea to ignore the
> remaining
> GCC_ERROR bugs: those don't need to be filed.
>
On 05/12/2013 05:01 PM, Lucas Nussbaum wrote:
> Hi!
>
> First, thanks all for volunteering!
>
> >From now on, let's use the debian-qa@ list for coordination (so, please
> subscribe, if not done already)
>
> I'll try to walk you through the tools used to do rebuilds and bug
> filing. There are three
s the most time-consuming part.
At the end of Step 2, you should have:
- all the logs for failed builds available somewhere on the web
- all the logs for failed builds available locally
- the list of failures, merged with the previous list, in e.g.
collab-qa/archive-rebuilds/2013-05-09-unst
On 13/05/13 at 22:24 +0200, David Suárez wrote:
> Hi,
>
> You can find the Failure logs at https://gist.github.com/deiv/5570248
>
> Im going for the bonus task.
Excellent!
> By the way, the same logic that do 'fetch-and-process-results-aws' can not
> be
> replicated with the -r argument of c
Hi,
You can find the Failure logs at https://gist.github.com/deiv/5570248
Im going for the bonus task.
By the way, the same logic that do 'fetch-and-process-results-aws' can not be
replicated with the -r argument of cqa-scanlogs, something like 'cqa-scanlogs
-r Failed' ? (assuming we will onl
move logs of failures to a public place. Currently, under
http://people.debian.org/~lucas/logs/, but we need to change that.
- prepare a list of failures that will be used for Step 3, such as
http://anonscm.debian.org/viewvc/collab-qa/archive-rebuilds/2013-05-09-unstable-amd64/failed.2013-05-0
OK, tasks generated with the correct upper and lower parameters. Build log
and packages logs in ec2 master node.
2013/5/13 Lucas Nussbaum
> On 12/05/13 at 23:37 +0200, David Suarez wrote:
> > El 12/05/2013 23:24, "Nathan Handler" escribió:
> > >
> > > On Sun, May 12, 2013 at 4:01 AM, Lucas N
On 12/05/13 at 23:37 +0200, David Suarez wrote:
> El 12/05/2013 23:24, "Nathan Handler" escribió:
> >
> > On Sun, May 12, 2013 at 4:01 AM, Lucas Nussbaum wrote:
> > > In that mail, I will address Step 1. Once at least two of you have
> achieved it,
> > > I'll move to Step 2.
> >
> > I have also c
El 12/05/2013 23:24, "Nathan Handler" escribió:
>
> On Sun, May 12, 2013 at 4:01 AM, Lucas Nussbaum wrote:
> > In that mail, I will address Step 1. Once at least two of you have
achieved it,
> > I'll move to Step 2.
>
> I have also completed all of the tasks in Step 1. My tasks and log
> files ar
On Sun, May 12, 2013 at 4:01 AM, Lucas Nussbaum wrote:
> In that mail, I will address Step 1. Once at least two of you have achieved
> it,
> I'll move to Step 2.
I have also completed all of the tasks in Step 1. My tasks and log
files are available at [1] for anyone interested.
Nathan
[1] http
On Domingo, 12 de mayo de 2013 13:58:45 usted escribió:
> On 12/05/13 at 13:43 +0200, david suarez wrote:
> > Hi,
> >
> > Here's my ssh key:
> > https://dl.dropboxusercontent.com/u/50951262/id_rsa.pub.asc
> >
> > Let me know when you added it.
>
> Added.
>
> Lucas
Hi,
Ok, step 1 done.
I clon
On Sun, May 12, 2013 at 4:01 AM, Lucas Nussbaum wrote:
> Hi!
Hello Lucas,
> First, thanks all for volunteering!
You are very welcome! I look forward to helping out with this task.
> From now on, let's use the debian-qa@ list for coordination (so, please
> subscribe, if not done already)
I am
On 2013-05-12 14:20, Thomas Goirand wrote:
> On 05/12/2013 05:54 PM, Niels Thykier wrote:
>> You probably want to sign the key.
>>
>> ~Niels
> Can an ssh key be pgp signed? I didn't know.
> How do I do that?
>
> Thomas
>
>
The key can be GPG signed like any other text file. If you clear sign
i
On 05/12/2013 05:54 PM, Niels Thykier wrote:
> You probably want to sign the key.
>
> ~Niels
Can an ssh key be pgp signed? I didn't know.
How do I do that?
Thomas
--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.de
Hi,
Here's my ssh key:
https://dl.dropboxusercontent.com/u/50951262/id_rsa.pub.asc
Let me know when you added it.
David
2013/5/12 Lucas Nussbaum
> Hi!
>
> First, thanks all for volunteering!
>
> From now on, let's use the debian-qa@ list for coordination (so, please
> subscribe, if not done
On 12/05/13 at 17:30 +0800, Paul Wise wrote:
> On Sun, May 12, 2013 at 5:01 PM, Lucas Nussbaum wrote:
>
> > our "master" node on EC2. That node must never be shut down.
>
> Why is this? Is it because the node isn't using a persistent IP
> address (I forget the correct terminology)?
Just because
On 12/05/13 at 17:47 +0800, Thomas Goirand wrote:
> On 05/12/2013 05:01 PM, Lucas Nussbaum wrote:
> > First, I need your SSH key, so that you can connect to AWS.
>
> Hi Lucas,
>
> Thanks for all these details. I haven't read it all yet, but I will.
>
> You may find it here:
> http://www.gplhost.
On 2013-05-12 11:47, Thomas Goirand wrote:
> On 05/12/2013 05:01 PM, Lucas Nussbaum wrote:
>> First, I need your SSH key, so that you can connect to AWS.
>
> Hi Lucas,
>
> Thanks for all these details. I haven't read it all yet, but I will.
>
> You may find it here:
> http://www.gplhost.com/ssh-
On 05/12/2013 05:01 PM, Lucas Nussbaum wrote:
> First, I need your SSH key, so that you can connect to AWS.
Hi Lucas,
Thanks for all these details. I haven't read it all yet, but I will.
You may find it here:
http://www.gplhost.com/ssh-pubkeys/zigo
Let me know when I can connect.
Thomas
--
On Sun, May 12, 2013 at 5:01 PM, Lucas Nussbaum wrote:
> our "master" node on EC2. That node must never be shut down.
Why is this? Is it because the node isn't using a persistent IP
address (I forget the correct terminology)?
--
bye,
pabs
http://wiki.debian.org/PaulWise
--
To UNSUBSCRIBE, e
Hi!
First, thanks all for volunteering!
>From now on, let's use the debian-qa@ list for coordination (so, please
subscribe, if not done already)
I'll try to walk you through the tools used to do rebuilds and bug
filing. There are three big steps.
Step 1: Use AWS to run all the tests and generat
lity of the distribution.
> Here is the "job" description: - maintain scripts to organize archive
> rebuilds, parse logs and file bugs Required skills: basic Ruby knowledge
> (or willingness to learn) scripts are in
I've been using ruby for about 3 years, especially to cre
n: - maintain scripts to organize archive
> rebuilds, parse logs and file bugs Required skills: basic Ruby knowledge
> (or willingness to learn) scripts are in
> http://anonscm.debian.org/gitweb/?p=collab-qa/cloud-scripts.git and
> http://anonscm.debian.org/viewvc/collab-qa/co
On 05/09/2013 05:32 PM, Lucas Nussbaum wrote:
> Hi,
>
> I'm unlikely to be able to do much archive rebuild work in the coming year,
> so
> I would welcome help on that front.
>
> Here is the "job" description:
> [...]
Hi Lucas,
I would like to help!
I'm not sure I will have enough time, but I t
me. Due to real life, I am only able
to contribute to Debian every couple of weeks. However, when I do get
time to contribute, it is usually in a nice large chunk of time. This
would work out well for archive rebuilds.
> The task covers "normal" archive rebuilds (rebuilding all p
On 09/05/13 at 13:52 +0200, Andreas Beckmann wrote:
> Hi Lucas,
>
> On 2013-05-09 11:32, Lucas Nussbaum wrote:
> > I'm unlikely to be able to do much archive rebuild work in the coming year,
> > so
> > I would welcome help on that front.
>
> I'm not volunteering for the job :-)
>
> But your ma
Hi Lucas,
On 2013-05-09 11:32, Lucas Nussbaum wrote:
> I'm unlikely to be able to do much archive rebuild work in the coming year,
> so
> I would welcome help on that front.
I'm not volunteering for the job :-)
But your mail rises two questions:
* do we have a recent wheezy rebuild - ideally
Hi,
I'm unlikely to be able to do much archive rebuild work in the coming year, so
I would welcome help on that front.
Here is the "job" description:
- maintain scripts to organize archive rebuilds, parse logs and file bugs
Required skills: basic Ruby knowledge (or willi
* Charles Plessy , 2012-01-16, 07:58:
I think that the benefits would be greater if the archive rebuilds
were also filtering logs, since they use a sbuild version that has
that capacity.
FWIW, I don't think this is true. I believe buildds use a (modified?)
sbuild 0.61.0, whereas th
Le Sun, Jan 15, 2012 at 04:10:52PM +0100, Jakub Wilk a écrit :
> * Charles Plessy , 2012-01-15, 09:59:
> >I think that the benefits would be greater if the archive rebuilds
> >were also filtering logs, since they use a sbuild version that has
> >that capacity.
>
> FWIW,
* Charles Plessy , 2012-01-15, 09:59:
I think that the benefits would be greater if the archive rebuilds were
also filtering logs, since they use a sbuild version that has that
capacity.
FWIW, I don't think this is true. I believe buildds use a (modified?)
sbuild 0.61.0, whereas th
Le Sat, Jan 14, 2012 at 09:32:09PM -0500, Joseph R. Justice a écrit :
>
> Without knowing the contents of these logs, or of what's being
> filtered from them (I have looked at the bug log mentioned earlier in
> this thread), I make the following general observations:
Hi Joseph,
Here is an extrac
ive, that I either send to the packaging team's list
> or commit in the package's git repository, are filtered logs. I have not
> reveived any complain that filtration was harmful, and I feel that this
> feature
> has been benefical to me; it assisted me to spot key differences betwe
reveived any complain that filtration was harmful, and I feel that this feature
has been benefical to me; it assisted me to spot key differences between
builds. I think that the benefits would be greater if the archive rebuilds
were also filtering logs, since they use a sbuild version that has that
On Sat, Jan 14, 2012 at 11:54:46PM +0900, Charles Plessy wrote:
> The filtering makes my work easier, because it reduces the size of the diffs
> without extra action on my side.
And why can't you filter the logs on your own?
Bastian
--
Murder is contrary to the laws of man and God.
Le Sat, Jan 14, 2012 at 02:32:38PM +0100, Jakub Wilk a écrit :
> See http://bugs.debian.org/620589#15 for my arguments.
Hello Jakub,
Roger gave answers that I find convincing in http://bugs.debian.org/620589#20.
The filtering makes my work easier, because it reduces the size of the diffs
withou
* Lucas Nussbaum , 2012-01-14, 10:52:
in SVN revision 1966, you disabled log filtering in sbuild for the
archive rebuilds. However, this filtering helps to reduce the diff
with the maintainer's build log (I commit or post all the build logs
for the packages I upload), and therefore facili
On 14/01/12 at 17:49 +0900, Charles Plessy wrote:
> Le Sat, Jan 14, 2012 at 09:34:31AM +0100, Lucas Nussbaum a écrit :
> >
> > On 14/01/12 at 16:09 +0900, Charles Plessy wrote:
> > >
> > > in SVN revision 1966, you disabled log filtering in sbuild for the archi
Le Sat, Jan 14, 2012 at 09:34:31AM +0100, Lucas Nussbaum a écrit :
>
> On 14/01/12 at 16:09 +0900, Charles Plessy wrote:
> >
> > in SVN revision 1966, you disabled log filtering in sbuild for the archive
> > rebuilds. However, this filtering helps to reduce the diff w
Hi,
On 14/01/12 at 16:09 +0900, Charles Plessy wrote:
> Hello Lucas,
>
> in SVN revision 1966, you disabled log filtering in sbuild for the archive
> rebuilds. However, this filtering helps to reduce the diff with the
> maintainer's build log (I commit or post all th
Hello Lucas,
in SVN revision 1966, you disabled log filtering in sbuild for the archive
rebuilds. However, this filtering helps to reduce the diff with the
maintainer's build log (I commit or post all the build logs for the packages I
upload), and therefore facilitates the investigations.
El dc 24 de 08 de 2011 a les 10:54 +0200, en/na Lucas Nussbaum va
escriure:
> [ Mail Cc'ed to people interested in archive testing. Please subscribe
> to debian-qa@lists.debian.org if you are not subscribed yet, so we can
> use that list for coordination ]
>
> Hi,
>
> I've put the IRC log of yest
[ Mail Cc'ed to people interested in archive testing. Please subscribe
to debian-qa@lists.debian.org if you are not subscribed yet, so we can
use that list for coordination ]
Hi,
I've put the IRC log of yesterday's session on
http://wiki.debian.org/qa.debian.org/ArchiveTesting/IRCTutorial
Next s
On 23/08/11 at 08:40 +0200, Stefano Zacchiroli wrote:
> On Mon, Aug 22, 2011 at 11:18:50PM +0200, Lucas Nussbaum wrote:
> > Tomorrow at 18:30 UTC on #debian-qa, I will organize a follow-up to my
> > Debconf BOF on archive testing, where interested people will be able to
> > set up their environment
Hi,
Tomorrow at 18:30 UTC on #debian-qa, I will organize a follow-up to my
Debconf BOF on archive testing, where interested people will be able to
set up their environment to do log analysis + bug filing.
The goal is to get every participant to file a few dozen FTBFS bugs, and
then discuss how to
73 matches
Mail list logo
