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
Hi,
it appears that the packages gap [0] and gap-io [1] are blocked because
some of their r-dependent packages (e.g., gap-factint) actually in testing
fail one a their tests. The tests in question are similar and fail
because the last version of gap adds now a trailing slash to path directories
Am Sat, Feb 18, 2023 at 11:25:11AM +0100 schrieb Andreas Tille:
> > Does it call deb-new-upstream as well? That's the one that mainly seems
> > relevant here.
>
> I just learned about deb-new-upstream. Its parsing uscan manually but its not
> very robust and I should probably switch to use deb-n
Am Fri, Feb 17, 2023 at 10:32:06PM + schrieb Jelmer Vernooij:
> >
> > is your friend. It also calls scripts that are used by Janitor.
>
> Does it call deb-new-upstream as well? That's the one that mainly seems
> relevant here.
I just learned about deb-new-upstream. Its parsing uscan manual
On Fri, Feb 17, 2023 at 09:26:17PM +0100, Andreas Tille wrote:
> Hi Yaroslav,
>
> Am Wed, Jan 25, 2023 at 10:05:03AM -0500 schrieb Yaroslav Halchenko:
> > I just wanted to say Thank you for all the pointers! Overall, janitor
> > looks great and the most advanced and seems already covering various
Hi Yaroslav,
Am Wed, Jan 25, 2023 at 10:05:03AM -0500 schrieb Yaroslav Halchenko:
> I just wanted to say Thank you for all the pointers! Overall, janitor
> looks great and the most advanced and seems already covering various
> aspects but might be a bit "too big to tune for our own use-case", so
Hi Yaroslav,
On Wed, Jan 25, 2023 at 10:05:03AM -0500, Yaroslav Halchenko wrote:
> I just wanted to say Thank you for all the pointers! Overall, janitor
> looks great and the most advanced and seems already covering various
> aspects but might be a bit "too big to tune for our own use-case", so
Dear Andrej, Paul and undef,
I just wanted to say Thank you for all the pointers! Overall, janitor
looks great and the most advanced and seems already covering various
aspects but might be a bit "too big to tune for our own use-case", so we
might indeed pick up on ideas/implementations... we will
Hi,
On Fri, 20 Jan 2023, at 17:01, Yaroslav Halchenko wrote:
> Dear Debian gurus,
>
> Lazy me would love to get automation going akin to the one in
> conda-forge (see e.g. [1]) -- whenever a new upstream is released
> (as could be detected with a run of uscan) the CI would
<...>
> Is there any p
On Fri, 2023-01-20 at 11:01 -0500, Yaroslav Halchenko wrote:
> Is there any package/tool which already does something like that on CI?
> Or may be you see some issues with such a procedure?
The Debian Janitor is already doing some of that for all packages,
for both new upstreams and new upstream
Lazy me would love to get automation going akin to the one in
conda-forge (see e.g. [1]) -- whenever a new upstream is released
(as could be detected with a run of uscan) the CI would
It's not exactly what you describe (because we're rebasing), but the
Mobian team has been doing something l
Dear Debian gurus,
Lazy me would love to get automation going akin to the one in
conda-forge (see e.g. [1]) -- whenever a new upstream is released
(as could be detected with a run of uscan) the CI would
- would run uscan
- get new source {tarball}
- get new {uversion} (from uscan output/tarb
Hi,
udd provides RSS
Cheers,
Yadd
Le 21 novembre 2021 22:58:48 GMT+01:00, Alexis Murzeau a
écrit :
>Hi,
>
>Is there a way to receive a mail when a new upstream version is released ?
>
>I've subscribed to my package on https://tracker.debian.org but I don't
>re
Hi,
Is there a way to receive a mail when a new upstream version is released ?
I've subscribed to my package on https://tracker.debian.org but I don't
receive mails for new upstream releases.
Maybe there is other ways ?
--
Alexis Murzeau
PGP: B7E6 0EBB 9293 7B06 BDBC 2787 E7BD 1904
This is an issue with the checking system, not a bug in your package.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955268
Le 08/04/2020 à 08:54, Mechtilde Stehmann a écrit :
> Hello,
>
> for most of my packages I get the following message at
> tracker.debian.org (e.g. for tbsync)
>
>
> uscan had problems while searching for a new upstream version:
>
> In watchfile debian/watch
On 4/8/20 8:54 AM, Mechtilde Stehmann wrote:
> How can I solve it?
Run uscan on your own system to check for new upstream releases.
This is a known issue due to the high number of packages that are
checked by the QA servers, see: #955268.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4A
Hello,
for most of my packages I get the following message at
tracker.debian.org (e.g. for tbsync)
uscan had problems while searching for a new upstream version:
In watchfile debian/watch, reading webpage
https://github.com/jobisoft/TbSync/releases/ failed: 429 too many requests
How can I
Package: isc-kea
Version: 1.3.0-1
Severity: Wishlist
X-Debbugs-CC: debian-devel@lists.debian.org
This package has not had a lot of updates as the new versions come out. The
latest version brings a lot of improvements that would be great to make
available.
I am not sure if the maintainer has orpha
On Sat, Apr 06, 2013 at 07:18:50PM -0300, Santiago Torres Batán wrote:
> Hi, sorry for the delay.
> Yes, I'm active. I was waiting the new realease to find a sponsor and work
> with the new version of the package.
>
> Thanks for the bug reports. I'm going to check them out.
Dear Santiago, are yo
On Sat, Apr 06, 2013 at 07:18:50PM -0300, Santiago Torres Batán wrote:
> Hi, sorry for the delay.
> Yes, I'm active. I was waiting the new realease to find a sponsor and work
> with the new version of the package.
>
> Thanks for the bug reports. I'm going to check them out.
Hi,
did you find a sp
Hi, sorry for the delay.
Yes, I'm active. I was waiting the new realease to find a sponsor and work
with the new version of the package.
Thanks for the bug reports. I'm going to check them out.
2013/4/6
> fotoxx version 13.04 is available:
> http://www.kornelix.com/uploads/1/3/0/3/13035936/fot
fotoxx version 13.04 is available:
http://www.kornelix.com/uploads/1/3/0/3/13035936/fotoxx-13.04.tar.gz
The Debian watch file needs to be updated.
Is the package maintainer still active?
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble?
On Thu, 15 Nov 2012 11:05:02 +0100, Mari Wang wrote:
> >> libimage-exiftool-perl got its last update in July 2011.
> > This package could be also maintained by Debian-perl team.
> > Mari, do you have any objection if Debian-perl team adopt
> > libimage-exif-perl ?
> > Note that you are more than w
Dominique Dumont writes:
> On Tuesday 13 November 2012 12:12:14 random.numb...@gmx.com wrote:
>> libimage-exiftool-perl got its last update in July 2011.
> ...
>> Mari's last reaction to this bug was five months ago.
>
> This package could be also maintained by Debian-perl team.
>
> Mari, do you
About 10 days ago I sent an email to m...@qu.debian.org requesting that this
package be orphaned. They suggested that I email the sponsor/co-maintainer,
Petter Reinholdtsen, which I did, but I have so far had no response from him
either.
- Phil
--
To UNSUBSCRIBE, email to debian-devel-requ..
On Tuesday 13 November 2012 12:12:14 random.numb...@gmx.com wrote:
> libimage-exiftool-perl got its last update in July 2011.
...
> Mari's last reaction to this bug was five months ago.
This package could be also maintained by Debian-perl team.
Mari, do you have any objection if Debian-perl team
On Tue, Oct 02, 2012 at 07:05:30AM -0400, Phil Harvey wrote:
> Mari is M.I.A.
>
> libimage-exiftool-perl needs a new maintainer.
>
> - Phil
Dear all,
libimage-exiftool-perl got its last update in July 2011.
In the meanwhile, Phil released several new versions of exiftool:
Sept. 24,2011 - V
On Tue, Oct 02, 2012 at 07:05:30AM -0400, Phil Harvey wrote:
> Mari is M.I.A.
>
> libimage-exiftool-perl needs a new maintainer.
>
> - Phil
Please orphan this package. The maintainer seems to be no longer active.
Regards
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with
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
On Wed, Sep 15, 2010 at 10:12:29PM +0200, Bernd Zeimetz wrote:
> On 09/15/2010 06:33 PM, Henrique de Moraes Holschuh wrote:
> > On Wed, 15 Sep 2010, Giuseppe Sacco wrote:
> >>> IMO, you should try to get yourself better acquinted with quilt before
> >>> using it, or you can end up with a mess.
> >>
On Wed, 15 Sep 2010, Henrique de Moraes Holschuh wrote:
> On Wed, 15 Sep 2010, Goswin von Brederlow wrote:
> > QUILT_PATCHES=debian/patches quilt push
> >
> > will do the same. You only need QUILT_PATCHES for the first quilt call.
>
> Is that so? That would be good news, but it doesn't match m
On 09/15/2010 06:33 PM, Henrique de Moraes Holschuh wrote:
> On Wed, 15 Sep 2010, Giuseppe Sacco wrote:
>>> IMO, you should try to get yourself better acquinted with quilt before
>>> using it, or you can end up with a mess.
>>
>> Right. That's why I am testing this process while upstream only produ
On Wed, 15 Sep 2010, Goswin von Brederlow wrote:
> QUILT_PATCHES=debian/patches quilt push
>
> will do the same. You only need QUILT_PATCHES for the first quilt call.
Is that so? That would be good news, but it doesn't match my
experience... although the last time I tried that was some months
Christoph Egger writes:
> Giuseppe Sacco writes:
>> here it fails with message "No patches in series" because it doesn't
>> look for debian/patches/series but only for patches/series.
>
> export QUILT_PATCHES=debian/patches
Actually not needed.
Just type "debuild" or "dpkg-buildpackage". It wi
Giuseppe Sacco writes:
> here it fails with message "No patches in series" because it doesn't
> look for debian/patches/series but only for patches/series.
export QUILT_PATCHES=debian/patches
--
9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731
Debian Developer | Lisp Hacker | CaCert Assurer
A
On Wed, 15 Sep 2010, Giuseppe Sacco wrote:
> > IMO, you should try to get yourself better acquinted with quilt before
> > using it, or you can end up with a mess.
>
> Right. That's why I am testing this process while upstream only produced
> and rc version.
I've found that using dpkg-source forma
Il giorno mer, 15/09/2010 alle 13.14 -0300, Henrique de Moraes Holschuh
ha scritto:
[...]
> "man quilt" explains it all.
thanks
> IMO, you should try to get yourself better acquinted with quilt before
> using it, or you can end up with a mess.
Right. That's why I am testing this process while up
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 09/15/2010 11:58 AM, Giuseppe Sacco wrote:
>
> here it fails with message "No patches in series" because it doesn't
> look for debian/patches/series but only for patches/series.
>
See section 3.1 of the New Maintainers Guide.
Regards,
- --
On Wed, 15 Sep 2010, Giuseppe Sacco wrote:
> here it fails with message "No patches in series" because it doesn't
> look for debian/patches/series but only for patches/series.
You have to set the QUILT_PATCHES environment variable or tell quilt where
to find the patches through its config file.
"
Hi all, I have recently packaged hylafax 6.0.4-10 using quilt. Now I am
moving to a new upstream release 6.0.5 and I am trying to update my
package following
http://www.debian.org/doc/maint-guide/ch-update.en.html#s-newupstream
but I failed to it properly.
What I do:
1. untar new upstream release
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Package: dcraw
Followup-For: Bug #519604
Followup-For: Bug #506705
Followup-For: Bug #523789
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 v
Hi,
Please could you aim at 4.58beta instead? It's the first version that can
be used by grub-pc for compression of boot blocks.
See:
http://lists.gnu.org/archive/html/grub-devel/2008-07/msg00036.html
thanks
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will dec
Il giorno gio, 17/07/2008 alle 17.30 -0500, William Pitcock ha scritto:
> > audacious-plugins is already compatible with the new version of
> > libprojectM... I've looked at the logs of buildd of
> audacious-plugins
> > and the projectM plugin isn't build from version 1.4.5-1, so the
> update
> > o
On Thu, 2008-07-17 at 19:18 +0200, Francesco Namuri wrote:
> Il giorno mer, 16/07/2008 alle 17.46 -0500, William Pitcock ha scritto:
> > Hi,
> >
> > On Wed, 2008-07-16 at 22:59 +0200, Francesco Namuri wrote:
> > > Hi,
> > > I've packaged the new version of this library, the upstream author has
> >
Il giorno mer, 16/07/2008 alle 17.46 -0500, William Pitcock ha scritto:
> Hi,
>
> On Wed, 2008-07-16 at 22:59 +0200, Francesco Namuri wrote:
> > Hi,
> > I've packaged the new version of this library, the upstream author has
> > changed the SONAME, and so I've changed the name of the lib and -data
Il giorno mer, 16/07/2008 alle 19.37 -0500, William Pitcock ha scritto:
> On Thu, 2008-07-17 at 00:57 +0200, Francesco Namuri wrote:
> > Il giorno mer, 16/07/2008 alle 17.46 -0500, William Pitcock ha scritto:
> > > Hi,
> > >
> > > On Wed, 2008-07-16 at 22:59 +0200, Francesco Namuri wrote:
> > > >
On Thu, 2008-07-17 at 00:57 +0200, Francesco Namuri wrote:
> Il giorno mer, 16/07/2008 alle 17.46 -0500, William Pitcock ha scritto:
> > Hi,
> >
> > On Wed, 2008-07-16 at 22:59 +0200, Francesco Namuri wrote:
> > > Hi,
> > > I've packaged the new version of this library, the upstream author has
> >
Il giorno mer, 16/07/2008 alle 17.46 -0500, William Pitcock ha scritto:
> Hi,
>
> On Wed, 2008-07-16 at 22:59 +0200, Francesco Namuri wrote:
> > Hi,
> > I've packaged the new version of this library, the upstream author has
> > changed the SONAME, and so I've changed the name of the lib and -data
Hi,
On Wed, 2008-07-16 at 22:59 +0200, Francesco Namuri wrote:
> Hi,
> I've packaged the new version of this library, the upstream author has
> changed the SONAME, and so I've changed the name of the lib and -data
> package, not changed the name of the -dev file because the old
> maintainer has ch
Hi,
I've packaged the new version of this library, the upstream author has
changed the SONAME, and so I've changed the name of the lib and -data
package, not changed the name of the -dev file because the old
maintainer has chosen to not version the package.
This is my first library package, and I'
tags 460501 + help
thanks
Hi,
Actually, I have already prepared a package for the new upstream release
(4.57)[0]. The package is almost ready, it's just that I don't know how
to update lzmp patch[1], I would need some help for that...
Regards,
Arnaud Fontaine
[0] http://git.debian.org/?p=colla
On Tue, 31 Jan 2006, Jaldhar H. Vyas wrote:
Package: libxml-atom-perl
Oops that wasn't supposed to have a x-debbugs-cc. Sorry.
--
Jaldhar H. Vyas <[EMAIL PROTECTED]>
La Salle Debain - http://www.braincells.com/debian/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubsc
Package: libxml-atom-perl
Version: 0.09-1
Severity: wishlist
The package has gotten out of date again. Can you package the latest version,
0.16? Or if you are busy, let me know and I can do an NMU.
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.10-xenU-p4
t;[EMAIL PROTECTED]>; Wed, 15 May 2002 13:40:54 +0900 (JST)
Date: Wed, 15 May 2002 13:40:45 +0900
From: ISHIKAWA Mutsumi <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: libjcode-pm-perl: new upstream version
User-Agent: Wanderlust/2.9.11 (Unchained Melody) SEMI/1.14.3 (Ushinoya)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: hasciicam
Version: 0.9.1
Severity: wishlist
new upstream version, major bugfixes included to support more devices,
ftp fixes and better grabbing code. SGI crossplatform support has been
dropped, also fixes to autoconf/automake files. thanks
On Sun, Oct 11, 1998 at 01:27:01PM +0200, Christoph Martin wrote:
> So, which formats do you consider to be important for the defaults?
This is my preference:
All packages that install TeX formats (including tetex-*), do in
postinst a 'fmtutil -byfmt blah' for every format they include.
Ideally t
Hello,
On Sun, Oct 11, 1998 at 01:27:01PM +0200, Christoph Martin wrote:
> Antti-Juhani Kaijanaho writes:
> >
> > * The new fmtutil has a config file (fmtutil.cnf) that controls which
> >formats get remade with 'texconfig init' (which is now equivalent to
> >'fmtutil --all'). The d
Antti-Juhani Kaijanaho writes:
>
> * The new fmtutil has a config file (fmtutil.cnf) that controls which
>formats get remade with 'texconfig init' (which is now equivalent to
>'fmtutil --all'). The defaults are hyperconservative IMO (eg. no
>pdf*tex or amstex formats are made).
77 matches
Mail list logo
