Le Wed, May 08, 2024 at 08:41:47PM +0200, Paul Gevers a écrit :
> Hi,
>
> On 08-05-2024 6:06 p.m., Bill Allombert wrote:
> > Agreed, but gap does not actually breaks anything, it is just the tests
> > in testing that are broken. So I can do that but that seems a bit
> > artificial.
>
> Aha, that
Hi,
On 08-05-2024 6:06 p.m., Bill Allombert wrote:
Agreed, but gap does not actually breaks anything, it is just the tests
in testing that are broken. So I can do that but that seems a bit artificial.
Aha, that wasn't at all clear to me. If you don't want to do the
artificial thing (which is
On Wed, May 08, 2024 at 03:21:12PM +, Graham Inggs wrote:
> Hi Bill
>
> On Wed, 8 May 2024 at 13:58, Bill Allombert wrote:
> > The problem is that all the debs in testing and sid are correct, it is the
> > autopkgtest in
> > testing which are wrong (they are relying on undocumented behaviour
Hi Bill
On Wed, 8 May 2024 at 13:58, Bill Allombert wrote:
> The problem is that all the debs in testing and sid are correct, it is the
> autopkgtest in
> testing which are wrong (they are relying on undocumented behaviour).
> They are fixed in sid.
I think an upload of gap, with Breaks on the
Le Sat, May 04, 2024 at 02:32:22PM +0200, Paul Gevers a écrit :
> Hi,
>
> On 04-05-2024 11:39 a.m., Jerome BENOIT wrote:
> > What would be the best way to unblock the migration of gap and gap-io ?
>
> If gap isn't going to change (which might be the easiest solution), then
> file bugs and fix tho
Hi,
On 04-05-2024 11:39 a.m., Jerome BENOIT wrote:
What would be the best way to unblock the migration of gap and gap-io ?
If gap isn't going to change (which might be the easiest solution), then
file bugs and fix those reverse dependencies. Those bugs are RC and in
due time will cause autor
On Wed, 12 Sep 2012 17:20:17 +0800, Chow Loong Jin wrote:
> >> If the Debian maintainer uses the 3.0 format, the debian/ directory is
> >> magically removed from the upstream tarball anyway.
> > Right, but it's still annyoing when importing into a VCS.
> git import-orig --filter=debian/ might help
On 12/09/2012 05:29, gregor herrmann wrote:
> On Tue, 11 Sep 2012 22:33:28 +0200, Tollef Fog Heen wrote:
>
>> If the Debian maintainer uses the 3.0 format, the debian/ directory is
>> magically removed from the upstream tarball anyway.
>
> Right, but it's still annyoing when importing into a VCS.
On Tue, 11 Sep 2012 22:33:28 +0200, Tollef Fog Heen wrote:
> If the Debian maintainer uses the 3.0 format, the debian/ directory is
> magically removed from the upstream tarball anyway.
Right, but it's still annyoing when importing into a VCS.
Cheers,
gregor
--
.''`. Homepage: http://info.
On Tue, Sep 11, 2012 at 10:33:28PM +0200, Tollef Fog Heen wrote:
> As long as the debian/ directory is properly maintained, I don't really
> see a downside in shipping it upstream.
In the case in question it is a fork of a quite outdated packaging.
Kind regards
Andreas.
--
http://fam
]] Peter Samuelson
> [Neil Williams]
> > These are not native packages, they are expressly used by other
> > distributions than Debian or even Debian derivatives - just because
> > I'm on the upstream team / am the entire upstream team does NOT mean
> > that I am justified in polluting the tarbal
[Neil Williams]
> These are not native packages, they are expressly used by other
> distributions than Debian or even Debian derivatives - just because
> I'm on the upstream team / am the entire upstream team does NOT mean
> that I am justified in polluting the tarball released to RPM users
> with
Andreas Tille writes ("Re: New upstream version of velvet contains debian/
dir"):
> On Mon, Sep 10, 2012 at 11:34:54AM +0100, Neil Williams wrote:
> > Stop being lazy and be a friendly upstream to
> > non-Debian downstreams.
>
> Charles is not upstream itself - he
On Mon, Sep 10, 2012 at 11:34:54AM +0100, Neil Williams wrote:
> Stop being lazy and be a friendly upstream to
> non-Debian downstreams.
Charles is not upstream itself - he just gave an advise to upstream to
diverge from what we usually propose and I wanted to check whether our
advise remains vali
On Mon, 10 Sep 2012 18:57:45 +0900
Charles Plessy wrote:
> For the package velvet: I created it. I sometimes use it. I uploaded it 14
> times. I met the developer in the real life (5 minutes...). It has been some
> time I have been considering switching the source package to Git in order to
Le Mon, Sep 10, 2012 at 11:35:25AM +0200, Andreas Tille a écrit :
>
> On Mon, Sep 10, 2012 at 04:30:38PM +0900, Charles Plessy wrote:
> >
> > For the packages that I started and on which I am still a major
> > contributor, I
> > would like Upstream to include a debian directory in his source tar
[History of thread:
http://lists.debian.org/debian-med/2012/09/msg00024.html
and following
Please stick to debian-devel when responding - reply-to set]
Hi Charles,
On Mon, Sep 10, 2012 at 04:30:38PM +0900, Charles Plessy wrote:
> I answer on debian-med only to avoid adding to the confusion
Hi,
thanks for the hint to debian-mentors. So I add that list and attach the
original mail to that mail. I set also a reply-to for debian-mentors und
myself (I am not subscribed to debian-mentor 'til now). I left also
debian-devel to show where the follow up is going on. (Urgh, NNTP is
that better
Le Sat, Oct 24, 2009 at 02:45:13PM +0100, Klaus Ethgen a écrit :
>
> I am not a debian maintainer, but I can create a NMU and send it to
> Steve King (Maintainer of dcraw) for regular upload by you or give it to
> another maintainer to load up the NMU if the regular maintainer is to
> busy. For th
On Sat, Oct 24, 2009 at 02:45:13PM +0100, Klaus Ethgen wrote:
> I updated dcraw strait forward to version 8.95-0. This can be done in
> less than 5 minutes. And even this is not the newest version. The reason
> I need that version was that the version in debian doesn't support my
> EOS500D.
>
> Ho
20 matches
Mail list logo
