Bug#921282: sbuild: emits many messages “Alias ‘[...]’ already associated with ‘[...]’ chroot”

2020-12-02 Thread Anthony Fok
Hello,

On Mon, 4 Feb 2019 09:53:56 +1100 Ben Finney  wrote:
> Control: retitle -1 schroot: emits many messages “Alias ‘[...]’ already 
> associated with ‘[...]’ chroot”
> Control: found -1 schroot/1.6.10-6+b1
>
> On 03-Feb-2019, Johannes Schauer wrote:
> > it seems that this message comes from schroot and not sbuild. Thus,
> > reassigning.
>
> Thanks. I am also altering the metadata for the version of ‘schroot’
> installed.

I ran into the same problem myself today, and found this bug report.

The problem started after I have added a second sbuild chroot with the
following command:

sudo sbuild-debian-developer-setup --suite=stable

And, thanks to your hint that the issue is actually schroot related, I
found in /etc/schroot/chroot.d/ two config files
unstable-amd64-build-XX and stable-amd64-build-XX, both
created by sbuild-debian-developer-setup.  And, sure enough, both
files contain the line

aliases=UNRELEASED,sid

which is correct for unstable but inappropriate for stable.  schroot's
"Alias already associated" warnings are valid.  The actual bug is
found somewhere else, from whomever or from whatever command that
created those schroot chroot.d config files.

And, sure enough, we can find in /usr/bin/sbuild-debian-developer-setup:


https://sources.debian.org/src/sbuild/0.80.0/bin/sbuild-debian-developer-setup/#L56-L57

when it calls sbuild-createchroot, it indiscriminately adds the flags

--alias=UNRELEASED
--alias=sid

which are appropriate for unstable only.

So, perhaps this bug should be re-assigned to the
sbuild-debian-developer-setup binary package?  :-)

Cheers,

Anthony



Bug#921282: sbuild: emits many messages “Alias ‘[...]’ already associated with ‘[...]’ chroot”

2020-12-02 Thread Roger Leigh
On 2 Dec 2020, at 08:46, Anthony Fok  wrote:
> 
> And, sure enough, we can find in /usr/bin/sbuild-debian-developer-setup:
> 
>
> https://sources.debian.org/src/sbuild/0.80.0/bin/sbuild-debian-developer-setup/#L56-L57
> 
> when it calls sbuild-createchroot, it indiscriminately adds the flags
> 
>--alias=UNRELEASED
>--alias=sid
> 
> which are appropriate for unstable only.
> 
> So, perhaps this bug should be re-assigned to the
> sbuild-debian-developer-setup binary package?  :-)

Yes, I think so.  This is not a schroot bug: the warnings are simply due to it 
being misconfigured, not due to a problem in schroot itself.

Kind regards,
Roger


Le luxe à petit prix 

2020-12-02 Thread ARIZONA FERME BRETONNE
In order to see your message, click on the following link: 
http://link.news-sarouty.ma/v/443/de86ac2aa9610f17c367da5f58f758c48de5a97f6a48af20

Bug#402916: marked as done (gftp-gtk doesn't allow for quickly jumping to particular files)

2020-12-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Dec 2020 13:18:36 +
with message-id 
and subject line Bug#402916: fixed in gftp 2.7.0b-1
has caused the Debian Bug report #402916,
regarding gftp-gtk doesn't allow for quickly jumping to particular files
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 ow...@bugs.debian.org
immediately.)


-- 
402916: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=402916
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gftp
Version: 2.0.18-16
Severity: normal

gftp-gtk should jump to a particular file when you press the key
coresponding to that file's first letter, and allow you to continue to
refine this search method by typing more or use the cursor keys to
navigate between all matching files, as Nautilus or GTK allows elsewhere.

This feature greatly speeds up the finding of files when you have lots of
files in a directory.


--- End Message ---
--- Begin Message ---
Source: gftp
Source-Version: 2.7.0b-1
Done: =?utf-8?q?Andreas_R=C3=B6nnquist?= 

We believe that the bug you reported is fixed in the latest version of
gftp, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 402...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Rönnquist  (supplier of updated gftp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 01 Dec 2020 15:18:35 +0100
Source: gftp
Architecture: source
Version: 2.7.0b-1
Distribution: unstable
Urgency: medium
Maintainer: Andreas Rönnquist 
Changed-By: Andreas Rönnquist 
Closes: 402916 846284
Changes:
 gftp (2.7.0b-1) unstable; urgency=medium
 .
   * New upstream version 2.7.0b
 - Allow to quickly jump to specific file (Closes: #402916)
   * Adopt package (Closes: #846284)
   * Update watch file to match github releases
   * Add a gbp.conf with branch specifics and pristine-tar info
   * Remove patch fix-configure.in.patch, file to patch removed
   * Remove patch glibc-2.30.patch, applied upstream
   * Update gftp-common doc files
   * Remove gftp-common.examples - files removed
   * Remove empty folder gftp-common/examples
   * Add hardening flags to fix hardening-no-bindnow
   * Make gftp-common Arch: all
   * Build-depend on intltool
   * Upgrade Debhelper compat to 13
   * Upgrade to Standards Version 4.5.1 (No changes required)
   * Add Vcs-* fields
   * Use Breaks + Replaces instead of Conflicts
   * Update patch fixing desktop file to remove %u option
   * Add patch fixing build
 - fix_format_not_a_string_literal_and_no_format_argument_given
   * Fix trailing-whitespace lintian warning in d/changelog
   * Install files in proper packages to silence dh_missing
   * Convert to machine-readable copyright
   * Remove as-needed linker flag from rules, shouldn't be
 necessary any longer
   * Add a d/upstream/metadata file
Checksums-Sha1:
 fe7f300a43c1cf3625e6ca541329ea7ec4c65da8 2048 gftp_2.7.0b-1.dsc
 23b8f4e5a6cf3b810c388a68224f13647010f0d7 1038156 gftp_2.7.0b.orig.tar.xz
 72370ae86f21c06e65e27a88dceefca0d65c30e3 10204 gftp_2.7.0b-1.debian.tar.xz
 2c3aba09c2547cf64bb645d0d03c2317383ea590 12657 gftp_2.7.0b-1_source.buildinfo
Checksums-Sha256:
 d9b9791ca1e660b6d10a78b202118a58b6f08b497d9bcdbc320a7d72ac5fc9b8 2048 
gftp_2.7.0b-1.dsc
 6f749b7c5c104a394ff856e50e85e8017f056adca049804fe2f140fc0ec7c7da 1038156 
gftp_2.7.0b.orig.tar.xz
 a6b1613a057dc30c4c33230fafb8e50aff2b6634d5088975ad7047bdc1e09885 10204 
gftp_2.7.0b-1.debian.tar.xz
 46607e6a0ae5530d94215aa843f9f47f7f59f938b8f52ff6ffed9e40eb8c0b82 12657 
gftp_2.7.0b-1_source.buildinfo
Files:
 8fcfd565e9b81e19ece5daed84fd6281 2048 net optional gftp_2.7.0b-1.dsc
 6d42576ce4ac8058c6f5f352e8dfdfe1 1038156 net optional gftp_2.7.0b.orig.tar.xz
 ed82a8e1adf3f90ac71fa60237783d5e 10204 net optional gftp_2.7.0b-1.debian.tar.xz
 17b01fc00a9068967d5b1aed81b16bda 12657 net optional 
gftp_2.7.0b-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE2zBuSxD/2Y7021XXGUtjGrLaKIgFAl/Hj5oRHGd1c25hbkBn
dXNuYW4uc2UACgkQGUtjGrLaKIiZShAAj1bGARiYykCvb53IcWV5ryM5oSDwgFNN
H5tQvtYcRbYb8APp7mF83uXtnhNeNpjuB+2ofUQeM+1hjbE6512TiQUqmcUVJawx
DXPaiDzgg5EOinN66IfLR6lbWGlGkfZItDgfhK6ccJmeLRhXxHkw5/1s1jel8DaB
a+TQfkS0HZdB/gG/LPxDK0KKHeWu3MmaeE04mA