Grub Password configuration during install

[Timothy M Butterworth]

All,

Would it be possible to add a section to the installer when Grub is being
installed and configured to configure a grub password?

Thanks

Tim

-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀

Re: Reducing allowed Vcs for packaging?

[Joerg Jaspert]

On 16792 March 1977, Adrian Bunk wrote:

for the contents of packages in the archive the ftp team requires that 
everything is in the preferred form of modification.


Yes. Of course.

But git or svn or even sccs and rcs is NOT, in any way, preferred for of 
modification. Only one way of storage and handling some metadata.


--
bye, Joerg

Re: Reducing allowed Vcs for packaging?

[Scott Kitterman]

On March 4, 2023 5:25:35 PM UTC, Adrian Bunk  wrote:
>On Wed, Mar 01, 2023 at 05:54:38PM -0700, Sean Whitton wrote:
>> Hello,
>
>Hi Sean,
>
>> On Sun 26 Feb 2023 at 11:38PM +02, Adrian Bunk wrote:
>> 
>> > On Sun, Feb 26, 2023 at 09:57:34PM +0100, Diederik de Haas wrote:
>> >> On Sunday, 26 February 2023 20:06:26 CET Adrian Bunk wrote:
>> >>...
>> >> > For anything in Debian, the package sources in Debian would not
>> >> > disappear when a repository (or salsa) disappears.
>> >>
>> >> Question as I don't know: is that only the package change that gets 
>> >> uploaded
>> >> to the Debian archive, or is there also a place where the (git) history 
>> >> of the
>> >> changes leading up to a new upload gets stored?
>> >>
>> >> To use an analogy: I'd like that not only the 'destination' is preserved, 
>> >> but
>> >> also the lead up to the destination.
>> >
>> > What goes into the Debian archive is based on tarballs and quilt patches.
>> > Nothing is stored there except the files you upload.
>> 
>> This is a matter of perspective.  The fact that dak doesn't store git
>> histories and send them out to mirrors is an implementation detail, to
>> me.  salsa and dgit-repos are both just as significant Debian archives,
>> even if they're not what we refer to when we write "Debian archive".
>
>for the contents of packages in the archive the ftp team requires that 
>everything is in the preferred form of modification.
>
>It is therefore surprising that you as member of the ftp team declare 
>that there is no requirement at all that the packages themselves that 
>get uploaded to the archive are in the preferred form of modification
>as long as the preferred form of modification is in salsa.
>
>Maintainers are now permitted to clone the upstream git tree, take one 
>commit as upstream, work on top of that, and then upload this without 
>the kludge of pristine-tar or restrictions due to quilt.
>
>Formats 1.0 or 3.0 (native) will be the natural formats generated for
>the Debian archive.
>
>Format 3.0 (quilt) will be another option, where a generated tarball is 
>uploaded as upstream source (as is already required by the ftp team for 
>repacks) plus one debian/patches/debian.patch containing all changes to 
>the upstream sources.
>
>Generating one quilt patch per commit that changes the upstream sources
>would not always be technically possible due to limitations of quilt.

Putting something in a git repository doesn't make a particular file more or 
less the preferred form of modification.  It's the same form.  IMO you are 
conflating two separate concepts here.  I don't find  Sean's perspective at all 
surprising.

Scott K

Re: Bug#1011666: need help with groff 1.23.0 (1.23.0~rc3-1 package prepared)

[Alejandro Colomar]

Hi Colin,

On 3/3/23 19:12, Colin Watson wrote:
> This isn't really analogous to your situation, though.  git-dpm is more
> like a workflow tool (such as stgit) than it is like a program you use
> to generate one-off scripted patches.  I don't think it would be
> appropriate or reasonable to try to embed this sort of thing in every
> commit generated by git-dpm, which is quite a lot of the commits that
> end up in my packaging branches.

If it's recurrent, maybe doing it only once would be nice.

> 
> I'd be happy to write a debian/README.source file, which would be a
> better place for this sort of thing.  I'm not sure exactly when I'll get
> round to it, but I've added it to my to-do list.

Sure, that would also help!

Cheers,

Alex

-- 

GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5


OpenPGP_signature
Description: OpenPGP digital signature

impossible to build bookworm xz-utils-5.4.1 with CFLAGS="-g"

[ijaaskelainen]

propably need to set -DNDEBUG or something.

Re: Reducing allowed Vcs for packaging?

[Adrian Bunk]

On Wed, Mar 01, 2023 at 05:54:38PM -0700, Sean Whitton wrote:
> Hello,

Hi Sean,

> On Sun 26 Feb 2023 at 11:38PM +02, Adrian Bunk wrote:
> 
> > On Sun, Feb 26, 2023 at 09:57:34PM +0100, Diederik de Haas wrote:
> >> On Sunday, 26 February 2023 20:06:26 CET Adrian Bunk wrote:
> >>...
> >> > For anything in Debian, the package sources in Debian would not
> >> > disappear when a repository (or salsa) disappears.
> >>
> >> Question as I don't know: is that only the package change that gets 
> >> uploaded
> >> to the Debian archive, or is there also a place where the (git) history of 
> >> the
> >> changes leading up to a new upload gets stored?
> >>
> >> To use an analogy: I'd like that not only the 'destination' is preserved, 
> >> but
> >> also the lead up to the destination.
> >
> > What goes into the Debian archive is based on tarballs and quilt patches.
> > Nothing is stored there except the files you upload.
> 
> This is a matter of perspective.  The fact that dak doesn't store git
> histories and send them out to mirrors is an implementation detail, to
> me.  salsa and dgit-repos are both just as significant Debian archives,
> even if they're not what we refer to when we write "Debian archive".

for the contents of packages in the archive the ftp team requires that 
everything is in the preferred form of modification.

It is therefore surprising that you as member of the ftp team declare 
that there is no requirement at all that the packages themselves that 
get uploaded to the archive are in the preferred form of modification
as long as the preferred form of modification is in salsa.

Maintainers are now permitted to clone the upstream git tree, take one 
commit as upstream, work on top of that, and then upload this without 
the kludge of pristine-tar or restrictions due to quilt.

Formats 1.0 or 3.0 (native) will be the natural formats generated for
the Debian archive.

Format 3.0 (quilt) will be another option, where a generated tarball is 
uploaded as upstream source (as is already required by the ftp team for 
repacks) plus one debian/patches/debian.patch containing all changes to 
the upstream sources.

Generating one quilt patch per commit that changes the upstream sources
would not always be technically possible due to limitations of quilt.

> Sean Whitton

cu
Adrian

Processed: Re: Bug#1030280: general: General non-recognized errors (im novice) after the installation: drivers, battery, booting errors...

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 installation-reports
Bug #1030280 [general] general: General non-recognized errors (im novice) after 
the installation: drivers, battery, booting errors...
Bug reassigned from package 'general' to 'installation-reports'.
Ignoring request to alter found versions of bug #1030280 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1030280 to the same values 
previously set
> tag -1 moreinfo
Bug #1030280 [installation-reports] general: General non-recognized errors (im 
novice) after the installation: drivers, battery, booting errors...
Added tag(s) moreinfo.

-- 
1030280: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030280
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1030280: general: General non-recognized errors (im novice) after the installation: drivers, battery, booting errors...

[Ben Hutchings]

Control: reassign -1 installation-reports
Control: tag -1 moreinfo

On Thu, 2023-02-02 at 00:18 +0100, Miguel González Jiménez wrote:
> Package: general
> Severity: normal
> X-Debbugs-Cc: migui...@hotmail.com
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where appropriate ***
> 
>* What led up to the situation?
> After the installation, I proceed to use the hardware and no correct firmware 
> had been installed. Couldn't use neither the touchpad, the wifi card (AX200 
> Intel) nor several screen caracteristics.
> I've tried to install its drivers but they dont work. I think something went 
> wrong during the installation. Besides, battery is running out quite fast and 
> fans are most of the time active. After installing wifi card Intel drivers, 
> booting errors has became to show up on the log booting screen, refeering 
> bugs about usb and bluetooth ports.
> The partition on the solid disk (what also holds Windows 10) has been made 
> fine I think.
> 

Unfortunately the official installation images for Debian 11 do not
include non-free firmware that's required to support some devices.
There are alternate images with non-free firmware included at
.

For the next release, Debian 12 "bookworm", we will include and install
non-free firmware by default.  If you want to test the next release,
installation images for that are at
.

Please report back whether you still have problems after using one of
these installers.

Ben.

-- 
Ben Hutchings
The two most common things in the universe are hydrogen and stupidity.


signature.asc
Description: This is a digitally signed message part

Bug#1032354: ITP: srcpd -- SRCP server daemon to control digital model railroads

[Hilmar Preusse]

Package: wnpp
Severity: wishlist
Owner: Hilmar Preusse 
X-Debbugs-Cc: debian-devel@lists.debian.org

* Package name: srcpd
  Version : 2.1.5
  Upstream Contact: Guido Scholz 
* URL : https://sourceforge.net/projects/srcpd/
* License : GPL2
  Programming Lang: C, Shell
  Description : SRCP server daemon to control digital model railroads

The srcpd is a server daemon that enables you to control and play with
a digital model railroad using any SRCP client. Currently it supports many
interface (both self made and commercally) and direct signal generation.

More information about SRCP and links to many really cool clients (and
other servers for different hardware) can be found at
http://srcpd.sourceforge.net/ and http://www.der-moba.de/

 - The package seems to be interesting for people running
   a model railroad, which should be controlled by a computer.
   Currently I'm not aware of similar packages in Debian.
 - I plan to maintain the package myself. I'm a Debian Maintainer
   with upload permits, hence I would not need a regular sponsor.

-- 
sigmentation fault


signature.asc
Description: PGP signature

Re: icc-profiles_2.2_source.changes REJECTED

[Jonas Smedegaard]

Quoting Bastien Roucariès (2023-03-03 22:21:49)
> Le lundi 27 février 2023, 12:11:27 UTC Jonas Smedegaard a écrit :
> Could you double check your package and create a simple test case ?

Here is a easy (but not simple: requires unstable Debian, deb-src in
apt, and network access) test case:

apt source icc-profiles
lintian icc-profiles_*.dsc


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Re: icc-profiles_2.2_source.changes REJECTED

[Jonas Smedegaard]

Quoting Bastien Roucariès (2023-03-03 23:57:47)
> Le vendredi 3 mars 2023, 22:35:24 UTC Jonas Smedegaard a écrit :
> > Quoting Bastien Roucariès (2023-03-03 22:21:49)
> > > Le lundi 27 février 2023, 12:11:27 UTC Jonas Smedegaard a écrit :
> > > Hi jonas,
> > > 
> > > I have just checked the source code of lintian. Could you double check 
> > > your package and create a simple test case ?
> > > 
> > > According to:
> > > https://salsa.debian.org/lintian/lintian/-/blob/master/lib/Lintian/Check/Files/NonFree.pm#L91
> > > The test should not raise
> > 
> > Sorry, I don't understand what you ask me to do.
> > 
> > In case it was unclear from my previous posts: The rejection messages I
> > shared was not from a lintian check done locally by me, but a rejection
> > message I received from ftpmaster.
> > 
> > Locally I did not experience the same messages.  Are you asking me to
> > test again that I (again) do not experience the kind of messages that
> > ftpmasters for some reason unknown to me trigger?
> 
> Yes could you double check ?
> 
> If you do not experience the kind of messages with locally installed lintian, 
> it means that lintian need to be backported and that ftpmaster should install 
> a backport version.

Ah, now I understand - sorry for being dense.

I do get those files detected on my up-to-date untable system, but only
as warnings:

$ lintian --tag-display-limit 0 *_amd64.changes
W: icc-profiles source: file-without-copyright-information 
ECI/ISOcoated_v2_to_PSOcoated_v3_DeviceLink_info_DE.pdf [debian/copyright]
W: icc-profiles source: file-without-copyright-information 
ECI/ISOcoated_v2_to_PSOcoated_v3_DeviceLink_info_EN.pdf [debian/copyright]
W: icc-profiles source: file-without-copyright-information 
ECI/PSO_Coated_300_NPscreen_ISO12647_eci_info.pdf [debian/copyright]
W: icc-profiles source: file-without-copyright-information 
ECI/PSO_Coated_NPscreen_ISO12647_eci_info.pdf [debian/copyright]
W: icc-profiles source: file-without-copyright-information 
ECI/PSO_Coated_v3_Glossy_laminate_info.pdf [debian/copyright]
W: icc-profiles source: file-without-copyright-information 
ECI/PSO_Coated_v3_Matte_laminate_info.pdf [debian/copyright]
W: icc-profiles source: file-without-copyright-information 
ECI/PSO_LWC_Improved_eci_info.pdf [debian/copyright]
W: icc-profiles source: file-without-copyright-information 
ECI/PSO_LWC_Standard_eci_info.pdf [debian/copyright]
W: icc-profiles source: file-without-copyright-information 
ECI/PSO_MFC_Paper_eci_info.pdf [debian/copyright]
W: icc-profiles source: file-without-copyright-information 
ECI/PSO_SNP_Paper_eci_info.pdf [debian/copyright]
W: icc-profiles source: file-without-copyright-information 
ECI/PSO_Uncoated_ISO12647_eci_info.pdf [debian/copyright]
W: icc-profiles source: file-without-copyright-information 
ECI/PSO_Uncoated_NPscreen_ISO12647_eci_info.pdf [debian/copyright]
W: icc-profiles source: file-without-copyright-information 
ECI/PSOcoated_v3_info.pdf [debian/copyright]
W: icc-profiles source: file-without-copyright-information 
ECI/PSOcoated_v3_to_ISOcoated_v2_DeviceLink_info_DE.pdf [debian/copyright]
W: icc-profiles source: file-without-copyright-information 
ECI/PSOcoated_v3_to_ISOcoated_v2_DeviceLink_info_EN.pdf [debian/copyright]
W: icc-profiles source: file-without-copyright-information 
ECI/PSOsc-b_paper_v3_info.pdf [debian/copyright]
W: icc-profiles source: file-without-copyright-information 
ECI/PSOuncoated_v3_FOGRA52_info.pdf [debian/copyright]
W: icc-profiles source: file-without-copyright-information 
ECI/PSR_LWC_Plus_V2_info.pdf [debian/copyright]
W: icc-profiles source: file-without-copyright-information 
ECI/PSR_LWC_STD_V2_info.pdf [debian/copyright]
W: icc-profiles source: file-without-copyright-information 
ECI/PSR_SC_Plus_V2_info.pdf [debian/copyright]
W: icc-profiles source: file-without-copyright-information 
ECI/PSR_SC_STD_V2_info.pdf [debian/copyright]
W: icc-profiles source: file-without-copyright-information 
ECI/SC_paper_info.pdf [debian/copyright]
W: icc-profiles source: file-without-copyright-information ECI/eciRGB.txt 
[debian/copyright]
W: icc-profiles source: file-without-copyright-information ECI/licence.rtf 
[debian/copyright]
W: icc-profiles source: file-without-copyright-information HP/c55.pdf 
[debian/copyright]
W: icc-profiles source: file-without-copyright-information 
IDEAlliance/Introducing PrintWide - Idealliance.pdf [debian/copyright]
W: icc-profiles source: file-without-copyright-information 
IDEAlliance/Introducing the XCMYK Profile 12.1.17.11.pdf [debian/copyright]
W: icc-profiles source: file-without-copyright-information 
IDEAlliance/PrintWide2020 - Idealliance.icc [debian/copyright]
W: icc-profiles source: file-without-copyright-information IDEAlliance/README 
PrintWide - Idealliance.txt [debian/copyright]
W: icc-profiles source: file-without-copyright-information 
JPMA/JC_ICCprofile__Appendix.pdf [debian/copyright]
W: icc-profiles source: file-without-copyright-information 
color.org/ICC_ITU.txt [debian/co