On Fri, Apr 09, 2021 at 01:09:43PM +0200, Lucas Nussbaum wrote:
> On 09/04/21 at 12:33 +0200, Adam Borowski wrote:
> > On Fri, Apr 09, 2021 at 10:42:22AM +0200, Raphael Hertzog wrote:
> > > I don't think there's a valid technical reason to not use a newer format.
> > > Some dislike the choices made
xture of quilt patches and
direct changes.
> Also, while I was aware of this workflow for the X team, it seems that
> there's at least one outlier:
> https://salsa.debian.org/xorg-team/app/xterm/-/tree/debian-unstable/debian/patches
More to the point, xterm actually uses format 3.0 now.
On 09/04/21 at 19:49 +0200, Sven Joachim wrote:
> The X Strike Force is still sticking to format 1.0, with one of the main
> reasons being that it makes it easier to cherry-pick one or several
> upstream commits. In the 3.0 format you have to create a separate patch
> and later remove it when merg
On Thu, Apr 08, 2021 at 06:53:12PM +0200, Mattia Rizzolo wrote:
> > right, so the severity of these bugs should be wishlist or maybe normal,
> > but I don't think important would be justified, and serious seriously not.
> Yes, totally. I don't think anybody ever talked about the severity of
> any
On 2021-04-08 18:02 +0200, Mattia Rizzolo wrote:
> On Thu, Apr 08, 2021 at 03:53:06PM +, Holger Levsen wrote:
>> On Thu, Apr 08, 2021 at 02:58:14PM +0200, Lucas Nussbaum wrote:
>> > 166 1.0, quilt
>>
>> I don't see what's wrong with these.
>
> Nothing *wrong* as the hard meaning of that
ons)
> > which makes it behave like source format 1.0 and auto-generates/updates a
> > single patch in the series based on the changes you made compared to
> > upstream.
> >
> > I don't think there's a valid technical reason to not use a newer format
s/updates a
> single patch in the series based on the changes you made compared to
> upstream.
>
> I don't think there's a valid technical reason to not use a newer format.
> Some dislike the choices made and the fact that many new features are
> coupled to the new format
On Fri, 09 Apr 2021, Raphael Hertzog wrote:
> "debian-single-patch" option (that you can put in debian/source/options)
"single-debian-patch", sorry
https://manpages.debian.org/buster/dpkg-dev/dpkg-source.1.en.html#Format:_3.0_(quilt)
Cheers,
--
⢀⣴⠾⠻⢶⣦⠀ Raphaël Hertzog
⣾⠁⢠⠒⠀⣿⡁
⢿⡄⠘⠷⠚⠋
Hello,
On Thu, 08 Apr 2021, Bastian Blank wrote:
> How do you export changes? And no, creating separate patches breaks as
> soon as the history is not linear, like after merging a new upstream
> release. Sure, you could rease, but that is not an automatic process.
As Mattia pointed
Hi Lucas
On Thu, Apr 08, 2021 at 04:01:38PM +0200, Lucas Nussbaum wrote:
> Is that a real issue in practice? If you can export the changes made to
> upstream sources as a single big diff, surely you can also export them
> as separate patches in 3.0 (quilt)?
How do you export changes
On Thu, Apr 08, 2021 at 04:15:45PM +, Holger Levsen wrote:
> > IMHO, they aren't "wrong" or "inherently bad", but I believe keeping
> > them that way is more of technical debt than anything else.
>
> right, so the severity of these bugs should be wishlist or maybe normal,
> but I don't think i
On Thu, Apr 08, 2021 at 06:02:35PM +0200, Mattia Rizzolo wrote:
> Nothing *wrong* as the hard meaning of that word.
> But:
> * They carry the usual set of downsides of 1.0 vs 3.0, like:
>- no support for .tar.(bz2|xz|…)
>- no support for multi tarballs
those don't seem to be relevant for
On Thu, Apr 08, 2021 at 03:53:06PM +, Holger Levsen wrote:
> On Thu, Apr 08, 2021 at 02:58:14PM +0200, Lucas Nussbaum wrote:
> > 166 1.0, quilt
>
> I don't see what's wrong with these.
Nothing *wrong* as the hard meaning of that word.
But:
* They carry the usual set of downsides of 1.0
On Thu, Apr 08, 2021 at 02:58:14PM +0200, Lucas Nussbaum wrote:
> 166 1.0, quilt
I don't see what's wrong with these.
--
cheers,
Holger
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org
⢿⡄⠘⠷⠚⠋⠀ PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A
RSN.
> 166 1.0, quilt
And also think something about this, though I'd have to see some data
about them, but I'm interested in also moving this set forward.
> 374 1.0, no changes
I think it would be interesting to see data about "freshness" of these
sources, main
On Thu, Apr 08, 2021 at 04:01:38PM +0200, Lucas Nussbaum wrote:
> On 08/04/21 at 11:33 +0200, Bastian Blank wrote:
> > On Wed, Apr 07, 2021 at 02:03:47PM +0200, Lucas Nussbaum wrote:
> > > - source format 1.0 with direct changes in .diff.gz (no patch system)
> >
> >
Hi Bastian,
On 08/04/21 at 11:33 +0200, Bastian Blank wrote:
> Hi Lucas
>
> On Wed, Apr 07, 2021 at 02:03:47PM +0200, Lucas Nussbaum wrote:
> > - source format 1.0 with direct changes in .diff.gz (no patch system)
>
> For this I disagree. At least until we have something
On 08/04/21 at 09:06 +0200, Mattia Rizzolo wrote:
> > - source format 1.0 with direct changes in .diff.gz (no patch system)
>
> Also dpatch. And also 1.0+quilt (ugh). !
So the breakdown for testing is:
27 1.0, dpatch
166 1.0, quilt
374 1.0, no changes
395 1.0, di
Your message dated Sun, 18 Feb 2018 15:22:32 +0100
with message-id <20180218142208.ga7...@brokenwa.re>
and subject line Re: Bug#844201: debsources: updater broken by recent
(Sources.gz removal, maybe sha1 removal) dak changes
has caused the Debian Bug report #844201,
regarding debsources: u
Package: qa.debian.org
Severity: serious
User: qa.debian@packages.debian.org
Usertags: debsources
Context is:
https://lists.debian.org/debian-devel-announce/2016/11/msg5.html
Here are some relevant entries from debsources.log:
Use of uninitialized value $sha1 in string eq at /usr/bi
On Fri, 2016-11-11 at 14:33 +0100, Cyril Brulebois wrote:
> Is the code really deployed?
Yes.
> I suspected maybe only new news pages would have this change (others
> might have been generated/cached already) but that doesn't seem to be
> the case, e.g.:
> https://tracker.debian.org/news/8143
Paul Wise (2016-11-11):
> On Fri, Nov 11, 2016 at 11:20 AM, Cyril Brulebois wrote:
>
> > I think the attached patch should do the job.
> >
> > But I suspect the following bits from the CSS might need updating (the
> > naked “a” part notably), since this anchor gets highlighted in blue,
> > which
Your message dated Fri, 11 Nov 2016 11:40:43 +0800
with message-id
and subject line Re: Bug#843944: tracker.debian.org: please add “changes”
anchor in news entries
has caused the Debian Bug report #843944,
regarding tracker.debian.org: please add “changes” anchor in news entries
to be marked as
Processing control commands:
> tag -1 patch
Bug #843944 [tracker.debian.org] tracker.debian.org: please add “changes”
anchor in news entries
Added tag(s) patch.
--
843944: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843944
Debian Bug Tracking System
Contact ow...@bugs.debian.org w
Control: tag -1 patch
Cyril Brulebois (2016-11-11):
> It would be nice if an anchor could be added on the “Changes:” line of
> the news entry. For example, when trying to point to recent grub2
> changes, this link would lead to a page full of descriptions (one for
> each binary
Package: tracker.debian.org
Severity: wishlist
Hi,
It would be nice if an anchor could be added on the “Changes:” line of
the news entry. For example, when trying to point to recent grub2
changes, this link would lead to a page full of descriptions (one for
each binary):
https
Hi,
On Wed, 09 Mar 2016, Osamu Aoki wrote:
> In retrospective for backport, string should have been kept if possible.
Not only for backports, but for backwards compatibility in general... I
don't think that the string changes are justified in the --dehs output.
> In old code, erro
On Wed, Mar 09, 2016 at 04:06:13PM +0100, Raphael Hertzog wrote:
>
> It's still quite wrong to have to compare textual strings. You should have
> some booleans or keywords exported in the --dehs output so that we can
> easily query the status without fearing further changes i
the very helpful explanation. So if I would like to restore
> > the old behavior I would need to discuss the strings in a bug report
> > against uscan, right? From my naive point of view the changes of the
> > strings is not a good idea (besides the side effect in UDD). Wha
I would need to discuss the strings in a bug report
> against uscan, right? From my naive point of view the changes of the
> strings is not a good idea (besides the side effect in UDD). What do
> others think?
In retrospective for backport, string should have been kept if possible.
no such
> > package at upstream site.
>
> It changed when a backport of devscripts >= 2.15.10 was installed on the
> QA systems.
Thanks for the very helpful explanation. So if I would like to restore
the old behaviour I would need to discuss the strings in a bug report
against
On Wed, Mar 09, 2016 at 09:28:10AM +0100, Andreas Tille wrote:
> Hi,
>
> when I query for the possible values of status I get:
>
> udd=> select status, count(*) from upstream group by status ;
> status| count
> --+---
>
Hi,
when I query for the possible values of status I get:
udd=> select status, count(*) from upstream group by status ;
status| count
--+---
| 4420
newer package available | 4409
up to date
Your message dated Fri, 11 Dec 2015 22:23:28 +0100
with message-id <20151211212328.ga28...@home.ouaza.com>
and subject line Re: Bug#788835: tracker.debian.org: Display of CVE links in
changes files includes invalid markup
has caused the Debian Bug report #788835,
regarding tracker.debi
Hi,
On Fri, 04 Dec 2015, James McCoy wrote:
> On Fri, Dec 04, 2015 at 11:20:25PM +0100, Raphael Hertzog wrote:
> > Next step is to transfer all mail subscriptions from packages.qa.debian.org
> > to tracker.debian.org and to close the mail part on
> > packages.qa.debian.org (mails to p...@qa.debian
On Fri, Dec 04, 2015 at 11:20:25PM +0100, Raphael Hertzog wrote:
> Next step is to transfer all mail subscriptions from packages.qa.debian.org
> to tracker.debian.org and to close the mail part on
> packages.qa.debian.org (mails to p...@qa.debian.org will be redirected to
> cont...@tracker.debian.o
Hello,
I did some work on the mail infrastructure of tracker.debian.org (cf
#754745 and #754913). It affects the way mails are forwarded to users
and the way we collect the news displayed in the web interface.
It's quite likely that this will put in light some small problems
like showing some new
Zack Weinberg writes:
> It's not terribly important, but what ordering are you using to define
> it as the "first patch"?
The order you sent the patches.
Andreas.
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for
On Mon, Nov 16, 2015 at 10:34 AM, Andreas Schwab wrote:
> Zack Weinberg writes:
>>
>> ... should only be possible as a consequence of the patch numbered 0002-.
>
> Which is the first patch.
It's not terribly important, but what ordering are you using to define
it as the "first patch"?
> ./src/b
Zack Weinberg writes:
> On Mon, Nov 16, 2015 at 9:37 AM, Andreas Schwab wrote:
>> Here are the first fallouts from the first patch:
>
> Which do you mean by "the first patch"? This ...
>
>> https://build.opensuse.org/package/live_build_log/home:Andreas_Schwab:glibc/gpm/rebuild/x86_64
>> prog/di
On Sun, Nov 15, 2015 at 9:26 PM, Paul Wise wrote:
>
> I'm not involved in the archive rebuilds stuff but the documentation
> for it is here:
>
> https://wiki.debian.org/qa.debian.org/ArchiveTesting
Thanks, but unfortunately it doesn't help me much, because I'm not a
DD, and because it doesn't exp
On Mon, Nov 16, 2015 at 9:37 AM, Andreas Schwab wrote:
> Here are the first fallouts from the first patch:
Which do you mean by "the first patch"? This ...
> https://build.opensuse.org/package/live_build_log/home:Andreas_Schwab:glibc/gpm/rebuild/x86_64
> prog/display-buttons.c:69:4: error: unkn
Here are the first fallouts from the first patch:
https://build.opensuse.org/package/live_build_log/home:Andreas_Schwab:glibc/gpm/rebuild/x86_64
prog/display-buttons.c:69:4: error: unknown type name 'fd_set'
https://build.opensuse.org/package/live_build_log/home:Andreas_Schwab:glibc/sysvinit/reb
Zack Weinberg writes:
> We have identified two potential changes which could fix this problem;
> unfortunately both of them have fairly high risk of breaking software
> which expects stdlib.h to include sys/types.h, sys/types.h to include
> sys/sysmacros.h, or both. (Neither
On Mon, Nov 16, 2015 at 5:19 AM, Zack Weinberg wrote:
> How can we arrange for this to happen?
I'm not involved in the archive rebuilds stuff but the documentation
for it is here:
https://wiki.debian.org/qa.debian.org/ArchiveTesting
--
bye,
pabs
https://wiki.debian.org/PaulWise
show_bug.cgi?id=19239 and the libc-alpha
discussion starting at
https://sourceware.org/ml/libc-alpha/2015-11/msg00253.html .
We have identified two potential changes which could fix this problem;
unfortunately both of them have fairly high risk of breaking software
which expects stdlib.h to include
On Mon, 15 Jun 2015, Stuart Prescott wrote:
> The rendering of CVE items in the changelog section of the changes files
> includes invalid HTML markup. As an example:
Duh, the maintainer included the link
"https://security-tracker.debian.org/tracker/CVE-2014-8483"; in the
changel
Package: tracker.debian.org
Severity: normal
Hi!
The rendering of CVE items in the changelog section of the changes files
includes invalid HTML markup. As an example:
https://tracker.debian.org/news/584136
which includes
konversation (1.5-2) unstable; urgency=medium
.
* Backport
Package: tracker.debian.org
Severity: wishlist
I would like to see the changes of package in backports in the news
section / RSS feed. So far the tracker seems to report changes only for
experimental, unstable, testing and stable.
Thanks
Ronny
--
To UNSUBSCRIBE, email to debian-qa-requ
Package: qa.debian.org
Severity: wishlist
User: qa.debian@packages.debian.org
Usertags: debsources
Debsources should offer a parseable feed of changes to its dataset (package
addition, removal, suite changes, etc). RSS/Atom is the most natural format to
use here. Implementing this will need a
Hello,
The Maintainer Dashboard[1] is a tool for answering the question "I have
a few hours for Debian, what should I do now?".
Lately we had some improvements:
- The user interface is revamped and styled according to debian main
websites.
- A RSS feed of todo tasks is available for every l
to start to using the '-d' flag of masternode script
to avoid conflicts beetween users. It changes the build-logs output dir (see -h
for help).
Thanks, and sorry for the incoveniences that this change can cause.
David
--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.
to avoid email wrappering. I also want to note:
This query demonstrates that the transition from the
debian-devel-changes.201307 file to the debian-devel-changes.current (AKA
inbound mail) is smooth.
We also might want to fix the code to avoid the historical problem with
believing that s
(just for historical purpose, we sorted this out on irc)
On Tue, 28 Aug 2012, Olivier Berger wrote:
> What's the process to try and have changes deployed to
> packages.qa.debian.org ?
Usually the person who commits can also do the "svn update" on
packages.qa.debian.org. B
Hi.
What's the process to try and have changes deployed to
packages.qa.debian.org ?
Maybe no one cares, but at least I've received to negative comments on
my proposal on generating RDF pages for the packages on the PTS, so I'd
like to roll out these changes so that it goes
Hi,
I have tested the current state inside SVN for ten days without any
problem. I would love if somebody else would apply the changes for
two reasons:
1. Another pair of eyeballs are locking onto it
2. I have very slow access to the host (always need to recover
screen sessions
Hi,
On Sat, Feb 18, 2012 at 04:07:07PM +0100, Lucas Nussbaum wrote:
> On 18/02/12 at 15:14 +0100, Andreas Tille wrote:
> > I do not want to push against Lenny data inside UDD. I just want to
> > bring up the topic because I realised that the UDD hosting machine is
> > not as powerfull as sometime
Hi,
On 18/02/12 at 15:14 +0100, Andreas Tille wrote:
> Hi,
>
> I do not want to push against Lenny data inside UDD. I just want to
> bring up the topic because I realised that the UDD hosting machine is
> not as powerfull as sometimes needed and we are starting to include more
> derivatives than
Hi,
I do not want to push against Lenny data inside UDD. I just want to
bring up the topic because I realised that the UDD hosting machine is
not as powerfull as sometimes needed and we are starting to include more
derivatives than just Ubuntu. So it might make sense to consider droping
Lenny da
Your message dated Tue, 1 Nov 2011 13:08:52 +
with message-id <2001130852.ga12...@master.debian.org>
and subject line qa.debian.org: changes needed in ldap2bugs / bugs.txt
generation
has caused the Debian Bug report #509548,
regarding qa.debian.org: changes needed in ldap2bugs / bu
Hi,
I wrote a script named find_overrides[1] which finds
packages depending on packages with a lower priority
and proposes overrides to increase the priority of
the lower-priority package.
The tool is run with the name(s) of the archive(s)
(like "unstable") as its argument(s). It uses the
local A
Mark Brown wrote:
> Look, I'm not saying that there's no problem with the upload here. What
> I'm saying is that an e-mail such as that which was sent originally sent
> tended rather to the hostile and appears to have unrealistic expectation
> as to the sort of work that a maintainer is going to d
On Wed, Apr 28, 2010 at 03:10:34PM +0200, Jan Hauke Rahm wrote:
> On Wed, Apr 28, 2010 at 11:29:20AM +0100, Mark Brown wrote:
> > *sigh* Lintian just isn't the right tool for this job, the sort of
> > random things that lintian identifies just aren't interesting for an
> > upload like this.
> An
On Wed, Apr 28, 2010 at 11:29:20AM +0100, Mark Brown wrote:
> On Wed, Apr 28, 2010 at 12:01:22PM +0200, Cyril Brulebois wrote:
> > Mark Brown (28/04/2010):
> > > I'm orphaning the package. What part of that makes you think I'm
> > > going to be interested in fixing random lintian warnings?
>
> >
On Wed, Apr 28, 2010 at 12:01:22PM +0200, Cyril Brulebois wrote:
> Mark Brown (28/04/2010):
> > I'm orphaning the package. What part of that makes you think I'm
> > going to be interested in fixing random lintian warnings?
> Random lintian warnings (and errors) like the ones you're generating
>
Mark Brown (28/04/2010):
> I'm orphaning the package. What part of that makes you think I'm
> going to be interested in fixing random lintian warnings?
Random lintian warnings (and errors) like the ones you're generating
by orphaning the package in an improper manner? If you're not used to
that
On Tue, Apr 27, 2010 at 08:11:06PM -0500, Raphael Geissert wrote:
> From the changelog:
> >* Orphan package.
> Right, but orphaned packages are _not_ set to this discussion ML.
Thanks for your helpful response!
> Even running lintian on the package you uploaded points you to the right
> d
Hi Mark,
Archive Administrator wrote:
>
> Accepted:
> gob2_2.0.16-3.debian.tar.gz
> to main/g/gob2/gob2_2.0.16-3.debian.tar.gz
> gob2_2.0.16-3.dsc
> to main/g/gob2/gob2_2.0.16-3.dsc
> gob2_2.0.16-3_amd64.deb
> to main/g/gob2/gob2_2.0.16-3_amd64.deb
>
>
> Override entries for your package:
Accepted:
gob2_2.0.16-3.debian.tar.gz
to main/g/gob2/gob2_2.0.16-3.debian.tar.gz
gob2_2.0.16-3.dsc
to main/g/gob2/gob2_2.0.16-3.dsc
gob2_2.0.16-3_amd64.deb
to main/g/gob2/gob2_2.0.16-3_amd64.deb
Override entries for your package:
gob2_2.0.16-3.dsc - source devel
gob2_2.0.16-3_amd64.deb -
gob2_2.0.16-3_amd64.changes uploaded successfully to localhost
along with the files:
gob2_2.0.16-3.dsc
gob2_2.0.16-3.debian.tar.gz
gob2_2.0.16-3_amd64.deb
Greetings,
Your Debian queue daemon (running on host ries.debian.org)
--
To UNSUBSCRIBE, email to debian-qa-requ
reassign 559419 ftp.debian.org
retitle 559419 http://ftp-master.debian.org/new.html: links to individual
packages broken
severity 559419 normal
affects 559419 qa.debian.org
thanks
Hi,
On Fri, Dec 04, 2009 at 09:41:00AM +0100, Micha Lenk wrote:
> if an upload sits in NEW for approval by the ftp m
Processing commands for cont...@bugs.debian.org:
> reassign 559419 ftp.debian.org
Bug #559419 [qa.debian.org] DDPO: Invalid link to changes file for packages in
NEW
Bug reassigned from package 'qa.debian.org' to 'ftp.debian.org'.
> retitle 559419 http://ftp-master.deb
Package: qa.debian.org
Severity: minor
Hi,
if an upload sits in NEW for approval by the ftp masters, it version is
shown below the version available in unstable, and linked to some file
on ftp-master.debian.org. This link is broken.
Take for example my [1]DDPO page: Currently Gnucash 2.2.9-2 si
On Sun, Jul 19, 2009 at 11:45 AM, Lucas
Nussbaum wrote:
> On 19/07/09 at 09:00 -0400, Jonathan Yu wrote:
>> Hi:
>>
>> On Thu, Jul 16, 2009 at 4:28 PM, Lucas Nussbaum
>> wrote:
>> > Hi,
>> >
>> > I've squashed a few items o
On 19/07/09 at 09:00 -0400, Jonathan Yu wrote:
> Hi:
>
> On Thu, Jul 16, 2009 at 4:28 PM, Lucas Nussbaum
> wrote:
> > Hi,
> >
> > I've squashed a few items off my TODO list about UDD. I did the
> > following changes:
> >
> > - 'release
On 19/07/09 at 10:17 +0100, Enrico Zini wrote:
> On Sun, Jul 19, 2009 at 10:08:51AM +0100, Enrico Zini wrote:
>
> > > - all_packages_distrelcomparch (which was a hack) was replaced by two
> > > different tables (for Debian and Ubuntu) and a
> > > all_packages_distrelcomparch view.
> >
> > It lo
On 19/07/09 at 10:58 +0100, Enrico Zini wrote:
> On Thu, Jul 16, 2009 at 04:28:57PM -0400, Lucas Nussbaum wrote:
>
> > However, turning release into an ENUM required changes in related tables
> > (packages and packages_summary), and the only way to sanely apply them
> > w
Hi:
On Thu, Jul 16, 2009 at 4:28 PM, Lucas Nussbaum wrote:
> Hi,
>
> I've squashed a few items off my TODO list about UDD. I did the
> following changes:
>
> - 'release' columns are now ENUMs everywhere. This allows to compare two
> releases ('etch'
On Thu, Jul 16, 2009 at 04:28:57PM -0400, Lucas Nussbaum wrote:
> However, turning release into an ENUM required changes in related tables
> (packages and packages_summary), and the only way to sanely apply them
> was to drop the table and create them again. Which I did, so the tab
On Sun, Jul 19, 2009 at 10:08:51AM +0100, Enrico Zini wrote:
> > - all_packages_distrelcomparch (which was a hack) was replaced by two
> > different tables (for Debian and Ubuntu) and a
> > all_packages_distrelcomparch view.
>
> It looks like some permission is missing:
>
> d...@merkel:/srv/dd
On Thu, Jul 16, 2009 at 04:28:57PM -0400, Lucas Nussbaum wrote:
> - all_packages_distrelcomparch (which was a hack) was replaced by two
> different tables (for Debian and Ubuntu) and a
> all_packages_distrelcomparch view.
It looks like some permission is missing:
d...@merkel:/srv/dde.debian.ne
Hi,
I've squashed a few items off my TODO list about UDD. I did the
following changes:
- 'release' columns are now ENUMs everywhere. This allows to compare two
releases ('etch' < 'squeeze') or to order by release.
- all_packages_distrelcomparch
Hi,
I have changed the TZ config on merkel from MDT to UTC to match the way
all other systems are set up nowadays.
You have a non-* hour in at least one of your crontabs' lines on
merkel.debian.org. If the exact timing of your scheduled commands are
important you might have to adapt your crontab
Frank Lichtenheld wrote:
> On Sat, Feb 14, 2009 at 06:19:19PM +0100, Luk Claes wrote:
>> Frank: data/stats/output_stats refers to your home directory, can you
>> please integrate the needed things in the qa repository itself and
>> update it for the release, TIA.
>
> I really, really have no idea
On Sat, Feb 14, 2009 at 06:19:19PM +0100, Luk Claes wrote:
> Frank: data/stats/output_stats refers to your home directory, can you
> please integrate the needed things in the qa repository itself and
> update it for the release, TIA.
I really, really have no idea what that was and what I used that
;t
have to be updated in so much files when something changes...
I found some strange things when doing the changes:
Lucas: data/ddpo/ubuntu.pl refers to your home directory, can you please
integrate the needed things in the qa repository itself, TIA.
Christoph: data/ddpo/extract_incomi
On Tue, 27 Jan 2009, James Westby wrote:
I have just put an updated package at
http://people.ubuntu.com/~jamesw/packages/ncpfs_2.2.6-6/ncpfs_2.2.6-6.dsc
Thanks. Just uploading the sponsored package.
The remaining lintian issues are:
W: ncpfs source: ancient-libtool contrib/php/ltmain.sh 1
On Thu, 2009-01-15 at 17:14 +0100, Andreas Tille wrote:
> On Thu, 15 Jan 2009, James Westby wrote:
>
> > Some fixes had built up in Ubuntu's ncpfs package, and as the package
> > is QA maintained I rolled a proposed update for Debian. Would someone
> > kindly review and sponsor my package at
> >
>
On Thu, 15 Jan 2009, James Westby wrote:
E: ncpfs source: outdated-autotools-helper-file contrib/php/config.sub
2003-10-07
E: ncpfs source: outdated-autotools-helper-file contrib/php/config.guess
2003-10-07
These I should have fixed I realise.
Yes.
W: ncpfs: binary-without-manpage sbin/m
On Thu, 2009-01-15 at 17:14 +0100, Andreas Tille wrote:
> On Thu, 15 Jan 2009, James Westby wrote:
>
> > Some fixes had built up in Ubuntu's ncpfs package, and as the package
> > is QA maintained I rolled a proposed update for Debian. Would someone
> > kindly review and sponsor my package at
> >
>
On Thu, 15 Jan 2009, James Westby wrote:
Some fixes had built up in Ubuntu's ncpfs package, and as the package
is QA maintained I rolled a proposed update for Debian. Would someone
kindly review and sponsor my package at
http://people.ubuntu.com/~jamesw/packages/ncpfs_2.2.6-6/ncpfs_2.2.6-6.dsc
Hi,
Some fixes had built up in Ubuntu's ncpfs package, and as the package
is QA maintained I rolled a proposed update for Debian. Would someone
kindly review and sponsor my package at
http://people.ubuntu.com/~jamesw/packages/ncpfs_2.2.6-6/ncpfs_2.2.6-6.dsc
I haven't been able to test it in acti
Package: qa.debian.org
Severity: normal
The scripts should be fixed to cope with "src:foo" as package assignment.
dondelelcaro: wishlist, could the BTS refuse package names with ":" in
it ?
example: 504907
it ends up creation problems further down in automated scripts that rely on
the fact t
On Sun, Sep 21, 2008 at 09:21:40PM +0200, Lucas Nussbaum wrote:
> On 21/09/08 at 20:37 +0200, Kurt Roeckx wrote:
> > Hi,
> >
> > I'd like to make some minor changes the current udd schema:
> > - Make severity an enum instead of text:
> > CREATE TYPE bug
On 21/09/08 at 20:37 +0200, Kurt Roeckx wrote:
> Hi,
>
> I'd like to make some minor changes the current udd schema:
> - Make severity an enum instead of text:
> CREATE TYPE bugs_severity AS ENUM ('fixed', 'wishlist', 'minor', 'normal'
Hi,
I'd like to make some minor changes the current udd schema:
- Make severity an enum instead of text:
CREATE TYPE bugs_severity AS ENUM ('fixed', 'wishlist', 'minor', 'normal',
'important', 'serious', 'grave',
[please follow up to -project or -admin or just me, depending on what
seems more appropriate.]
Hi,
if you use sudo on project machines this will affect you.
The short version:
If you want to use sudo in the future, go to http://db.debian.org/ and set a
sudo password for you.
A slightly long
On Tue, Jul 22, 2008 at 07:36:43PM +0200, Filippo Giunchedi wrote:
> The weekly update period is rather arbitrary, can be switched to daily
> effortlessly.
There's now a script subscribed to d-d-changes so the updates should be live and
pushed rather than pulled.
I'm welcomin
On Tue, Jul 22, 2008 at 12:45:34AM +0200, Filippo Giunchedi wrote:
> Hi,
> I've produced a script[0] to parse d-d-changes archives to a sane format so to
> produce an history of uploads made to debian[1] in this form:
>
> Source: netselect
> Version: 0.3.ds1-12.1
> Date:
On 22/07/08 at 19:36 +0200, Filippo Giunchedi wrote:
> On Tue, Jul 22, 2008 at 09:29:49AM +0200, Stefano Zacchiroli wrote:
> > On Tue, Jul 22, 2008 at 12:45:34AM +0200, Filippo Giunchedi wrote:
> > > I've produced a script[0] to parse d-d-changes archives to a s
1 - 100 of 674 matches
Mail list logo
