[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#500656: marked as done (ability to create patches from older states of topic branches)



Your message dated Tue, 16 Sep 2025 11:35:40 +0000
with message-id <[🔎] E1uyTyG-00HNYV-04@fasolo.debian.org>
and subject line Bug#1115196: Removed package(s) from unstable
has caused the Debian Bug report #500656,
regarding ability to create patches from older states of topic branches
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
500656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500656
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: topgit
Version: 0.3-1
Severity: wishlist
Tags: upstream

To my understanding, topgit can create a patch for the current state
of a topic branch. It would be nice if it could extract patches
corresponding to a historical state too.

Specifically, assume that there's a 'pristine' branch, a number of
topgit branches, and a branch (topgit or not) from where a Debian
package is built. Once the package is built, the commit is tagged,
e.g. debian/1.0-1. Development continues, the topgit branches are
tg-updated, and now it seems impossible to extract the topgit
patches that went into debian/1.0-1.

It seems like the solution is a tg-tag command, which, when called
like

  tg-tag debian/1.0-1 tgbranch[, tgbranch, ...]

tags the top-bases and tips of all specified tg-branches, e.g. like
this:

  refs/top-tags/debian/1.0-1/base and
  refs/top-tags/debian/1.0-1/tip

Now, tg-patch could learn to deal with a tag name, and it would
simply use those two refs instead of the top-base of the current
branch and the tip.

Does this seem like a viable approach?

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_GB, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages topgit depends on:
ii  git-core                     1:1.5.6.5-1 fast, scalable, distributed revisi

topgit recommends no packages.

topgit suggests no packages.

-- no debconf information


-- 
 .''`.   martin f. krafft <madduck@debian.org>
: :'  :  proud Debian developer, author, administrator, and user
`. `'`   http://people.debian.org/~madduck - http://debiansystem.info
  `-  Debian - when you have better things to do than fixing systems

Attachment: digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)


--- End Message ---
--- Begin Message ---
Version: 0.8-3+rm

Dear submitter,

as the package topgit has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1115196

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)

--- End Message ---

Reply to: