changing existing entries in debian/changelog

[Bastian Venthur]

Hi,

I'm having troubles finding the relevant parts in the developers 
reference. I've uploaded a version to experimental and later found out 
that this version fixes several bugs.


Can I rewrite existing changelog entries for already uploaded versions 
with the next upload, i.e. by adding the relevant "closes" line to the 
previsions version?



Cheers,

Bastian

--
Dr. Bastian Venthur https://venthur.de
Debian Developer venthur at debian org

Re: changing existing entries in debian/changelog

[Andrey Rakhmatullin]

On Fri, May 24, 2024 at 09:30:44AM +0200, Bastian Venthur wrote:
> I'm having troubles finding the relevant parts in the developers reference.
> I've uploaded a version to experimental and later found out that this
> version fixes several bugs.
> 
> Can I rewrite existing changelog entries for already uploaded versions with
> the next upload, i.e. by adding the relevant "closes" line to the previsions
> version?
You can if you want but it won't close the bugs, you'll still need to
close them properly with manual action. SO it may be easier to just not
edit them.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Re: changing existing entries in debian/changelog

[Johannes Schauer Marin Rodrigues]

Quoting Andrey Rakhmatullin (2024-05-24 09:37:45)
> On Fri, May 24, 2024 at 09:30:44AM +0200, Bastian Venthur wrote:
> > I'm having troubles finding the relevant parts in the developers reference.
> > I've uploaded a version to experimental and later found out that this
> > version fixes several bugs.
> > 
> > Can I rewrite existing changelog entries for already uploaded versions with
> > the next upload, i.e. by adding the relevant "closes" line to the previsions
> > version?
> You can if you want but it won't close the bugs, you'll still need to
> close them properly with manual action. SO it may be easier to just not edit
> them.

When I forget to add the "closes:" line to d/changelog, I will add it
retroactively (after having closed the bugs with the correct version manually)
because it allows others as well as future-me to look up in d/changelog to
which changes correspond to which bugs and bugs will have much more context for
a problem than a line in d/changelog.

Thanks!

cheers, josch

signature.asc
Description: signature

Re: changing existing entries in debian/changelog

[Bill Allombert]

Le Fri, May 24, 2024 at 09:30:44AM +0200, Bastian Venthur a écrit :
> Hi,
> 
> I'm having troubles finding the relevant parts in the developers reference.
> I've uploaded a version to experimental and later found out that this
> version fixes several bugs.
> 
> Can I rewrite existing changelog entries for already uploaded versions with
> the next upload, i.e. by adding the relevant "closes" line to the previsions
> version?

You need to use the option -v of dpkg-genchanges so that the relevant
bugs are listed in the .changes file, so that they get automatically
closed.

Cheers,
-- 
Bill. 

Imagine a large red swirl here.

Re: changing existing entries in debian/changelog

[Johannes Schauer Marin Rodrigues]

Quoting Bill Allombert (2024-05-24 10:54:32)
> Le Fri, May 24, 2024 at 09:30:44AM +0200, Bastian Venthur a écrit :
> > Hi,
> > 
> > I'm having troubles finding the relevant parts in the developers reference.
> > I've uploaded a version to experimental and later found out that this
> > version fixes several bugs.
> > 
> > Can I rewrite existing changelog entries for already uploaded versions with
> > the next upload, i.e. by adding the relevant "closes" line to the previsions
> > version?
> 
> You need to use the option -v of dpkg-genchanges so that the relevant
> bugs are listed in the .changes file, so that they get automatically closed.

But then they get closed by the wrong version, no? Dev-ref says:

https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#when-bugs-are-closed-by-new-uploads

> To close any remaining bugs that were fixed by your upload, email the
> .changes file to xxx-d...@bugs.debian.org, where XXX is the bug number, and
> put Version: YYY and an empty line as the first two lines of the body of the
> email, where YYY is the first version where the bug has been fixed.

When I don't have the .changes file anymore, I just mail
xxx-d...@bugs.debian.org with a mail that has the "Version: YYY" line at the
top and then in the body explains that I'm manually closing it because I made a
mistake.

Thanks!

cheers, josch

signature.asc
Description: signature

salsa web server broken?

[Vincent Lefevre]

Is the salsa web server broken?

The display of https://salsa.debian.org/python-team/packages/fail2ban
is completely wrong, and https://salsa.debian.org/ gives an
error 500 "We're sorry. Something went wrong on our end.".

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: salsa web server broken?

[Alexander Wirt]

Am Fri, May 24, 2024 at 11:23:44AM +0200 schrieb Vincent Lefevre:
> Is the salsa web server broken?
> 
> The display of https://salsa.debian.org/python-team/packages/fail2ban
> is completely wrong, and https://salsa.debian.org/ gives an
>
We are in maintenance. 

Alex
 

Re: salsa web server broken?

[Vincent Lefevre]

On 2024-05-24 11:51:15 +0200, Alexander Wirt wrote:
> Am Fri, May 24, 2024 at 11:23:44AM +0200 schrieb Vincent Lefevre:
> > Is the salsa web server broken?
> > 
> > The display of https://salsa.debian.org/python-team/packages/fail2ban
> > is completely wrong, and https://salsa.debian.org/ gives an
> >
> We are in maintenance. 

OK. A mail is usually sent to debian-infrastructure-announce, but
this time, there was no such mail.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1071786: ITP: liblog-ger-perl -- lightweight, flexible logging framework

[gregor herrmann]

Package: wnpp
Owner: gregor herrmann 
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org, debian-p...@lists.debian.org

* Package name: liblog-ger-perl
  Version : 0.042
  Upstream Author : perlancar 
* URL : https://metacpan.org/release/Log-ger
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : lightweight, flexible logging framework

Log::ger is yet another logging framework with the following features:

 * separation of producers and consumers/listeners
 * lightweight and fast
 * fFlexible

The package will be maintained under the umbrella of the Debian Perl Group.

--
Generated with the help of dpt-gen-itp(1) from pkg-perl-tools.


signature.asc
Description: Digital Signature

Re: Debian 10 "buster" moved to archive.debian.org

[Otto Kekäläinen]

Hi!

So just to clarify, are you saying that a copy of
https://security.debian.org/debian-security/dists/buster/ will never
be archived at https://archive.debian.org/debian-security/dists/ like
previous releases have been so far?

This is not about getting *new security updates*, but purely a
question of how moving Buster to archival works and how e.g. CI
systems that test upgrades from Buster should work.

I see that e.g.
https://deb.debian.org/debian/dists/buster/main/binary-armel and
https://deb.debian.org/debian/dists/buster-updates/main/binary-armel
no longer exists, but have been archived at
https://archive.debian.org/debian/dists/buster/main/binary-armel/ and
https://archive.debian.org/debian/dists/buster-updates/main/binary-armel/.

The 
https://security.debian.org/debian-security/dists/buster/updates/main/binary-armel
is now gone, is the intent for it to show up on archive.debian.org in
some form?